Skip to content

drafael/coding-harness / skills/diagram-design

diagram-design

Verified

Create branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, bar, line, Gantt and scatter charts, high-level, process, medallion, data flow, DP integration, DP security matrix, Sankey, fishbone, Wardley map, kanban, user journey, deployment, dependency graph, UML class, story map, or database schema diagrams as standalone HTML/SVG/PNG. Redraw .drawio/.drawio.png/.drawio.svg or Mermaid .mmd sources at a chosen size/detail; onboard brand tokens from a website; add semantic patterns, callouts, accessible motion, or sketchy/hand-drawn styling.

FileKindSize
LICENSEother1.0 KB
README.mdmarkdown5.6 KB
SKILL.mdskill md38.6 KB
THIRD_PARTY_LICENSES.mdmarkdown2.6 KB
assets/example-architecture-dark.htmlother11.8 KB
assets/example-architecture-full.htmlother14.6 KB
assets/example-architecture.htmlother11.8 KB
assets/example-bar-dark.htmlother8.8 KB
assets/example-bar-full.htmlother11.0 KB
assets/example-bar.htmlother8.7 KB
assets/example-bubble-dark.htmlother11.2 KB
assets/example-bubble-full.htmlother14.8 KB
assets/example-bubble.htmlother11.1 KB
assets/example-data-flow-dark.htmlother12.7 KB
assets/example-data-flow-full.htmlother15.5 KB
assets/example-data-flow.htmlother12.5 KB
assets/example-datalake-dark.htmlother24.3 KB
assets/example-datalake-full.htmlother27.7 KB
assets/example-datalake.htmlother25.8 KB
assets/example-db-schema-dark.htmlother24.1 KB
assets/example-db-schema-full.htmlother27.0 KB
assets/example-db-schema.htmlother23.9 KB
assets/example-dependency-dark.htmlother17.4 KB
assets/example-dependency-full.htmlother20.6 KB
assets/example-dependency.htmlother17.2 KB
assets/example-deployment-dark.htmlother13.2 KB
assets/example-deployment-full.htmlother16.4 KB
assets/example-deployment.htmlother13.1 KB
assets/example-dp-integration-dark.htmlother14.4 KB
assets/example-dp-integration-full.htmlother16.9 KB
assets/example-dp-integration.htmlother14.4 KB
assets/example-dp-security-matrix-dark.htmlother10.0 KB
assets/example-dp-security-matrix-full.htmlother12.3 KB
assets/example-dp-security-matrix.htmlother10.7 KB
assets/example-er-dark.htmlother13.9 KB
assets/example-er-full.htmlother16.7 KB
assets/example-er.htmlother13.8 KB
assets/example-fishbone-dark.htmlother8.5 KB
assets/example-fishbone-full.htmlother11.1 KB
assets/example-fishbone.htmlother8.4 KB
assets/example-flowchart-dark.htmlother9.0 KB
assets/example-flowchart-full.htmlother11.9 KB
assets/example-flowchart.htmlother9.0 KB
assets/example-gantt-dark.htmlother10.0 KB
assets/example-gantt-full.htmlother11.6 KB
assets/example-gantt.htmlother9.8 KB
assets/example-high-level-dark.htmlother23.6 KB
assets/example-high-level-full.htmlother27.8 KB
assets/example-high-level-vertical-dark.htmlother24.4 KB
assets/example-high-level-vertical-full.htmlother28.1 KB
assets/example-high-level-vertical.htmlother29.7 KB
assets/example-high-level.htmlother26.3 KB
assets/example-import-drawio.htmlother11.8 KB
assets/example-import-mermaid.htmlother7.9 KB
assets/example-it-state-dark.htmlother11.7 KB
assets/example-it-state-full.htmlother13.9 KB
assets/example-it-state.htmlother12.2 KB
assets/example-journey-dark.htmlother8.9 KB
assets/example-journey-full.htmlother11.5 KB
assets/example-journey.htmlother8.9 KB
assets/example-kanban-dark.htmlother10.8 KB
assets/example-kanban-full.htmlother13.6 KB
assets/example-kanban.htmlother10.7 KB
assets/example-layers-dark.htmlother6.8 KB
assets/example-layers-full.htmlother9.8 KB
assets/example-layers.htmlother6.7 KB
assets/example-line-dark.htmlother7.3 KB
assets/example-line-full.htmlother9.8 KB
assets/example-line.htmlother7.3 KB
assets/example-loop-dark.htmlother6.7 KB
assets/example-loop-full.htmlother9.7 KB
assets/example-loop-terminal.htmlother9.8 KB
assets/example-loop.htmlother6.6 KB
assets/example-medallion-dark.htmlother12.7 KB
assets/example-medallion-full.htmlother15.5 KB
assets/example-medallion.htmlother12.6 KB
assets/example-nested-dark.htmlother6.6 KB
assets/example-nested-full.htmlother9.6 KB
assets/example-nested.htmlother6.7 KB
assets/example-org-chart-dark.htmlother11.3 KB
assets/example-org-chart-full.htmlother11.8 KB
assets/example-org-chart.htmlother11.3 KB
assets/example-paved-road-animated.htmlother27.6 KB
assets/example-polar-dark.htmlother10.2 KB
assets/example-polar-full.htmlother12.4 KB
assets/example-polar.htmlother10.1 KB
assets/example-policy-trace-animated.htmlother24.9 KB
assets/example-process-dark.htmlother14.7 KB
assets/example-process-full.htmlother17.1 KB
assets/example-process.htmlother14.6 KB
assets/example-pyramid-dark.htmlother6.5 KB
assets/example-pyramid-full.htmlother9.5 KB
assets/example-pyramid.htmlother6.4 KB
assets/example-quadrant-consultant.htmlother11.6 KB
assets/example-quadrant-dark.htmlother6.5 KB
assets/example-quadrant-full.htmlother9.4 KB
assets/example-quadrant.htmlother6.4 KB
assets/example-queue-animated.htmlother29.2 KB
assets/example-radar-dark.htmlother7.5 KB
assets/example-radar-full.htmlother10.2 KB
assets/example-radar.htmlother7.7 KB
assets/example-ridgeline-dark.htmlother10.1 KB
assets/example-ridgeline-full.htmlother13.9 KB
assets/example-ridgeline.htmlother10.0 KB
assets/example-sankey-dark.htmlother8.8 KB
assets/example-sankey-full.htmlother11.5 KB
assets/example-sankey.htmlother8.7 KB
assets/example-scatter-dark.htmlother9.3 KB
assets/example-scatter-full.htmlother11.3 KB
assets/example-scatter.htmlother9.2 KB
assets/example-sequence-dark.htmlother13.5 KB
assets/example-sequence-full.htmlother17.8 KB
assets/example-sequence-oauth-dark.htmlother11.8 KB
assets/example-sequence-oauth-full.htmlother16.2 KB
assets/example-sequence-oauth.htmlother14.0 KB
assets/example-sequence.htmlother13.4 KB
assets/example-slopegraph-dark.htmlother10.2 KB
assets/example-slopegraph-full.htmlother13.6 KB
assets/example-slopegraph.htmlother10.1 KB
assets/example-state-dark.htmlother8.5 KB
assets/example-state-full.htmlother11.4 KB
assets/example-state.htmlother8.5 KB
assets/example-story-map-dark.htmlother12.0 KB
assets/example-story-map-full.htmlother15.1 KB
assets/example-story-map.htmlother11.9 KB
assets/example-swimlane-dark.htmlother10.3 KB
assets/example-swimlane-full.htmlother13.2 KB
assets/example-swimlane.htmlother10.2 KB
assets/example-timeline-dark.htmlother7.2 KB
assets/example-timeline-full.htmlother10.1 KB
assets/example-timeline.htmlother7.2 KB
assets/example-tree-dark.htmlother10.8 KB
assets/example-tree-full.htmlother13.7 KB
assets/example-tree.htmlother10.7 KB
assets/example-treemap-dark.htmlother7.5 KB
assets/example-treemap-full.htmlother10.5 KB
assets/example-treemap.htmlother7.4 KB
assets/example-uml-class-dark.htmlother12.1 KB
assets/example-uml-class-full.htmlother15.3 KB
assets/example-uml-class.htmlother12.1 KB
assets/example-venn-dark.htmlother6.5 KB
assets/example-venn-full.htmlother9.7 KB
assets/example-venn.htmlother5.0 KB
assets/example-wardley-dark.htmlother8.7 KB
assets/example-wardley-full.htmlother11.1 KB
assets/example-wardley.htmlother8.7 KB
assets/icons.htmlother106.0 KB
assets/index.htmlother15.2 KB
assets/template-dark.htmlother3.1 KB
assets/template-full.htmlother22.0 KB
assets/template-motion.htmlother19.4 KB
assets/template-terminal.htmlother4.8 KB
assets/template.htmlother3.2 KB
local-patches/playwright-chromium-discovery.patchother32.2 KB
references/animation.mdmarkdown11.5 KB
references/doctor.mdmarkdown5.4 KB
references/export.mdmarkdown8.3 KB
references/import-drawio.mdmarkdown12.8 KB
references/import-mermaid.mdmarkdown8.7 KB
references/onboarding.mdmarkdown13.5 KB
references/output-spec.mdmarkdown10.9 KB
references/primitive-annotation.mdmarkdown1.7 KB
references/primitive-icons.mdmarkdown103.5 KB
references/primitive-sketchy.mdmarkdown1.7 KB
references/primitive-terminal.mdmarkdown3.8 KB
references/profiles.mdmarkdown13.9 KB
references/semantic-patterns.mdmarkdown10.1 KB
references/style-guide.mdmarkdown8.5 KB
references/type-architecture.mdmarkdown4.9 KB
references/type-bar.mdmarkdown13.3 KB
references/type-data-flow.mdmarkdown20.8 KB
references/type-db-schema.mdmarkdown4.8 KB
references/type-dependency.mdmarkdown4.1 KB
references/type-deployment.mdmarkdown4.1 KB
references/type-dp-integration.mdmarkdown21.7 KB
references/type-dp-security-matrix.mdmarkdown18.6 KB
references/type-er.mdmarkdown1.5 KB
references/type-fishbone.mdmarkdown5.6 KB
references/type-flowchart.mdmarkdown1.1 KB
references/type-gantt.mdmarkdown2.4 KB
references/type-high-level.mdmarkdown26.1 KB
references/type-it-state.mdmarkdown29.3 KB
references/type-journey.mdmarkdown5.0 KB
references/type-kanban.mdmarkdown4.2 KB
references/type-layers.mdmarkdown1.5 KB
references/type-line.mdmarkdown26.8 KB
references/type-loop.mdmarkdown12.3 KB
references/type-medallion.mdmarkdown21.7 KB
references/type-nested.mdmarkdown1.4 KB
references/type-org-chart.mdmarkdown3.0 KB
references/type-polar.mdmarkdown7.6 KB
references/type-process.mdmarkdown27.9 KB
references/type-pyramid.mdmarkdown1.7 KB
references/type-quadrant.mdmarkdown6.1 KB
references/type-radar.mdmarkdown5.5 KB
references/type-sankey.mdmarkdown8.7 KB
references/type-scatter.mdmarkdown11.0 KB
references/type-sequence.mdmarkdown6.5 KB
references/type-state.mdmarkdown1.1 KB
references/type-story-map.mdmarkdown4.7 KB

