docs

To create technical architecture documentation, use structured templates that prioritize high-level system design and visual diagrams over prose. This approach enforces minimal documentation standards by capturing only what the code cannot explain, ensuring your architecture documents remain clear and maintainable.

The best way to write runbooks is to apply principle-driven templates that focus on operational clarity and actionable procedures. By standardizing runbook creation around high-level system design, you ensure incident response procedures are scannable and effective for on-call teams.

To generate onboarding guides with minimal documentation standards, use structured templates that document only what code cannot explain. This principle-driven writing approach prioritizes architecture over implementation details, accelerating new engineer onboarding without creating bloated, outdated guides.

Yes, you can use structured templates to standardize changelogs and technical writing. The framework enforces a philosophy of documenting only essential information, relying on visual diagrams over prose to maintain system truth and prevent documentation bloat across user-facing and technical content.

You should use visual diagrams instead of prose whenever you need to maintain system truth in technical documentation. The skill enforces a principle-driven approach that prioritizes architecture over implementation, requiring visual diagrams to ensure high-level system design remains scannable and clear.