Post Setup

Ask the user a few open-ended questions in plain text to understand the project. Do NOT use AskUserQuestion — just ask conversationally and let them respond naturally.

Start with something like:

Before I generate the project docs, I'd like to understand what you're building. Tell me about this project — what is it, what problem does it solve, and who is it for?

Then follow up based on their answer. You might ask about:

• Key technical decisions or constraints (specific APIs, data sources, deployment targets)
• Anything contributors should understand about the intended architecture
• Whether the default package.json description should be updated

Keep it to 2–3 exchanges. Don't over-interview.

Phase 3: Generate Documentation

The README.md and CLAUDE.md have already been scaffolded with deterministic content (project structure, prerequisites, available scripts, conventions). Your job is to fill in the project-specific sections.

Based on the user's answers from Phase 2:

1. Update README.md:

   • Replace the <!-- CLAUDE:PROJECT_DESCRIPTION --> placeholder with a real project description
   • Replace the <!-- CLAUDE:ARCHITECTURE_NOTES --> placeholder with architecture context from the interview

2. Update CLAUDE.md:

   • Replace the <!-- CLAUDE:PROJECT_CONTEXT --> placeholder with architectural context from the interview
   • Add any project-specific conventions or notes the user mentioned

3. Update package.json description if the user gave a better one than the default.

4. Run bun run format and then bun run format:check to ensure all edits are cleanly formatted.

Known Issues to Watch For

• Lefthook prepare fails: Ensure .git/ exists before bun install.
• shadcn uses npm internally: You may see warnings about different package managers. These are harmless — bun takes over on workspace install.
• Biome format differences from shadcn defaults: shadcn scaffolds with its own formatting. Run bun run format to normalize everything to the project's Biome config before running bun run format:check.