Conciseness

Every line carries library-specific knowledge Claude would not have (codemod behavior, the `await super.getRequestInit` spread gotcha, `body: undefined` semantics, `.data` interceptor caveat) with zero padding or explanation of known concepts. Fits the 5 anchor ('every token earns its place'); the 4 anchor's 'minor instances of over-explanation' does not apply to anything present.

Actionability

Copy-paste ready throughout: `npx --no data-client-skills`, `npx @data-client/codemods axios-to-rest src/` with a version fallback command, complete executable `BaseEndpoint` and `resource()` TypeScript snippets, and concrete fixer commands (`prettier --write`, `eslint --fix`, `biome check --write`). Fits the 5 anchor ('copy-paste ready; specific examples cover the common cases').

Workflow Clarity

Three clearly sequenced steps with a per-library decision table, and the axios sub-workflow includes explicit checkpoints: verify `git status` is clean before the codemod, resolve each `TODO(data-client)` marker, run the type checker and tests, and only uninstall axios when no import or TODO remains. Error recovery is also covered (fallback command when `data-client-skills` is missing, `try/catch` pattern for status handling). Fits the 5 anchor; the 4 anchor's 'minor validation gaps' is not the case here.

Progressive Disclosure

The body is a lean overview and all detail lives one level deep in references/, every linked file (RestEndpoint, resource, per-library migrations, hookifyResource, auth, django) exists, and cited anchors (`#content`, `#getRequestInit`, `#server-error-messages`) resolve to real headings. The `<name>.vue.md` convention is explicitly documented. Fits the 5 anchor ('well-signaled one-level-deep references; easy navigation').

Specificity

Lists several concrete actions — 'Set up and migrate to @data-client/rest', 'Detects existing HTTP patterns (axios, fetch, ky, superagent, got)', 'Creates custom RestEndpoint base class' — with only 'common behaviors' left generic. Not 5 because 'common behaviors' and the migration targets are not fully enumerated as concrete outcomes; not 3 because it clearly names the domain plus three or more specific actions.

Completeness

Explicitly answers 'what' (setup, detection, migration, base-class creation) and 'when' ('Use when adopting @data-client/rest in a new or existing project'). Not 5 because the 'when' clause covers only adoption and could cite concrete trigger phrases like migrating from axios; not 3 because a clear 'Use when...' clause is present.

Trigger Term Quality

Strong natural terms users would actually say: 'REST APIs', 'axios', 'fetch', 'ky', 'superagent', 'got', 'migrate'. Not 5 because common variations like 'HTTP client', 'API calls', or 'data fetching' are missing; not 3 because library names plus 'REST APIs' go well beyond some relevant keywords.

Distinctiveness Conflict Risk

Names a specific package (@data-client/rest) and specific libraries, carving a clear niche with minimal overlap risk against generic HTTP or migration skills. Fits the 5 anchor ('clear niche with distinct triggers'); the 4 anchor's 'minor overlap risk' would understate how targeted the named package and library list are.