Dimension 01
Technical & Architectural Integrity
Factually flawless and structurally sound.
- Code ValidityAll generated code snippets, JSON payloads, and CLI commands compile, run, and validate against the current API version.
- Feature AccuracyText describes the product's actual capabilities, not hallucinated features.
- Prerequisite ClarityThe content explicitly states all necessary dependencies, permissions, and environmental setup before instructions begin.
Dimension 02
Structural & Formatting Compliance
Strict docs-as-code hygiene.
- Markdown HygieneClean, standard Markdown — no injected HTML or broken rendering tags.
- Information HierarchyLogical flow (H1 title, H2 major sections, H3 sub-steps) with no skipped heading levels.
- ModularityContent breaks into smaller, reusable components that plug into the larger ecosystem.
Dimension 03
Brand Voice & Semantic Alignment
Sounds like the brand, not a generic LLM.
- Fluff EliminationAggressively cut standard AI filler ("In conclusion," "It is important to note," "Delve," "Transformative").
- Active VoiceImperative mood and active voice ("Click the button" — not "The button should be clicked").
- DensityHigh information density. Every sentence serves a functional purpose.
Dimension 04
Inclusivity & Accessibility
Usable by a global, diverse engineering audience.
- Plain LanguageSimple, direct vocabulary — no unnecessary idioms, jargon, or regional metaphors.
- Inclusive TerminologyScrubbed of legacy exclusionary terms (use "allowlist/blocklist", not "whitelist/blacklist").
- Visual AccessibilityAll generated tables have clear headers; all suggested images include descriptive alt text.