Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, example-driven reference that respects the context window and provides near-executable guidance for every itBundled feature area. The main gaps are minor: pseudo-syntax in option listings, placeholder file content in one example, and an implicit rather than explicit test-run verification step.
Suggestions
Make the option blocks executable by using real single values (e.g. format: "esm") with a comment listing valid alternatives, so examples can be pasted directly into a test.
Replace the `...` placeholder in the edgecase/InvalidLoader example with real file content so it runs as written, and note that expect/toMatchSnapshot come from bun:test alongside the itBundled/dedent import.
Add a short explicit verification step (e.g. 'run bun bd test <file> and confirm the new test passes before committing') to close the workflow loop when adding a test.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Zero padding and no explanation of concepts Claude already knows — every section is terse code or a bare fact ('Test ID format: `category/TestName`', run commands, env-var filters). Every token earns its place. | 5 / 5 |
Actionability | Nearly all examples are copy-paste-ready (basic usage, DCE markers, capture, run commands), but the options blocks use non-executable union pseudo-syntax ("format": "esm" | "cjs"), one example uses `...` as file content, and `expect`/`toMatchSnapshot` appear in onAfterBundle without import context — minor gaps that keep it below fully-executable. | 4 / 5 |
Workflow Clarity | The write-test → run ('bun bd test') → filter/debug (BUN_BUNDLER_TEST_FILTER, BUN_BUNDLER_TEST_DEBUG) loop is clear with section-level sequencing, but there is no explicit 'verify the test passes' checkpoint and the sequence is implicit across sections rather than a numbered workflow. Not a destructive/batch skill, so no cap applies. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the ~220-line body is well-sectioned with clear headers and a logical progression from basic usage to edge cases — good structure with everything appropriately inline at this size. Not 5 because nothing is split out or referenced, though at this compact size separate files are arguably unnecessary. | 4 / 5 |
Total | 17 / 20 Passed |