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.
A skill your agent uses when designing states, transitions, animations, error handling, loading patterns, feedback, or any behaviour that responds to user action — ensures interactions are…
Install Interaction Design
$ npx skills add Owl-Listener/designpowers --skill interaction-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers interaction-design --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/interaction-design .claude/skills/interaction-design && 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 "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .claude/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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/interaction-designType 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 interaction-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers interaction-design --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/interaction-design .agents/skills/interaction-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .agents/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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 interaction-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers interaction-design --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/interaction-design .cursor/skills/interaction-design && 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 "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .cursor/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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/interaction-design--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 interaction-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers interaction-design --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/interaction-design .gemini/skills/interaction-design && 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 "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .gemini/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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 interaction-designInstalls 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 interaction-design -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/interaction-design .github/skills/interaction-design && 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 "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .github/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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 interaction-design -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 interaction-design --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/interaction-design .opencode/skills/interaction-design && 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 "interaction-design" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/interaction-design into .opencode/skills/interaction-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "interaction-design", 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
interaction-design- GitHub stars
- 251
- Token cost
- ~1.3k tokens
- SKILL.md length
- 622 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing states, transitions, animations, error handling, loading patterns, feedback, or any behaviour that responds to user action — ensures interactions are…
- Works in 6 steps: Map All States → Design Feedback Patterns → Error Handling → …
- Designing states
- SKILL.md covers When to Use, Process, Integration and Red Flags
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Interaction Design is an agent skill from Owl-Listener/designpowers. Use when designing states, transitions, animations, error handling, loading patterns, feedback, or any behaviour that responds to user action — ensures interactions are perceivable, operable, and inclusive
Its SKILL.md is about 1.3k 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
- Designing states
- Loading patterns
- Any behaviour that responds to user action — ensures interactions are perceivable
Example prompts
- “/interaction-design”
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
Interaction Design loads about 1.3k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 622 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). 622 words, ~1,324 tokens.
Download SKILL.mdSave it as
.claude/skills/interaction-design/SKILL.md (or your agent's skills folder).- name
- interaction-design
- description
- Use when designing states, transitions, animations, error handling, loading patterns, feedback, or any behaviour that responds to user action — ensures interactions are perceivable, operable, and inclusive
Interaction Design
Interactions are promises. Every button says "click me and something will happen." Every loading spinner says "wait, it is coming." This skill ensures those promises are kept for everyone, regardless of how they interact with the interface.
When to Use
- Designing component states (default, hover, active, focus, disabled, error)
- Creating transitions or animations
- Handling errors, empty states, or edge cases
- Designing loading and progress patterns
- Defining feedback mechanisms (success, warning, error confirmations)
- Designing gesture or touch interactions
Process
Step 1: Map All States
For every interactive element, define:
| State | Visual | Screen Reader | Keyboard | Touch |
|---|---|---|---|---|
| Default | [appearance] | [announcement] | [behaviour] | [behaviour] |
| Hover | [appearance] | n/a | n/a | n/a |
| Focus | [appearance + focus ring] | [announcement] | [how to reach] | n/a |
| Active/Pressed | [appearance] | [announcement] | [trigger key] | [gesture] |
| Disabled | [appearance, not just greyed] | [announcement + reason] | [skip in tab order?] | [behaviour] |
| Error | [appearance + message] | [announcement + guidance] | [focus moved?] | [behaviour] |
| Loading | [appearance] | [live region update] | [interaction blocked?] | [behaviour] |
| Success | [appearance] | [announcement] | [next focus target] | [behaviour] |
Step 2: Design Feedback Patterns
Every user action deserves a response. Map the feedback:
Immediate feedback (< 100ms):
- Visual state change on interaction (button press, toggle flip)
- Must be perceivable without relying on colour alone
Short wait feedback (100ms - 1s):
- Loading indicator or skeleton screen
- ARIA live region announcement: "Loading..."
Long wait feedback (> 1s):
- Progress indicator with estimated time or progress percentage
- Ability to cancel or navigate away
- ARIA live region updates at intervals
Completion feedback:
- Clear success or error state
- Screen reader announcement of outcome
- Logical next focus target
Step 3: Error Handling
Errors are not edge cases — they are guaranteed states. Design for them:
- Prevention first — inline validation, clear constraints, sensible defaults
- Clear identification — what went wrong, in plain language
- Specific guidance — what the person should do next
- Accessible delivery — errors announced to screen readers, focus moved to the error, not just a colour change
- Recovery path — preserve user input, allow correction without starting over
Error message format: [What happened] + [What to do about it]
- Yes: "That email address is already registered. Try signing in instead, or use a different email."
- No: "Error: invalid input"
Show full SKILL.md (275 more words)Show less
Step 4: Animation and Motion
Animations serve a purpose or they serve nobody:
When to animate:
- To show a relationship between elements (a panel sliding in from its trigger)
- To maintain spatial orientation (a page transition showing direction)
- To provide feedback (a subtle bounce on a successful action)
When NOT to animate:
- Decoration without function
- Anything that delays the user from completing their task
- Anything that loops indefinitely
Inclusive motion:
- Respect
prefers-reduced-motion— always provide a reduced or no-motion alternative - Keep durations short: 150-300ms for micro-interactions, 300-500ms for transitions
- Avoid parallax, auto-playing video, flashing content (3 flashes per second maximum per WCAG)
- Provide pause/stop controls for any animation longer than 5 seconds
Step 5: Gesture and Input Design
If the design includes gesture interactions:
- Every gesture must have a non-gesture alternative (button, keyboard shortcut)
- Swipe actions must be discoverable without trial-and-error
- Drag-and-drop must have a keyboard-accessible alternative
- Touch targets: 44x44px minimum, with adequate spacing between targets
Step 6: Document the Interaction Spec
For each interaction, document:
- Trigger (what initiates the interaction)
- Behaviour (what happens, step by step)
- States (all states the element passes through)
- Feedback (what the user perceives at each stage)
- Accessibility (screen reader announcements, keyboard behaviour, motion reduction)
Integration
- Called by:
writing-design-plans(as part of plan execution) - Pairs with:
ui-composition(visual states),cognitive-accessibility(interaction complexity),accessible-content(error messages) - Reviewed by:
designpowers-critique
Red Flags
| Flag | Response |
|---|---|
| Component with only default and hover states | Map ALL states including focus, error, loading, disabled |
| Animation without prefers-reduced-motion support | Add motion reduction. This is not optional |
| Error state that only changes colour | Add text, icon, and screen reader announcement |
| Gesture without alternative input method | Add keyboard and/or button alternative |
© 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/interaction-design of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Interaction Design 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 |
|---|---|---|---|---|---|---|
| Interaction Design this skillOwl-Listener/designpowers | 251 | — | ~1.3k | 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 | 98 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 Interaction Design
What does Interaction Design do?
A skill your agent uses when designing states, transitions, animations, error handling, loading patterns, feedback, or any behaviour that responds to user action — ensures interactions are…. Interaction Design is an agent skill from Owl-Listener/designpowers.
When should I use Interaction Design?
Interaction Design fits situations like: designing states; loading patterns; any behaviour that responds to user action — ensures interactions are perceivable.
How do I install Interaction Design in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill interaction-design -a claude-code`. Or copy the skill folder (skills/interaction-design in Owl-Listener/designpowers) into .claude/skills/interaction-design in your project. Claude Code loads it when a task matches its description.
How do I install Interaction Design in Codex?
Run `npx skills add Owl-Listener/designpowers --skill interaction-design -a codex`. Or copy the skill folder (skills/interaction-design in Owl-Listener/designpowers) into .agents/skills/interaction-design in your project. Codex loads it when a task matches its description.
Can I use Interaction Design 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 interaction-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interaction-design, .gemini/skills/interaction-design, .github/skills/interaction-design and .opencode/skills/interaction-design in your project.
What does Interaction Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Interaction Design is instructions for the agent only.
Does Interaction Design 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 Interaction Design 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 Interaction Design use?
Interaction Design 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 Interaction Design use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Interaction Design?
Skills that share tags, products or a category with Interaction Design: 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 Interaction Design?
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.