// Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing.
| name | requirement-clarification |
| description | Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing. |
See rules.md for question templates and anti-patterns.
JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.
Go conventions for hexagonal architecture, project structure, error handling, testing, and observability. Use when writing Go services.
Code quality practices: error handling, validation, logging, and DRY. Use when writing or reviewing code.
Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.
System architecture: modules, project structure, ADRs, and testing. Use when designing or reviewing systems.
CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.
