The body is lean and assumes Claude's competence — it never explains what WebGPU, SSR, or blend modes are, and every line directs action ('Implement the exact trail as progressive enhancement', 'Install `shaders`...'), matching the lean-and-efficient anchor.

Guidance is concrete and executable: exact package subpaths ('shaders/react', 'shaders/vue'...), named files to copy from 'assets/react/', and a copy-paste bash verification command with argument positions, satisfying the fully-executable anchor.

An explicit 8-step Workflow is followed by a dedicated Validate section running lint/typecheck/build plus a verification script and a checklist of accessibility/static conditions, providing clear sequencing with explicit validation checkpoints.

The body is an overview that signals one-level-deep references to real bundle files — 'Read [references/implementation.md]', 'copy and adapt the files in assets/react/', and the verify script — all of which exist on disk, matching the clear-overview-with-well-signaled-references anchor.

Names multiple concrete capabilities — 'white twinkling halftone cursor trail driven by ChromaFlow, masked through a DotGrid, finished with chromatic ripples and film grain' plus 'static, touch, accessibility, SSR, and performance fallbacks' — matching the score-3 anchor listing several specific actions.

Explicitly answers both what (the described shader effect and its fallbacks) and when via an explicit 'Use when a user asks for...' clause, matching the score-3 anchor that requires both with explicit triggers.

The 'Use when' clause surfaces natural phrasings users would actually say — 'shader mouse effect', 'halftone cursor trail', 'interactive WebGPU hero/contact background', 'cursor-following shader layer' — with broad framework coverage, satisfying the good-coverage anchor.

The effect is tied to a very specific niche (Tidal Commons hero halftone cursor trail with named ChromaFlow/DotGrid nodes) with distinct triggers, making accidental firing for unrelated skills unlikely.