Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Use during the build phase to show the user intermediate visual output and ask for taste direction before the full build completes — enables mid-flight course correction so taste mismatches are…
Install Taste Feedback
$ npx skills add Owl-Listener/designpowers --skill taste-feedback -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers taste-feedback --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/taste-feedback .claude/skills/taste-feedback && 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 "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .claude/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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/taste-feedbackType 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 taste-feedback -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers taste-feedback --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/taste-feedback .agents/skills/taste-feedback && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .agents/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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 taste-feedback -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers taste-feedback --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/taste-feedback .cursor/skills/taste-feedback && 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 "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .cursor/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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/taste-feedback--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 taste-feedback -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers taste-feedback --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/taste-feedback .gemini/skills/taste-feedback && 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 "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .gemini/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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 taste-feedbackInstalls 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 taste-feedback -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/taste-feedback .github/skills/taste-feedback && 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 "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .github/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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 taste-feedback -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 taste-feedback --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/taste-feedback .opencode/skills/taste-feedback && 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 "taste-feedback" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/taste-feedback into .opencode/skills/taste-feedback/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "taste-feedback", 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
taste-feedback- GitHub stars
- 251
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,011 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use during the build phase to show the user intermediate visual output and ask for taste direction before the full build completes — enables mid-flight course correction so taste mismatches are…
- Works in 6 steps: Identify Checkpoints → Prepare the Checkpoint → Present the Checkpoint → …
- Frontend & Design work in your project
- SKILL.md covers When to Use, Do Not Use When, Process and Checkpoint Frequency, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Taste Feedback is an agent skill from Owl-Listener/designpowers. Use during the build phase to show the user intermediate visual output and ask for taste direction before the full build completes — enables mid-flight course correction so taste mismatches are caught early, not in review
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 Frontend & Design. 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
- Frontend & Design work in your project
Example prompts
- “/taste-feedback”
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.
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
Taste Feedback loads about 2.1k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,011 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). 1,011 words, ~2,127 tokens.
Download SKILL.mdSave it as
.claude/skills/taste-feedback/SKILL.md (or your agent's skills folder).- name
- taste-feedback
- description
- Use during the build phase to show the user intermediate visual output and ask for taste direction before the full build completes — enables mid-flight course correction so taste mismatches are caught early, not in review
Live Taste Feedback
The standard Designpowers pipeline catches taste mismatches at critique — after the full build is done. That's expensive. A wrong colour palette discovered after 8 components are built means rebuilding all 8. This skill interrupts the build at strategic moments to show intermediate output and ask: "Is this heading in the right direction?"
When to Use
- During
design-builderexecution, at natural visual checkpoints - When the build involves subjective aesthetic decisions (colour, typography, spacing, tone)
- When this project's taste direction (
design-taste) is ambiguous on the decision at hand - When the project is new and there's little explicit direction yet for this decision
- When the design-lead's direction was based on interpretation, not explicit user instruction
Do Not Use When
- The user is in auto mode and hasn't opted into taste checks
- The build is purely structural (data models, API integration, routing)
- This project's
design-tastedirection already settles this decision clearly - The user has explicitly said "just build it, I'll review at the end"
Process
Step 1: Identify Checkpoints
Before the build begins, identify 2-4 moments where taste feedback is most valuable. More than 4 interruptions becomes annoying. Choose wisely.
High-value checkpoints:
| Checkpoint | Why It Matters | When to Show |
|---|---|---|
| Colour and typography applied | The foundational visual layer — everything else builds on this | After the first component is styled |
| Layout structure visible | Spatial relationships, density, whitespace | After the primary screen scaffold is built |
| First interaction implemented | How the interface moves and responds | After the first stateful component works |
| Content integrated | How real words look in the design | After content-writer's copy is in place |
Low-value checkpoints (avoid):
| Checkpoint | Why It's Low Value |
|---|---|
| Unstyled HTML structure | Nothing to react to aesthetically |
| Individual component in isolation | Context-free judgement is unreliable |
| After every small change | Interruption fatigue kills the creative flow |
Step 2: Prepare the Checkpoint
At each checkpoint, capture the current state:
- Take a screenshot of the running output (or describe the visual state precisely if screenshots aren't available)
- Identify the taste-sensitive decisions visible in the current output
- Prepare specific questions — do not ask "does this look good?" (too vague)
Good taste questions are specific and answerable:
| Bad Question | Good Question |
|---|---|
| "Does this look good?" | "The heading is set in 32px Inter Medium — is that weight right, or do you want bolder/lighter?" |
| "Any feedback?" | "The cards have 16px padding and 8px radius. Does this density feel right, or do you want more breathing room?" |
| "Is this the right direction?" | "I went warm grey (#F5F3F0) for the background instead of pure white. Does this warmth match what you had in mind?" |
Step 3: Present the Checkpoint
Show the user the intermediate state with targeted questions:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TASTE CHECK [1 of 3]
Phase: [e.g., "Colour & Typography"]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Screenshot or detailed visual description]
DECISIONS VISIBLE:
• [Decision 1 — e.g., "Sage green (#8FAE8B) as primary"]
• [Decision 2 — e.g., "Space Grotesk for headings, Inter for body"]
• [Decision 3 — e.g., "Generous padding, low density"]
TASTE QUESTIONS:
1. [Specific question about a visible decision]
2. [Specific question about a visible decision]
Quick responses welcome:
• "Looks right" → continue building
• "Warmer/cooler/bolder/quieter" → adjust and continue
• "Stop — wrong direction" → pause build, discuss
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━Step 4: Process the Response
The user's response determines what happens next:
| Response | Action | Taste Signal |
|---|---|---|
| "Looks right" / "Yes" / "Continue" | Resume building. No changes needed | Moderate positive — note in design-memory as confirmed direction |
| Specific adjustment ("make it warmer") | Apply the adjustment, show confirmation, then continue | Strong — record the adjustment and the direction they moved from/to |
| "Wrong direction" / "Stop" | Pause the build. Ask what feels off. This is the most valuable taste data | Very strong negative — record what was rejected and why |
| Detailed feedback ("I like the type but the colour feels too muted") | Apply partial changes. Acknowledge what works, adjust what doesn't | Mixed signal — record both the positive and negative separately |
| "Skip these checks" | Disable further taste checks for this build. Respect the preference | Meta-preference — they want to review at the end instead |
Show full SKILL.md (436 more words)Show less
Step 5: Adjust and Confirm
When the user requests a change:
- Make the adjustment
- Show the updated state briefly — do not re-present the full checkpoint
- Confirm: "Updated [what changed]. Continuing the build."
- Do not ask for re-approval unless the change was ambiguous
If the change cascades (e.g., new colour palette affects multiple components already built):
- Flag the cascade: "This colour change will affect the 3 components already built. I'll update them all."
- Update everything before continuing
- Optionally show the cascaded result at the next checkpoint
Step 6: Record Taste Data
After each checkpoint interaction, update taste signals:
- Record confirmed decisions as positive signals in
design-memory - Record adjustments with before/after — these are the richest taste data
- Record rejections as anti-pattern candidates
- Note the direction of adjustments — "wanted warmer", "wanted more contrast", "wanted tighter spacing" — these directional signals generalize across projects
Checkpoint Frequency
Adapt based on user behaviour:
| User Behaviour | Adjust To |
|---|---|
| Approves every checkpoint quickly | Reduce to 1-2 checkpoints — they trust the direction |
| Gives detailed feedback at every checkpoint | Maintain 3-4 — they want to shape the output |
| Says "skip" or seems impatient | Drop to 1 checkpoint or none — ask at the end |
| Requests more checkpoints | Add checkpoints — they want more control |
The system should learn this preference over time via design-memory.
Integration With Pipeline Modes
| Mode | Behaviour |
|---|---|
| Direct | Taste checkpoints are shown naturally — they fit the approval flow |
| Auto | Taste checkpoints are disabled by default in auto mode. The user chose speed. If the user opts in ("auto but check my taste"), enable minimal checkpoints (1-2 max) |
Integration
- Called by:
design-builder(at visual checkpoints during build),using-designpowers(can be enabled/disabled) - Calls:
design-memory(to record taste signals from feedback) - Reads from: Taste profile (to determine checkpoint frequency and known preferences),
design-state.md(for current decisions) - Pairs with:
design-memory,ui-composition,designpowers-critique
Anti-Patterns
| Pattern | Why It Fails |
|---|---|
| Asking "does this look good?" | Too vague. The user can't give actionable feedback without specific questions |
| Checking after every change | Interruption fatigue. 2-4 checkpoints per build, maximum |
| Showing unstyled output | There's nothing to react to. Wait until visual decisions are visible |
| Ignoring "skip" signals | If the user wants to review at the end, respect that. Don't force mid-flight checks |
| Not recording feedback | Every checkpoint interaction is taste data. If you don't record it, you'll ask the same questions next project |
| Presenting in auto mode without consent | Auto mode means "don't interrupt me." Only show taste checks if the user explicitly opted in |
| Asking about non-visual decisions | "Is this the right React component pattern?" is not a taste question. Keep checks visual and aesthetic |
© 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/taste-feedback of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Taste Feedback 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 |
|---|---|---|---|---|---|---|
| Taste Feedback this skillOwl-Listener/designpowers | 251 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
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 Taste Feedback
What does Taste Feedback do?
Use during the build phase to show the user intermediate visual output and ask for taste direction before the full build completes — enables mid-flight course correction so taste mismatches are…. Taste Feedback is an agent skill from Owl-Listener/designpowers.
When should I use Taste Feedback?
Taste Feedback fits situations like: frontend & Design work in your project.
How do I install Taste Feedback in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill taste-feedback -a claude-code`. Or copy the skill folder (skills/taste-feedback in Owl-Listener/designpowers) into .claude/skills/taste-feedback in your project. Claude Code loads it when a task matches its description.
How do I install Taste Feedback in Codex?
Run `npx skills add Owl-Listener/designpowers --skill taste-feedback -a codex`. Or copy the skill folder (skills/taste-feedback in Owl-Listener/designpowers) into .agents/skills/taste-feedback in your project. Codex loads it when a task matches its description.
Can I use Taste Feedback 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 taste-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/taste-feedback, .gemini/skills/taste-feedback, .github/skills/taste-feedback and .opencode/skills/taste-feedback in your project.
What does Taste Feedback need to run?
SKILL.md names no scripts, command-line tools or credentials: Taste Feedback is instructions for the agent only.
Does Taste Feedback 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 Taste Feedback 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 Taste Feedback use?
Taste Feedback 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 Taste Feedback 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 Taste Feedback?
Skills that share tags, products or a category with Taste Feedback: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Taste Feedback?
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.