spk-doctrine-show-me

# spk-doctrine-show-me Make the current point visible. Skip the preamble, keep prose brief, and pick the smallest representation that answers the question. Do not add a diagram when a sentence or short list is clearer. ## Choose the Shape - Logic or an algorithm: compact pseudocode. - Runtime behavior: call tree or sequence diagram. - UI composition: component tree with only relevant state and boundaries. - Ownership or refactor scope: shallow file tree with one responsibility per entry. - Existing-to-proposed change: `diff` over the matching tree, flow, or pseudocode. - Domain lifecycle: state diagram. - Data or concept relationships: entity-relationship or class diagram. - Architecture: C4 Context first, then Container or Component only when useful. - Dense visual UI/layout comparison: one focused HTML artifact when the host can open it; keep durable project documentation diagram-as-code. Place each visual beside the text it supports. Include only the calls, files, states, relationships, and boundaries needed for the current decision. Label relationships and preserve source paths or identifiers that make the visual checkable against code and artifacts. ## Load Spec Kitty's Diagram Doctrine Prefer Mermaid inline; use PlantUML when richer layout, C4 support, or its DSL earns the rendering cost. Read `references/spec-kitty-diagram-sources.md`, then load only the needed toolguide, directive, or tactic through `spec-kitty charter context --include ...`. It maps portable ...