メニュー
Use when changing JS/TS package exports, startup/import cost, package size, public subpaths, dependency direction, optional peers, tree-shaking, or package-boundary tests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding ShapeShift Labs Evidence Kit to a JS/TS project, initializing the full tests/fuzzers/benchmarks/package-boundary/perf-wiki harness, or helping an AI agent establish maximum evidence coverage in another repository.
Use when creating, adapting, reviewing, or debugging JS/TS fuzzers, corpus fixtures, replay files, shrinkers, repro writers, or deterministic random test harnesses.
Use when mining external JS/TS libraries, runtimes, papers, benchmark suites, bug corpora, or production systems for ideas that should become local tests, fuzzers, benchmarks, or evidence notes.
Use when adapting ShapeShift Labs Evidence Kit to a specific JS/TS project by deriving target-owned source lists, correctness contracts, corpus cases, fuzz generators, benchmark fixtures, source-pass plans, or evidence acceptance criteria from that project's own code, docs, tests, issues, or fetched sources.
Use for JS/TS performance-sensitive changes, benchmark additions, benchmark regressions, benchmark result JSON, or any claim that code is faster, smaller, cheaper, or not slower.
Use when creating or updating JS/TS performance evidence notes, iteration logs, research notes, generated docs/perf indexes, or searchable benchmark/result summaries.
| name | package-boundary-guardian |
| description | Use when changing JS/TS package exports, startup/import cost, package size, public subpaths, dependency direction, optional peers, tree-shaking, or package-boundary tests. |
Treat package shape as a tested contract from the beginning of a project.
Identify public entry points from package.json exports.
Identify forbidden dependency directions for each entry point.
Keep checks for:
npm pack --dry-run files and unpacked bytes,If ShapeShift Labs Evidence Kit is installed, run:
npx evidence-kit scope
npm run bench:startup:check
npm run bench:package:gates
npm run docs:perf:search -- package-boundary startup
Use the scope result to decide whether startup or package benchmarks need refresh.