doc-hygiene
Documentation Hygiene
Prevent documentation drift through structural rules — not manual vigilance.
The Count Problem
Hardcoded counts (e.g., "109 skills", "28 instructions", "6 agents") in prose become stale within days during active development. Every count is a future bug.
Rules
| Rule | Do | Don't |
|---|---|---|
| No counts in prose | "See the skills catalog for the current list" | "Alex has 109 skills" |
| Counts in tables OK | Tables with ` | Count |
| Single source of truth | One canonical location per metric | Same count in 5 files |
| Link, don't copy | "See [SKILLS-CATALOG.md]" | Duplicate the catalog inline |
| Timestamp proximity | Counts near a "Last Updated" date are acceptable | Undated counts |
Canonical Sources
More from fabioc-aloha/lithium
bicep avm mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure
9brain qa
Semantic, logic, code, and architectural validation of Alex's cognitive architecture — not just file counts, but meaning coherence
1infrastructure as code skill
**Domain**: DevOps & Cloud Engineering
1skill-activation
Internal metacognitive skill for automatic capability discovery — self-triggers when uncertain about available skills
1dream-state
Neural maintenance, synapse validation, automated health diagnostics, and unconscious processing
1ui/ux design
User interface design, user experience optimization, accessibility compliance, design systems
1