Conciseness

Mostly dense, proprietary-API knowledge Claude genuinely lacks (ErrorHandle truthiness, ResultSection interpolation, exhaustiveness requirements), but there is more than minor fat: the INSTANCE_SWAP-vs-SLOT distinction is restated in at least five places (Step 3, the property-mapping table, the SLOT section, the descendants table, and Rule 5), the Inline Quick Reference (~70 lines) duplicates the earlier property-mapping tables and references/api.md, the Complete Worked Example re-narrates all six steps verbatim, and two pitfalls share the number 7. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 4's 'minor instances'.

Actionability

Fully executable guidance throughout: exact MCP tool invocations with named parameters ("get_code_connect_suggestions with fileKey... nodeId... excludeMappingPrompt: true"), copy-paste-ready template code with WRONG/CORRECT contrasts, concrete URL-parsing rules with a worked example, and a complete end-to-end Button.figma.ts example covering the common case. Matches the anchor-5 'copy-paste ready code; specific examples cover the common cases'.

Workflow Clarity

A clear six-step sequence with explicit validation and feedback loops: Step 2 handles each error response verbatim ("No published components found in this selection" → inform and stop), Step 4 requires user confirmation before proceeding, and Step 6 is a read-back validation checklist (property coverage, typed code, no hardcoded children, interpolation wrapping). This matches anchor 5's 'explicit validation steps; feedback loops for error recovery; checklists'.

Progressive Disclosure

Good structure with real, verified, one-level-deep references — [api.md](references/api.md) carries the full API reference and [advanced-patterns.md](references/advanced-patterns.md) the advanced nesting patterns, both clearly signaled at point of need. It stops short of anchor 5 because reference-appropriate content is inlined: the full method-signature tables in the Inline Quick Reference overlap api.md, and the 520-line body keeps the complete worked example inline rather than splitting it out — fitting 'most content is appropriately placed; minor organization gaps'.

Specificity

"Creates and maintains Figma Code Connect template files that map Figma components to code snippets" names the domain plus several concrete actions (create, maintain, map components to code), matching the 'several specific actions; minor gaps in coverage' anchor. It falls short of anchor 5 because it lists only ~3 actions rather than the comprehensive multi-action coverage of the top example, while clearly exceeding anchor 3's '1-2 concrete actions'.

Completeness

It explicitly answers both questions: the "what" ("Creates and maintains Figma Code Connect template files that map Figma components to code snippets") and the "when" ("Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files") with concrete trigger phrases — a direct match for the anchor-5 example. It is not anchor 4 because the 'when' clause is fully explicit, not merely present.

Trigger Term Quality

The triggers "Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files" cover the feature name, two natural synonyms, and both file extensions — comprehensive coverage of natural terms including synonyms and extensions, matching the anchor-5 pattern ("PDF files, PDFs, forms, document extraction, .pdf").

Distinctiveness Conflict Risk

"Figma Code Connect template files", "Figma component mapping", and ".figma.ts or .figma.js files" define a clear niche with distinct, product-specific triggers and minimal overlap risk with any generic skill — matching the anchor-5 'clear niche with distinct triggers' example. It is well above anchor 4's 'minor overlap risk with closely related skills'.