diagram-arch
Draw a C4-style context view of the system (people, deployable containers, external systems) with containers taken from workspace manifests and deploy config and every box and arrow cited. Use when onboarding, asking how the pieces fit together, or before adding a service or integration.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- diagram-arch
- metadata
- { "layer": "L3" }
- description
- Draw a C4-style context view of the system (people, deployable containers, external systems) with containers taken from workspace manifests and deploy config and every box and arrow cited. Use when onboarding, asking how the pieces fit together, or before adding a service or integration.
03 SKILL.md 正文
Diagram arch
One picture of the system from the outside: who uses it, what runs, and what it talks to. Containers come from manifests and deploy config, not from folder names.
1. Containers
- Run
ven-profile adapter workspace.list(JSON) and readven-profile get workspaces(name, path, kind). - A container runs on its own: an app, a worker, a scheduled job, a data store. Libraries and tools are not containers; fold them into the app that uses them.
- Confirm each container in deploy config: the line that builds or starts it (container definitions, process files, deploy jobs in CI;
ven-profile detectlists the runtime and CI files). That line is the container's citation. - A workspace with no deploy entry is drawn dashed and labelled
not deployed?. Ask about it rather than guessing.
On exit 3, read the workspace manifests and deploy files yourself, per the no-adapter rule of the badge protocol in diagram-deps.
2. People and external systems
- External systems: outbound hosts, client setup and credential names in config and env example files. Cite the config line or the line that constructs the client. Name each one the way the repo names it.
- People: the user roles that reach a container, when the code makes them plain (an auth role, a separate admin app). Cite the line or leave them out.
3. Edges
- Container to container: cite the line that configures the client or makes the call (
ven-profile adapter code.search --var pattern=<host, queue or client name>). - Container to data store or external system: cite the connection or client config line.
- Label each edge with the verb that matters: "reads/writes", "enqueues reports", "sends mail".
4. Draw and check
flowchart LR
owner([account owner])
subgraph system[widget system]
web[web app]
api[api]
worker[report worker]
db[(main store)]
end
mail[mail provider]:::external
owner --> web
web -->|calls| api
api -->|reads/writes| db
api -->|enqueues reports| worker
worker -->|sends mail| mail
classDef external stroke-dasharray:4 3
The claim table that citation-check builds gets one row per container (its deploy line) and one per edge. Run citation-check; the caption counts edges, HYBRID (n/n edges cited), and a container whose row fails is fixed or removed like an edge. Save it per the badge protocol as arch-context. Render it per Rendering in the badge protocol of diagram-deps.
Keep it to one level. A request to zoom into one container goes to diagram-deps for its modules or diagram-flow for one request through it.
04 同仓库更多 Skills
yeet
Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.
write-docs
Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.
why
Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.
verify
Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.
unslop
Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.
type-discipline
Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.