skills/ux-get-inspired/SKILL.md
Step 6.1 of Sketch the Solution. Research UI patterns and build an inspiration reference. Use when asked to 'get inspired', 'UI inspiration', 'research UI patterns', 'pattern library', or 'design inspiration'.
npx skillsauth add arndvs/ctrlshft ux-get-inspiredInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Output "Read UX Get Inspired skill." to chat to acknowledge you read this file.
Phase: /ux-interface-design → Step 1 of 3
"Good artists copy, great artists steal."
Before sketching, gather inspiration from established products and UI pattern libraries. Create an "inspiration wall" of references for each screen type.
For each screen in the flow, identify the screen type:
Research relevant patterns:
Generate inspiration reference:
## Inspiration Reference
### [Screen Name] — [Screen Type]
**Reference Products:**
- [Product 1] — [what to borrow: e.g., "card-based layout for browse"]
- [Product 2] — [what to borrow: e.g., "sidebar filter pattern"]
**Relevant UI Patterns:**
- [Pattern name] — [when to use: e.g., "faceted search for directory"]
- [Pattern name] — [when to use: e.g., "infinite scroll for content feed"]
**Key Components Needed:**
- [e.g., "Filter bar with pills/tags"]
- [e.g., "Member card snippet: avatar + name + skills"]
Start interface-design.md with Inspiration Reference section.
development
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
development
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
tools
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
testing
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.