Improve getting started flow/guides

[nagyv]

I've spent several hours reading through the codebase in the RefakTs repo to better understand all its finesse, and I love what I saw, but ... Even in the end, I'm puzzled on how should I connect it into my repo?

What options do I see?

1. Run npm install -g refakts and tell Claude-Code that it can use the refakts tools (I'll have to explain it what to use it for, as it likely does not know it). While this seems to be the recommended approach, it requires a lot of setup and refakts is not really integrated into my repo and workflow.
2. Have a refakts MCP server that I can easily configure in my repo. Does refakts offer one? I could not find any sign of it.
3. Have a custom agent that knows the tools, and is invoked for refactorings. In reality, this would be added after one of the previous points is set up.
4. ???

My preference is for an MCP as that's the most user friendly, but even better documentation on how to set up the tool use or just emphasizing that that's the recommended approach would be an improvement on the current instructions.

Dependencies (if applicable)

• Depends on #X (feature-name) - Explanation of why this dependency exists

Acceptance Criteria

• Specific, testable requirement
• Another requirement
• Final requirement (e.g., update documentation)

---

Available Labels:

• RefakTS Command - New commands for the product
• House Keeping - Development flow and codebase organization
• Quality Checks - Post-commit quality check system additions
• Good first issue - Easy tasks for new contributors

[nagyv]

I did not add that label on purpose. It could be a new command to start an MCP server. :)

[devill]

Hi! I just noticed this issue, for some reason I didn't get the notification email about it.

Either way, that is a really good point. I didn't really publish a version yet that could be used with other projects. That is something I want to do quite soon.

An MCP server variant is often suggested, so we can definitely add that option later on. My observation was that the agent prefers command line tools over MCP servers, but there are some other advantages of an MCP server, so why not.