[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERVPDN9MBDW5MY6DWWV1HB":3,"skill-same:01M7ERVPDN9MBDW5MY6DWWV1HB":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ERVPDN9MBDW5MY6DWWV1HB","forge-adapter",null,"Write a capability adapter (import graph, boundaries, schema, search, symbols, workspaces, custom rules) as a script with a fixture test, register it in adapters.json and prove it. Use when a skill reports a missing or unproven adapter, or a pack needs a capability.","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\u002Fforge-adapter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: forge-adapter\ndescription: \"Write a capability adapter (import graph, boundaries, schema, search, symbols, workspaces, custom rules) as a script with a fixture test, register it in adapters.json and prove it. Use when a skill reports a missing or unproven adapter, or a pack needs a capability.\"\nmetadata:\n  layer: L3\n  source: cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md\n  license: MIT\n---\n\n# Forge an adapter\n\nVisual and conventions skills ask for a capability with `ven-profile adapter \u003Ccapability>`; the adapter is the repo-specific command behind it. An adapter that was never executed is a draft: it counts only once its fixture test and `ven-profile prove-adapters` both pass.\n\n**Input:** a capability and the pack that will hold the script. The usual trigger is `ven-profile adapter \u003Ccapability>` exiting 3 with \"no adapter\" or \"prove it first\". Here `\u003Cpack dir>` is `$(ven-profile path)\u002Fpacks\u002F\u003Cpack>\u002F`, `\u003Cven root>` is `$(ven-profile root)`, and `\u003Cslug>` is the capability with `.` replaced by `-`.\n\n## Capabilities\n\n| Capability | Prints | Exits 1 when |\n|---|---|---|\n| `graph.imports` | module import edges, JSON `[{from,to}]` | never |\n| `graph.boundaries` | boundary violations, JSON `[{from,to,rule}]` | never |\n| `schema.read` | entities, JSON `{entities:[{name,fields,relations}]}` | never |\n| `code.search` | `path:line:text` lines matching `{pattern}` | never |\n| `symbols.list` | `name kind line` for the symbols in `{file}` | never |\n| `workspace.list` | workspaces or containers, JSON | never |\n| `lint.custom`, `rules.structural` | `path:line: rule: message` per violation | it finds a violation |\n\nThe template's `FORMAT` map prints these shapes; `collect()` only gathers the data.\n\n## 1. Pick the source\n\nLook before writing: `ven-profile adapters` (an unproven entry may only need a fix), the repo's dev dependencies and scripts, and tools on the PATH (`command -v \u003Ctool>`). Prefer, in order:\n\n1. A tool the repo already has, wrapped so its output takes the capability's shape.\n2. A script that reads the files itself, using only the runtime ven's own tools need.\n3. A new tool, only with the user's consent. Ask the user: what it is, where it installs, and the script you would write instead. Never install without a yes.\n\n## 2. Fixture first\n\n1. Build `\u003Cpack dir>\u002Fadapters\u002Ffixtures\u002F\u003Cslug>\u002Frepo\u002F`: the smallest copy of real repo files that exercises the capability, including one awkward case the repo really has.\n2. Write `\u003Cpack dir>\u002Fadapters\u002Ffixtures\u002F\u003Cslug>\u002Fexpected.txt` by hand, from reading those files: the exact output, ending in a newline.\n3. Copy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fadapter\u002Fadapter.test.mjs` to `\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs` and fill its placeholders.\n4. `node --test \u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs` fails: there is no script yet. That is the red run.\n\n## 3. Write the script\n\nCopy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fadapter\u002Fadapter.mjs` to `\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs` and write `collect()`:\n\n- **Read-only:** it never writes to the repo and never calls the network.\n- **Deterministic:** sorted output and repo-relative paths, so two runs diff clean.\n- **Scoped:** it honors `--root` and takes its file list from `git ls-files`, so ignored and generated files stay out.\n- **Baseline-aware:** a rule capability reports only violations missing from `$(ven-profile path)\u002Fbaseline\u002F\u003Ccapability>.txt`, so today's tree exits 0.\n\nDone when the fixture test passes.\n\n## 4. Run it on the real repo\n\nRun `node \u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs --root=\u003Crepo root>` with the arguments a skill would pass. Check three entries against the files they name, and one fact you know must appear. A wrong entry is a missing fixture case: add it to the fixture (red), fix `collect()` (green), run again. Apply **prove-it-works**: the output you read is the proof, not the passing test alone.\n\n## 5. Register and prove\n\n1. Add the command under the capability in `$(ven-profile path)\u002Fadapters.json`, keeping only the flags the capability uses:\n\n   ```json\n   \"\u003Ccapability>\": { \"run\": \"node '\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs' --root=. --file={file} --pattern={pattern}\", \"status\": \"unverified\", \"cwd\": \".\", \"timeout_s\": 120, \"evidence\": \"\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs\" }\n   ```\n\n   Replacing an entry whose status is `verified` needs the user's yes.\n2. Prove it with the arguments a skill would pass: `ven-profile prove-adapters \u003Ccapability> --file \u003Cpath>` (or `--var pattern=\u003Ca word that exists>`) prints `ok` and records the result under `proof`. A bare `ven-profile prove-adapters` must pass too; the template treats an unfilled `{file}` or `{pattern}` as absent.\n3. `ven-profile adapter \u003Ccapability>` with the same arguments prints what step 4 printed.\n4. Add `{ \"capability\", \"script\": \"adapters\u002F\u003Cslug>.mjs\", \"test\": \"adapters\u002F\u003Cslug>.test.mjs\" }` to `adapters` in `\u003Cpack dir>\u002Fpack.json`, and bump its patch `version`.\n\nThen rerun the skill that asked for the capability.\n","# Forge an adapter\n\nVisual and conventions skills ask for a capability with `ven-profile adapter \u003Ccapability>`; the adapter is the repo-specific command behind it. An adapter that was never executed is a draft: it counts only once its fixture test and `ven-profile prove-adapters` both pass.\n\n**Input:** a capability and the pack that will hold the script. The usual trigger is `ven-profile adapter \u003Ccapability>` exiting 3 with \"no adapter\" or \"prove it first\". Here `\u003Cpack dir>` is `$(ven-profile path)\u002Fpacks\u002F\u003Cpack>\u002F`, `\u003Cven root>` is `$(ven-profile root)`, and `\u003Cslug>` is the capability with `.` replaced by `-`.\n\n## Capabilities\n\n| Capability | Prints | Exits 1 when |\n|---|---|---|\n| `graph.imports` | module import edges, JSON `[{from,to}]` | never |\n| `graph.boundaries` | boundary violations, JSON `[{from,to,rule}]` | never |\n| `schema.read` | entities, JSON `{entities:[{name,fields,relations}]}` | never |\n| `code.search` | `path:line:text` lines matching `{pattern}` | never |\n| `symbols.list` | `name kind line` for the symbols in `{file}` | never |\n| `workspace.list` | workspaces or containers, JSON | never |\n| `lint.custom`, `rules.structural` | `path:line: rule: message` per violation | it finds a violation |\n\nThe template's `FORMAT` map prints these shapes; `collect()` only gathers the data.\n\n## 1. Pick the source\n\nLook before writing: `ven-profile adapters` (an unproven entry may only need a fix), the repo's dev dependencies and scripts, and tools on the PATH (`command -v \u003Ctool>`). Prefer, in order:\n\n1. A tool the repo already has, wrapped so its output takes the capability's shape.\n2. A script that reads the files itself, using only the runtime ven's own tools need.\n3. A new tool, only with the user's consent. Ask the user: what it is, where it installs, and the script you would write instead. Never install without a yes.\n\n## 2. Fixture first\n\n1. Build `\u003Cpack dir>\u002Fadapters\u002Ffixtures\u002F\u003Cslug>\u002Frepo\u002F`: the smallest copy of real repo files that exercises the capability, including one awkward case the repo really has.\n2. Write `\u003Cpack dir>\u002Fadapters\u002Ffixtures\u002F\u003Cslug>\u002Fexpected.txt` by hand, from reading those files: the exact output, ending in a newline.\n3. Copy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fadapter\u002Fadapter.test.mjs` to `\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs` and fill its placeholders.\n4. `node --test \u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs` fails: there is no script yet. That is the red run.\n\n## 3. Write the script\n\nCopy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fadapter\u002Fadapter.mjs` to `\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs` and write `collect()`:\n\n- **Read-only:** it never writes to the repo and never calls the network.\n- **Deterministic:** sorted output and repo-relative paths, so two runs diff clean.\n- **Scoped:** it honors `--root` and takes its file list from `git ls-files`, so ignored and generated files stay out.\n- **Baseline-aware:** a rule capability reports only violations missing from `$(ven-profile path)\u002Fbaseline\u002F\u003Ccapability>.txt`, so today's tree exits 0.\n\nDone when the fixture test passes.\n\n## 4. Run it on the real repo\n\nRun `node \u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs --root=\u003Crepo root>` with the arguments a skill would pass. Check three entries against the files they name, and one fact you know must appear. A wrong entry is a missing fixture case: add it to the fixture (red), fix `collect()` (green), run again. Apply **prove-it-works**: the output you read is the proof, not the passing test alone.\n\n## 5. Register and prove\n\n1. Add the command under the capability in `$(ven-profile path)\u002Fadapters.json`, keeping only the flags the capability uses:\n\n   ```json\n   \"\u003Ccapability>\": { \"run\": \"node '\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.mjs' --root=. --file={file} --pattern={pattern}\", \"status\": \"unverified\", \"cwd\": \".\", \"timeout_s\": 120, \"evidence\": \"\u003Cpack dir>\u002Fadapters\u002F\u003Cslug>.test.mjs\" }\n   ```\n\n   Replacing an entry whose status is `verified` needs the user's yes.\n2. Prove it with the arguments a skill would pass: `ven-profile prove-adapters \u003Ccapability> --file \u003Cpath>` (or `--var pattern=\u003Ca word that exists>`) prints `ok` and records the result under `proof`. A bare `ven-profile prove-adapters` must pass too; the template treats an unfilled `{file}` or `{pattern}` as absent.\n3. `ven-profile adapter \u003Ccapability>` with the same arguments prints what step 4 printed.\n4. Add `{ \"capability\", \"script\": \"adapters\u002F\u003Cslug>.mjs\", \"test\": \"adapters\u002F\u003Cslug>.test.mjs\" }` to `adapters` in `\u003Cpack dir>\u002Fpack.json`, and bump its patch `version`.\n\nThen rerun the skill that asked for the capability.\n",{"name":5,"metadata":24,"description":7},{"layer":25,"source":26,"license":15},"L3","cursor\u002Fplugins@1e5c90a:pstack\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fforge-adapter","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Ventorius\u002Fven-stack --skill forge-adapter",{"tool":40,"command":41},"bunx","bunx skills add Ventorius\u002Fven-stack --skill forge-adapter",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill forge-adapter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fforge-adapter\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]