Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
HTML agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdeepseek-harnessdeveloper-toolsdiagramsdiagrams-as-codedsh-pluginflowchartllmmermaidopencodesequence-diagramsoftware-architecturesystem-designvisualization
docs(skill): scope layout receipts to supported diagram types
tt-a1ia68ef18a059b
diff --git a/archify.zip b/archify.zipindex 4dc7fde7..76b7ab46 100644Binary files a/archify.zip and b/archify.zip differdiff --git a/archify/SKILL.md b/archify/SKILL.mdindex ef69e1f8..58b36a9d 100644--- a/archify/SKILL.md+++ b/archify/SKILL.md@@ -18,7 +18,7 @@ Use this bounded path for ordinary generation. Do not read the optional Viewer R1. Choose `architecture`, `workflow`, `sequence`, `dataflow`, or `lifecycle` from the question.2. Read one matching schema in `schemas/`, `schemas/common.schema.json`, and one matching JSON example in `examples/`. Read only those files. Fresh authorship means new stable IDs, domain wording, and layout; use the example for field shape, not facts. New workflow sources use `schema_version: 2` and its readable layout contract; keep `schema_version: 1` only when preserving an existing workflow's fixed geometry. When real product identity matters, query `node bin/archify.mjs brands "<name>" --json`; read `references/brand-marks.md` only for an unknown brand with a user-provided URL.-3. Artifact first: the next tool action must write the candidate. Write the candidate before inspecting renderer internals. Do not plan exact coordinates in prose. Start with one clear main path, short side branches, and sparse labels. Use roughly 12 primary nodes as an initial readability budget. Preserve every node and relationship required by the user's question; for larger diagrams, group related content where the selected schema supports it. Set `meta.quality_profile` to `"showcase"` unless the user explicitly requests a dense `standard` map. Start with automatic routes and labels. Do not add `via`, `channelX`, `channelY`, or `labelAt` before a diagnostic calls for one; repair one diagnosed geometry problem at a time. Before manual routing, inspect `validate <type> <candidate.json> --layout-json` and the relevant routing rules in `references/authoring-contract.md`. Check whether unnecessary agent-added controls disable automatic port spread; preserve user-required route intent. If several edges share a constrained channel, plan the smallest coupled change from measured geometry and validate it together.+3. Artifact first: the next tool action must write the candidate. Write the candidate before inspecting renderer internals. Do not plan exact coordinates in prose. Start with one clear main path, short side branches, and sparse labels. Use roughly 12 primary nodes as an initial readability budget. Preserve every node and relationship required by the user's question; for larger diagrams, group related content where the selected schema supports it. Set `meta.quality_profile` to `"showcase"` unless the user explicitly requests a dense `standard` map. Start with automatic routes and labels. Do not add `via`, `channelX`, `channelY`, or `labelAt` before a diagnostic calls for one; repair one diagnosed geometry problem at a time. Before manual routing, read the relevant routing rules in `references/authoring-contract.md` and inspect layout evidence: use `validate <type> <candidate.json> --layout-json` for architecture/workflow; for other types, use validation diagnostics and the rendered SVG geometry. Check whether unnecessary agent-added controls disable automatic port spread; preserve user-required route intent. If several edges share a constrained channel, plan the smallest coupled change from measured geometry and validate it together.4. Validate after every candidate edit and immediately before handoff:```bashdiff --git a/archify/references/authoring-contract.md b/archify/references/authoring-contract.mdindex 948b3b8b..2f93c07e 100644--- a/archify/references/authoring-contract.md+++ b/archify/references/authoring-contract.md@@ -133,9 +133,10 @@ its endpoints fully imply it, explain why the wording is redundant; this is asemantic authoring choice, not a spacing repair. In workflow v2, let the compilerallocate its measured mask before applying a diagnosed `labelAt`,`labelDx`/`labelDy`, or `labelSegment`. Apply one diagnosed geometry control at-a time unless several edges share a constrained channel. In that case, inspect-`validate <type> <candidate.json> --layout-json`, plan the smallest coupled change-using measured rectangles, paths and label masks, then validate it together.+a time unless several edges share a constrained channel. In that case, plan the smallest coupled change from measured geometry and+validate it together. Architecture/workflow provide layout evidence through+`validate <type> <candidate.json> --layout-json`; for other types, use validation+diagnostics and the rendered SVG geometry.Before adding manual routes, check whether unnecessary agent-added controlsdisable automatic port spread; preserve user-required route intent. Use themeasured clearance rules above rather than guessing coordinates.