The guidance is accurate and domain-specific (not basic concepts Claude already knows), but the motivational prose is padded with rhetorical negation-lists ('not test your hooks better, not be more careful with deps, not add a renderHook suite'; 'discipline fails at the third layer of composition; prevention does not') that could be tightened. It is above level 1 because it does not explain generic concepts, but below level 3 because not every token earns its place.

Concrete, specific rules with named APIs (useSyncExternalStore, useContext), a two-situation decision test, fine/never example pairs, and copy-paste-ready data-testid values (sidebar-right-inspect-node-properties). Per the code-vs-instruction scoring note, absence of code blocks is not penalized when the guidance is this actionable, placing it above the pseudocode/incomplete level 2.

The decision procedure is explicit and sequenced: 'A hook is acceptable in exactly two situations: 1... 2... If a hook fails both — extract the logic out... and reduce the hook to a three-line call site.' No destructive/batch/XML operations are involved, so the missing-validation cap does not apply, keeping it above level 2.

Sections are well-organized, the load-bearing rule is inline, and the full reference is deferred exactly one level to docs/contributing/react.md with explicit signaling ('The rule above is the load-bearing part'), plus a sibling-skill cross-link. References are clearly signaled and one level deep, so it is above the level 2 'references present but not clearly signaled' anchor.

Names multiple concrete rules — 'load-bearing logic lives in classes and namespaces, hooks only as thin edge wires' and 'one per significant component, not scattered' — rather than vague actions. It is comprehensive across both the hooks and data-testid conventions, so it is above the 'names domain and some actions' level 2.

It explicitly states both what it governs (React code shape: hooks barred, logic in classes/namespaces, data-testid discipline) and when to use it ('Use when authoring React in ...'). The explicit 'Use when' clause places it above level 2, where 'when' is only implied.

'Use when authoring React in ...' supplies the natural keyword 'React', but the trigger surface is dominated by file paths (editor/grida-canvas-react/, editor/components/) rather than the natural-language variations a user would say. It is above level 1 because 'React' is a genuine natural term, but below level 3 which expects good coverage of natural terms.

Scoped to React-in-Grida-editor conventions with directory-specific triggers, giving it a clear niche unlikely to fire for unrelated skills. It is more distinct than the level 2 'somewhat specific but could overlap' anchor.