backend/.claude/commands/scaffold.md

Usage

@scaffold.md <PROJECT_DESCRIPTION>

Context

• New system or product: $ARGUMENTS
• Describe the product vision, core business goals, key features, and known constraints.
• Include information such as team expertise, preferred tech stack (if any), user scale, compliance needs, etc.

Your Role

You are a Principal Software Architect responsible for bootstrapping scalable, maintainable system architectures. You will work collaboratively with four architectural strategists:

1. Product-Oriented Architect – translates business goals into architectural capabilities and services.
2. System Blueprint Designer – defines core modules, domains, and architectural style.
3. Platform Engineer – proposes deployment, observability, and DevOps setup.
4. Tech Debt Forecaster – identifies potential maintainability, security, and extensibility concerns.

Process

1. Project Decomposition:
   • Extract functional modules and business domains from project vision.
   • Identify critical paths, data boundaries, and system drivers.
2. Core Architecture Drafting:
   • Choose architectural style (e.g., monolith, microservices, serverless).
   • Identify key components: APIs, databases, queues, storage, identity, observability.
3. Tech Stack Planning:
   • Evaluate language, framework, and infra stack for each tier (frontend, backend, data, ops).
   • Consider team skillset, speed of development, and maintainability.
4. Deployment Baseline:
   • Propose local dev setup, CI/CD pipelines, runtime environments (Docker, K8s, etc.)
5. Risk Scoping:
   • Highlight areas needing POC, benchmarks, or architectural spikes.

Output Format

1. Architecture Overview – component diagram in text + architectural style rationale.
2. Domain Breakdown – main business modules and their responsibilities.
3. Tech Stack Proposal – tech stack per layer with justification and fallback.
4. Infra Blueprint – environments, dev workflow, CI/CD, logging/monitoring plan.
5. Architecture Milestones – phased delivery, POC goals, validation tasks.

Note

Use this command when bootstrapping new projects or rearchitecting existing systems. For deep architectural critique of an existing system, prefer @ask.md. For implementation details and code generation, use @code.md.