refslisted

# /refs Reads every folder under `references/*/`, extracts patterns per aspect, surfaces conflicts, and produces two artifacts: - `references/proposal.md` — recommendations for `/design-lock`. - `references/approved-manifest.md` — a flat list of required elements the user approved (see Step 5b). ## When to use - After `brief/05-design.md` is filled. - The user placed references in `references/`. - Before `/design-lock`. ## Requirements - At least 1 reference exists somewhere under `references/*/`. - `brief/05-design.md` is filled (mood, associations). If no references at all — offer to base the design on `brief/05-design.md` and skip this skill. ## Process **Step 1. Walk every aspect folder.** For each folder in `references/`: - `animation/`, `structure/`, `typography/`, `color/`, `layout/`, `motion/`, `micro-interactions/`, `mood/`, `full-sites/` - Read every subfolder: `source.txt`, `notes.md`, media files. - If the user provided a URL but no screenshot, WebFetch the visual/structure (do not pull code). **Step 2. Extract the common pattern per aspect.** For each aspect, articulate what's shared across references: ``` ## animation From 3 references: - Common pattern: subtle scale-up on hover (1.02×), fade + slight lift on scroll - Common ease: cubic-bezier(0.22, 1, 0.36, 1) - Common duration: ~300ms - Outlier: <linear-refs uses longer 500ms> ## typography - Serif heading + sans body (2 of 3) - Ratio ~1.333 (Perfect Fourth) - Weights: 400 body, 700 headings — onl