[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758AWPM7CE440NBAYJHD44J":3,"skill-same:01M758AWPM7CE440NBAYJHD44J":48},{"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":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M758AWPM7CE440NBAYJHD44J","type-declarations",null,"Add, audit, or update @nubjs\u002Ftypes declarations for Nub runtime APIs. Use whenever Nub adds or changes a user-visible global, built-in method, module loader type, or TC39 proposal; when TypeScript or @types\u002Fnode gains an overlapping declaration; and before every release to reconcile runtime changes since the previous tag. Covers conflict-safe global augmentation, compiler-version routing, fixture matrices, and package verification.","nubjs\u002Fnub","nubjs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6785695?v=4","01M7583N3EYYHSNB6FJQXCDMQH","Nub","01M7583N44MVMSN8385QEF3C8V",4440,"MIT","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftype-declarations\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: type-declarations\ndescription: >-\n  Add, audit, or update @nubjs\u002Ftypes declarations for Nub runtime APIs. Use\n  whenever Nub adds or changes a user-visible global, built-in method, module\n  loader type, or TC39 proposal; when TypeScript or @types\u002Fnode gains an\n  overlapping declaration; and before every release to reconcile runtime\n  changes since the previous tag. Covers conflict-safe global augmentation,\n  compiler-version routing, fixture matrices, and package verification.\nmetadata:\n  internal: true\n---\n\n# Writing Nub type declarations\n\n`@nubjs\u002Ftypes` describes user-visible runtime behavior that the consumer's selected TypeScript libraries and `@types\u002Fnode` do not already describe. Runtime truth comes first: declarations follow shipped behavior; they never advertise an unimplemented convenience or preserve a stale shape for compatibility.\n\nThe package lives under `npm\u002Fnub-types\u002F`:\n\n- `common.d.ts` — declarations shared by every supported compiler.\n- `index.d.ts` — the current-compiler entry point and focused standard-library references.\n- `ts5.9\u002Findex.d.ts` — the legacy entry selected through `typesVersions`.\n- `test\u002Ffixtures\u002F` — compile-time compatibility and negative controls.\n\n## Start with an ownership audit\n\n1. Trace the runtime surface from its implementation and its row in `crates\u002Fnub-core\u002Fsrc\u002Fnode\u002Ffeature_matrix.rs`. Check `runtime\u002Fpolyfills.cjs`, `runtime\u002Fpreload-common.cjs`, loader modules, or other owning code rather than inferring a signature from a feature name.\n2. Check the exact TypeScript libraries supported by the fixture matrix and current `@types\u002Fnode`. ECMAScript built-ins normally belong to TypeScript's `lib.*.d.ts`; Node and web globals may belong to `@types\u002Fnode`.\n3. Consult primary declarations: TypeScript's `src\u002Flib` or installed `lib.*.d.ts`, DefinitelyTyped's `types\u002Fnode`, and Bun's types when looking for a proven step-aside pattern. A proposal README or specification establishes semantics, but the official TypeScript declaration is the compatibility target once one exists.\n4. Add a declaration only for the remaining gap. If a focused TypeScript library already owns the surface, reference that library instead of copying it.\n\n## Choose the conflict-safe pattern\n\n### Merge members into existing built-ins\n\nAugment the interface that owns an existing global:\n\n```ts\ninterface PromiseConstructor {\n  allKeyed\u003CT extends object>(promises: T): Promise\u003C{ -readonly [K in keyof T]: Awaited\u003CT[K]> }>;\n}\n```\n\nUse the same pattern for `IteratorObject`, `Math`, `Atomics`, `SymbolConstructor`, typed-array instances, and typed-array constructors. Never redeclare `var Promise`, `var Symbol`, or another built-in value just to add a method. Method members merge as overloads when a future standard library adds them.\n\nProperty members are stricter: their modifiers and type must match the official settled declaration exactly. `Symbol.metadata`, for example, must remain `readonly` and `unique symbol`.\n\n### Step aside from an optional global owner\n\nSome globals are absent from Node's normal type environment but collide when a consumer also selects `lib.dom`. Follow the conditional `globalThis` pattern used by Node and Bun types: detect the other library, adopt its constructor type, and reduce Nub's interface extension to `{}`. The current helpers are `__NubLibDomIsLoaded` and `__NubUseLibDomIfAvailable` in `common.d.ts`.\n\nDo not solve a global collision with `skipLibCheck`, a broad `any`, or a second incompatible `declare var`. The fixtures compile with `skipLibCheck: false` specifically to expose these conflicts.\n\n### Route declarations that cannot merge\n\nClasses, type aliases, and some namespace members cannot safely coexist with a later official library. Route those declarations by compiler version through `typesVersions`:\n\n- TypeScript 5.9 and earlier receive Nub's inlined Temporal declarations.\n- TypeScript 6 and later reference the official `esnext.temporal` library.\n- Both routes reference `common.d.ts` for declarations that merge safely.\n\nKeep version routing as narrow as possible. Add a new route only after reproducing a real collision, and set its boundary to the first compiler that ships the official declaration. Do not fork the whole package for one incompatible surface.\n\n### Preserve the global-script invariant\n\n`common.d.ts` must remain a global script. Never add a top-level `import`, `export`, or `export {}`: doing so makes wildcard declarations such as `declare module \"*.yaml\"` module-local and silently removes Nub globals from consumers.\n\nUse triple-slash `lib` and `path` references in versioned entry points. If a declaration needs an external type, prefer a qualified ambient reference that does not convert `common.d.ts` into a module.\n\n## Match runtime and inference precisely\n\n- Copy an official TypeScript signature byte-for-byte when Nub backfills an API already declared by a newer compiler.\n- For a proposal without official TypeScript declarations, derive the narrowest useful signature from the proposal and runtime implementation. Preserve keys, readonly removal, `Awaited`, generic buffer types, and overload behavior where they are observable to callers.\n- Document runtime facts the type system cannot express, such as null prototypes or enumerable-key filtering, without pretending the signature enforces them.\n- Keep vendored declarations tied to the bundled implementation version. When the Temporal polyfill changes, reconcile the TypeScript 5.9 fallback against that exact package version.\n- Do not duplicate surfaces already supplied by the selected TypeScript library or `@types\u002Fnode`.\n\n## Add the smallest comprehensive fixture coverage\n\nEvery changed public declaration needs a concrete use in `test\u002Ffixtures\u002Fpositive`; assert useful inferred types rather than merely checking that a property exists.\n\nWhen a declaration could later land upstream, also update `test\u002Ffixtures\u002Ffuture-stdlib\u002Fofficial-proposals.d.ts` with the expected official duplicate. That fixture must compile with both declaration sources active and `skipLibCheck: false`.\n\nPreserve the rest of the matrix:\n\n- TypeScript 5.9 exercises the legacy route.\n- TypeScript 6 exercises the first official Temporal route.\n- The current preview\u002Fcompiler exercises forward compatibility.\n- `stepaside-dom` and `stepaside-stub` verify global-owner coexistence.\n- `negative-export` must fail only because YAML resolution and `reportError` disappear after `common.d.ts` is converted into a module.\n\nRun the fixture package through Nub against a freshly packed tarball. Do not rely on the checked-in `file:..` dependency for release verification: a package-manager content store may reuse an older local-package snapshot, which can hide or invent routing failures. The tarball workflow also proves the artifact users receive:\n\n```bash\ntmp=$(mktemp -d)\ncp -R npm\u002Fnub-types \"$tmp\u002Fnub-types\"\ncd \"$tmp\u002Fnub-types\"\nnub pack --json\nTARBALL=$(find \"$PWD\" -maxdepth 1 -name '*.tgz' -print -quit)\npython3 - \"$PWD\u002Ftest\u002Fpackage.json\" \"$(basename \"$TARBALL\")\" \u003C\u003C'PY'\nimport json, pathlib, sys\npath = pathlib.Path(sys.argv[1])\ndata = json.loads(path.read_text())\ndata[\"devDependencies\"][\"@nubjs\u002Ftypes\"] = f\"file:..\u002F{sys.argv[2]}\"\npath.write_text(json.dumps(data, indent=2) + \"\\n\")\nPY\ncd test\nnub install\nnub run test\n```\n\nIf the repository's minimum-release-age policy rejects a deliberately current compiler pin, pass `--minimum-release-age=0` for this disposable verification install; do not weaken the repository policy.\n\n## Verify the published package, not just source files\n\nWhen adding an entry point or shared declaration, include it in `npm\u002Fnub-types\u002Fpackage.json`'s `files` list. Keep `types` and `typesVersions` aligned with the on-disk layout. Avoid a package `exports` map unless every supported module-resolution mode and `typesVersions` route has been proven: an exports condition can bypass compiler-version routing.\n\nFrom `npm\u002Fnub-types\u002F`, run `nub pack --dry-run --json` and inspect the file list. For every release, use the real-tarball fixture workflow above. A passing source-tree fixture does not prove the npm artifact contains the routed file or that compiler-version routing survives installation.\n\n## Mandatory release audit\n\nBefore every release, set `PREV=$(git describe --tags --abbrev=0)` and inspect `$PREV..HEAD` for user-visible runtime changes. At minimum, review:\n\n```bash\ngit diff --name-only \"$PREV\"..HEAD -- \\\n  runtime\u002F crates\u002Fnub-core\u002Fsrc\u002Fnode\u002Ffeature_matrix.rs npm\u002Fnub-types\u002F \\\n  wiki\u002Fruntime\u002F site\u002Fcontent\u002Fdocs\u002F\n```\n\nFor every added or changed API, record one conclusion while working:\n\n1. the selected TypeScript library or `@types\u002Fnode` already declares the exact shipped shape; or\n2. `@nubjs\u002Ftypes` has been updated, covered by the compiler\u002Fcollision fixtures, and verified in the packed artifact.\n\nThis audit is a release blocker and happens before `make version`. An empty declaration diff is valid only after every runtime change has an explicit owner.\n\n## Common failure modes\n\n- Assuming a Node runtime release means `@types\u002Fnode` owns an ECMAScript proposal.\n- Declaring an entire constructor when an interface member merge is sufficient.\n- Copying a future official class or type alias into `common.d.ts` instead of routing by compiler version.\n- Testing only one TypeScript version or enabling `skipLibCheck`.\n- Updating `index.d.ts` but omitting the new file from the package allowlist.\n- Adding a top-level import\u002Fexport to `common.d.ts` and losing wildcard data modules.\n- Trusting a source-tree test without inspecting and testing the packed tarball.\n","# Writing Nub type declarations\n\n`@nubjs\u002Ftypes` describes user-visible runtime behavior that the consumer's selected TypeScript libraries and `@types\u002Fnode` do not already describe. Runtime truth comes first: declarations follow shipped behavior; they never advertise an unimplemented convenience or preserve a stale shape for compatibility.\n\nThe package lives under `npm\u002Fnub-types\u002F`:\n\n- `common.d.ts` — declarations shared by every supported compiler.\n- `index.d.ts` — the current-compiler entry point and focused standard-library references.\n- `ts5.9\u002Findex.d.ts` — the legacy entry selected through `typesVersions`.\n- `test\u002Ffixtures\u002F` — compile-time compatibility and negative controls.\n\n## Start with an ownership audit\n\n1. Trace the runtime surface from its implementation and its row in `crates\u002Fnub-core\u002Fsrc\u002Fnode\u002Ffeature_matrix.rs`. Check `runtime\u002Fpolyfills.cjs`, `runtime\u002Fpreload-common.cjs`, loader modules, or other owning code rather than inferring a signature from a feature name.\n2. Check the exact TypeScript libraries supported by the fixture matrix and current `@types\u002Fnode`. ECMAScript built-ins normally belong to TypeScript's `lib.*.d.ts`; Node and web globals may belong to `@types\u002Fnode`.\n3. Consult primary declarations: TypeScript's `src\u002Flib` or installed `lib.*.d.ts`, DefinitelyTyped's `types\u002Fnode`, and Bun's types when looking for a proven step-aside pattern. A proposal README or specification establishes semantics, but the official TypeScript declaration is the compatibility target once one exists.\n4. Add a declaration only for the remaining gap. If a focused TypeScript library already owns the surface, reference that library instead of copying it.\n\n## Choose the conflict-safe pattern\n\n### Merge members into existing built-ins\n\nAugment the interface that owns an existing global:\n\n```ts\ninterface PromiseConstructor {\n  allKeyed\u003CT extends object>(promises: T): Promise\u003C{ -readonly [K in keyof T]: Awaited\u003CT[K]> }>;\n}\n```\n\nUse the same pattern for `IteratorObject`, `Math`, `Atomics`, `SymbolConstructor`, typed-array instances, and typed-array constructors. Never redeclare `var Promise`, `var Symbol`, or another built-in value just to add a method. Method members merge as overloads when a future standard library adds them.\n\nProperty members are stricter: their modifiers and type must match the official settled declaration exactly. `Symbol.metadata`, for example, must remain `readonly` and `unique symbol`.\n\n### Step aside from an optional global owner\n\nSome globals are absent from Node's normal type environment but collide when a consumer also selects `lib.dom`. Follow the conditional `globalThis` pattern used by Node and Bun types: detect the other library, adopt its constructor type, and reduce Nub's interface extension to `{}`. The current helpers are `__NubLibDomIsLoaded` and `__NubUseLibDomIfAvailable` in `common.d.ts`.\n\nDo not solve a global collision with `skipLibCheck`, a broad `any`, or a second incompatible `declare var`. The fixtures compile with `skipLibCheck: false` specifically to expose these conflicts.\n\n### Route declarations that cannot merge\n\nClasses, type aliases, and some namespace members cannot safely coexist with a later official library. Route those declarations by compiler version through `typesVersions`:\n\n- TypeScript 5.9 and earlier receive Nub's inlined Temporal declarations.\n- TypeScript 6 and later reference the official `esnext.temporal` library.\n- Both routes reference `common.d.ts` for declarations that merge safely.\n\nKeep version routing as narrow as possible. Add a new route only after reproducing a real collision, and set its boundary to the first compiler that ships the official declaration. Do not fork the whole package for one incompatible surface.\n\n### Preserve the global-script invariant\n\n`common.d.ts` must remain a global script. Never add a top-level `import`, `export`, or `export {}`: doing so makes wildcard declarations such as `declare module \"*.yaml\"` module-local and silently removes Nub globals from consumers.\n\nUse triple-slash `lib` and `path` references in versioned entry points. If a declaration needs an external type, prefer a qualified ambient reference that does not convert `common.d.ts` into a module.\n\n## Match runtime and inference precisely\n\n- Copy an official TypeScript signature byte-for-byte when Nub backfills an API already declared by a newer compiler.\n- For a proposal without official TypeScript declarations, derive the narrowest useful signature from the proposal and runtime implementation. Preserve keys, readonly removal, `Awaited`, generic buffer types, and overload behavior where they are observable to callers.\n- Document runtime facts the type system cannot express, such as null prototypes or enumerable-key filtering, without pretending the signature enforces them.\n- Keep vendored declarations tied to the bundled implementation version. When the Temporal polyfill changes, reconcile the TypeScript 5.9 fallback against that exact package version.\n- Do not duplicate surfaces already supplied by the selected TypeScript library or `@types\u002Fnode`.\n\n## Add the smallest comprehensive fixture coverage\n\nEvery changed public declaration needs a concrete use in `test\u002Ffixtures\u002Fpositive`; assert useful inferred types rather than merely checking that a property exists.\n\nWhen a declaration could later land upstream, also update `test\u002Ffixtures\u002Ffuture-stdlib\u002Fofficial-proposals.d.ts` with the expected official duplicate. That fixture must compile with both declaration sources active and `skipLibCheck: false`.\n\nPreserve the rest of the matrix:\n\n- TypeScript 5.9 exercises the legacy route.\n- TypeScript 6 exercises the first official Temporal route.\n- The current preview\u002Fcompiler exercises forward compatibility.\n- `stepaside-dom` and `stepaside-stub` verify global-owner coexistence.\n- `negative-export` must fail only because YAML resolution and `reportError` disappear after `common.d.ts` is converted into a module.\n\nRun the fixture package through Nub against a freshly packed tarball. Do not rely on the checked-in `file:..` dependency for release verification: a package-manager content store may reuse an older local-package snapshot, which can hide or invent routing failures. The tarball workflow also proves the artifact users receive:\n\n```bash\ntmp=$(mktemp -d)\ncp -R npm\u002Fnub-types \"$tmp\u002Fnub-types\"\ncd \"$tmp\u002Fnub-types\"\nnub pack --json\nTARBALL=$(find \"$PWD\" -maxdepth 1 -name '*.tgz' -print -quit)\npython3 - \"$PWD\u002Ftest\u002Fpackage.json\" \"$(basename \"$TARBALL\")\" \u003C\u003C'PY'\nimport json, pathlib, sys\npath = pathlib.Path(sys.argv[1])\ndata = json.loads(path.read_text())\ndata[\"devDependencies\"][\"@nubjs\u002Ftypes\"] = f\"file:..\u002F{sys.argv[2]}\"\npath.write_text(json.dumps(data, indent=2) + \"\\n\")\nPY\ncd test\nnub install\nnub run test\n```\n\nIf the repository's minimum-release-age policy rejects a deliberately current compiler pin, pass `--minimum-release-age=0` for this disposable verification install; do not weaken the repository policy.\n\n## Verify the published package, not just source files\n\nWhen adding an entry point or shared declaration, include it in `npm\u002Fnub-types\u002Fpackage.json`'s `files` list. Keep `types` and `typesVersions` aligned with the on-disk layout. Avoid a package `exports` map unless every supported module-resolution mode and `typesVersions` route has been proven: an exports condition can bypass compiler-version routing.\n\nFrom `npm\u002Fnub-types\u002F`, run `nub pack --dry-run --json` and inspect the file list. For every release, use the real-tarball fixture workflow above. A passing source-tree fixture does not prove the npm artifact contains the routed file or that compiler-version routing survives installation.\n\n## Mandatory release audit\n\nBefore every release, set `PREV=$(git describe --tags --abbrev=0)` and inspect `$PREV..HEAD` for user-visible runtime changes. At minimum, review:\n\n```bash\ngit diff --name-only \"$PREV\"..HEAD -- \\\n  runtime\u002F crates\u002Fnub-core\u002Fsrc\u002Fnode\u002Ffeature_matrix.rs npm\u002Fnub-types\u002F \\\n  wiki\u002Fruntime\u002F site\u002Fcontent\u002Fdocs\u002F\n```\n\nFor every added or changed API, record one conclusion while working:\n\n1. the selected TypeScript library or `@types\u002Fnode` already declares the exact shipped shape; or\n2. `@nubjs\u002Ftypes` has been updated, covered by the compiler\u002Fcollision fixtures, and verified in the packed artifact.\n\nThis audit is a release blocker and happens before `make version`. An empty declaration diff is valid only after every runtime change has an explicit owner.\n\n## Common failure modes\n\n- Assuming a Node runtime release means `@types\u002Fnode` owns an ECMAScript proposal.\n- Declaring an entire constructor when an interface member merge is sufficient.\n- Copying a future official class or type alias into `common.d.ts` instead of routing by compiler version.\n- Testing only one TypeScript version or enabling `skipLibCheck`.\n- Updating `index.d.ts` but omitting the new file from the package allowlist.\n- Adding a top-level import\u002Fexport to `common.d.ts` and losing wildcard data modules.\n- Trusting a source-tree test without inspecting and testing the packed tarball.\n",{"name":5,"metadata":24,"description":7},{"internal":25},true,"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Ftype-declarations",71,"https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub","https:\u002F\u002Fnubjs.com","https:\u002F\u002Fgithub.com\u002Fnubjs","The all-in-one Node.js toolkit","2026-11-14 14:11:35",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add nubjs\u002Fnub --skill type-declarations",{"tool":41,"command":42},"bunx","bunx skills add nubjs\u002Fnub --skill type-declarations",{"tool":44,"command":45},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill type-declarations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftype-declarations\u002FSKILL.md",[],[49,55,61,68,75,82],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M758BSH88RVXBG8TPCT427TY","nub","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fskills\u002Fnub\u002FSKILL.md",[],[],{"skillNo":56,"name":51,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M758BKPRHXS5MS27WG908PBG","This project uses nub, a single Rust CLI that runs on the project's installed Node and replaces the everyday Node toolchain. ALWAYS prefer nub over node, bun, npm, npx, pnpm, and yarn for: executing JS\u002FTS files, running package.json scripts, the npx-equivalent, installing dependencies, watch mode, and Node version management. Surfaces whenever you would otherwise reach for node\u002Fbun\u002Fnpm\u002Fnpx or a package manager.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fsite\u002Fpublic\u002Fskill.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M758BCR8A21H8P4TQ0YRHTC7","worktree","Create and manage isolated git worktrees for parallel build\u002Ftest\u002Flanding work on the nub repo. Invoke (via the Skill tool) whenever you need a fresh worktree to land a change, when you want to know what `.worktreeinclude` does or how to add an entry, or when cleaning up after a merge. Encodes the one-command setup (`nub scripts\u002Fnew-worktree.ts \u003Cslug>` or `node …`) that bakes in the proven recipe — worktree off origin\u002Fmain (vendor\u002Faube is plain in-tree files now, no submodule init), the shared CARGO_TARGET_DIR (`~\u002F.cache\u002Fnub\u002Fshared-target`) that all worktrees reuse, and applying `.worktreeinclude` — plus the eagerly-pull-the-shared-tree discipline and the safe cleanup path. Pairs with the `dev-loop` build skill.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworktree\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M758B9NZ1GQMD1A6B25NK0D9","windows-vm-test","Run ad-hoc Nub tests and debugging probes in the maintainer's existing local Windows 11 ARM64 QEMU\u002FHVF VM when its external disk and runbook are present. Use for interactive win32-arm64 or Windows-on-ARM x64-emulation checks; use ci-adhoc-test for true x64-native behavior or when the local VM is unavailable.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwindows-vm-test\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"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},"01M758B2JHMBB6YJTGYSJR65S4","visual-review","Verify UI\u002Flayout\u002Fstyling changes are correct by computing occlusion, clipping, and alignment from the browser's resolved paint order via the chrome-devtools MCP `evaluate_script` tool — instead of eyeballing a flat screenshot. Invoke BEFORE declaring any UI, site, or styling\u002Flayout change correct. Screenshots have no depth buffer, so z-index\u002Focclusion\u002Fclip bugs are exactly where \"just look at it\" fails; the `evaluate_script` routines below turn those fuzzy visual judgments into deterministic measurements — including optical center-of-mass, which measures the glyph ink's true visual center so differently-sized labels can be aligned by more than eye.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fvisual-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M758ARA9YKHET16KTPXNTZXR","soak","Manages the repo's supply-chain soak window (SOAK_DAYS) — checks and fixes the derived surfaces, bumps or disables the window, adds dated per-package exclusions, and bumps pinned external tools. Use when a task touches minimumReleaseAge, min-release-age, min-publish-age, external-tools.json, renovate.json, or taze cooldowns, or when investigating why a freshly published version won't install.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsoak\u002FSKILL.md",[],[]]