references/semantic-patterns.md

View on GitHub
# Semantic patterns

Semantic patterns describe **what a system does**; the 39 visual types describe **how information is arranged**. Choose a pattern first when behavior, state, enforcement, or risk is load-bearing, then use its nearest visual type as the layout grammar. If no pattern matches, choose a visual type directly.

Use one primary pattern per figure. A second pattern may supply at most one supporting primitive; if both need full treatment, split overview and detail. Labels and outcomes must remain complete in a static frame.

## Routing table

| The reader must understand… | Semantic pattern | Nearest visual type |
|---|---|---|
| Many arrivals competing for finite service capacity | **Fan-in queue / bottleneck** | Data flow |
| Repeated questions, inputs, controls, and outputs across stages | **Stage framework with semantic slots** | Process |
| A loose conversation becoming a durable structured record | **Unstructured input → structured artifact** | Data flow |
| Why two policy decisions differ and where they first diverge | **Paired policy-evaluation traces** | Flowchart |
| Which routes cross a trust boundary and which routes are blocked | **Secure paved road** | Architecture |
| Which controls apply at each enforcement surface | **Governance / control catalog** | Layer stack |
| How defenses reduce risk and what risk remains | **Compensating security layers** | Layer stack |

## 1. Fan-in queue / bottleneck

