[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72S65EETJAQTHN2P5220QQH":3,"skill-same:01M72S65EETJAQTHN2P5220QQH":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M72S65EETJAQTHN2P5220QQH","check-libqc",null,"Search the sibling `libqc` SDK for public exports, chain resolvers, storage interfaces, and type definitions before implementing or modifying anything in quantum-vault that consumes the SDK. Use to verify API field semantics and exported surface.","p-11\u002Fquantum-vault","p-11","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F187643446?v=4","01M72S62G38VYPMH9WSPQHE8MA","Project Eleven","01M72S62H61Y0MHGKSG7JTBZ1D",3,"MIT","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcheck-libqc\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: check-libqc\ndescription: >-\n  Search the sibling `libqc` SDK for public exports, chain resolvers, storage interfaces,\n  and type definitions before implementing or modifying anything in quantum-vault that\n  consumes the SDK. Use to verify API field semantics and exported surface.\nargument-hint: '[search-term or feature-name]'\n---\n\n# Check libqc\n\nquantum-vault consumes `@project-eleven\u002Flibqc` as a pinned published package (see `package.json`). SDK removals or renames break the extension at build time or, worse, at runtime. Verify the SDK surface before assuming a function\u002Ftype exists.\n\n## Repo Path\n\nFor source-level verification, `libqc` must be checked out as a sibling of this repo in the same parent directory. All commands below assume you run them from the `quantum-vault` repo root, so `..\u002Flibqc` always resolves to the SDK checkout. The installed version in `node_modules` must match `package.json` (enforced by `pnpm verify:libqc-source`); do not substitute with `file:`\u002F`link:`\u002F`workspace:` overrides.\n\n| Repo  | Location (relative to quantum-vault repo root) |\n| ----- | ---------------------------------------------- |\n| libqc | `..\u002Flibqc`                                     |\n\n## What to Search (per layer)\n\n| Layer                  | Path                 | What to find                                      |\n| ---------------------- | -------------------- | ------------------------------------------------- |\n| Public API             | `src\u002Findex.ts`       | The SDK boundary. Everything the extension consumes exits through here. |\n| Chain dispatch         | `src\u002Fchain\u002F`         | `getChainKind`, chain registries, chain unions    |\n| Resolvers              | `src\u002F*\u002Fresolver.ts`  | Resolver contracts (input -> output)              |\n| Resolver implementations | `src\u002F*\u002Fresolvers\u002F`  | Per-kind implementations (`evm.ts`, `solana.ts`, `bitcoin.ts`) |\n| Storage                | `src\u002Fstate.ts`       | Encrypted vault persistence + storage interfaces  |\n| Validators \u002F AA        | `src\u002FzeroDev\u002F`       | Account abstraction, validator configuration      |\n| Shared types           | `src\u002Ftypes\u002F`         | `Chain`, `ChainKind`, `CoinKey`, `AccountCoinKey` |\n| Crypto                 | `src\u002Fcryptography\u002F`  | Key derivation, encryption, AES-GCM + scrypt      |\n\n## Usage\n\n```\n\u002Fcheck-libqc [search-term]\n```\n\n## Search Strategy\n\n### 1. Verify the export exists\n\nAlways start at the SDK boundary:\n\n```bash\n# Show all exports\nrg -n \"^export \" ..\u002Flibqc\u002Fsrc\u002Findex.ts\n# Search for a specific name in the boundary\nrg -n \"\u003Csearch-term>\" ..\u002Flibqc\u002Fsrc\u002Findex.ts\n```\n\nIf the name is not exported from `src\u002Findex.ts`, it is not part of the public API and quantum-vault must not import it directly. Either add the export (and own the compatibility) or find an alternative.\n\n### 2. Find the chain-dispatch seam\n\n```bash\nrg -n \"\u003Csearch-term>\" ..\u002Flibqc\u002Fsrc\u002Fchain\u002F\nrg -n \"resolver\" ..\u002Flibqc\u002Fsrc\u002F\n```\n\n### 3. Read the resolver contract\n\n```bash\nrg -n \"type .*Resolver\" ..\u002Flibqc\u002Fsrc\u002F**\u002Fresolver.ts\n```\n\nVerify the input and output shapes the quantum-vault consumer needs to pass and handle.\n\n### 4. Check storage surface\n\n```bash\nrg -n \"Storage\" ..\u002Flibqc\u002Fsrc\u002Fstate.ts\n```\n\nConfirm serialization expectations for anything that lands in `chrome.storage.local`.\n\n## Output\n\nReport:\n\n1. **Exported name** - does it exist on `src\u002Findex.ts`?\n2. **Type signatures** - exact input\u002Foutput types\n3. **Field semantics** - for each numeric\u002Fdiscriminated field, what does it mean? (e.g., per-unit vs total, raw vs decoded)\n4. **Chain coverage** - which chain kinds have a resolver; which throw on unsupported\n5. **Security sensitivity** - is this function in the vault\u002Fcrypto\u002FAA path? If yes, flag for extra review.\n6. **Version \u002F file** - which files define the surface so the caller can verify on the current SDK version\n\n## Rules\n\n- Never infer field meaning from the field name alone - open the resolver implementation\n- Never reach past `src\u002Findex.ts` from quantum-vault application code (deep imports forbidden)\n- If the SDK is missing an export you need, the orchestrator must decide: add it to libqc (new PR) or route around it in quantum-vault\n- When changing libqc public API, re-run `pnpm build:dev` and `pnpm test:unit` in quantum-vault against the updated sibling\n","# Check libqc\n\nquantum-vault consumes `@project-eleven\u002Flibqc` as a pinned published package (see `package.json`). SDK removals or renames break the extension at build time or, worse, at runtime. Verify the SDK surface before assuming a function\u002Ftype exists.\n\n## Repo Path\n\nFor source-level verification, `libqc` must be checked out as a sibling of this repo in the same parent directory. All commands below assume you run them from the `quantum-vault` repo root, so `..\u002Flibqc` always resolves to the SDK checkout. The installed version in `node_modules` must match `package.json` (enforced by `pnpm verify:libqc-source`); do not substitute with `file:`\u002F`link:`\u002F`workspace:` overrides.\n\n| Repo  | Location (relative to quantum-vault repo root) |\n| ----- | ---------------------------------------------- |\n| libqc | `..\u002Flibqc`                                     |\n\n## What to Search (per layer)\n\n| Layer                  | Path                 | What to find                                      |\n| ---------------------- | -------------------- | ------------------------------------------------- |\n| Public API             | `src\u002Findex.ts`       | The SDK boundary. Everything the extension consumes exits through here. |\n| Chain dispatch         | `src\u002Fchain\u002F`         | `getChainKind`, chain registries, chain unions    |\n| Resolvers              | `src\u002F*\u002Fresolver.ts`  | Resolver contracts (input -> output)              |\n| Resolver implementations | `src\u002F*\u002Fresolvers\u002F`  | Per-kind implementations (`evm.ts`, `solana.ts`, `bitcoin.ts`) |\n| Storage                | `src\u002Fstate.ts`       | Encrypted vault persistence + storage interfaces  |\n| Validators \u002F AA        | `src\u002FzeroDev\u002F`       | Account abstraction, validator configuration      |\n| Shared types           | `src\u002Ftypes\u002F`         | `Chain`, `ChainKind`, `CoinKey`, `AccountCoinKey` |\n| Crypto                 | `src\u002Fcryptography\u002F`  | Key derivation, encryption, AES-GCM + scrypt      |\n\n## Usage\n\n```\n\u002Fcheck-libqc [search-term]\n```\n\n## Search Strategy\n\n### 1. Verify the export exists\n\nAlways start at the SDK boundary:\n\n```bash\n# Show all exports\nrg -n \"^export \" ..\u002Flibqc\u002Fsrc\u002Findex.ts\n# Search for a specific name in the boundary\nrg -n \"\u003Csearch-term>\" ..\u002Flibqc\u002Fsrc\u002Findex.ts\n```\n\nIf the name is not exported from `src\u002Findex.ts`, it is not part of the public API and quantum-vault must not import it directly. Either add the export (and own the compatibility) or find an alternative.\n\n### 2. Find the chain-dispatch seam\n\n```bash\nrg -n \"\u003Csearch-term>\" ..\u002Flibqc\u002Fsrc\u002Fchain\u002F\nrg -n \"resolver\" ..\u002Flibqc\u002Fsrc\u002F\n```\n\n### 3. Read the resolver contract\n\n```bash\nrg -n \"type .*Resolver\" ..\u002Flibqc\u002Fsrc\u002F**\u002Fresolver.ts\n```\n\nVerify the input and output shapes the quantum-vault consumer needs to pass and handle.\n\n### 4. Check storage surface\n\n```bash\nrg -n \"Storage\" ..\u002Flibqc\u002Fsrc\u002Fstate.ts\n```\n\nConfirm serialization expectations for anything that lands in `chrome.storage.local`.\n\n## Output\n\nReport:\n\n1. **Exported name** - does it exist on `src\u002Findex.ts`?\n2. **Type signatures** - exact input\u002Foutput types\n3. **Field semantics** - for each numeric\u002Fdiscriminated field, what does it mean? (e.g., per-unit vs total, raw vs decoded)\n4. **Chain coverage** - which chain kinds have a resolver; which throw on unsupported\n5. **Security sensitivity** - is this function in the vault\u002Fcrypto\u002FAA path? If yes, flag for extra review.\n6. **Version \u002F file** - which files define the surface so the caller can verify on the current SDK version\n\n## Rules\n\n- Never infer field meaning from the field name alone - open the resolver implementation\n- Never reach past `src\u002Findex.ts` from quantum-vault application code (deep imports forbidden)\n- If the SDK is missing an export you need, the orchestrator must decide: add it to libqc (new PR) or route around it in quantum-vault\n- When changing libqc public API, re-run `pnpm build:dev` and `pnpm test:unit` in quantum-vault against the updated sibling\n",{"name":5,"description":7,"argument-hint":24},"[search-term or feature-name]","main","94843b628446f86d412a5c5661cf42a26c828b51",".claude\u002Fskills\u002Fcheck-libqc","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault","https:\u002F\u002Fgithub.com\u002Fp-11","https:\u002F\u002Fwww.projecteleven.com","Securing digital assets for the post-quantum era","2026-10-22 17:23:20",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add p-11\u002Fquantum-vault --skill check-libqc",{"tool":39,"command":40},"bunx","bunx skills add p-11\u002Fquantum-vault --skill check-libqc",{"tool":42,"command":43},"pnpm","pnpm dlx skills add p-11\u002Fquantum-vault --skill check-libqc","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcheck-libqc\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M72S75MAGAJ9BT5N5CM75TJ1","resolve-pr-comments","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fresolve-pr-comments\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"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":57,"categories":58,"keywords":59,"publishedAt":19},"01M72S74P33WDYNZZVQB9PPSYQ","orchestrate","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Forchestrate\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"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":63,"categories":64,"keywords":65,"publishedAt":19},"01M72S73TEY2KR8F7ZKKWE1BTA","finish","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Ffinish\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M72S72X56SDNX8TGRV3MHB5J","figma","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Ffigma\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"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":75,"categories":76,"keywords":77,"publishedAt":19},"01M72S7218NT062SK66MMZJYJD","delegate","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fdelegate\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"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":81,"categories":82,"keywords":83,"publishedAt":19},"01M72S7144W92BM272E9CDAJM6","commit","https:\u002F\u002Fgithub.com\u002Fp-11\u002Fquantum-vault\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fcommit\u002FSKILL.md",[],[]]