[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XQ67DFD4E8P919WSJ06NK":3,"skill-same:01M77XQ67DFD4E8P919WSJ06NK":68},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M77XQ67DFD4E8P919WSJ06NK","vs-setup-adr",null,"Set up ADR support in the current repository. Creates an `adr\u002F` directory with a README, adds an adoption ADR, and updates the repo's existing guidance surfaces so architecture-impacting or hard-to-reverse decisions live in ADRs. Use when user says 'setup adr', 'add adr support', 'adopt adrs', 'create adr directory', 'architecture decision records', or wants to bootstrap ADRs in a repo.","vltansky\u002Fvs","vltansky","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5851280?v=4","01M77XJAE230PB81N52XJHT5A1","Vlad Tansky","01M77XJAET1CMBAZ2TWTT4ZQT8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vs-setup-adr\ndescription: \"Set up ADR support in the current repository. Creates an `adr\u002F` directory with a README, adds an adoption ADR, and updates the repo's existing guidance surfaces so architecture-impacting or hard-to-reverse decisions live in ADRs. Use when user says 'setup adr', 'add adr support', 'adopt adrs', 'create adr directory', 'architecture decision records', or wants to bootstrap ADRs in a repo.\"\ndisable-model-invocation: true\nmetadata:\n  verified: true\n---\n\n# Setup ADR\n\nInstall a minimal ADR surface for the current repo.\n\nThis skill is for one explicit job: make ADRs the durable home for repo-level decisions without turning the repo into a planning graveyard.\n\n## Default outcome\n\nUnless the user asks for something broader, set up ADRs with the smallest useful change set:\n\n1. Add `adr\u002FREADME.md`\n2. Add one adoption ADR such as `adr\u002Fadopt-adrs-for-repo-level-decisions.md`\n3. Update the repo's existing guidance files so they point architecture-impacting repo decisions at ADRs\n\nDo **not** default to migrating or deleting old RFC\u002Fspec\u002Fplanning docs in the same run.\n\n## Phase 1: Inspect before editing\n\nBefore creating files:\n\n- Check `git status --short` and treat unfamiliar edits as in-progress work from someone else\n- Inspect the repo's existing guidance surfaces and contributor docs\n- Inspect the repo root to see whether `adr\u002F`, `docs\u002Fdecisions\u002F`, or another ADR-like location already exists\n- Search for `ADR`, `decision record`, `RFC`, `design doc`, `adr\u002F`, and `docs\u002Fdecisions`\n\nGoal: understand the repo's current document surfaces before you add a new one.\n\n## Phase 2: Choose the target shape\n\nUse these rules:\n\n- If the repo already has a healthy ADR surface, do not create a duplicate. Fill the missing pieces instead.\n- If the repo has repo-level policy scattered across root docs and PR lore, create `adr\u002F` at the repo root.\n- Default ADR filenames to lowercase, dash-separated, present-tense imperative verb phrases.\n- Do not use numeric prefixes; use the slug alone as the identifier to avoid merge conflicts when multiple ADRs land in parallel.\n- Do not add a `Status` field by default; treat merge as approval unless the repo already has a stronger existing ADR convention.\n\nDo not ask the user for naming or template preferences unless the repo already has conflicting conventions that make the choice genuinely strategic.\n\n## Phase 3: Add the ADR scaffolding\n\nRead these bundled references before writing:\n\n- [references\u002Fdecisions-readme-template.md](references\u002Fdecisions-readme-template.md)\n- [references\u002Fadr-template.md](references\u002Fadr-template.md)\n- [references\u002Fadopt-adrs-example.md](references\u002Fadopt-adrs-example.md)\n\nAdapt them to the current repo rather than copying blindly.\n\nRequirements:\n\n- `adr\u002FREADME.md` explains when an ADR is required, when it is not required, how ADRs are named, and how superseding works\n- The adoption ADR explains why this repo is using ADRs and what kinds of decisions belong there\n- Do not add a target-repo `template.md` file unless the user explicitly wants one\n\n## Phase 4: Align root guidance\n\nUpdate only the files that exist.\n\nPriority order:\n\n1. Repo-specific agent instructions if they exist (`AGENTS.md`, `CLAUDE.md`, or equivalent)\n2. Contributor docs (`CONTRIBUTING.md` or equivalent)\n3. The root `README.md`, only if it currently misdescribes the role of `adr\u002F` or `docs\u002F`\n\n### Agent or repo instructions\n\nAdd or update concise rules that:\n\n- point architecture-impacting or hard-to-reverse repo decisions at `adr\u002F`\n- keep session artifacts or temporary exploration out of ADRs\n- keep the root file short and navigational\n\n### Contributor docs\n\nAdd one concise contributor-facing rule:\n\n- add or update an ADR when a change introduces a cross-cutting or hard-to-reverse repo decision\n\n### Root `README.md`\n\nOnly touch the README if it currently misdescribes the role of `adr\u002F` or if the repo layout section should mention ADRs separately from `docs\u002F`.\n\nDo not bloat the README with ADR process detail.\n\n## Phase 5: Preserve scope\n\nThis skill sets up the ADR surface. It does **not** automatically:\n\n- delete legacy RFC\u002Fspec docs\n- migrate historical docs into ADRs\n- add CI validation\n- create a full governance framework\n\nThose can be follow-up changes if the user asks.\n\n## Verification\n\nAfter editing:\n\n- Re-run targeted searches for `adr\u002F`, `ADR`, and root guidance mentions\n- Review the diff for scope creep\n- Confirm the setup is internally consistent: root docs, `adr\u002FREADME.md`, and the adoption ADR should all say the same thing\n\n## Output\n\nReport:\n\n- which files were added or updated\n- whether the repo already had ADR-related conventions\n- any legacy docs you intentionally left untouched\n\n## Output style\n\nApply the [shared output style](..\u002Fvs-internal-shared\u002Freferences\u002Foutput-style.md)\nto every user-facing message.\n\n## Workflow\n\nDirect: emit **Next** only. Composed: return to caller.\n\n**Prev:** architecture decision | `\u002Fvs-shape-it`\n**Next:** `\u002Fvs-shape-it`\n**Relevant:** `\u002Fvs-rfc-research` | `\u002Fvs-to-issues`\n","# Setup ADR\n\nInstall a minimal ADR surface for the current repo.\n\nThis skill is for one explicit job: make ADRs the durable home for repo-level decisions without turning the repo into a planning graveyard.\n\n## Default outcome\n\nUnless the user asks for something broader, set up ADRs with the smallest useful change set:\n\n1. Add `adr\u002FREADME.md`\n2. Add one adoption ADR such as `adr\u002Fadopt-adrs-for-repo-level-decisions.md`\n3. Update the repo's existing guidance files so they point architecture-impacting repo decisions at ADRs\n\nDo **not** default to migrating or deleting old RFC\u002Fspec\u002Fplanning docs in the same run.\n\n## Phase 1: Inspect before editing\n\nBefore creating files:\n\n- Check `git status --short` and treat unfamiliar edits as in-progress work from someone else\n- Inspect the repo's existing guidance surfaces and contributor docs\n- Inspect the repo root to see whether `adr\u002F`, `docs\u002Fdecisions\u002F`, or another ADR-like location already exists\n- Search for `ADR`, `decision record`, `RFC`, `design doc`, `adr\u002F`, and `docs\u002Fdecisions`\n\nGoal: understand the repo's current document surfaces before you add a new one.\n\n## Phase 2: Choose the target shape\n\nUse these rules:\n\n- If the repo already has a healthy ADR surface, do not create a duplicate. Fill the missing pieces instead.\n- If the repo has repo-level policy scattered across root docs and PR lore, create `adr\u002F` at the repo root.\n- Default ADR filenames to lowercase, dash-separated, present-tense imperative verb phrases.\n- Do not use numeric prefixes; use the slug alone as the identifier to avoid merge conflicts when multiple ADRs land in parallel.\n- Do not add a `Status` field by default; treat merge as approval unless the repo already has a stronger existing ADR convention.\n\nDo not ask the user for naming or template preferences unless the repo already has conflicting conventions that make the choice genuinely strategic.\n\n## Phase 3: Add the ADR scaffolding\n\nRead these bundled references before writing:\n\n- [references\u002Fdecisions-readme-template.md](references\u002Fdecisions-readme-template.md)\n- [references\u002Fadr-template.md](references\u002Fadr-template.md)\n- [references\u002Fadopt-adrs-example.md](references\u002Fadopt-adrs-example.md)\n\nAdapt them to the current repo rather than copying blindly.\n\nRequirements:\n\n- `adr\u002FREADME.md` explains when an ADR is required, when it is not required, how ADRs are named, and how superseding works\n- The adoption ADR explains why this repo is using ADRs and what kinds of decisions belong there\n- Do not add a target-repo `template.md` file unless the user explicitly wants one\n\n## Phase 4: Align root guidance\n\nUpdate only the files that exist.\n\nPriority order:\n\n1. Repo-specific agent instructions if they exist (`AGENTS.md`, `CLAUDE.md`, or equivalent)\n2. Contributor docs (`CONTRIBUTING.md` or equivalent)\n3. The root `README.md`, only if it currently misdescribes the role of `adr\u002F` or `docs\u002F`\n\n### Agent or repo instructions\n\nAdd or update concise rules that:\n\n- point architecture-impacting or hard-to-reverse repo decisions at `adr\u002F`\n- keep session artifacts or temporary exploration out of ADRs\n- keep the root file short and navigational\n\n### Contributor docs\n\nAdd one concise contributor-facing rule:\n\n- add or update an ADR when a change introduces a cross-cutting or hard-to-reverse repo decision\n\n### Root `README.md`\n\nOnly touch the README if it currently misdescribes the role of `adr\u002F` or if the repo layout section should mention ADRs separately from `docs\u002F`.\n\nDo not bloat the README with ADR process detail.\n\n## Phase 5: Preserve scope\n\nThis skill sets up the ADR surface. It does **not** automatically:\n\n- delete legacy RFC\u002Fspec docs\n- migrate historical docs into ADRs\n- add CI validation\n- create a full governance framework\n\nThose can be follow-up changes if the user asks.\n\n## Verification\n\nAfter editing:\n\n- Re-run targeted searches for `adr\u002F`, `ADR`, and root guidance mentions\n- Review the diff for scope creep\n- Confirm the setup is internally consistent: root docs, `adr\u002FREADME.md`, and the adoption ADR should all say the same thing\n\n## Output\n\nReport:\n\n- which files were added or updated\n- whether the repo already had ADR-related conventions\n- any legacy docs you intentionally left untouched\n\n## Output style\n\nApply the [shared output style](..\u002Fvs-internal-shared\u002Freferences\u002Foutput-style.md)\nto every user-facing message.\n\n## Workflow\n\nDirect: emit **Next** only. Composed: return to caller.\n\n**Prev:** architecture decision | `\u002Fvs-shape-it`\n**Next:** `\u002Fvs-shape-it`\n**Relevant:** `\u002Fvs-rfc-research` | `\u002Fvs-to-issues`\n",{"name":5,"metadata":24,"description":7,"disable-model-invocation":25},{"verified":25},true,"master","72448991571c9e5f0e76cccf189b8522d442e6eb","skills\u002Fvs-setup-adr",1,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs","https:\u002F\u002Fgithub.com\u002Fvltansky","2026-11-06 18:47:54",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add vltansky\u002Fvs --skill vs-setup-adr",{"tool":39,"command":40},"bunx","bunx skills add vltansky\u002Fvs --skill vs-setup-adr",{"tool":42,"command":43},"pnpm","pnpm dlx skills add vltansky\u002Fvs --skill vs-setup-adr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002FSKILL.md",[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",143,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"README.md",825,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002FREADME.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fadopt-adrs-example.md",1911,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002Freferences\u002Fadopt-adrs-example.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fadr-template.md",762,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002Freferences\u002Fadr-template.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fdecisions-readme-template.md",1575,"https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-setup-adr\u002Freferences\u002Fdecisions-readme-template.md",[69,76,82,87,94,99],{"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},"01M77XSKWFMPKFXM0311QKEJHH","vs-write","Use when asked to write, rewrite, edit, tighten, simplify, or polish prose for clarity, or to put text in STE, ASD-STE100, or controlled language. Produces plain, direct, accessible copy without losing substance or precision.","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-write\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77XSJNX2V560HSKQKQD67KP","vs-fake-verify","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-verify\u002Ftest\u002Ffixtures\u002Fpath-end-state\u002Fstub-rejector\u002FSKILL.md",[],[],{"skillNo":83,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M77XSHHBEMMYZ6B4PD384NZH","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-verify\u002Ftest\u002Ffixtures\u002Fpath-end-state\u002Fstructure-paste\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M77XSE2Y7MW0KP3DTFNEE2E8","vs-verify","Use when asked to verify, prove it works, check completion, or before claiming done. Produces evidence-backed PASS\u002FWARN\u002FFAIL status.","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-verify\u002Ftest\u002Ffixtures\u002Fpath-end-state\u002Fpublished-pair\u002FSKILL.md",[],[],{"skillNo":95,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77XSAXFQXNE6VCRC7275Z0X","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-verify\u002Ftest\u002Ffixtures\u002Fpath-end-state\u002Fphrase-complete-beside\u002FSKILL.md",[],[],{"skillNo":100,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M77XS6R0E9X1E5KKSS00WYSS","https:\u002F\u002Fgithub.com\u002Fvltansky\u002Fvs\u002Fblob\u002Fmaster\u002Fskills\u002Fvs-verify\u002FSKILL.md",[],[]]