Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
A skill your agent uses when the team needs aesthetic references, interaction examples, or visual inspiration beyond competitive research — finds design patterns, UI references, and creative…
Install Inspiration Scouting
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers inspiration-scouting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inspiration-scouting .claude/skills/inspiration-scouting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .claude/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scoutingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers inspiration-scouting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/inspiration-scouting .agents/skills/inspiration-scouting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .agents/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers inspiration-scouting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/inspiration-scouting .cursor/skills/inspiration-scouting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .cursor/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designpowers.git --path skills/inspiration-scouting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers inspiration-scouting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/inspiration-scouting .gemini/skills/inspiration-scouting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .gemini/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designpowers inspiration-scoutingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/inspiration-scouting .github/skills/inspiration-scouting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .github/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designpowers inspiration-scouting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/inspiration-scouting .opencode/skills/inspiration-scouting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "inspiration-scouting" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/inspiration-scouting into .opencode/skills/inspiration-scouting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "inspiration-scouting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
inspiration-scouting- GitHub stars
- 251
- Token cost
- ~2.1k tokens
- SKILL.md length
- 869 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the team needs aesthetic references, interaction examples, or visual inspiration beyond competitive research — finds design patterns, UI references, and creative…
- Works in 6 steps: Define the Inspiration Brief → Search Across Layers → Curate a Mood Board → …
- The team needs aesthetic references
- SKILL.md covers When to Use, Do Not Use When, Process and Integration With Taste Profile, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Inspiration Scouting is an agent skill from Owl-Listener/designpowers. Use when the team needs aesthetic references, interaction examples, or visual inspiration beyond competitive research — finds design patterns, UI references, and creative approaches that match the brief and taste profile
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Design patterns. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- The team needs aesthetic references
- Interaction examples
- Visual inspiration beyond competitive research — finds design patterns
- Creative approaches that match the brief and taste profile
Example prompts
- “/inspiration-scouting”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb00757. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Inspiration Scouting loads about 2.1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 869 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 869 words, ~2,131 tokens.
Download SKILL.mdSave it as
.claude/skills/inspiration-scouting/SKILL.md (or your agent's skills folder).- name
- inspiration-scouting
- description
- Use when the team needs aesthetic references, interaction examples, or visual inspiration beyond competitive research — finds design patterns, UI references, and creative approaches that match the brief and taste profile
Inspiration Scouting
The design-scout does competitive research — who else solves this problem and how. Inspiration scouting is different. It finds aesthetic and interaction references that shape the feel of the design, even when they come from completely different domains. A banking app can be inspired by a meditation app's calm. A children's education tool can borrow pacing from a well-designed game.
When to Use
- After design-discovery and design-strategy, before visual design begins
- When the design-lead needs a visual direction and wants reference material
- When the user says "show me some inspiration" or "what could this look like?"
- When the taste profile exists but the project needs a fresh direction within it
- When the team is stuck and needs outside input to break a creative block
Do Not Use When
- The user has already provided specific visual references — use those directly
- The design system is locked and visual direction is predetermined
- The task is a fix or iteration, not a new direction
Process
Step 1: Define the Inspiration Brief
Before searching, define what you're looking for:
## Inspiration Brief
**Project:** [Name and one-line description]
**Feel we're going for:** [2-3 adjectives — e.g., "calm, confident, playful"]
**Feel we're avoiding:** [2-3 adjectives — e.g., "clinical, childish, corporate"]
**Taste constraints:** [From taste profile — known preferences and anti-patterns]
**Domain:** [The project's domain — e.g., "pet care", "fintech", "education"]
**Cross-domain openness:** [How far outside the domain to look — same domain / adjacent / anywhere]
**Specific needs:** [e.g., "onboarding flow inspiration", "dashboard layout patterns", "empty state ideas"]Step 2: Search Across Layers
Inspiration operates at multiple layers. Search each:
Visual Layer
- Colour: Palette approaches, colour psychology, brand colour usage
- Typography: Type pairing, scale, weight distribution, editorial vs UI
- Layout: Grid systems, density, whitespace philosophy, asymmetry
- Imagery: Photography style, illustration approach, iconography
- Surface: Texture, depth, glassmorphism, neumorphism, flat — what's appropriate
Interaction Layer
- Navigation: Patterns, transitions between views, wayfinding
- Feedback: How the interface responds — micro-interactions, loading, success, error
- Onboarding: First-run experiences, progressive disclosure, tutorials
- Data entry: Form patterns, input methods, validation approaches
- Empty states: What the app feels like before there's content
Emotional Layer
- Personality: How the interface expresses character through details
- Pacing: Fast and efficient vs slow and contemplative
- Trust signals: How the interface builds confidence
- Delight moments: Where and how the interface surprises positively
- Restraint: What the interface deliberately does not do
Step 3: Curate a Mood Board
Compile findings into a structured mood board. Quality over quantity — 5 excellent references beat 20 mediocre ones.
For each reference:
### [Reference Name]
**Source:** [App/site/product name and what it does]
**Why it's relevant:** [1-2 sentences connecting this to the project brief]
**What to take:** [The specific element or quality to learn from]
**What to leave:** [What doesn't apply — this prevents wholesale copying]
**Taste alignment:** [How it connects to the user's taste profile]
**Layer:** Visual / Interaction / EmotionalStep 4: Cross-Domain Connections
The best inspiration often comes from outside the project's domain. Actively seek cross-domain references:
| Project Domain | Look At |
|---|---|
| Healthcare | Meditation apps (calm), fitness apps (motivation), journaling apps (reflection) |
| Finance | Productivity tools (clarity), weather apps (data viz), news apps (hierarchy) |
| Education | Games (engagement), music apps (progression), social apps (community) |
| E-commerce | Editorial sites (storytelling), gallery apps (browsing), travel apps (discovery) |
| Enterprise | Consumer apps (polish), design tools (power + clarity), documentation sites (wayfinding) |
Don't force connections — but don't limit yourself to competitors either.
Step 5: Present the Board
Present inspiration to the user and the design-lead as a curated collection:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
INSPIRATION BOARD
For: [Project Name]
Feel: [target adjectives]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VISUAL DIRECTION
◆ [Reference 1] — [what to take]
◆ [Reference 2] — [what to take]
INTERACTION PATTERNS
◆ [Reference 3] — [what to take]
◆ [Reference 4] — [what to take]
EMOTIONAL TONE
◆ [Reference 5] — [what to take]
CROSS-DOMAIN WILD CARD
◆ [Reference 6] — [unexpected connection]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Does any of this resonate? I can dig deeper
into any direction or find more references.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Step 6: Refine Based on Response
The user's reaction to inspiration is a powerful taste signal:
| Reaction | What to Do | Taste Signal |
|---|---|---|
| "Love that" | Dig deeper into similar references | Strong positive — record in design-memory |
| "Not quite" | Ask what's off — too bold? too safe? wrong tone? | Soft negative — refine search |
| "That but calmer" | The direction is right, the intensity is wrong | Record the adjustment as a taste nuance |
| "None of these" | Go back to Step 1 and redefine the feel | The inspiration brief needs rewriting |
| "Number 3, but for the layout, not the colour" | User is compositing — they see the design in pieces | Record which layers resonate separately |
After refinement, update the inspiration brief with what resonated and pass it to design-lead as part of their brief.
Show full SKILL.md (307 more words)Show less
Integration With Taste Profile
Inspiration is driven by this project's direction — the brief and the live taste calibration from design-taste — not by the cross-project design record. The design-memory record is observational and is not used to pre-filter or steer references; doing so would silently apply one project's habits to another. (If the user themselves says "I usually avoid gradients," that's live direction for this project — honour it because they said it now, not because a record predicted it.)
You may still record new signals into design-memory as observations after the fact (see below) — that's watching, not steering.
Integration
- Called by:
design-discovery(to set visual direction),design-strategy(for positioning references),using-designpowers(when user requests inspiration) - Calls:
design-memory(only to record new observations after the fact — never to read constraints that steer the scouting) - Hands off to:
design-lead(with curated references as visual brief),design-strategist(with emotional/UX references) - Pairs with:
design-memory,design-debate(inspiration can trigger a debate on direction) - Updated by: User reactions — every "love it" or "not for me" is a taste data point
Anti-Patterns
| Pattern | Why It Fails |
|---|---|
| Dumping 20 references without curation | Overwhelms. 5 excellent references with clear "what to take" beats 20 screenshots |
| Only looking at competitors | Competitors solve the same problem the same way. Cross-domain references unlock fresh approaches |
| Showing inspiration that violates accessibility | A beautiful reference with 2:1 contrast ratios is not inspiration — it's a cautionary tale. Flag accessibility issues in references |
| Copying instead of being inspired | Inspiration means "take the quality, not the pixels." Always specify what to take and what to leave |
| Ignoring this project's stated direction | If the user has said (now) they want a calm, gradient-free look, showing gradient-heavy references wastes their time. Drive from design-taste, not from the cross-project record |
| Presenting without "what to take" | A reference without a clear lesson is decoration. Every reference needs a reason |
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/inspiration-scouting of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Inspiration Scouting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Inspiration Scouting this skillOwl-Listener/designpowers | 251 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Swiftui View RefactorDimillian/Skills | 4k | 5 repos | ~2k | Automated safety check: Pass | MIT | |
| RTK Rust Design Patternsrtk-ai/rtk | 83k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Effect Client WrapperUsefulSoftwareCo/executor | 4.1k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Architecture PatternsKartikLabhshetwar/better-shot | 2.4k | 2 repos | ~1.4k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Swiftui View Refactor
Dimillian/Skills
Refactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage.
RTK Rust Design Patterns
rtk-ai/rtk
Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.
Effect Client Wrapper
UsefulSoftwareCo/executor
Pattern for wrapping third-party SDK clients (Stripe, Resend, AWS, etc.) with Effect.
Architecture Patterns
KartikLabhshetwar/better-shot
Deep dive into software architecture for macOS. An agent skill from KartikLabhshetwar/better-shot.
GitVersion .NET Development
GitTools/GitVersion
Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Related
Categories
Questions about Inspiration Scouting
What does Inspiration Scouting do?
A skill your agent uses when the team needs aesthetic references, interaction examples, or visual inspiration beyond competitive research — finds design patterns, UI references, and creative…. Inspiration Scouting is an agent skill from Owl-Listener/designpowers.
When should I use Inspiration Scouting?
Inspiration Scouting fits situations like: the team needs aesthetic references; interaction examples; visual inspiration beyond competitive research — finds design patterns; creative approaches that match the brief and taste profile.
How do I install Inspiration Scouting in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a claude-code`. Or copy the skill folder (skills/inspiration-scouting in Owl-Listener/designpowers) into .claude/skills/inspiration-scouting in your project. Claude Code loads it when a task matches its description.
How do I install Inspiration Scouting in Codex?
Run `npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a codex`. Or copy the skill folder (skills/inspiration-scouting in Owl-Listener/designpowers) into .agents/skills/inspiration-scouting in your project. Codex loads it when a task matches its description.
Can I use Inspiration Scouting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designpowers --skill inspiration-scouting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inspiration-scouting, .gemini/skills/inspiration-scouting, .github/skills/inspiration-scouting and .opencode/skills/inspiration-scouting in your project.
What does Inspiration Scouting need to run?
SKILL.md names no scripts, command-line tools or credentials: Inspiration Scouting is instructions for the agent only.
Does Inspiration Scouting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Inspiration Scouting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Inspiration Scouting use?
Inspiration Scouting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Inspiration Scouting use?
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Inspiration Scouting?
Skills that share tags, products or a category with Inspiration Scouting: Vercel Composition Patterns (supabase/supabase, 111k stars), Swiftui View Refactor (Dimillian/Skills, 4k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and Effect Client Wrapper (UsefulSoftwareCo/executor, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Inspiration Scouting?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.