**Selection triggers:** Several producers converge on one reviewer, service, gate, or constrained resource; the story depends on arrival rate, queue depth, wait, capacity, or backpressure.

**Required primitives:** Distinct sources; fanned ingress; an ordered queue with visible slots and count; a capacity/service-rate label; one constrained service point; admitted and deferred/rejected outcomes. Label units (`8/hour`, `3 slots`), not just “high.”

**Complexity budget:** ≤5 sources, ≤5 queue slots, one bottleneck, two outcomes, and ≤9 primary nodes. Aggregate excess sources as a named cohort.

**Anti-patterns:** Equal-width pipeline that hides contention; arrows merged before they can be traced; capacity implied only by box size; decorative pile-up; animation that changes item order; red alone meaning overloaded.

**Static fallback:** Show the representative final queue, numeric count/capacity, bottleneck label, and both outcome paths. A still must reveal why work waits.

**Nearest visual type:** **Data flow** by default; use **Process** when service stages, rather than sources, dominate.

## 2. Stage framework with semantic slots

**Selection triggers:** A lifecycle or operating model repeats the same semantic questions across stages, commonly Question, Input, Governance, and Output. Cross-stage comparability matters more than message timing.

**Required primitives:** Ordered stage headers; a consistent slot grid; explicit empty/not-applicable slots; stage-to-stage handoff; stable slot labels; one primary output per stage. Preserve slot order in every stage.

