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
Keep important opt-in boundaries visible in system overviews
tt-a1ib0239b0d48d8
diff --git a/archify.zip b/archify.zipindex 9c636ebb..99b3bbef 100644Binary files a/archify.zip and b/archify.zip differdiff --git a/archify/references/authoring-defaults.md b/archify/references/authoring-defaults.mdindex 476289b2..8a03d53d 100644--- a/archify/references/authoring-defaults.md+++ b/archify/references/authoring-defaults.md@@ -23,7 +23,7 @@ Examples demonstrate valid field shape. Before choosing a different boundary kin## Composition and meaning-- For Architecture, default to a system overview unless the user requests a detailed mechanism, module map, or deployment topology. Show the main participants, their essential interactions, and the boundaries needed to understand the requested system. Use one clear main path, short side branches, and sparse labels.+- For Architecture, default to a system overview unless the user requests a narrower mechanism, module map, or deployment topology. Cover the main user entry points, interactions, and important deployment/trust boundaries described by the project, including opt-in paths. An optional path may be a short branch or a sourced scope note; keep its role and boundary visible without expanding its internals. Name a deliberately narrower scope in the title rather than silently omitting it from a system overview. Use one clear main path, short side branches, and sparse labels.- Choose abstraction by the reader's question: would combining these responsibilities mislead the reader about the requested behavior, control ownership, trust, lifecycle, or persistence? If so, keep them separate; otherwise use an accurately named overview node with supporting labels and source references. Separate source files, classes, protocols, or internal services do not by themselves require separate nodes. For example, an overview may show one local HTTP / WebSocket service; a transport-mechanism diagram may expand it. A cloud relay and a local decrypting bridge stay distinct when the remote trust boundary matters.- Cover the requested meaning, with evidence for every claim. An overview need not enumerate every implementation role discovered during source reading. Put useful supporting facts in sublabels or concise cards; expand a subsystem in a focused diagram when its mechanism is requested. Guided views focus existing topology and do not collapse a crowded default overview. Add `meta.views` or cards only for a real reader question, with no quota.- Let the requested question and source facts determine node and relationship counts; never target a number. Choose scope and abstraction before routing. Once authoring or repairing an agreed detailed graph, preserve its required roles, relationships, meaningful labels, and evidence; geometry failures do not authorize silently reducing that scope.