frontend-reference-huntlisted
Install: claude install-skill LucasSantana-Dev/frontend-reference-hunt
# Frontend Reference Hunt
Turns "I want it to look premium, not AI-made" into a concrete, current reference board
sourced from real platforms, so build skills anchor on shipped work instead of
training-data averages (the root cause of slop convergence).
## Use When
- A frontend task needs visual direction and no reference board exists yet.
- A build skill (repaint, frontend-craft, ui-expert, premium-frontend-ui) is about to run
its reference-anchor phase and would otherwise anchor from memory.
- User asks for UI/UX/motion references, a moodboard, or "what does good look like" for a surface.
## Do Not Use When
- References already curated this session (reuse the existing board).
- The task is building or restyling UI itself — hand the board to `repaint` / `frontend-craft`.
- Pure motion implementation questions — `premium-frontend-ui` archetypes may suffice without a hunt.
## Inputs / Prereqs
- Brief: surface type (landing / dashboard / app / component), register (production-credible
vs art-directed), brand constraints (existing tokens? audience?), motion ambition (none / subtle / immersive).
- Browser: `claude-in-chrome` MCP against the user's Chrome (Mobbin and Pinterest gate most
content behind the user's logged-in session). Fallback for public pages: WebSearch + WebFetch.
## Workflow
1. **Lock the brief** (4 axes above). If a build skill dispatched this hunt, inherit its
register lock verbatim; never re-decide register here.
2. **Route platforms by goal**