[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ERVYCG91RWWTPJGS7YWBWA":3,"skill-same:01M7ERVYCG91RWWTPJGS7YWBWA":54},{"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},"01M7ERVYCG91RWWTPJGS7YWBWA","forge-pack",null,"Forge a pack for one technology or business domain of this repo: skills, playbooks, references and adapters built from evidence, enabled only when every eval passes. Use when onboarding proposes a pack or the user asks for one.","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-pack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: forge-pack\ndescription: \"Forge a pack for one technology or business domain of this repo: skills, playbooks, references and adapters built from evidence, enabled only when every eval passes. Use when onboarding proposes a pack or the user asks for one.\"\nmetadata:\n  layer: L3\n  source: EveryInc\u002Fcompound-engineering-plugin@7a68002:skills\u002Fce-setup\u002Freferences\u002Fpack-scaffold.md + garrytan\u002Fgstack@47d639a:skillify\u002FSKILL.md.tmpl\n  license: MIT\n---\n\n# Forge a pack\n\nA pack makes ven specific to one technology or one domain of this repo while core stays generic. It is a directory under `$(ven-profile path)\u002Fpacks\u002F` that the router reads when a task touches its files, registered only after its whole eval suite passes. The tree, `pack.json`, placeholders, the eval runner and the registration commands are in `references\u002Fpack-layout.md`.\n\n**Input:** a tech or domain name. Read the profile first (`ven-profile show`). A fact the evidence needs that the profile lacks, read from the repo; a command, record with `ven-profile learn`.\n\n**Writes:** only the state directory. Nothing is committed to the repo. A pack below 100% is never registered.\n\n## 1. Resolve the target\n\n- **Id:** the name in kebab-case. `\u003Cpack dir>` below means `$(ven-profile path)\u002Fpacks\u002F\u003Cpack>\u002F`; `\u003Cven root>` means `$(ven-profile root)`, the directory holding ven's skills.\n- **Kind:** `tech` when the name is a dependency in the lockfiles the profile lists (`ven-profile get stack.sources`); `domain` when it is a business area (`ven-profile get domain_nouns`, `$(ven-profile path)\u002FGLOSSARY.md`). Neither: ask.\n- No `$(ven-profile path)\u002Fpacks\u002F`: run `ven-profile init`.\n- `\u003Cpack dir>` already has a `pack.json`: the pack exists. Skip step 4 and send each new item to its forge skill. A `\u003Cpack dir>` without `pack.json`: stop and report it.\n\n## 2. Mine the evidence\n\n**delegate** read-only worker briefs, one per source. Each returns instances: source, date, `file:line` or link, what went wrong or was needed, and what fixed it.\n\n- **Corrections:** `ven-decisions list --step correction` first, kept to the pack's terms; then `ven-transcripts --kind corrections --since 90` and `--kind routes` as the fallback.\n- **Solutions:** entries in `$(ven-profile path)\u002Fsolutions\u002F` whose symptoms or `files:` touch the area.\n- **Merged PRs:** the code host CLI named by `ven-profile get repo.forge.cli`, read-only subcommands only, plus `git log --grep`. Review comments that repeat count; one-off typos don't.\n- **Code:** where the tech or domain lives (imports, domain nouns) gives `applies_when.paths`, with a match count per glob; dependency names and locked versions give `applies_when.deps`; heavily used libraries are reference candidates.\n\nCluster the instances into items:\n\n| Item | Bar | Forged by |\n|---|---|---|\n| reference | a library whose misuse shows up in the instances | **forge-reference** |\n| adapter | a capability a skill needs that `ven-profile adapters` lacks | **forge-adapter** |\n| skill | one idea that meets the pack bar | **forge-skill** |\n| playbook | a task shape that meets the pack bar and no core playbook fits | **forge-playbook** |\n\nThe pack bar is the promotion rule in **encode-lessons-in-structure**: 3 real instances.\n\n- A correction a type, import rule, lint rule or hook can catch is not a skill. List it as a ratchet candidate; once the pack is registered, the ratchet skill places it in the pack's `rules\u002F`.\n- A cluster under the bar becomes a proposed **compound** entry, not pack content.\n- No item clears the bar: forge nothing; report the instances and the proposed entries.\n\n## 3. Preview and ask once\n\nShow the whole plan in one message. Each skill carries its settled scope, so the approval also settles **forge-skill**'s steps 1 and 2.\n\n```text\nPack \u003Cpack> (\u003Ckind>)\napplies_when  paths: \u003Cglob> (\u003Cn> files), ...   deps: \u003Cname> \u003Clocked version>, ...\nreferences    \u003Clibrary> \u003Cversion>\nadapters      \u003Ccapability> via \u003Cexisting tool | script>\nskills        \u003Cname> (L2|L3): \u003Cone idea>\n                trigger: \u003Cwords a task uses>  boundary: \u003Cwhat it never does>  cites: ven:\u003Cname>\n                evidence: \u003Cn> instances, one line each\nplaybooks     \u003Cname>: \u003Ctask shape> (\u003Cn> instances)\ndeferred      ratchet: \u003Ccorrections>; compound: \u003Cclusters under the bar>\nevals         \u003Ccases planned>; at most $15 per suite run\nwrites        \u003Cpack dir>, the profile's packs\n```\n\nAsk with a multiple-choice question when your agent has one: forge it, change the plan, or stop. Write nothing before \"forge it\". As a subagent, return `VEN-RESULT: BLOCKED: approve the pack plan` with the preview.\n\n## 4. Scaffold\n\n1. Copy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fpack\u002F` to `\u003Cpack dir>`, rename its `cases\u002F` to `evals\u002F`, and fill every placeholder. Done when `grep -rn '{{' \u003Cpack dir>` prints nothing.\n2. `\u003Cpack dir>\u002Fpack.json` parses and names the pack, its version and owner.\n\n## 5. Forge the items\n\nIn this order, since each kind uses the ones before it:\n\n1. Each reference: **forge-reference**.\n2. Each adapter: **forge-adapter**.\n3. Each skill: **forge-skill**, from its step 3; the approved plan is its evidence and scope.\n4. Each playbook: **forge-playbook**.\n\nEach forge skill writes its own entry into `pack.json` and runs its own cases. An item that cannot be proven is dropped and reported, never shipped half-done.\n\n## 6. Prove the pack\n\n1. `ven-lint-skills --pack \u003Cpack dir>` passes.\n2. The whole suite scores 1.00 on every case, through the runner in the reference, at `--runs 3 --max-cost-usd 15`. A failing case goes back to its item's forge skill; rerun the suite after each fix. Never lower `--threshold`.\n\n## 7. Register\n\n1. Follow \"Register\" in the reference.\n2. Record it: `ven-decisions add --step forge-pack --decision \"registered \u003Cpack>: \u003Cn> skills, \u003Cn> playbooks\" --evidence \"suite \u003Cn>\u002F\u003Cn> at 3 runs\"`.\n3. Tell the user which files now bring in which skills.\n\n## Promote\n\nA pack with nothing specific to this repo or to a business domain (kind `tech`, generic globs, no glossary terms) can serve other repos. Offer it; promote only on the user's yes, following \"Promote\" in the reference.\n","# Forge a pack\n\nA pack makes ven specific to one technology or one domain of this repo while core stays generic. It is a directory under `$(ven-profile path)\u002Fpacks\u002F` that the router reads when a task touches its files, registered only after its whole eval suite passes. The tree, `pack.json`, placeholders, the eval runner and the registration commands are in `references\u002Fpack-layout.md`.\n\n**Input:** a tech or domain name. Read the profile first (`ven-profile show`). A fact the evidence needs that the profile lacks, read from the repo; a command, record with `ven-profile learn`.\n\n**Writes:** only the state directory. Nothing is committed to the repo. A pack below 100% is never registered.\n\n## 1. Resolve the target\n\n- **Id:** the name in kebab-case. `\u003Cpack dir>` below means `$(ven-profile path)\u002Fpacks\u002F\u003Cpack>\u002F`; `\u003Cven root>` means `$(ven-profile root)`, the directory holding ven's skills.\n- **Kind:** `tech` when the name is a dependency in the lockfiles the profile lists (`ven-profile get stack.sources`); `domain` when it is a business area (`ven-profile get domain_nouns`, `$(ven-profile path)\u002FGLOSSARY.md`). Neither: ask.\n- No `$(ven-profile path)\u002Fpacks\u002F`: run `ven-profile init`.\n- `\u003Cpack dir>` already has a `pack.json`: the pack exists. Skip step 4 and send each new item to its forge skill. A `\u003Cpack dir>` without `pack.json`: stop and report it.\n\n## 2. Mine the evidence\n\n**delegate** read-only worker briefs, one per source. Each returns instances: source, date, `file:line` or link, what went wrong or was needed, and what fixed it.\n\n- **Corrections:** `ven-decisions list --step correction` first, kept to the pack's terms; then `ven-transcripts --kind corrections --since 90` and `--kind routes` as the fallback.\n- **Solutions:** entries in `$(ven-profile path)\u002Fsolutions\u002F` whose symptoms or `files:` touch the area.\n- **Merged PRs:** the code host CLI named by `ven-profile get repo.forge.cli`, read-only subcommands only, plus `git log --grep`. Review comments that repeat count; one-off typos don't.\n- **Code:** where the tech or domain lives (imports, domain nouns) gives `applies_when.paths`, with a match count per glob; dependency names and locked versions give `applies_when.deps`; heavily used libraries are reference candidates.\n\nCluster the instances into items:\n\n| Item | Bar | Forged by |\n|---|---|---|\n| reference | a library whose misuse shows up in the instances | **forge-reference** |\n| adapter | a capability a skill needs that `ven-profile adapters` lacks | **forge-adapter** |\n| skill | one idea that meets the pack bar | **forge-skill** |\n| playbook | a task shape that meets the pack bar and no core playbook fits | **forge-playbook** |\n\nThe pack bar is the promotion rule in **encode-lessons-in-structure**: 3 real instances.\n\n- A correction a type, import rule, lint rule or hook can catch is not a skill. List it as a ratchet candidate; once the pack is registered, the ratchet skill places it in the pack's `rules\u002F`.\n- A cluster under the bar becomes a proposed **compound** entry, not pack content.\n- No item clears the bar: forge nothing; report the instances and the proposed entries.\n\n## 3. Preview and ask once\n\nShow the whole plan in one message. Each skill carries its settled scope, so the approval also settles **forge-skill**'s steps 1 and 2.\n\n```text\nPack \u003Cpack> (\u003Ckind>)\napplies_when  paths: \u003Cglob> (\u003Cn> files), ...   deps: \u003Cname> \u003Clocked version>, ...\nreferences    \u003Clibrary> \u003Cversion>\nadapters      \u003Ccapability> via \u003Cexisting tool | script>\nskills        \u003Cname> (L2|L3): \u003Cone idea>\n                trigger: \u003Cwords a task uses>  boundary: \u003Cwhat it never does>  cites: ven:\u003Cname>\n                evidence: \u003Cn> instances, one line each\nplaybooks     \u003Cname>: \u003Ctask shape> (\u003Cn> instances)\ndeferred      ratchet: \u003Ccorrections>; compound: \u003Cclusters under the bar>\nevals         \u003Ccases planned>; at most $15 per suite run\nwrites        \u003Cpack dir>, the profile's packs\n```\n\nAsk with a multiple-choice question when your agent has one: forge it, change the plan, or stop. Write nothing before \"forge it\". As a subagent, return `VEN-RESULT: BLOCKED: approve the pack plan` with the preview.\n\n## 4. Scaffold\n\n1. Copy `\u003Cven root>\u002Fsetup\u002Fassets\u002Ftemplates\u002Fpack\u002F` to `\u003Cpack dir>`, rename its `cases\u002F` to `evals\u002F`, and fill every placeholder. Done when `grep -rn '{{' \u003Cpack dir>` prints nothing.\n2. `\u003Cpack dir>\u002Fpack.json` parses and names the pack, its version and owner.\n\n## 5. Forge the items\n\nIn this order, since each kind uses the ones before it:\n\n1. Each reference: **forge-reference**.\n2. Each adapter: **forge-adapter**.\n3. Each skill: **forge-skill**, from its step 3; the approved plan is its evidence and scope.\n4. Each playbook: **forge-playbook**.\n\nEach forge skill writes its own entry into `pack.json` and runs its own cases. An item that cannot be proven is dropped and reported, never shipped half-done.\n\n## 6. Prove the pack\n\n1. `ven-lint-skills --pack \u003Cpack dir>` passes.\n2. The whole suite scores 1.00 on every case, through the runner in the reference, at `--runs 3 --max-cost-usd 15`. A failing case goes back to its item's forge skill; rerun the suite after each fix. Never lower `--threshold`.\n\n## 7. Register\n\n1. Follow \"Register\" in the reference.\n2. Record it: `ven-decisions add --step forge-pack --decision \"registered \u003Cpack>: \u003Cn> skills, \u003Cn> playbooks\" --evidence \"suite \u003Cn>\u002F\u003Cn> at 3 runs\"`.\n3. Tell the user which files now bring in which skills.\n\n## Promote\n\nA pack with nothing specific to this repo or to a business domain (kind `tech`, generic globs, no glossary terms) can serve other repos. Offer it; promote only on the user's yes, following \"Promote\" in the reference.\n",{"name":5,"metadata":24,"description":7},{"layer":25,"source":26,"license":15},"L3","EveryInc\u002Fcompound-engineering-plugin@7a68002:skills\u002Fce-setup\u002Freferences\u002Fpack-scaffold.md + garrytan\u002Fgstack@47d639a:skillify\u002FSKILL.md.tmpl","main","e57e3dd5c8aec0fe40658397aee9fd9b1d77bb60","plugins\u002Fven\u002Fskills\u002Fforge-pack","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-pack",{"tool":40,"command":41},"bunx","bunx skills add Ventorius\u002Fven-stack --skill forge-pack",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Ventorius\u002Fven-stack --skill forge-pack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fforge-pack\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fpack-layout.md","REFERENCE","参考文档",5781,"https:\u002F\u002Fgithub.com\u002FVentorius\u002Fven-stack\u002Fblob\u002Fmain\u002Fplugins\u002Fven\u002Fskills\u002Fforge-pack\u002Freferences\u002Fpack-layout.md",[55,62,69,76,83,90],{"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},"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":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},"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":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},"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":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},"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":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},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]