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): bound measured repairs for coupled routes on dev
tt-a1i7ad809173c53
diff --cc archify.zipindex b75a9d23,79fea225..4dc7fde7Binary files differdiff --cc archify/SKILL.mdindex f60c32a9,755a79bc..ef69e1f8--- a/archify/SKILL.md+++ b/archify/SKILL.md@@@ -18,7 -18,7 +18,7 @@@ Use this bounded path for ordinary gene1. 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, sparse labels, and at most 12 primary nodes. 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; apply at most one diagnosed geometry control per repair. **Plan-first mode for manual routing:** when validation reports geometry errors or visual inspection reveals edge overlaps, switch workflow before attempting fixes: (a) run `validate <type> <candidate.json> --layout-json` to obtain exact node rects and resolved edge polylines; (b) **prefer automatic over manual** — when edges overlap on the same node side, first check whether port spread is disabled for any of them by `route` presets, `via`, `channelX/Y`, or `labelAt`; if so, evaluate whether removing the disabling control lets spread resolve the overlap automatically — only proceed to manual `via` if spread cannot help; (c) read the route-preset behaviors and port-spread rules in `references/authoring-contract.md` (§ Executable geometry rules, § Spacing and labels) to understand what each route mode produces — do not trial-and-error route modes; (d) for each affected edge, calculate whether the planned route has sufficient channel width for labels (`mask width + 8px`) and clearance from adjacent segments (`≥4px`); (e) implement all spatially coupled geometry controls together as a batch, then validate once.-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; apply at most one diagnosed geometry control per repair.++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.4. Validate after every candidate edit and immediately before handoff:```bashdiff --cc archify/references/authoring-contract.mdindex ee0361cd,6c5c8df3..948b3b8b--- a/archify/references/authoring-contract.md+++ b/archify/references/authoring-contract.md@@@ -133,11 -133,7 +133,12 @@@ its endpoints fully imply it, explain wsemantic 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 — EXCEPT when multiple edges share a spatial channel (e.g. two vertical- segments bounding a label corridor): plan all coupled controls (`via`,- `labelAt`, `channelY`) as a batch using `--layout-json` evidence, then apply- and validate together. Blind single-step iteration in a shared channel causes- cascading fixes.-a time.++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.++Before adding manual routes, check whether unnecessary agent-added controls++disable automatic port spread; preserve user-required route intent. Use the++measured clearance rules above rather than guessing coordinates.### Repair order