docs-codebase

# Technical Documentation Execution-ready patterns for clear, maintainable technical documentation. **Modern best practices (January 2026)**: docs-as-code, ownership + review cadence, documentation QA gates (links/style/spelling), AI-assisted drafting + review, OpenAPI 3.2.0 where streaming schemas matter, and GEO (Generative Engine Optimization) for AI search. ## Quick Reference | Documentation Type | Template | When to Use | |-------------------|----------|-------------| | **Project README** | [readme-template.md](assets/project-management/readme-template.md) | New project, onboarding | | **Architecture Decision** | [adr-template.md](assets/architecture/adr-template.md) | Technical decisions | | **API Reference** | [api-docs-template.md](assets/api-reference/api-docs-template.md) | REST/GraphQL APIs | | **Changelog** | [changelog-template.md](assets/project-management/changelog-template.md) | Version history | | **Contributing Guide** | [contributing-template.md](assets/project-management/contributing-template.md) | Open source, teams | ## Workflow 1. Identify the documentation type and audience. 2. Find existing patterns in the repo; follow local conventions. 3. Start from the closest template in `assets/` and adapt. 4. Add ownership + review cadence for critical docs (runbooks, onboarding, API reference). 5. Run documentation QA (links, formatting, spelling, examples) before merging. ### Docs Folder / LLM-Generated Revamp Mode (Any Repo) Use this mode when a repo'...