**Complexity budget:** 3–6 stages, 3–4 slot kinds, ≤20 populated cells, ≤2 lines per cell. Split detail when a cell needs prose.

**Anti-patterns:** Each stage invents a different internal layout; slot meaning encoded by position with no labels; fake precision from dozens of cells; confusing stage order with ownership lanes; shrinking text to keep one canvas.

**Static fallback:** Render the full stage × slot matrix with handoffs and explicit `—` or `Not applicable` entries. Do not depend on staged reveal to teach the schema.

**Nearest visual type:** **Process**; use **Swimlane** only when the repeated rows represent owners rather than semantic slots.

## 3. Unstructured input → structured artifact

**Selection triggers:** Dialogue, notes, prompts, or a rambling request are elicited, normalized, and written into a durable brief, ticket, record, schema, or other structured artifact.

**Required primitives:** Source utterance(s); clarifying questions; extracted field/value pairs; a named transformation; the durable artifact boundary; provenance links from representative statements to fields; missing/unknown state.

**Complexity budget:** ≤4 exchanges, ≤6 artifact fields, one transformation, and ≤3 provenance links. Show representative content, not a transcript.

**Anti-patterns:** “AI magic” sparkle between two boxes; artifact shown as another chat bubble; fields appearing without sources; inventing certainty for missing facts; typing animation as the only readable copy.

**Static fallback:** Show a short source excerpt beside the completed labeled artifact, with at least one provenance mapping and any unknown fields visible.

**Nearest visual type:** **Data flow**; use **Process** when elicitation has several ordered gates.

## 4. Paired policy-evaluation traces

**Selection triggers:** Two otherwise similar requests reach different outcomes; the reader needs rule-by-rule `PASS`, `FAIL`, `SKIPPED`, or `NOT REACHED` state and the first divergence.

**Required primitives:** The same ordered rules on both traces; explicit status text plus symbol/shape; inputs that differ; final outcomes; a labeled first-divergence marker; a distinction between `SKIPPED` (applicable flow intentionally bypassed) and `NOT REACHED` (evaluation stopped earlier).

**Complexity budget:** Exactly 2 traces, 3–6 rules, one first divergence, ≤12 status cells, and one outcome per trace. Move rule prose to notes if labels exceed one line.

