[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DM6HZ7YN9M3WGXVN64AW1":3,"skill-same:01M79DM6HZ7YN9M3WGXVN64AW1":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79DM6HZ7YN9M3WGXVN64AW1","init",null,"Install the INSPIRE runtime into this repository: materialize the skills, validators, hooks and knowledge-base skeleton, register the hooks, and freeze the runtime version. Run once per project. Use when setting up INSPIRE in a new or existing repo.","Genomcore\u002Finspire","Genomcore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67845649?v=4","01M79DGNHB5DVE1Q8TC7F3K4FY","01M79DGNM14QF64G5NWT5X00SY",0,"MIT","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Finit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: init\ndescription: \"Install the INSPIRE runtime into this repository: materialize the skills, validators, hooks and knowledge-base skeleton, register the hooks, and freeze the runtime version. Run once per project. Use when setting up INSPIRE in a new or existing repo.\"\n---\n\n# \u002Finspire:init — install INSPIRE into this project\n\nMaterializes the plugin's inert payload into the repository and registers it. Once\ncommitted, the runtime travels with the repo: teammates and CI need no plugin.\n\n## Preconditions\n\n1. **A git repository.** Run `git rev-parse --show-toplevel`. If it fails, stop and tell\n   the operator to `git init` first.\n2. **Tools.** `yq` (Mike Farah v4) and `jq` 1.6+ must be on `PATH`. Check with\n   `command -v yq jq`. If either is missing, stop and report which.\n3. **Not already installed.** If `.inspire.lock` exists, stop — this project is already\n   initialized. Direct the operator to `\u002Finspire:update` instead.\n4. **Not the template repo.** If `plugin\u002F.claude-plugin\u002Fplugin.json` exists at the\n   project root, stop: this is the INSPIRE template itself, and installing here would\n   activate the runtime against it.\n5. **Not an unmigrated pre-0.3 project.** If `.inspire_kb\u002F` exists and `inspire_kb\u002F` does\n   not, stop: this is a v0.2 layout that has not been migrated, and `\u002Finspire:init` never\n   migrates — it only installs fresh. `materialize.sh` refuses this too (exit 1), but say\n   it here rather than surfacing it as an error — initializing over it would strand the\n   entire knowledge base at `.inspire_kb\u002F`, where no v0.3 skill looks. The remedy is to\n   run `\u002Finspire:update`, which migrates a pre-0.3 project: it detects the old layout and\n   runs the hop chain to bring it forward, then applies the current base around whatever\n   survives.\n\n## Step 1 — Detect the shape\n\nRecord, before writing anything:\n\n- `BROWNFIELD` — whether the repo has code already. Heuristic: any of `package.json`,\n  `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, `Gemfile` at root, or a `src\u002F`\n  directory. Used only to recommend roots in Step 2.\n- `EXISTING_KB` — whether `inspire_kb\u002F` is already present. With no `.inspire.lock`\n  (precondition 3), that means this is an **adoption**, not a fresh install: a completed\n  v0.2 migration, a restored backup, a KB vendored in before init, or a lock deleted by\n  hand. `materialize.sh` seeds the KB additively — it replaces nothing under\n  `inspire_kb\u002F` — but the operator must be told, not have it inferred.\n\n## Step 2 — Ask the operator\n\nOne `AskUserQuestion` with these questions:\n\n1. **Product roots.** Greenfield (`source_root: source`, `prototype_root: prototype`) or\n   brownfield-in-place (`source_root: .`, `prototype_root: none`)? Recommend by\n   `BROWNFIELD`.\n2. **Declare the marketplace for teammates?** If yes, Step 3 passes `--declare-marketplace`\n   to `materialize.sh`, which writes `extraKnownMarketplaces` + `enabledPlugins` into\n   `.claude\u002Fsettings.json` so a teammate who trusts the repo folder is prompted to install\n   the plugin. Recommend yes. Declining breaks nothing — the runtime is in the repo either\n   way; only running a future `\u002Finspire:update` needs the plugin.\n\n## Step 3 — Show the plan, then materialize\n\nEverything mechanical is handled by `materialize.sh` — copying (including the\n`inspire_kb\u002F` skeleton, seeded once here and never again), `chmod`, the `test\u002F`\nexclusion, design-system seeding, a provisional root `CLAUDE.md`, the `.gitignore`\nblock, product roots, the `settings.json` merge and `.inspire.lock`. This skill does\nnot reimplement any of it, and must not perform file operations of its own.\n\nFirst a dry run, and show the operator what it will do:\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmaterialize.sh\" \\\n  --mode init \\\n  --plugin-root \"${CLAUDE_PLUGIN_ROOT}\" \\\n  --project-root \"$(git rev-parse --show-toplevel)\" \\\n  --source-root \"\u003Canswer>\" --prototype-root \"\u003Canswer>\" \\\n  [--declare-marketplace] \\\n  --dry-run\n```\n\nSummarize the returned JSON for the operator: what will be created, what already exists and\nwill be left alone. Two fields need more than a summary line:\n\n- **`existing_kb: true`** — the run is adopting a KB that is already there. Say so\n  explicitly and confirm before proceeding: *\"`inspire_kb\u002F` already exists (N files). Init\n  will keep everything in it and only add skeleton files it lacks. Proceed?\"* If the\n  operator did not expect a KB to be there, stop — a KB present without a lock usually\n  means an interrupted migration or a restored backup, and it is worth understanding\n  which before writing.\n- **`warnings: [...]`** — print each one verbatim. These are conditions the run cannot fix\n  on the operator's behalf. A `.gitignore` that excludes the runtime is the common one,\n  and it silently defeats the point of committing the runtime at all.\n\nThen run the same command **without** `--dry-run`.\n\nIf it exits non-zero, report its stderr verbatim and stop. Do not hand-patch a partial\ninstall: on exit 2 the payload may already be on disk, but the settings block and\n`.inspire.lock` were not written. Because the lock is written last, its absence means the\ninstall did not complete — re-running `\u002Finspire:init` is the correct recovery.\n\nParse the JSON summary from stdout and use it for Step 4's report. Report what the script\nsays it did, never what you assume it did.\n\n## Step 4 — Report, and hand off\n\nPrint what was created — and re-print any `warnings` from the final run, above the handoff\nrather than buried under it. A warning the operator scrolls past is a warning that did not\nhappen. Then:\n\n```\nINSPIRE \u003Cversion> installed.\n\n  Run:  \u002Freload-skills\n  Then: \u002Finspire-bootstrap init\n\n  (\u002Freload-skills picks up the newly materialized skills; \u002Finspire-bootstrap init\n  fills in CLAUDE.md's placeholders and starts the KB.)\n```\n\nDo not invoke `\u002Freload-skills` or `\u002Finspire-bootstrap init` on the operator's behalf —\n`\u002Freload-skills` is the operator's action, and chaining `\u002Finspire-bootstrap init` across it\nwould run against whatever skill state existed before the reload. Instruct, don't chain.\n\nRemind the operator to **commit** the result — that is what makes the runtime available to\nteammates and CI.\n\n## Rules\n\n1. **All file operations go through `materialize.sh`.** This skill never copies, `chmod`s,\n   or edits `settings.json` itself. Mechanics live in the script so they are testable and\n   shared with `\u002Finspire:update`; judgment lives here. If something mechanical is missing,\n   fix the script — do not work around it in prose.\n2. **Report the script's JSON, not your assumptions.** The summary on stdout is the record\n   of what happened.\n3. **Stop rather than guess.** Every *Precondition* above is a hard stop with a clear\n   message, never a thing to work around — and a non-zero exit from the script is a stop\n   too, not something to patch up by hand.\n4. **This skill does not author content.** Language, stack, theme and the project README\n   belong to `\u002Finspire-bootstrap init`.\n5. **Instruct, don't chain.** Report the handoff and stop; `\u002Freload-skills` and\n   `\u002Finspire-bootstrap init` are the operator's next actions, not this skill's.\n","# \u002Finspire:init — install INSPIRE into this project\n\nMaterializes the plugin's inert payload into the repository and registers it. Once\ncommitted, the runtime travels with the repo: teammates and CI need no plugin.\n\n## Preconditions\n\n1. **A git repository.** Run `git rev-parse --show-toplevel`. If it fails, stop and tell\n   the operator to `git init` first.\n2. **Tools.** `yq` (Mike Farah v4) and `jq` 1.6+ must be on `PATH`. Check with\n   `command -v yq jq`. If either is missing, stop and report which.\n3. **Not already installed.** If `.inspire.lock` exists, stop — this project is already\n   initialized. Direct the operator to `\u002Finspire:update` instead.\n4. **Not the template repo.** If `plugin\u002F.claude-plugin\u002Fplugin.json` exists at the\n   project root, stop: this is the INSPIRE template itself, and installing here would\n   activate the runtime against it.\n5. **Not an unmigrated pre-0.3 project.** If `.inspire_kb\u002F` exists and `inspire_kb\u002F` does\n   not, stop: this is a v0.2 layout that has not been migrated, and `\u002Finspire:init` never\n   migrates — it only installs fresh. `materialize.sh` refuses this too (exit 1), but say\n   it here rather than surfacing it as an error — initializing over it would strand the\n   entire knowledge base at `.inspire_kb\u002F`, where no v0.3 skill looks. The remedy is to\n   run `\u002Finspire:update`, which migrates a pre-0.3 project: it detects the old layout and\n   runs the hop chain to bring it forward, then applies the current base around whatever\n   survives.\n\n## Step 1 — Detect the shape\n\nRecord, before writing anything:\n\n- `BROWNFIELD` — whether the repo has code already. Heuristic: any of `package.json`,\n  `pyproject.toml`, `go.mod`, `Cargo.toml`, `pom.xml`, `Gemfile` at root, or a `src\u002F`\n  directory. Used only to recommend roots in Step 2.\n- `EXISTING_KB` — whether `inspire_kb\u002F` is already present. With no `.inspire.lock`\n  (precondition 3), that means this is an **adoption**, not a fresh install: a completed\n  v0.2 migration, a restored backup, a KB vendored in before init, or a lock deleted by\n  hand. `materialize.sh` seeds the KB additively — it replaces nothing under\n  `inspire_kb\u002F` — but the operator must be told, not have it inferred.\n\n## Step 2 — Ask the operator\n\nOne `AskUserQuestion` with these questions:\n\n1. **Product roots.** Greenfield (`source_root: source`, `prototype_root: prototype`) or\n   brownfield-in-place (`source_root: .`, `prototype_root: none`)? Recommend by\n   `BROWNFIELD`.\n2. **Declare the marketplace for teammates?** If yes, Step 3 passes `--declare-marketplace`\n   to `materialize.sh`, which writes `extraKnownMarketplaces` + `enabledPlugins` into\n   `.claude\u002Fsettings.json` so a teammate who trusts the repo folder is prompted to install\n   the plugin. Recommend yes. Declining breaks nothing — the runtime is in the repo either\n   way; only running a future `\u002Finspire:update` needs the plugin.\n\n## Step 3 — Show the plan, then materialize\n\nEverything mechanical is handled by `materialize.sh` — copying (including the\n`inspire_kb\u002F` skeleton, seeded once here and never again), `chmod`, the `test\u002F`\nexclusion, design-system seeding, a provisional root `CLAUDE.md`, the `.gitignore`\nblock, product roots, the `settings.json` merge and `.inspire.lock`. This skill does\nnot reimplement any of it, and must not perform file operations of its own.\n\nFirst a dry run, and show the operator what it will do:\n\n```bash\n\"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fmaterialize.sh\" \\\n  --mode init \\\n  --plugin-root \"${CLAUDE_PLUGIN_ROOT}\" \\\n  --project-root \"$(git rev-parse --show-toplevel)\" \\\n  --source-root \"\u003Canswer>\" --prototype-root \"\u003Canswer>\" \\\n  [--declare-marketplace] \\\n  --dry-run\n```\n\nSummarize the returned JSON for the operator: what will be created, what already exists and\nwill be left alone. Two fields need more than a summary line:\n\n- **`existing_kb: true`** — the run is adopting a KB that is already there. Say so\n  explicitly and confirm before proceeding: *\"`inspire_kb\u002F` already exists (N files). Init\n  will keep everything in it and only add skeleton files it lacks. Proceed?\"* If the\n  operator did not expect a KB to be there, stop — a KB present without a lock usually\n  means an interrupted migration or a restored backup, and it is worth understanding\n  which before writing.\n- **`warnings: [...]`** — print each one verbatim. These are conditions the run cannot fix\n  on the operator's behalf. A `.gitignore` that excludes the runtime is the common one,\n  and it silently defeats the point of committing the runtime at all.\n\nThen run the same command **without** `--dry-run`.\n\nIf it exits non-zero, report its stderr verbatim and stop. Do not hand-patch a partial\ninstall: on exit 2 the payload may already be on disk, but the settings block and\n`.inspire.lock` were not written. Because the lock is written last, its absence means the\ninstall did not complete — re-running `\u002Finspire:init` is the correct recovery.\n\nParse the JSON summary from stdout and use it for Step 4's report. Report what the script\nsays it did, never what you assume it did.\n\n## Step 4 — Report, and hand off\n\nPrint what was created — and re-print any `warnings` from the final run, above the handoff\nrather than buried under it. A warning the operator scrolls past is a warning that did not\nhappen. Then:\n\n```\nINSPIRE \u003Cversion> installed.\n\n  Run:  \u002Freload-skills\n  Then: \u002Finspire-bootstrap init\n\n  (\u002Freload-skills picks up the newly materialized skills; \u002Finspire-bootstrap init\n  fills in CLAUDE.md's placeholders and starts the KB.)\n```\n\nDo not invoke `\u002Freload-skills` or `\u002Finspire-bootstrap init` on the operator's behalf —\n`\u002Freload-skills` is the operator's action, and chaining `\u002Finspire-bootstrap init` across it\nwould run against whatever skill state existed before the reload. Instruct, don't chain.\n\nRemind the operator to **commit** the result — that is what makes the runtime available to\nteammates and CI.\n\n## Rules\n\n1. **All file operations go through `materialize.sh`.** This skill never copies, `chmod`s,\n   or edits `settings.json` itself. Mechanics live in the script so they are testable and\n   shared with `\u002Finspire:update`; judgment lives here. If something mechanical is missing,\n   fix the script — do not work around it in prose.\n2. **Report the script's JSON, not your assumptions.** The summary on stdout is the record\n   of what happened.\n3. **Stop rather than guess.** Every *Precondition* above is a hard stop with a clear\n   message, never a thing to work around — and a non-zero exit from the script is a stop\n   too, not something to patch up by hand.\n4. **This skill does not author content.** Language, stack, theme and the project README\n   belong to `\u002Finspire-bootstrap init`.\n5. **Instruct, don't chain.** Report the handoff and stop; `\u002Freload-skills` and\n   `\u002Finspire-bootstrap init` are the operator's next actions, not this skill's.\n",{"name":5,"description":7},"main","5a473fa1c15fb2b1d2820e7fe347894a62d6cce0","plugin\u002Fskills\u002Finit",1,"https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire","https:\u002F\u002Finspire.openbims.dev","https:\u002F\u002Fgithub.com\u002FGenomcore","https:\u002F\u002Fgenomcore.com","2026-11-13 22:27:32",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Genomcore\u002Finspire --skill init",{"tool":38,"command":39},"bunx","bunx skills add Genomcore\u002Finspire --skill init",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Genomcore\u002Finspire --skill init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Finit\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M79DMDSD4Z004V0CB01EYKT4","update","Update this project's INSPIRE runtime to the installed plugin's version: report drift, re-materialize unchanged files, and refuse to clobber local edits. Use after \u002Fplugin update inspire reports a newer base.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fupdate\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79DMAENSXPJJPWTRA9CMBV0","migrate","Move this project's knowledge base from the layered layout (01_adr, 02_modules, 03_features, 04_domain, 05_screens and the surface roster) to the concept layout under inspire_kb\u002F01_spec\u002F, where every artifact has a typed extension, and convert its [[wikilinks]] to relative Markdown links. Run once, on purpose, after \u002Finspire:update reports the layered layout or counts wikilinks. Rebuilds nothing that is already built.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmigrate\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79DM28JSC3GWEJ82346VGW6","inspire-workspace","Workspace-level validation: the global pre-PR review (orchestrating module + cross-module checks) and vault-structure validation. Use for the required pre-merge gate and top-level structure checks. ADR lifecycle lives in \u002Finspire-adr; the task tracker in \u002Finspire-task.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-workspace\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79DKYPKA8TKJCW1GF0W2WAN","inspire-task","Task tracker: create \u002F update \u002F close \u002F list \u002F show tickets in inspire_kb\u002F99_tracker\u002F. A plain-file kanban (one Markdown file per ticket, no external tool) for tracking work, drift, and skill-feedback. Use to open, advance, close, or query tickets.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-task\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79DKTXQWFBW2P6VMQW3DYWX","inspire-spike","Vertical spikes: register and harvest external functional-prototype repos. A spike is a narrow, deep, throwaway build in its OWN repo that answers 'can we build it as we think?'. Use to register such a repo (name\u002Freference it, set up its learnings hygiene) and to capture its learnings into the vault as a gap analysis against the current project.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-spike\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79DKQDXVS3TJ6GG6KXYTMXF","inspire-screens","Create and validate screens (a screen is the UI spec for one view). A screen declares its own bindings — data sources, dispatches, navigation, states — and names a shared layout and shared components as dependencies. Use when designing or reviewing an application's screens.","https:\u002F\u002Fgithub.com\u002FGenomcore\u002Finspire\u002Fblob\u002Fmain\u002Fplugin\u002Fbase\u002Fskills\u002Finspire-screens\u002FSKILL.md",[],[]]