Problem
The default standards/coding-standards.md is NestJS/TypeScript-oriented. Phase 0 setup rewrites it based on the chosen tech stack, but the agent generates it from scratch each time. For consistent, battle-tested standards, teams want pre-built template packs.
Proposed solution
A templates/ directory with tech-stack-specific presets:
templates/
├── nestjs-typescript/
│ ├── coding-standards.md
│ ├── api-design.md
│ └── project-structure.md
├── spring-boot-java/
│ ├── coding-standards.md
│ ├── api-design.md
│ └── project-structure.md
├── fastapi-python/
│ └── ...
├── go-echo/
│ └── ...
└── nextjs-react/
└── ...
Phase 0 setup would:
- Ask tech stack
- Copy the matching template pack to
standards/
- Allow customization on top
Community can contribute template packs via PRs.
Problem
The default
standards/coding-standards.mdis NestJS/TypeScript-oriented. Phase 0 setup rewrites it based on the chosen tech stack, but the agent generates it from scratch each time. For consistent, battle-tested standards, teams want pre-built template packs.Proposed solution
A
templates/directory with tech-stack-specific presets:Phase 0 setup would:
standards/Community can contribute template packs via PRs.