Content
78%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 well-crafted conventions skill: high-signal project-specific rules, concrete inline code patterns, and exemplary progressive disclosure with a verified, accurately described reference bundle. The main weaknesses are mild — a few overloaded run-on bullets and the absence of any decision ordering or priority among the flat rule list.
Suggestions
Split the longest run-on rules (the read-methods bullet and the `satisfies`-generic bullets) into shorter statements or move the extended rationale into their linked reference files to tighten conciseness.
Add a brief prioritization note (e.g., which rules are hard constraints vs. defaults, or which to check first when editing an existing file) so the flat Core Rules list doubles as a lightweight workflow.
Convert abstract directives like "New named types must earn their place" into a one-line decision test or a do/don't example pair to raise actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific, non-inferable rules (per-package `.ts`/`.js` import extensions, ADR-0769, `#platform/*` splits, specific package names) and explains nothing Claude already knows. A handful of run-on bullets — notably the read-methods rule and the noisy-`satisfies` rules — carry nested clauses that could be trimmed, placing it just below the every-token-earns-its-place level. | 4 / 5 |
Actionability | Concrete, adaptable patterns appear throughout: `createMailbox({ db })`, `Base & Extra` vs `Omit<Base, 'k'> & { k: U }`, `ReturnType<typeof createThing>`, `export type CapturesHarness = Awaited<ReturnType<typeof openCaptures>>`, and `default: value satisfies never`. It stops short of fully copy-paste-ready coverage because several rules are abstract directives ("New named types must earn their place", "Treat local shape copies as boundary smells"). | 4 / 5 |
Workflow Clarity | As a conventions skill rather than a multi-step process, it has no validation checkpoints to include and no destructive/batch operations that would cap the score. Content is organized into clear sections (Core Rules, Go-to-Definition Awareness, Reference Map) with per-reference "read when" guidance, but the rules form a flat list with no ordering or priority guidance for when rules interact. | 4 / 5 |
Progressive Disclosure | The ~60-line body is a clean overview split into three well-labeled sections, with eight one-level-deep reference files that all exist and whose contents match their one-line descriptions in the Reference Map. Inline links to `references/project-conventions.md` and `references/factory-patterns.md` point to real files, and navigation is easy — a clear match for the top anchor. | 5 / 5 |
Total | 17 / 20 Passed |