[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERTMR3FKP579QR4FJ4AHA0":3,"skill-same:01M7ERTMR3FKP579QR4FJ4AHA0":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ERTMR3FKP579QR4FJ4AHA0","diagram-flow",null,"Draw the runtime sequence of one request or event, every arrow citing the file:line that makes the call, checked by citation-check. Use for \"what happens when X runs\", tracing a request or event end to end, or before changing a flow.","Ventorius\u002Fven-stack","Ventorius","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5689509?v=4","01M7ERRDPQ5YXCNXJZWEKQNP50","Sebastian Basznianin","01M7ERRDQ9S0ZD9YMH1RN1WVP7",0,"MIT","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdiagram-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagram-flow\ndescription: Draw the runtime sequence of one request or event, every arrow citing the file:line that makes the call, checked by citation-check. Use for \"what happens when X runs\", tracing a request or event end to end, or before changing a flow.\nmetadata:\n  layer: L3\n---\n\n# Diagram flow\n\nTrace one request or event from its entry point to its last effect and draw it as a sequence. You draw it; the code backs every arrow.\n\n## 1. Pin the trigger\n\n- One trigger per diagram: a route, a command, a message type, a scheduled job, a user action. If the request names several or none and the conversation doesn't settle it, ask which (as a multiple-choice question).\n- Draw the common success path. A failure path is a second diagram.\n- Map domain words to code names with `$(ven-profile path)\u002FGLOSSARY.md`.\n\n## 2. Trace\n\n1. Find the entry point: `ven-profile adapter code.search --var pattern=\u003Cregex>` prints `path:line:text`. On exit 3, use the built-in search tool and follow the no-adapter rule of the badge protocol in **diagram-deps**.\n2. Read the entry point and follow each call that crosses a participant: a module, a process, a store, an external system. For each hop, write one claim row: what happens, and the `path:line` of the call.\n3. Keep one zoom level. Participants are modules or containers, not every function. Helpers and pure functions fold into their caller.\n4. An async hop (a published message, a queued job, a callback) is two arrows: sender to the queue or bus, citing the send line, then queue or bus to the handler, citing where the handler is registered.\n5. Stop at the last effect: the response, the write, the emitted event. Past about 15 arrows, split into two diagrams at a natural seam.\n6. What you could not trace (dynamic dispatch, routing read from config) becomes a `Note over` on the diagram, never an arrow.\n7. Draw a return arrow only when it carries data the reader needs. It cites the line that returns or replies.\n\n## 3. Draw\n\nNumber the arrows so they line up with the claim table that **citation-check** builds (`E1` is arrow 1).\n\n```mermaid\nsequenceDiagram\n  autonumber\n  participant U as user\n  participant H as widget handler\n  participant S as widget store\n  participant Q as report queue\n  participant W as report worker\n  U->>H: create widget\n  H->>S: insert widget\n  H->>Q: enqueue report job\n  H-->>U: widget id\n  Q->>W: deliver report job\n```\n\n| id | claim, in words | citation |\n|---|---|---|\n| E1 | the route sends \"create widget\" to the handler | `src\u002Fwidgets\u002Froutes:12` |\n| E2 | the handler inserts the widget | `src\u002Fwidgets\u002Fhandler:40` |\n| E3 | the handler enqueues a report job | `src\u002Fwidgets\u002Fhandler:44` |\n| E4 | the handler replies with the new id | `src\u002Fwidgets\u002Fhandler:47` |\n| E5 | the worker registers as the report job's handler | `src\u002Freports\u002Fworker:8` |\n\n## 4. Check and badge\n\nRun **citation-check** on the table. Fix the citation, redraw the arrow, or remove it until every row passes; then the caption is `HYBRID (n\u002Fn edges cited)`. Save and reuse it per the badge protocol in **diagram-deps**, as `flow-\u003Ctrigger>`.\n\nRender it per **Rendering** in the badge protocol of **diagram-deps**. Under it, list what you folded away and what you could not trace, so the reader knows where the picture stops.\n","# Diagram flow\n\nTrace one request or event from its entry point to its last effect and draw it as a sequence. You draw it; the code backs every arrow.\n\n## 1. Pin the trigger\n\n- One trigger per diagram: a route, a command, a message type, a scheduled job, a user action. If the request names several or none and the conversation doesn't settle it, ask which (as a multiple-choice question).\n- Draw the common success path. A failure path is a second diagram.\n- Map domain words to code names with `$(ven-profile path)\u002FGLOSSARY.md`.\n\n## 2. Trace\n\n1. Find the entry point: `ven-profile adapter code.search --var pattern=\u003Cregex>` prints `path:line:text`. On exit 3, use the built-in search tool and follow the no-adapter rule of the badge protocol in **diagram-deps**.\n2. Read the entry point and follow each call that crosses a participant: a module, a process, a store, an external system. For each hop, write one claim row: what happens, and the `path:line` of the call.\n3. Keep one zoom level. Participants are modules or containers, not every function. Helpers and pure functions fold into their caller.\n4. An async hop (a published message, a queued job, a callback) is two arrows: sender to the queue or bus, citing the send line, then queue or bus to the handler, citing where the handler is registered.\n5. Stop at the last effect: the response, the write, the emitted event. Past about 15 arrows, split into two diagrams at a natural seam.\n6. What you could not trace (dynamic dispatch, routing read from config) becomes a `Note over` on the diagram, never an arrow.\n7. Draw a return arrow only when it carries data the reader needs. It cites the line that returns or replies.\n\n## 3. Draw\n\nNumber the arrows so they line up with the claim table that **citation-check** builds (`E1` is arrow 1).\n\n```mermaid\nsequenceDiagram\n  autonumber\n  participant U as user\n  participant H as widget handler\n  participant S as widget store\n  participant Q as report queue\n  participant W as report worker\n  U->>H: create widget\n  H->>S: insert widget\n  H->>Q: enqueue report job\n  H-->>U: widget id\n  Q->>W: deliver report job\n```\n\n| id | claim, in words | citation |\n|---|---|---|\n| E1 | the route sends \"create widget\" to the handler | `src\u002Fwidgets\u002Froutes:12` |\n| E2 | the handler inserts the widget | `src\u002Fwidgets\u002Fhandler:40` |\n| E3 | the handler enqueues a report job | `src\u002Fwidgets\u002Fhandler:44` |\n| E4 | the handler replies with the new id | `src\u002Fwidgets\u002Fhandler:47` |\n| E5 | the worker registers as the report job's handler | `src\u002Freports\u002Fworker:8` |\n\n## 4. Check and badge\n\nRun **citation-check** on the table. Fix the citation, redraw the arrow, or remove it until every row passes; then the caption is `HYBRID (n\u002Fn edges cited)`. Save and reuse it per the badge protocol in **diagram-deps**, as `flow-\u003Ctrigger>`.\n\nRender it per **Rendering** in the badge protocol of **diagram-deps**. Under it, list what you folded away and what you could not trace, so the reader knows where the picture stops.\n",{"name":5,"metadata":24,"description":7},{"layer":25},"L3","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fdiagram-flow","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack","https:\u002F\u002Fgithub.com\u002FVentorius","Heavy testing believer. Workflow automation fan. Fullstack JS developer.","2026-11-04 04:05:46",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Ventorius\u002Fven-stack --skill diagram-flow",{"tool":39,"command":40},"bunx","bunx skills add Ventorius\u002Fven-stack --skill diagram-flow",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill diagram-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdiagram-flow\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7ES1P06ZPAGTT7YS4V6MS32","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7ES1JHVQEN3YYMRZEBM2E79","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwrite-docs\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ES1DD3YVMF1MY7D51R6516","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ES18XVRZGQ0V1BBZH63Q8W","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ES15Z3W8QTJH4CRAJ53D2G","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ES12GT9WD9NE2X3M1B29ZZ","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.","https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Ftype-discipline\u002FSKILL.md",[],[]]