okhp3-mermaid-core

Topics in the source

• okhp3-mermaid-core
• 1. Audience Declaration (do this first)
• 2. Type Selection
• 3. Design System
• 4. Naming & Registry
• 5. Validation - Three Gates (mandatory)
• Execution contract
• 6. Output & Publish

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Foundation for the Mermaid family. Every Mermaid task starts here, even if it ends in a domain skill. Before generating anything, determine the audience. If not stated, ask one question: Executive, Analyst, or Technical? See references/audience-profiles.md for what each implies (node count, detail level, vocabulary). A diagram produced for the wrong audience is a design failure independent of syntax correctness. Consult references/type-selection-matrix.md. It catalogs all 27 current Mermaid diagram types (stable + beta, as of v11.15) with OKHP3 disposition: core-handled, routed to a domain skill, or explicitly excluded with rationale. If the matrix routes to a domain skill (bpmn / architecture / data), load that skill's SKILL.md now for the type-specific syntax and patterns. Core handles selection and theming; domain skills handle vocabulary. Apply OKHP3 theming per references/design-system.md. Every classDef sets fill, stroke, AND color - no exceptions, this is the single most common cause of dark/light-mode failures in community skills reviewed. File naming and the DIAGRAMS.md registry pattern are defined in references/naming

This is an excerpt. Refer to the complete source and its current requirements.