Pre-publish safety reviewer for @dunx/ packages. Run before committing to main to catch issues that would result in a bad npm publish. Checks exports maps, package.json fields, accidentally exposed internals, and dist output integrity.
Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%. Use after adding a package, when coverage numbers look implausible, or when the GitHub Pages coverage site is stale or broken.
Revise one documentation file so it states facts instead of performing insight, and get it under the budgets in scripts/no-slop.test.ts. Use when writing a new guide or README, when a reader reports the docs read like AI output, or when bun test scripts/no-slop.test.ts fails.
Add a workspace to the dunx monorepo - a published package under packages/, a published CLI under tools/, a private workspace under internal/, or an example under examples/ - with correct manifest fields, tsconfig, exports-driven build entrypoints, README, and coverage badge. Use when creating @dunx/http…
Version and publish @dunx/ packages to npm. Use when cutting a release, when a publish failed or a package is missing from npm, when a package needs its first npm version, or when touching scripts/version.ts, the pinned npm version, or the publish job in ci.yml.
Resolve an open technical question by measuring it on real Bun instead of assuming, then record the verified result in docs/architecture/constraints.md. Use for the "Spikes to resolve" items, before committing to any API shape that depends on runtime or tsc behaviour, and whenever a design argument turns on "does…
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in docs/ROADMAP.md. Use before /compact or /clear, at the end of a task block, when the context window crosses 50%, or when…
Instructions for petarzarkov/dunx, covering dunx - claude code instructions, rule 1 - native implementations only, never reimplement what bun already does, never invent what a mature library already solves and reuse the @arkv workspace - and extend it upstream.