[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7881A8MT7ARFW595KXVCZTW":3,"skill-same:01M7881A8MT7ARFW595KXVCZTW":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7881A8MT7ARFW595KXVCZTW","document-feature",null,"Add or update a Chimaera feature page under docs\u002Ffeatures\u002F so the feature catalog stays true as capabilities ship. Use when a change adds or changes user-facing behavior — a new pane surface, route, agent capability, CLI command — or when you find a feature page that's stale or missing. Defines the page structure, the derived-vs-intent split, and the rule that a feat: PR must carry its doc update.","martinappberg\u002Fchimaera","martinappberg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17358377?v=4","01M787ZFA9CVKJKRZWAMAQVA9N","Martin Kjellberg","01M787ZFB4YKBEAFBABXX26F53",7,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocument-feature\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: document-feature\ndescription: \"Add or update a Chimaera feature page under docs\u002Ffeatures\u002F so the feature catalog stays true as capabilities ship. Use when a change adds or changes user-facing behavior — a new pane surface, route, agent capability, CLI command — or when you find a feature page that's stale or missing. Defines the page structure, the derived-vs-intent split, and the rule that a feat: PR must carry its doc update.\"\n---\n\n# Documenting a Chimaera feature\n\nThe [feature catalog](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) is what tells an agent (or a person)\nwhat the app *does*, feature by feature, and where each capability is wired — so it can be\nlocated and extended without re-exploring the tree. It only stays true if updating it is part\nof shipping. This skill is how you do that.\n\n## When this runs\n\n- **Always for a `feat:`** — a genuinely new user-facing capability (the same bar as a minor\n  version bump, defined once in [`scripts\u002Fversion-bump.sh`](..\u002F..\u002F..\u002Fscripts\u002Fversion-bump.sh)).\n  A `feat:` PR **must** carry its feature-page update; the [ship-pr](..\u002Fship-pr\u002FSKILL.md) flow\n  checks for it. A `feat:` also runs [capture-feature-intent](..\u002Fcapture-feature-intent\u002FSKILL.md).\n- **When you change existing user-facing behavior** in a way a page describes (a new route, a\n  changed flow, a new constraint) — update the page in the same change. The\n  [doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh) warns (never blocks) when a feature's entry points\n  changed but its page didn't.\n- **Not for** pure internal refactors, chores, or fixes with no user-visible change — those\n  touch the derived facts at most (update a path if it moved), never the Intent section.\n\n## Which page\n\nMap the feature to an existing page using the current\n[index](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) table. Add a new page only\nfor a genuinely new capability area (a whole new subsystem) — then add its row to the index\ntable **and** a feature entry in `docs\u002Ffeatures\u002Fregistry.json` (paths, maps, rules, checks) — the\n[doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh) and CI's change-impact job read it. For an existing\npage, add or extend its entry there. Then run `node scripts\u002Fcheck-feature-registry.mjs --write`.\n\n## The page is a feature contract (derived vs intent — the split is load-bearing)\n\nA page states a contract: what the feature promises a user, what it depends on, and\nhow to extend and check it. An agent derives everything above the `## Intent` divider from code and may\nregenerate it. Keep it lean — this is on-demand reference, not\nalways-on context. For each feature:\n\n- **What & when** — one or two lines: what it does and when you would use it.\n- **How it's used** — the user behavior: the concrete flow through the Web UI \u002F\n  daemon \u002F CLI, enough to operate or demo it.\n- **Where it lives** — the code entry points **and** the daemon↔UI touch points (the\n  routes \u002F WS channels \u002F IPC commands), plus the other features and services it\n  depends on. This is what makes the page worth more than reading the code cold.\n- **Key behaviors \u002F constraints \u002F edge cases** — the non-obvious rules (auth, caps,\n  error states, resource discipline) a code reader would miss.\n- **How to extend it** — the steps to add a variant (a setting, a preview type, a\n  provider), as links to the owning area map instead of repeated procedure.\n- **Acceptance checks** — the commands and live scenarios that prove the feature\n  still works (a test name, a `just` target, a **verify-app** scenario).\n- Flag honestly: **Status: partial** for a half-built capability; and where a *why* can't be\n  derived from code, leave it for the Intent section rather than guessing.\n\nWrite in the internal style of the\n[robustness plan, section 6](..\u002F..\u002F..\u002Fdocs\u002Fdesign\u002Frobustness-and-agent-experience-plan.md#writing-rules)\n(ASD-STE100 profile): one instruction per step, one main idea per sentence, active voice,\nconditions before the action. Use the stable terms workspace, session, window, pane,\nhost, job, and provider. Keep API identifiers, commands, and filenames exact. Keep\nrequirements, observed behavior, and history in separate places.\n\nBelow the divider is the **`## Intent`** section — human-authored ground truth, **never**\ngenerated or inferred from code. You do not write it from your own reasoning; it is filled only\nby [capture-feature-intent](..\u002Fcapture-feature-intent\u002FSKILL.md) from the human's answers. A new\npage ships with Intent reading *pending*.\n\nMatch an existing page's shape (e.g. [linked-terminals.md](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002Flinked-terminals.md)\nis a compact two-feature page; [chat-mode.md](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002Fchat-mode.md) is a large one) —\nsame headings, same derived\u002Fintent divider, same footer block.\n\n## Verify before you claim it\n\n- Every path, route, and command you write must resolve against the code **now** — derive it,\n  don't remember it. `node scripts\u002Fcheck-doc-links.mjs` catches broken markdown links + anchors.\n- The page is reference material: it should be reached on demand, not duplicated into the index\n  or a `AGENTS.md`. Only the [index](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) is pointed at from the root\n  [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md).\n- **Semantic review.** After the paths resolve, read each claim against the code and\n  ask: does the page still describe what the code does? A link check cannot answer\n  this. Check the user flow, the constraints, and the acceptance checks one by one.\n  Fix every claim that no longer holds, in the same change.\n\n## When no doc change is needed\n\nIf a change touches a feature's entry points but its behavior did not change (a pure\nrefactor, a rename that kept every route and flow, a test-only change), do not edit\nthe page to satisfy the [doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh). Write one sentence\nin the PR: which feature page you reviewed, and why its described behavior is unchanged.\nA meaningless edit is worse than this explanation. An unchanged page with no explanation\nreads as forgotten.\n","# Documenting a Chimaera feature\n\nThe [feature catalog](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) is what tells an agent (or a person)\nwhat the app *does*, feature by feature, and where each capability is wired — so it can be\nlocated and extended without re-exploring the tree. It only stays true if updating it is part\nof shipping. This skill is how you do that.\n\n## When this runs\n\n- **Always for a `feat:`** — a genuinely new user-facing capability (the same bar as a minor\n  version bump, defined once in [`scripts\u002Fversion-bump.sh`](..\u002F..\u002F..\u002Fscripts\u002Fversion-bump.sh)).\n  A `feat:` PR **must** carry its feature-page update; the [ship-pr](..\u002Fship-pr\u002FSKILL.md) flow\n  checks for it. A `feat:` also runs [capture-feature-intent](..\u002Fcapture-feature-intent\u002FSKILL.md).\n- **When you change existing user-facing behavior** in a way a page describes (a new route, a\n  changed flow, a new constraint) — update the page in the same change. The\n  [doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh) warns (never blocks) when a feature's entry points\n  changed but its page didn't.\n- **Not for** pure internal refactors, chores, or fixes with no user-visible change — those\n  touch the derived facts at most (update a path if it moved), never the Intent section.\n\n## Which page\n\nMap the feature to an existing page using the current\n[index](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) table. Add a new page only\nfor a genuinely new capability area (a whole new subsystem) — then add its row to the index\ntable **and** a feature entry in `docs\u002Ffeatures\u002Fregistry.json` (paths, maps, rules, checks) — the\n[doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh) and CI's change-impact job read it. For an existing\npage, add or extend its entry there. Then run `node scripts\u002Fcheck-feature-registry.mjs --write`.\n\n## The page is a feature contract (derived vs intent — the split is load-bearing)\n\nA page states a contract: what the feature promises a user, what it depends on, and\nhow to extend and check it. An agent derives everything above the `## Intent` divider from code and may\nregenerate it. Keep it lean — this is on-demand reference, not\nalways-on context. For each feature:\n\n- **What & when** — one or two lines: what it does and when you would use it.\n- **How it's used** — the user behavior: the concrete flow through the Web UI \u002F\n  daemon \u002F CLI, enough to operate or demo it.\n- **Where it lives** — the code entry points **and** the daemon↔UI touch points (the\n  routes \u002F WS channels \u002F IPC commands), plus the other features and services it\n  depends on. This is what makes the page worth more than reading the code cold.\n- **Key behaviors \u002F constraints \u002F edge cases** — the non-obvious rules (auth, caps,\n  error states, resource discipline) a code reader would miss.\n- **How to extend it** — the steps to add a variant (a setting, a preview type, a\n  provider), as links to the owning area map instead of repeated procedure.\n- **Acceptance checks** — the commands and live scenarios that prove the feature\n  still works (a test name, a `just` target, a **verify-app** scenario).\n- Flag honestly: **Status: partial** for a half-built capability; and where a *why* can't be\n  derived from code, leave it for the Intent section rather than guessing.\n\nWrite in the internal style of the\n[robustness plan, section 6](..\u002F..\u002F..\u002Fdocs\u002Fdesign\u002Frobustness-and-agent-experience-plan.md#writing-rules)\n(ASD-STE100 profile): one instruction per step, one main idea per sentence, active voice,\nconditions before the action. Use the stable terms workspace, session, window, pane,\nhost, job, and provider. Keep API identifiers, commands, and filenames exact. Keep\nrequirements, observed behavior, and history in separate places.\n\nBelow the divider is the **`## Intent`** section — human-authored ground truth, **never**\ngenerated or inferred from code. You do not write it from your own reasoning; it is filled only\nby [capture-feature-intent](..\u002Fcapture-feature-intent\u002FSKILL.md) from the human's answers. A new\npage ships with Intent reading *pending*.\n\nMatch an existing page's shape (e.g. [linked-terminals.md](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002Flinked-terminals.md)\nis a compact two-feature page; [chat-mode.md](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002Fchat-mode.md) is a large one) —\nsame headings, same derived\u002Fintent divider, same footer block.\n\n## Verify before you claim it\n\n- Every path, route, and command you write must resolve against the code **now** — derive it,\n  don't remember it. `node scripts\u002Fcheck-doc-links.mjs` catches broken markdown links + anchors.\n- The page is reference material: it should be reached on demand, not duplicated into the index\n  or a `AGENTS.md`. Only the [index](..\u002F..\u002F..\u002Fdocs\u002Ffeatures\u002FREADME.md) is pointed at from the root\n  [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md).\n- **Semantic review.** After the paths resolve, read each claim against the code and\n  ask: does the page still describe what the code does? A link check cannot answer\n  this. Check the user flow, the constraints, and the acceptance checks one by one.\n  Fix every claim that no longer holds, in the same change.\n\n## When no doc change is needed\n\nIf a change touches a feature's entry points but its behavior did not change (a pure\nrefactor, a rename that kept every route and flow, a test-only change), do not edit\nthe page to satisfy the [doc-drift hook](..\u002F..\u002Fhooks\u002Fdoc-drift.sh). Write one sentence\nin the PR: which feature page you reviewed, and why its described behavior is unchanged.\nA meaningless edit is worse than this explanation. An unchanged page with no explanation\nreads as forgotten.\n",{"name":5,"description":7},"main","018562a00d38ea6f3865b4faafdc462a09900b19",".claude\u002Fskills\u002Fdocument-feature",1,"https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera","https:\u002F\u002Fchimaera.sh\u002F","https:\u002F\u002Fgithub.com\u002Fmartinappberg","Genetics PhD student @ Stanford","2026-11-12 07:28:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add martinappberg\u002Fchimaera --skill document-feature",{"tool":39,"command":40},"bunx","bunx skills add martinappberg\u002Fchimaera --skill document-feature",{"tool":42,"command":43},"pnpm","pnpm dlx skills add martinappberg\u002Fchimaera --skill document-feature","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdocument-feature\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},"01M7881YD8EBQZBNS5PCQA6R02","worktree-lifecycle","Keep Chimaera's git worktrees and their Rust build output from filling the disk — when to remove your worktree, how to run scripts\u002Fworktree-gc (dry run, --apply, --self), what the SessionStart\u002FSessionEnd hooks do, and the hard rule never to touch an ACTIVE worktree. Use when your PR has merged, when disk space is low or a session-start hook flagged it, before a big cargo build (just check, cargo test --workspace, an app build), or when asked to clean up worktrees or target\u002F dirs.","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree-lifecycle\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},"01M7881SDKX58RNEYP1CTXM6KQ","verify-app","Verify a Chimaera change end-to-end against the real daemon, UI, and PTY layer before claiming it works. Use after changing daemon\u002Fserver\u002FPTY\u002FUI behavior — especially terminal, reconnect, resize, previews, or agent-launch flows, which have all had bugs that only reproduce live. Skip for pure docs\u002Fcomment changes.","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fverify-app\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},"01M7881NE4W5TX0GW5HYR17AK1","ship-pr","Open a pull request for Chimaera correctly — the CI gates that must pass, the Conventional-Commit prefix that drives the automatic version bump, and the [skip release] marker for docs\u002Fchore PRs that shouldn't ship a version. Use when creating a PR, choosing a commit\u002FPR title, or deciding whether a change should cut a release.","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fship-pr\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},"01M7881EXTJZZCG3HJ7RTQKGT9","refresh-public-messaging","Refresh Chimaera's public face — the README and the GitHub Pages site (site\u002Findex.html + site\u002Fdocs.html) — so it matches what the product actually does now, and brainstorm positioning with the maintainer. Use when the README or website has drifted behind shipped features, when revisiting the selling points \u002F tagline, or on a periodic \"is our public face still current and well-said?\" pass. Positioning is the maintainer's call — never rewrite it unilaterally.","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frefresh-public-messaging\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},"01M788141DR3AFJH2JAVZJXFZG","develop","Run Chimaera locally and iterate on it — the daemon + Vite web-UI dev loop, ports, dev-mode auth, the build-embeds-UI gotcha, the isolated per-worktree daemon (chimaerad-isolated), and where things live. Use when starting to develop or run the app, when a change needs the real daemon\u002FUI to see, when working in a git worktree or alongside another daemon, or when the dev server won't come up (port in use, Node version, blank UI).","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdevelop\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},"01M7880XTENRQMGQYZ1975FQW8","debug-live-app","Debug a running Chimaera daemon + web UI against a live isolated preview — read daemon logs, the browser console, and network traffic; reproduce a failure; and recognize the common failure modes (blank UI, 401, port in use, HMR vs rebuild). Use when the app misbehaves at runtime, a change doesn't show up, the UI won't connect, or you need to see what the daemon is actually doing.","https:\u002F\u002Fgithub.com\u002Fmartinappberg\u002Fchimaera\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdebug-live-app\u002FSKILL.md",[],[]]