code-quality
Code Quality Standards
Non-negotiable code quality standards. These are not preferences — they are requirements.
The Problem
AI agents produce code that works but diverges. Each session picks slightly different names, nesting patterns, and error handling approaches — not by design, but by independence. Over time this drift compounds: the codebase accumulates three ways to handle errors, four naming conventions, and scattered magic numbers that almost-but-don't-quite match. These standards collapse that divergence to zero so refactoring stays small and infrequent.
Consumption
- Builders: Read
## Builder Checklistbefore writing code. Reference narrative sections when a checklist item is ambiguous. - Refactorers: Use
## Enforced Rulesas your issue list. Read narrative sections for fix guidance. - Both: Narrative sections are the authoritative standard. Checklist and rules table are compressed views of the same content.
Test-Driven Development: 4-Layer Validation Framework
Layer 1 — Unit Tests (does the logic work?)
More from alexanderstephenthompson/claude-hub
unity-csharp
C# patterns for Unity - MonoBehaviour, async, architecture, and VR/mobile performance optimization
52design
Design and UI standards for accessibility, semantic HTML, and responsive layouts
38architecture
Architecture principles, module boundaries, folder structure, and project type profiles
36vrc-udon
VRChat Udon and UdonSharp patterns - networking, sync, interactions
35data-python
Python patterns for data processing - pandas, polars, pyspark
35web-performance
Performance patterns for Apollo caching, Redis, and CloudFront optimization
35