Project Setup & Workflows

Core Principles

1. Interactive over passive — Don't dump a generic template. Ask questions, gather context, then generate a customized result tailored to the specific project.
2. MCP-driven analysis — Use Roslyn MCP tools for health checks and migration analysis instead of reading files manually. Token-efficient and semantically accurate.
3. Generate, don't template — CLAUDE.md files should be fully populated with specific choices (not [PLACEHOLDER] values). Every section should reflect the actual project decisions.
4. Architecture-first — Every workflow starts by understanding or selecting the project's architecture. Architecture drives folder structure, naming, patterns, and test organization.
5. Verify after action — After any workflow completes (init, migration, health check), verify the result. Run builds, tests, or health checks to confirm success.

Patterns

Project Init Workflow

Interactive conversational flow for new projects. Execute steps in order, waiting for user input at each decision point.