[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CD2CKSDT3XNJG7B7V3J9M0":3,"skill-same:01M7CD2CKSDT3XNJG7B7V3J9M0":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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CD2CKSDT3XNJG7B7V3J9M0","lane",null,"Use lane in this repository — create isolated worktrees, read existing context before editing, and record constraints that future work must preserve.","Whamp\u002Fpi-extensions","Whamp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1115485?v=4","01M6GV45K5PM2S7V3H0JERGBXN","Will Hampson","01M7CD24WR8BM48CT1X6HWVASD",1,"MIT","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flane\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lane\ndescription: Use lane in this repository — create isolated worktrees, read existing context before editing, and record constraints that future work must preserve.\n---\n\n# lane\n\nThis repository keeps durable context \u002F memories as Markdown under `.lane\u002F`.\nYou must read before editing a file, via `lane why \u003Cpath>`, then record only the non-obvious constraints or decisions another agent would otherwise have to rediscover.\n\n## Workflow\n\n```bash\nlane new fix-login     # create a branch and worktree\n# edit and commit as usual\nlane merge             # land on local trunk\nlane merge --squash    # land on local trunk as one commit\nlane push              # push the lane for a pull request\n```\n\n`lane new` prints the worktree path. Work there, not in the parent checkout.\n\n`lane merge` rebases, audits memory, updates local trunk, and removes the lane. Commit or stash tracked changes first.\n\nThe push workflow is for protected trunks. After the pull request merges, run `lane prune`. Use `lane ls --json` for machine-readable lane state.\n\n## Read before editing\n\n```bash\nlane why src\u002Fauth.rs\nlane why src\u002F\n```\n\nRun `lane why` for every file you intend to edit. A directory returns all notes beneath it; `--json` includes full ids, anchors, timestamps, and note text.\n\nRun `lane check` before landing. For every stale note, take exactly one action:\n\n```bash\nlane note confirm \u003Cid>              # the note is still true\nlane note replace \u003Cid> \"\u003Crewrite>\"  # the constraint has changed\nlane note retire \u003Cid>               # the constraint no longer applies\n```\n\nAn unambiguous id prefix is enough. Use `lane note edit \u003Cid>` for the interactive menu, or the direct commands above in scripts and agent workflows.\n\nOther lifecycle commands:\n\n```bash\nlane note restore \u003Cid>  # restore a retired note\nlane note pin \u003Cid>      # protect a note from eviction\nlane note unpin \u003Cid>    # remove that protection\n```\n\n## Record what must stay true\n\nNot every file or commit needs a note. Only record significant, non-obvious constraints — never a summary of the change.\n\n### Commit Message Trailer(s)\n\nIf `lane install hooks` has been run, then `git` hooks are active and you can add notes while writing commit messages.\nInclude a `Why:` trailer when the finding belongs with a commit:\n\n```text\nmake verification constant-time\n\nWhy: src\u002Fauth.rs#fn verify | early return leaks token length\n```\n\nThe form is `Why: \u003Cpath>[#\u003Canchor>] | \u003Ctext>`. The path and ` | ` separator are required; omit the anchor to target the whole file.\n\nRun `lane install hooks` once if trailers are not being captured.\n\n### Manually\n\nRecord a finding directly when it does not belong to a commit, or if `lane install hooks` has not been run:\n\n```bash\nlane note add src\u002Fauth.rs -a \"fn verify\" \"must stay constant-time\"\n```\n\nSupplying text is non-interactive and defaults to `@file` when `-a` is omitted. Omit the text only when you want the interactive prompt.\n\n## Anchors\n\nAn anchor describes what a note is about:\n\n| anchor | matches |\n|---|---|\n| `fn verify` | a declaration by kind and name |\n| `verify` | a uniquely named declaration |\n| `#script`, `#style` | a top-level component block |\n| `## Rate limiting` | a Markdown section |\n| `@file` | the whole file |\n\nRun `lane anchors \u003Cpath> --json` and prefer the canonical anchor it returns. Ambiguous declaration names are refused with their available choices.\n\n## Rules\n\n- Never edit `.lane\u002F` by hand; use the `lane note` commands.\n- Do not pass `--dirty` unless the lane should inherit the parent checkout's uncommitted work.\n- Keep each note to one constraint.\n- Do not record what a commit changed.\n\nRun `lane --help` for the command list, or `lane \u003Ccommand> --help` for details.\n","# lane\n\nThis repository keeps durable context \u002F memories as Markdown under `.lane\u002F`.\nYou must read before editing a file, via `lane why \u003Cpath>`, then record only the non-obvious constraints or decisions another agent would otherwise have to rediscover.\n\n## Workflow\n\n```bash\nlane new fix-login     # create a branch and worktree\n# edit and commit as usual\nlane merge             # land on local trunk\nlane merge --squash    # land on local trunk as one commit\nlane push              # push the lane for a pull request\n```\n\n`lane new` prints the worktree path. Work there, not in the parent checkout.\n\n`lane merge` rebases, audits memory, updates local trunk, and removes the lane. Commit or stash tracked changes first.\n\nThe push workflow is for protected trunks. After the pull request merges, run `lane prune`. Use `lane ls --json` for machine-readable lane state.\n\n## Read before editing\n\n```bash\nlane why src\u002Fauth.rs\nlane why src\u002F\n```\n\nRun `lane why` for every file you intend to edit. A directory returns all notes beneath it; `--json` includes full ids, anchors, timestamps, and note text.\n\nRun `lane check` before landing. For every stale note, take exactly one action:\n\n```bash\nlane note confirm \u003Cid>              # the note is still true\nlane note replace \u003Cid> \"\u003Crewrite>\"  # the constraint has changed\nlane note retire \u003Cid>               # the constraint no longer applies\n```\n\nAn unambiguous id prefix is enough. Use `lane note edit \u003Cid>` for the interactive menu, or the direct commands above in scripts and agent workflows.\n\nOther lifecycle commands:\n\n```bash\nlane note restore \u003Cid>  # restore a retired note\nlane note pin \u003Cid>      # protect a note from eviction\nlane note unpin \u003Cid>    # remove that protection\n```\n\n## Record what must stay true\n\nNot every file or commit needs a note. Only record significant, non-obvious constraints — never a summary of the change.\n\n### Commit Message Trailer(s)\n\nIf `lane install hooks` has been run, then `git` hooks are active and you can add notes while writing commit messages.\nInclude a `Why:` trailer when the finding belongs with a commit:\n\n```text\nmake verification constant-time\n\nWhy: src\u002Fauth.rs#fn verify | early return leaks token length\n```\n\nThe form is `Why: \u003Cpath>[#\u003Canchor>] | \u003Ctext>`. The path and ` | ` separator are required; omit the anchor to target the whole file.\n\nRun `lane install hooks` once if trailers are not being captured.\n\n### Manually\n\nRecord a finding directly when it does not belong to a commit, or if `lane install hooks` has not been run:\n\n```bash\nlane note add src\u002Fauth.rs -a \"fn verify\" \"must stay constant-time\"\n```\n\nSupplying text is non-interactive and defaults to `@file` when `-a` is omitted. Omit the text only when you want the interactive prompt.\n\n## Anchors\n\nAn anchor describes what a note is about:\n\n| anchor | matches |\n|---|---|\n| `fn verify` | a declaration by kind and name |\n| `verify` | a uniquely named declaration |\n| `#script`, `#style` | a top-level component block |\n| `## Rate limiting` | a Markdown section |\n| `@file` | the whole file |\n\nRun `lane anchors \u003Cpath> --json` and prefer the canonical anchor it returns. Ambiguous declaration names are refused with their available choices.\n\n## Rules\n\n- Never edit `.lane\u002F` by hand; use the `lane note` commands.\n- Do not pass `--dirty` unless the lane should inherit the parent checkout's uncommitted work.\n- Keep each note to one constraint.\n- Do not record what a commit changed.\n\nRun `lane --help` for the command list, or `lane \u003Ccommand> --help` for details.\n",{"name":5,"description":7},"master","1d75a8ae76094c017ddb973723b6d6dfa1e0c1c3",".agents\u002Fskills\u002Flane",0,"https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions","https:\u002F\u002Fgithub.com\u002FWhamp","https:\u002F\u002Ftwitter.com\u002Fhampsonw","Motorcycles. Dogs. Bonds. Autodidact. http:\u002F\u002Fcourse.fast.ai  alum","2026-10-24 21:56:00",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Whamp\u002Fpi-extensions --skill lane",{"tool":39,"command":40},"bunx","bunx skills add Whamp\u002Fpi-extensions --skill lane",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Whamp\u002Fpi-extensions --skill lane","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Flane\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},"01M7CD9WQEV4QVY73VGX1TDQ43","sidekick-browser","Use the pinned local AXI launcher for explicit, isolated browser verification in a Sidekick child.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-sidekick\u002Fskills\u002Fsidekick-browser\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},"01M7CD9PVK6TRMX8DZR5B9QS1W","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\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},"01M7CD9KY7SH6P8ENEZG6463DV","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\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},"01M7CD9J8RY8ZH1XMHNC1A2423","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\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},"01M7CD9DY3PRH9Z1X7JTZMZRBG","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\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},"01M7CD9B6C9NXWJHEKGYPCFD6M","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]