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): budget every side-by-side labelled edge and keep junction tables beside both parents
tt-a1i1d7d3919e8ab
diff --git a/archify/references/authoring-contract.md b/archify/references/authoring-contract.mdindex ad4e98ee..18743452 100644--- a/archify/references/authoring-contract.md+++ b/archify/references/authoring-contract.md@@ -361,7 +361,10 @@ place their direct children beside or beneath them. Columns read left to right arows read top to bottom, so a relationship between neighbouring columns is onestraight corridor. Never place an unrelated entity between two aligned anchors;the router can detour around it, but the clear corridor is shorter and reads-better. Use `row`/`col` for this normal grouped layout, and only use explicit+better. A junction table has two parents: put it in a cell beside or between+both, not beneath one of them with tables stacked between it and the other,+and keep every table that shares its domain tag in one solid block of cells.+Use `row`/`col` for this normal grouped layout, and only use explicit`pos`/`via` after a diagnostic identifies a concrete geometry problem.State every key role a column carries in `key`, and the real references indiff --git a/archify/references/authoring-defaults.md b/archify/references/authoring-defaults.mdindex 1e0e7338..90807c7a 100644--- a/archify/references/authoring-defaults.md+++ b/archify/references/authoring-defaults.md@@ -22,7 +22,7 @@ Place Architecture nodes by their actual connections before assigning coordinateBefore writing positions, trace each non-main relationship: its straight or one-bend corridor must not pass another node or cross another relationship. If it does, move the endpoint that is off the main path. Start the main actor and its first connected step together near the canvas origin; use content rows for vertical rhythm. Omit `meta.viewBox` for a fresh Architecture so the Reader measures intrinsic height. Keep supplied fixed geometry authoritative.-Start with automatic routes and endpoint sides. Pin a side only for a necessary branch, return, or supplied geometry. For a fresh Architecture, leave adjacent request/reply directions automatic when no required side constraint prevents parallel straight lines; preserve supplied side pins. Reserve `via`, `channelX`, `channelY`, and label coordinates for measured defects. Before writing positions, budget each labeled main-path edge at `6.5px × ASCII units + 21px` of clear gap, counting CJK as two units; use its own label length, not a row-wide fixed gap. Keep an Architecture canvas within 1240px wide, or 1790px when it is at least 1.55 times as wide as tall; past that its 8px relationship labels drop below the desktop floor. Size Architecture sublabels for their preferred 9px text at `5.4px × text units + 8px`, with CJK counting twice; keep supporting copy concise without dropping required facts. Do not trade readability or meaning for fewer crossings. The [Geometry reference](authoring-contract.md#executable-geometry-rules) has measured spacing, port, canvas, and route rules for a diagnosed layout problem.+Start with automatic routes and endpoint sides. Pin a side only for a necessary branch, return, or supplied geometry. For a fresh Architecture, leave adjacent request/reply directions automatic when no required side constraint prevents parallel straight lines; preserve supplied side pins. Reserve `via`, `channelX`, `channelY`, and label coordinates for measured defects. Before writing positions, budget every labeled edge between side-by-side boxes, on the main path or not, at `6.5px × ASCII units + 21px` of clear gap, counting CJK as two units; use its own label length, not a row-wide fixed gap. Keep an Architecture canvas within 1240px wide, or 1790px when it is at least 1.55 times as wide as tall; past that its 8px relationship labels drop below the desktop floor. Size Architecture sublabels for their preferred 9px text at `5.4px × text units + 8px`, with CJK counting twice; keep supporting copy concise without dropping required facts. Do not trade readability or meaning for fewer crossings. The [Geometry reference](authoring-contract.md#executable-geometry-rules) has measured spacing, port, canvas, and route rules for a diagnosed layout problem.## Evidence and schema