Claude Code Agent Configuration (CLAUDE.md)

This repository adheres to the architecture, coding standards, test harness conventions, and CI/CD quality gates codified in AgenticEngineeringToolbelt.

---

Master Rules Reference

Always follow the complete guidelines in:

• Universal Agent Rules (AGENTS.md)
• Master Engineering Style Guide
• Simulation and Control Harnesses
• Code Review Foci and Operational Guardrails

---

Active Skills

• engineering-archetype: Enforces master architectural standards across C#, Python, TypeScript, and C++.
• scaffold-project: Scaffolds projects adhering to traditional Git Flow, living documentation, and 4-stage CI/CD.
• test-harness-builder: Builds closed-loop simulation harnesses, diagnostic tap points, Playwright UI drivers, and 6-part feedback envelopes.
• code-review-foci: Runs a 6-focus read-only code review (Requirement Traceability, Architecture & Serialization, Anti-Test-Theatre, Security & Container Immutability, UI & Real Screenshots, and Living Docs & Release Sync).

---

Core Execution Tenets

Workflow and Architecture Tenets

1. Traditional Git Flow: Work in feature/* branches off develop. Release through release/* branches to main with SemVer tags and sync back to develop. Route urgent fixes through hotfix/* off main (see Traditional Git Flow Discipline).
2. APIs First, MCP Later: Keep domain logic inside typed, standalone libraries and REST APIs. Expose Model Context Protocol (MCP) tools strictly as thin wrappers (see APIs First, MCP Later).
3. Living Documentation Standards: Apply Technical Writing Standards (≤ 25 words per sentence, active voice, imperative mood, section-scoped cross-links). Embed native Mermaid diagrams and publish via VitePress.

Verification and Anti-Test Theatre Tenets

1. Simulation and Control Harnesses: Treat software as an observable dynamic system with Diagnostic Tap Points, stress loops, disturbance injection, and Six-Part Agent Feedback Envelopes.
2. Tiered Testing Cadence: Follow the Tiered Testing Cadence across Tier 1 (inner loop on demand), Tier 2 (stabilization gate before manual testing), and Tier 3 (full matrix, harness sweeps, and Playwright audits before PR or release).
3. Anti-Test Theatre and Deterministic Protocols:
   • Test with real implementations (SQLite WAL, real DI, and full HTTP roundtrips) per the Four Pillars of Anti-Test Theatre.
   • Never mock internal interfaces or repositories, and never use mock.Verify() as a primary assertion.
   • Compute required test suite size using the Deterministic Test Budget Formula (1 + Branches + Boundaries + Disturbances).
   • Evaluate every dependency with the Deterministic Five-Question Mock Decision Tree.