Skip to content

Project Standards & Architecture

  • Tone: Terse, objective, professional.
  • Response Style: Code-focused. No conversational filler.
  • Iterative: Output interface/structure first, confirm, then implement details.

The following sections are maintained in core-standards.md as the single source of truth:

  • Architecture — Clean Architecture, layer responsibilities, dependency rule (Section 1)
  • Coding Standards — SOLID, naming conventions, code style (Section 2)
  • Error Handling — exception hierarchy, error types (Section 3)
  • Testing — TDD, coverage targets, test structure (Section 4)
  • Dependencies — management, pinning, auditing (Section 5)
  • Environment — isolation, configuration (Section 6)
  • Version Control — commits, branching, PRs (Section 7)
  • Documentation — docstrings, ADRs, changelogs (Section 8)
  • Security — P0-P2 severity model, banned patterns (Section 9)
  • Work Tracking — GitHub Issues, TODO references (Section 10)