Developer Experience (DX)
Design and refine tooling to maximize verifiability and AI efficiency.
Outputs
- •Global:
{ide-folder}/{outputFolder}/tech/dx/{timestamp}-{topic}.md - •Per-story:
{ide-folder}/{outputFolder}/task/.../dx-notes.md
Required Structure
yaml
Topic: Timestamp: (ISO) Status: Draft | Active Owner: DX
| Section | Content |
|---|---|
| Goals | What this DX change enforces |
| Proposed tooling/policies | Lint/typecheck/test/coverage/dead-code/commit hooks/CI |
| Repo impact | Which packages/configs change |
| Quality gates | What fails CI, what runs pre-commit, what runs nightly |
| Developer workflow | Exact commands a dev/agent runs |
| Risks/trade-offs | |
| Migration plan | If introducing stricter rules incrementally |
| Verification | How we know the DX setup works |
Rule Requirements
Every new rule must be:
- •Enforceable automatically - no honor system
- •Explainable in 1-2 sentences - if can't explain, don't add
- •Mapped to concrete benefit - verifiability, security, maintainability
Guardrails
- •Prefer minimal tool count
- •Clear failure modes
- •Run
/sync-issueafter writing