The body is dense and assumes Claude's competence — it never explains basic concepts (MCP, codegen, ESM) and every section earns its place with concrete JSON/code; only minimal meta-prose in the intro keeps it from padding.

Provides fully executable commands ('bun scripts/capture-tools.ts', 'npx vitest run'), copy-paste TypeScript and JSON examples, and concrete file paths, matching the 'fully executable, copy-paste ready' anchor.

The Traffic Light (Red→Green→Yellow) flow and the 'Supporting a New Tool' / 'Adding a New Side-Effect Method' pipelines are explicitly sequenced with validation checkpoints ('validate-generated.ts', 'npx tsc'), matching the clear-sequence-with-validation anchor.

Sections are well-organized with clear headers, but everything lives inline in one ~340-line file with no bundle references; the domain-map IR and side-effect membrane detail are candidates for separate reference files, matching the 'content that should be separate is inline' anchor.

Lists multiple concrete capability areas — 'generation pipeline, dual modality (agent vs SDK), error handling, and Traffic Light (Red-Green-Yellow) implementation workflow' — matching the 'lists multiple specific concrete actions' anchor.

Explicitly answers both what ('Develop the Stitch SDK. Covers...') and when ('Use when adding features, fixing bugs, or understanding the architecture'), matching the clear-both-with-explicit-triggers anchor; not a 2 because the 'Use when' trigger clause is present.

'Stitch SDK' is a specific natural term, but the when-triggers ('adding features, fixing bugs, or understanding the architecture') are generic dev activities missing common variations a user would say, so it sits at 'some relevant keywords but missing common variations'.

Anchored to the distinct 'Stitch SDK' niche with triggers unlikely to fire for unrelated skills; not a 2 because the domain is clearly scoped rather than merely 'somewhat specific'.