**Anti-patterns:** Comparing two independently ordered flows; green/red dots without words; treating skipped and not-reached as synonyms; highlighting every difference; continuing a denied trace as if downstream rules ran.

**Static fallback:** Show all rule states and both outcomes at once; use a persistent bracket/line and label for the first divergence.

**Nearest visual type:** **Flowchart** for ordered decision logic; use **Sequence** only when messages between actors and time are also load-bearing.

## 5. Secure paved road

**Selection triggers:** A supported architecture creates a bounded route from intake/build to deployment; trust boundaries, privileged moments, permitted ingress, forbidden ingress, and approved versus blocked deploy paths are the point.

**Required primitives:** Labeled trust boundaries; actors and identities; permitted ingress with a positive text label; forbidden ingress terminating at the boundary; approved deployment path; blocked bypass path; privileged gate; isolated runtime; audit destination. Use different line styles and stop symbols in addition to color.

**Complexity budget:** ≤3 trust zones, ≤8 components, ≤10 paths, ≤2 forbidden paths, and one privileged gate. Split control detail into a catalog figure.

**Anti-patterns:** Dashed box called “security” with no route semantics; forbidden arrow crossing into the protected zone; secrets or identity implied but unlabeled; every component styled as trusted; a bypass path that visually rejoins the approved route.

**Static fallback:** Render every boundary and both permitted/forbidden routes. Blocked paths must visibly stop before entry or deployment.

**Nearest visual type:** **Architecture**.

## 6. Governance / control catalog

**Selection triggers:** A control inventory must be understood by where it is enforced: authoring, workspace, merge/CI, deploy/runtime, or another named surface. A single checklist would hide those enforcement points.

**Required primitives:** Enforcement-surface groups; named controls; enforcement actor (`code`, `platform`, `human`); timing (`write`, `merge`, `deploy`, `run`); bypassability or exception route; coverage/gap notation.

**Complexity budget:** 3–5 surfaces, 3–7 controls per surface, ≤24 controls total, and ≤3 attributes per control. Summarize counts only when the item list exists elsewhere.

**Anti-patterns:** 35 tiny pills; grouping by vague themes instead of enforcement point; mixing aspirations with enforced controls; icons without control names; claiming defense-in-depth without showing surface coverage.

**Static fallback:** Show the complete grouped catalog with surface headers and text labels for actor and enforcement timing; preserve gaps and exceptions.

**Nearest visual type:** **Layer stack**; use **DP security matrix** when role permissions, not enforcement surfaces, are the dominant comparison.

## 7. Compensating security layers

**Selection triggers:** No layer is perfect; each defense covers a failure left by the previous layer, and residual risk must visibly narrow, transfer, or remain through the stack.

**Required primitives:** Ordered threat/risk input; named defensive layers; each layer's mitigation; explicit limitation or escape; residual-risk carrier between layers; final residual risk and consequence/response. Use labels or decreasing measures, never area alone.

**Complexity budget:** 3–5 layers, one primary risk thread, ≤2 mitigations per layer, and one final residual-risk statement. Split multiple unrelated threats into separate figures.

**Anti-patterns:** Implying the final layer makes risk zero; equal opaque slabs with no propagation; treating audit as prevention; shrinking shapes without numeric or verbal meaning; reversing prevention/detection/recovery order without explanation.

**Static fallback:** Show the complete propagation chain: initial risk → mitigation → escaped risk at every layer → final residual risk and response.

**Nearest visual type:** **Layer stack**; use **Nested** when containment boundaries, rather than ordered compensation, carry the meaning.

## Composition rules

- The semantic pattern may specialize status, boundary, queue, or propagation primitives; the selected type still owns page axis, connector grammar, spacing, and type-specific limits.
- Apply the stricter of the pattern budget and visual-type budget. Semantic cells/statuses are not permission to exceed the nine-node overview target.
- Use stable text for states and outcomes. Color, motion, and position reinforce meaning but never carry it alone.
- Optional animation is a presentation layer, not another pattern. Load [`animation.md`](animation.md) only when motion is requested or materially clarifies ordered change.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall