design-referenceslisted

# Design References Use the bundled catalog to answer a design question with inspected examples. The unit of discovery is a surface, not a domain: a product's landing page and dashboard can be separate sources with independent access and verification. ## 1. Frame the question Establish the component, design decision, audience, required interactions, and constraints from the request and available project evidence. Ask only for missing information that changes source selection. Finish with a short brief that names what a useful reference must demonstrate, then choose the evidence track: | Track | Required evidence | Eligible references | | --- | --- | --- | | Visual inspiration | Rendered component or screen inspected at the exact URL | Finished product interfaces, clearly labeled styled templates, or user-approved styled component examples | | Behavioral research | Relevant state transition tested or explicitly described by an authoritative source | Live examples or product documentation, with documented behavior distinguished from tested behavior | For a mixed brief, assign each required claim to its track; a reference may satisfy one track without satisfying the other. Approval never substitutes for evidence. Motion timing and triggers belong to the behavioral track; static styling belongs to the visual track. ## 2. Delegate exploration Dispatch one subagent with the brief, the absolute path to this skill folder, and the chosen track, required claims, inspection budge