Method
Read the package. Do not pretend that is a test.
Source first. We record an original publisher, immutable commit or declared version, license, stated requirements, and last check. When the skill source is mutable, we say so; a plugin version is not a substitute for a skill-file pin.
A preview is a decision interface. A project-bound local preview can help a person choose tokens, copy, and element-level changes before implementation. It is not evidence that the live route matches, works at required widths, or supports keyboard use. Compare it with the real route after applying the decision packet.
Claims stay labelled. Author guidance, community reports, and pool verification are different evidence tiers.
Task before popularity. Concept-led build, visual direction, design-and-build state modeling, project-bound visual feedback, component refactor, motion, state capture, exploratory QA, captured flow audit, code review, and performance review are different jobs.
Make the state model part of fit. For a substantial product surface, record the user and screen job, project components and tokens, real content, relevant empty, error, busy, success, and recovery states, viewports, and input methods. A happy-path screenshot does not certify a design system, accessibility, or resilient behavior.
Capture the thing you claim to review. A browser check needs a runnable target, isolated session, named route, retained output, backend, viewport, and session context. Targeted QA also needs one interaction and expected rendered state. Exploratory QA needs a reachable target, replayable repro evidence, and review of each finding. A flow audit needs a known journey and accepted screenshots. A code-first review needs the relevant files.
Proof resources are part of fit. A browser capture or QA report is evidence to inspect, not a verdict on the design. A workflow you cannot run is not a shortcut; it is a mismatch.
System context stays yours. A borrowed skill cannot reliably infer the components, tokens, constraints, state model, and view states that define your product. Name them before asking a workflow to judge consistency.
What this catalogue does not claim
We did not install these skills, run a benchmark, audit their security posture, or verify results in any coding agent. Compatibility depends on the chosen agent, installer, source revision, framework, browser target, required tools, captured flow, and local changes—not a badge a directory can grant.
See the research log for source links and unanswered questions.