[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERTBBCCY0GKFQTV2EKTS5A":3,"skill-same:01M7ERTBBCCY0GKFQTV2EKTS5A":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},"01M7ERTBBCCY0GKFQTV2EKTS5A","diagram-data",null,"Draw the entity\u002Frelationship view of the data model from the repo's schema adapter, or the data diff between two refs. Use for \"what data do we store and how does it relate\", before changing the data model, or to show what a branch changes in it.","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-data\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagram-data\ndescription: Draw the entity\u002Frelationship view of the data model from the repo's schema adapter, or the data diff between two refs. Use for \"what data do we store and how does it relate\", before changing the data model, or to show what a branch changes in it.\nmetadata:\n  layer: L3\n---\n\n# Diagram data\n\nShow the entities and how they relate, from the schema the repo declares. You choose the scope; the adapter supplies every entity, field and relation.\n\n## 1. Scope\n\n- One entity and its direct relations, a named group (one workspace's entities), or the whole model when it is small (about 15 entities).\n- Show the fields that matter to the question: keys, references to other entities, state fields, and the fields being changed. Write `+n more` for the rest.\n- Map domain words to entity names with `$(ven-profile path)\u002FGLOSSARY.md`.\n\n## 2. Generate\n\n1. Run `ven-profile adapter schema.read`. It prints `{entities:[{name,fields,relations}]}`.\n2. Keep the entities in scope plus one hop of relations. Entities outside the scope appear as stubs, name only.\n3. Draw each relation with the cardinality the output gives. Never invent one: when it is missing, draw `}o--o{`, the least committal form, and say so under the diagram.\n\n```mermaid\nerDiagram\n  ACCOUNT ||--o{ WIDGET : owns\n  WIDGET }o--o{ REPORT : \"appears in\"\n  ACCOUNT {\n    text id PK\n    text status\n  }\n  WIDGET {\n    text id PK\n    text account_id FK\n  }\n```\n\nBadge it `GENERATED ven-profile adapter schema.read @ \u003Cshort sha>`, per the badge protocol in **diagram-deps**.\n\n## 3. Data diff between two refs\n\n1. Run `schema.read` at head, then at the base ref as \"At another ref\" in the badge protocol describes.\n2. Compare by entity name: entities added or removed, fields added, removed or changed (type, nullability, default), relations added or removed.\n3. Draw only the changed entities plus their direct neighbours as stubs. Mark each change in the attribute comment (`text email \"added\"`, `int count \"type changed: was text\"`); draw removed entities with a `removed` comment on their key.\n4. Under the diagram, list each change as one line. Flag the ones that need a data migration or break existing readers.\n\nThe badge carries both refs: `@ \u003Cbase sha>..\u003Chead sha>`. Render it per **Rendering** in the badge protocol of **diagram-deps**.\n\n## Without the adapter\n\nFind where the data model is declared: schema files, migration files, model definitions (the profile's `stack` and `ven-profile detect` point at them). Each entity, field group and relation cites its declaring `file:line`, so the result is HYBRID under the protocol's no-adapter rule. When migrations are the only source, replay them in order and cite the migration that last touched each field.\n","# Diagram data\n\nShow the entities and how they relate, from the schema the repo declares. You choose the scope; the adapter supplies every entity, field and relation.\n\n## 1. Scope\n\n- One entity and its direct relations, a named group (one workspace's entities), or the whole model when it is small (about 15 entities).\n- Show the fields that matter to the question: keys, references to other entities, state fields, and the fields being changed. Write `+n more` for the rest.\n- Map domain words to entity names with `$(ven-profile path)\u002FGLOSSARY.md`.\n\n## 2. Generate\n\n1. Run `ven-profile adapter schema.read`. It prints `{entities:[{name,fields,relations}]}`.\n2. Keep the entities in scope plus one hop of relations. Entities outside the scope appear as stubs, name only.\n3. Draw each relation with the cardinality the output gives. Never invent one: when it is missing, draw `}o--o{`, the least committal form, and say so under the diagram.\n\n```mermaid\nerDiagram\n  ACCOUNT ||--o{ WIDGET : owns\n  WIDGET }o--o{ REPORT : \"appears in\"\n  ACCOUNT {\n    text id PK\n    text status\n  }\n  WIDGET {\n    text id PK\n    text account_id FK\n  }\n```\n\nBadge it `GENERATED ven-profile adapter schema.read @ \u003Cshort sha>`, per the badge protocol in **diagram-deps**.\n\n## 3. Data diff between two refs\n\n1. Run `schema.read` at head, then at the base ref as \"At another ref\" in the badge protocol describes.\n2. Compare by entity name: entities added or removed, fields added, removed or changed (type, nullability, default), relations added or removed.\n3. Draw only the changed entities plus their direct neighbours as stubs. Mark each change in the attribute comment (`text email \"added\"`, `int count \"type changed: was text\"`); draw removed entities with a `removed` comment on their key.\n4. Under the diagram, list each change as one line. Flag the ones that need a data migration or break existing readers.\n\nThe badge carries both refs: `@ \u003Cbase sha>..\u003Chead sha>`. Render it per **Rendering** in the badge protocol of **diagram-deps**.\n\n## Without the adapter\n\nFind where the data model is declared: schema files, migration files, model definitions (the profile's `stack` and `ven-profile detect` point at them). Each entity, field group and relation cites its declaring `file:line`, so the result is HYBRID under the protocol's no-adapter rule. When migrations are the only source, replay them in order and cite the migration that last touched each field.\n",{"name":5,"metadata":24,"description":7},{"layer":25},"L3","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fdiagram-data","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-data",{"tool":39,"command":40},"bunx","bunx skills add Ventorius\u002Fven-stack --skill diagram-data",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill diagram-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fdiagram-data\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",[],[]]