This file tracks known technical debt items that agents and engineers should be aware of. Items are added during code review, agent runs, and manual audits.
| ID | Category | Description | Location | Priority | Added |
|---|---|---|---|---|---|
| To be populated by agent runs and manual audits |
- pattern-violation — Code that doesn't follow established patterns
- missing-tests — Insufficient test coverage
- stale-docs — Documentation that doesn't match code
- deprecated-usage — Use of deprecated APIs or patterns
- accessibility — Known a11y gaps
- performance — Known performance issues
- ssr-safety — SSR-unsafe code patterns
- P0 — Blocking: breaks users or CI
- P1 — High: should fix in next sprint
- P2 — Medium: fix when touching the area
- P3 — Low: nice to have, no urgency
When you find technical debt during a fix or review, add a row to the table above. When you fix a debt item, remove its row.
Review this file when planning sprints. Use it to justify cleanup PRs.