[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75858HHD516HVZ0708PE6W0":3,"skill-same:01M75858HHD516HVZ0708PE6W0":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"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":28,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M75858HHD516HVZ0708PE6W0","catalog-probe",null,"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\u002Fcatalog-probe\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: catalog-probe\ndescription: Run the build-jail catalog probe — measure the minimum OS capability grant a package's lifecycle scripts need, sweep a worklist of packages, and collate the results into the catalog. Invoke (via the Skill tool) whenever you are about to run, restart, extend, or debug a grant sweep under tests\u002Fbuild-jail-search\u002F, whenever a probe reports HARNESS-ERROR \u002F HARNESS-CRASH \u002F BROKEN-EVEN-WITH-EVERYTHING, whenever you change the catalog SHAPE (the Rust parser, the collator, or the synthesized cell catalogs must all move together), or whenever you are about to draw a conclusion from sweep results. Carries the failure modes that have each already cost a full sweep: a binary rebuilt mid-run without the override feature, a pre-flight check that validated an artifact adjacent to the question, editing the harness while a batch runs, and a 54%-silent-failure sweep whose survivors were reported as the corpus.\n---\n\n# Running the build-jail catalog probe\n\nThe probe measures the **minimum capability grant** a package's lifecycle scripts need, by walking a\n54-state capability space in ascending cost order and taking the first state that reproduces an\nunjailed control. Its output is the build-jail catalog.\n\nEverything here is a failure that has already happened. None of it is hypothetical.\n\n## Before you run anything\n\n**1. Build with the override feature, or nothing works.**\n\n```sh\nscripts\u002Frust-build.sh build -p nub-cli --profile fast \\\n  --features nub-cli\u002Fbuild-jail-catalog-override\n```\n\n**Any cargo command on a profile rewrites that profile's binary with ITS features.** A\n`cargo test --profile fast` in another shell silently strips the override and every subsequent\npackage records a control failure. `run-batch.sh` snapshots the binary to defend against this, but a\nbare `nub` invocation outside the batch still uses the live one.\n\n**2. Never edit the harness while a batch is running.** Each package is a fresh\n`node search.mjs` invocation, so an edit mid-sweep changes the harness under the remaining packages.\nThis has produced a sweep where the first half and the second half were measured by different code —\nand, in the worst case, 54 of 100 packages crashed because the file changed beneath them.\n\n**3. Run one cheap package first as an instrument check.**\n\n```sh\n.\u002Frun-batch.sh \u003Cnub> --force is-odd@3.0.1     # expect verdict=MINIMUM, state=(nothing), 2 cells\n```\n\nIf that is not clean, nothing after it means anything.\n\n## Running a sweep\n\n```sh\n.\u002Frun-batch.sh \u003Cnub> --file worklist.txt          # a worklist, one pkg@version per line\n.\u002Frun-batch.sh \u003Cnub> --force \u003Cpkg>@\u003Cversion>      # one package, --force re-measures\n```\n\nLong sweeps go in a **background shell** (`run_in_background: true`), never a foreground call and\nnever `nohup`\u002F`setsid` — a detached run cannot be tracked and never wakes you.\n\n## Reading the results — coverage first, always\n\n```sh\nnode watch-sweep.mjs results\u002Fruns \u003Csince-ms> worklist.txt\n```\n\n**Pass the worklist.** Without it you get a summary of what succeeded and no idea what did not run.\nThe single most expensive mistake made with this tool was reporting the survivors of a sweep as its\nresult: 54 of 100 packages produced no record, the batch discarded their stderr, and the remaining\n46 looked like a finished corpus. **The failures are not randomly distributed** — heavy native\nbuilds fail most, and those are exactly the packages most likely to need a grant, so the surviving\nsample is biased toward \"needs nothing.\"\n\nRules for reading a sweep:\n\n- **`attempted` \u002F `recorded` \u002F `FAILED` is the headline**, printed at the end of every batch. If\n  `FAILED` is not zero, you do not have a corpus.\n- **A run of identical failures indicts the HARNESS, not the packages.** Check the FIRST one and\n  fix that; the other ninety-nine are the same fault repeated.\n- **Read the first error in a log, never the last.** A node stack trace ends with the version\n  banner, and an install log ends with a summary — the cause is usually ~40 lines earlier. Five\n  successive wrong diagnoses of one package all came from reading the tail.\n\n## The instrument has no test — the failure with no symptom\n\n**A change to the fixture or to `baseline.json` is a change to the measuring instrument.** Its\nfailure mode is not an error; it is that every package measures as needing NOTHING. Every verdict\n`MINIMUM`, coverage 100%, nothing fails. Three times in one session:\n\n- A hand-written `package-lock.json` with an empty `packages` map — nub believed the project had no\n  dependencies. Puppeteer's control fell from **9,629 installed files to 32**.\n- A baseline entry using `$home\u002F...` — the wrong grammar (see sentinels below), so the jail failed\n  to **compile** and no lifecycle script spawned. Surfaced as `failed to spawn`, which reads as a\n  nub defect.\n- Worst: a measurement taken *during* the second window was written up as a finding — \"this\n  package's grant dissolved\" — when the jail was simply not running.\n\nAll three were caught by **disbelieving the number**, never by a check. Eight packages needing\nnothing, including ones that cannot work without downloading a binary, is not a measurement.\n\n**The pre-flight now runs a FIXTURE CANARY**: `puppeteer@25.4.0` must install >5000 files and be\nmaterialized, or the batch refuses. It asserts the control's SHAPE, not a verdict — a package that\nlegitimately needs nothing looks identical either way, so `is-odd` cannot catch this.\n`NUB_PROBE_SKIP_CANARY=1` disables it when deliberately testing the fixture.\n\n**Never report a measurement taken while the harness was known-broken. Re-run it first.**\n\n## Three `$` vocabularies, and they are not interchangeable\n\n| Namespace | Valid names | Used by |\n|---|---|---|\n| Compiler fs sentinels | `$cache`, `$tmp` (closed set), plus `~\u002F` | baseline paths, catalog fs rules |\n| Harness path tokens | `$proj\u002F`, `$store\u002F`, `$home\u002F` | recorded paths, `writePaths` entries |\n| Network host sets | `$\u003Cname>` on the net axis | net rules only |\n\n`$home` is meaningful in the second and **invalid** in the first. The compiler rejects an unknown\nsentinel by name and lists the valid ones — that message is what makes this a one-step diagnosis.\n\n## Verdicts\n\n| Verdict | Means | Do |\n|---|---|---|\n| `MINIMUM` | Measured. `state` is the minimal grant. | Nothing. |\n| `HARNESS-CRASH` \u002F `HARNESS-TIMEOUT` | The probe itself failed. | Read `harness-stderr.log` beside the record. Never a package fact. |\n| `HARNESS-ERROR` | The catalog override did not engage in the control. | Wrong binary, **or** the harness emits a catalog shape the parser rejects. |\n| `BROKEN-IN-ENVIRONMENT` | Fails under npm too, same signature. | Grant nothing. Check `needsInvestigation`. |\n| `BROKEN-EVEN-WITH-EVERYTHING` | Fails jailed at the widest grant, but npm succeeds. | A nub defect — the most valuable output. Never a grant gap. |\n\n## Changing the catalog shape — five places move together\n\nWritten in one place, read in four. Missing one fails as something else entirely: a shape change\nthat reached the parser but not the harness produced a hundred-package sweep in which every package\nreported that the override had not engaged, which reads as a broken binary.\n\n1. `crates\u002Fnub-sandbox\u002Fsrc\u002Fcatalog_v2.rs` — types, parse, validation, resolution\n2. `crates\u002Fnub-sandbox\u002Fsrc\u002Fcatalog_override.rs` — grant count and lookup\n3. `tests\u002Fbuild-jail-search\u002Fcollate.mjs` — writes the catalog\n4. `catalogFor` in `tests\u002Fbuild-jail-search\u002Fsearch.mjs` — **synthesizes a catalog per cell, every run**\n5. `tests\u002Fbuild-jail-search\u002Foverrides\u002F` — hand-written entries\n\nPlus the `--selftest` assertions, which read the synthesized shape and will silently pass on the\nwrong one if not updated.\n\n**The pre-flight probe catalog must come from `catalogFor`, never a literal.** It is emitted by\n`search.mjs --emit-sample-catalog` for exactly this reason. A hand-written probe drifts from what\nthe harness emits, and a catalog with an empty package map is the worst possible probe because it\nparses under every shape there has ever been.\n\n## The oracle, and why it is shaped this way\n\n- **Judge the ARTIFACT, not the exit code.** A cell passes only if it reproduces the control on exit\n  code *and* on the digest of the sorted path list. A hook installer that cannot see the project\n  writes zero of seventeen hooks and exits 0.\n- **The control runs TWICE, combined by UNION.** Never intersection — that compares on fewer paths,\n  so a cell that failed to write an unstable path still passes and the recorded minimum is too\n  narrow, which is the exact failure the jail exists to avoid.\n- **Every other package is held at full grant**, so the package under test is the only variable.\n- **When the oracle says something impossible, suspect the oracle.** \"Failed all 55 cells,\n  nondeterministic\" was 3 varying paths out of 2,734 — all one timestamped log filename.\n\n## Ground truth\n\n- **The tarball manifest, not the packument.** They disagree: `fsevents@2.3.3`'s packument declares\n  `install: node-gyp rebuild` and its published tarball does not. nub runs the tarball.\n- **Prefer a global `baseline`\u002F`env` entry over a per-package grant or a harness filter.** A filter\n  hides one tool's write after the fact and must be re-derived per tool. Two entries already earn\n  their place: `PYTHONDONTWRITEBYTECODE=1` and `npm_config_logs_max=0`, each of which stops a write\n  happening at all rather than filtering it afterwards.\n- **Over-granting is the safe direction.** The failure to avoid is packages breaking.\n\n## Related\n\n- `wiki\u002Fdesign\u002Fbuild-jail.md` — the canonical design: capability model, bands, placement\n- `.frizz\u002Fbuild-jail-catalog-schema.md` — the catalog schema spec\n- `rust-build` — cargo mechanics and the profile\u002Ffeature trap\n","# Running the build-jail catalog probe\n\nThe probe measures the **minimum capability grant** a package's lifecycle scripts need, by walking a\n54-state capability space in ascending cost order and taking the first state that reproduces an\nunjailed control. Its output is the build-jail catalog.\n\nEverything here is a failure that has already happened. None of it is hypothetical.\n\n## Before you run anything\n\n**1. Build with the override feature, or nothing works.**\n\n```sh\nscripts\u002Frust-build.sh build -p nub-cli --profile fast \\\n  --features nub-cli\u002Fbuild-jail-catalog-override\n```\n\n**Any cargo command on a profile rewrites that profile's binary with ITS features.** A\n`cargo test --profile fast` in another shell silently strips the override and every subsequent\npackage records a control failure. `run-batch.sh` snapshots the binary to defend against this, but a\nbare `nub` invocation outside the batch still uses the live one.\n\n**2. Never edit the harness while a batch is running.** Each package is a fresh\n`node search.mjs` invocation, so an edit mid-sweep changes the harness under the remaining packages.\nThis has produced a sweep where the first half and the second half were measured by different code —\nand, in the worst case, 54 of 100 packages crashed because the file changed beneath them.\n\n**3. Run one cheap package first as an instrument check.**\n\n```sh\n.\u002Frun-batch.sh \u003Cnub> --force is-odd@3.0.1     # expect verdict=MINIMUM, state=(nothing), 2 cells\n```\n\nIf that is not clean, nothing after it means anything.\n\n## Running a sweep\n\n```sh\n.\u002Frun-batch.sh \u003Cnub> --file worklist.txt          # a worklist, one pkg@version per line\n.\u002Frun-batch.sh \u003Cnub> --force \u003Cpkg>@\u003Cversion>      # one package, --force re-measures\n```\n\nLong sweeps go in a **background shell** (`run_in_background: true`), never a foreground call and\nnever `nohup`\u002F`setsid` — a detached run cannot be tracked and never wakes you.\n\n## Reading the results — coverage first, always\n\n```sh\nnode watch-sweep.mjs results\u002Fruns \u003Csince-ms> worklist.txt\n```\n\n**Pass the worklist.** Without it you get a summary of what succeeded and no idea what did not run.\nThe single most expensive mistake made with this tool was reporting the survivors of a sweep as its\nresult: 54 of 100 packages produced no record, the batch discarded their stderr, and the remaining\n46 looked like a finished corpus. **The failures are not randomly distributed** — heavy native\nbuilds fail most, and those are exactly the packages most likely to need a grant, so the surviving\nsample is biased toward \"needs nothing.\"\n\nRules for reading a sweep:\n\n- **`attempted` \u002F `recorded` \u002F `FAILED` is the headline**, printed at the end of every batch. If\n  `FAILED` is not zero, you do not have a corpus.\n- **A run of identical failures indicts the HARNESS, not the packages.** Check the FIRST one and\n  fix that; the other ninety-nine are the same fault repeated.\n- **Read the first error in a log, never the last.** A node stack trace ends with the version\n  banner, and an install log ends with a summary — the cause is usually ~40 lines earlier. Five\n  successive wrong diagnoses of one package all came from reading the tail.\n\n## The instrument has no test — the failure with no symptom\n\n**A change to the fixture or to `baseline.json` is a change to the measuring instrument.** Its\nfailure mode is not an error; it is that every package measures as needing NOTHING. Every verdict\n`MINIMUM`, coverage 100%, nothing fails. Three times in one session:\n\n- A hand-written `package-lock.json` with an empty `packages` map — nub believed the project had no\n  dependencies. Puppeteer's control fell from **9,629 installed files to 32**.\n- A baseline entry using `$home\u002F...` — the wrong grammar (see sentinels below), so the jail failed\n  to **compile** and no lifecycle script spawned. Surfaced as `failed to spawn`, which reads as a\n  nub defect.\n- Worst: a measurement taken *during* the second window was written up as a finding — \"this\n  package's grant dissolved\" — when the jail was simply not running.\n\nAll three were caught by **disbelieving the number**, never by a check. Eight packages needing\nnothing, including ones that cannot work without downloading a binary, is not a measurement.\n\n**The pre-flight now runs a FIXTURE CANARY**: `puppeteer@25.4.0` must install >5000 files and be\nmaterialized, or the batch refuses. It asserts the control's SHAPE, not a verdict — a package that\nlegitimately needs nothing looks identical either way, so `is-odd` cannot catch this.\n`NUB_PROBE_SKIP_CANARY=1` disables it when deliberately testing the fixture.\n\n**Never report a measurement taken while the harness was known-broken. Re-run it first.**\n\n## Three `$` vocabularies, and they are not interchangeable\n\n| Namespace | Valid names | Used by |\n|---|---|---|\n| Compiler fs sentinels | `$cache`, `$tmp` (closed set), plus `~\u002F` | baseline paths, catalog fs rules |\n| Harness path tokens | `$proj\u002F`, `$store\u002F`, `$home\u002F` | recorded paths, `writePaths` entries |\n| Network host sets | `$\u003Cname>` on the net axis | net rules only |\n\n`$home` is meaningful in the second and **invalid** in the first. The compiler rejects an unknown\nsentinel by name and lists the valid ones — that message is what makes this a one-step diagnosis.\n\n## Verdicts\n\n| Verdict | Means | Do |\n|---|---|---|\n| `MINIMUM` | Measured. `state` is the minimal grant. | Nothing. |\n| `HARNESS-CRASH` \u002F `HARNESS-TIMEOUT` | The probe itself failed. | Read `harness-stderr.log` beside the record. Never a package fact. |\n| `HARNESS-ERROR` | The catalog override did not engage in the control. | Wrong binary, **or** the harness emits a catalog shape the parser rejects. |\n| `BROKEN-IN-ENVIRONMENT` | Fails under npm too, same signature. | Grant nothing. Check `needsInvestigation`. |\n| `BROKEN-EVEN-WITH-EVERYTHING` | Fails jailed at the widest grant, but npm succeeds. | A nub defect — the most valuable output. Never a grant gap. |\n\n## Changing the catalog shape — five places move together\n\nWritten in one place, read in four. Missing one fails as something else entirely: a shape change\nthat reached the parser but not the harness produced a hundred-package sweep in which every package\nreported that the override had not engaged, which reads as a broken binary.\n\n1. `crates\u002Fnub-sandbox\u002Fsrc\u002Fcatalog_v2.rs` — types, parse, validation, resolution\n2. `crates\u002Fnub-sandbox\u002Fsrc\u002Fcatalog_override.rs` — grant count and lookup\n3. `tests\u002Fbuild-jail-search\u002Fcollate.mjs` — writes the catalog\n4. `catalogFor` in `tests\u002Fbuild-jail-search\u002Fsearch.mjs` — **synthesizes a catalog per cell, every run**\n5. `tests\u002Fbuild-jail-search\u002Foverrides\u002F` — hand-written entries\n\nPlus the `--selftest` assertions, which read the synthesized shape and will silently pass on the\nwrong one if not updated.\n\n**The pre-flight probe catalog must come from `catalogFor`, never a literal.** It is emitted by\n`search.mjs --emit-sample-catalog` for exactly this reason. A hand-written probe drifts from what\nthe harness emits, and a catalog with an empty package map is the worst possible probe because it\nparses under every shape there has ever been.\n\n## The oracle, and why it is shaped this way\n\n- **Judge the ARTIFACT, not the exit code.** A cell passes only if it reproduces the control on exit\n  code *and* on the digest of the sorted path list. A hook installer that cannot see the project\n  writes zero of seventeen hooks and exits 0.\n- **The control runs TWICE, combined by UNION.** Never intersection — that compares on fewer paths,\n  so a cell that failed to write an unstable path still passes and the recorded minimum is too\n  narrow, which is the exact failure the jail exists to avoid.\n- **Every other package is held at full grant**, so the package under test is the only variable.\n- **When the oracle says something impossible, suspect the oracle.** \"Failed all 55 cells,\n  nondeterministic\" was 3 varying paths out of 2,734 — all one timestamped log filename.\n\n## Ground truth\n\n- **The tarball manifest, not the packument.** They disagree: `fsevents@2.3.3`'s packument declares\n  `install: node-gyp rebuild` and its published tarball does not. nub runs the tarball.\n- **Prefer a global `baseline`\u002F`env` entry over a per-package grant or a harness filter.** A filter\n  hides one tool's write after the fact and must be re-derived per tool. Two entries already earn\n  their place: `PYTHONDONTWRITEBYTECODE=1` and `npm_config_logs_max=0`, each of which stops a write\n  happening at all rather than filtering it afterwards.\n- **Over-granting is the safe direction.** The failure to avoid is packages breaking.\n\n## Related\n\n- `wiki\u002Fdesign\u002Fbuild-jail.md` — the canonical design: capability model, bands, placement\n- `.frizz\u002Fbuild-jail-catalog-schema.md` — the catalog schema spec\n- `rust-build` — cargo mechanics and the profile\u002Ffeature trap\n",{},"main","9b734566fd36ceed8379f67a92291bc68af60801",".claude\u002Fskills\u002Fcatalog-probe",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":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add nubjs\u002Fnub --skill catalog-probe",{"tool":38,"command":39},"bunx","bunx skills add nubjs\u002Fnub --skill catalog-probe",{"tool":41,"command":42},"pnpm","pnpm dlx skills add nubjs\u002Fnub --skill catalog-probe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcatalog-probe\u002FSKILL.md",true,[],[47,53,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M758BSH88RVXBG8TPCT427TY","nub","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002Fskills\u002Fnub\u002FSKILL.md",[],[],{"skillNo":54,"name":49,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M758AWPM7CE440NBAYJHD44J","type-declarations","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.","https:\u002F\u002Fgithub.com\u002Fnubjs\u002Fnub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ftype-declarations\u002FSKILL.md",[],[]]