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 any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to.
Install Design State
$ npx skills add Owl-Listener/designpowers --skill design-state -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers design-state --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/design-state .claude/skills/design-state && 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 "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .claude/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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/design-stateType 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 design-state -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers design-state --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/design-state .agents/skills/design-state && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .agents/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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 design-state -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers design-state --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/design-state .cursor/skills/design-state && 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 "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .cursor/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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/design-state--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 design-state -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers design-state --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/design-state .gemini/skills/design-state && 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 "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .gemini/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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 design-stateInstalls 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 design-state -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/design-state .github/skills/design-state && 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 "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .github/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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 design-state -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 design-state --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/design-state .opencode/skills/design-state && 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 "design-state" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/design-state into .opencode/skills/design-state/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-state", 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
design-state- GitHub stars
- 251
- Token cost
- ~1.6k tokens
- SKILL.md length
- 478 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to.
- Works in 6 steps: Every agent reads the design state… → Every agent appends to the decisions log… → Never delete from the decisions log — it… → …
- Any Designpowers agent starts work
- SKILL.md covers Welcome Gate, The File, When to Use This Skill and Structure, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design State is an agent skill from Owl-Listener/designpowers. Use when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to. Invoke to initialise, read, or update the living design state document
Its SKILL.md is about 1.6k 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
- Any Designpowers agent starts work
- Completes work — maintains the shared design state file that all agents read from and write to
Example prompts
- “/design-state”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Every agent reads the design state before starting — if it does not exist, something is wrong. Go back to discovery
- Every agent appends to the decisions log when done — decisions that are not recorded did not happen
- Never delete from the decisions log — it is append-only. If a decision is reversed, add a new entry that supersedes it
- Open questions are removed only when resolved — the resolution goes in the decisions log
- The handoff chain is mandatory — every agent-to-agent transition is recorded with what was passed and what needs attention
- Keep it scannable — this file will be read by every agent. Tables and one-liners, not paragraphs
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
Design State loads about 1.6k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 478 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). 478 words, ~1,646 tokens.
Download SKILL.mdSave it as
.claude/skills/design-state/SKILL.md (or your agent's skills folder).- name
- design-state
- description
- Use when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to. Invoke to initialise, read, or update the living design state document
Design State
The design state is a shared, living document that accumulates design decisions as the workflow progresses. Every Designpowers agent reads it before starting work and updates it when done. It is the single source of truth for the current state of the design.
Welcome Gate
BEFORE initialising or reading design state, check whether the Designpowers welcome sequence has been shown this session. If the user has not yet seen the welcome (the bird, the greeting, and the walkthrough offer), you MUST invoke the using-designpowers skill FIRST and complete the welcome sequence before returning here. The bird must appear before any work begins. No exceptions.
The File
The design state lives at design-state.md in the project root (or working directory). One file per project.
When to Use This Skill
- Initialise — when
design-discoverycompletes and a brief is approved, create the design state file - Read — before dispatching any Designpowers agent, confirm the design state file exists and is current
- Update — after any agent completes work, append their decisions and outputs to the state file
- Review — during critique or verification, use the state file as the definitive record of what was decided
Structure
Create and maintain the design state file with this structure:
# Design State: [Project Name]
_Last updated: [date] by [agent name]_
## Brief
- **Problem:** [one-line problem statement]
- **Primary persona:** [name and context]
- **Success metric:** [what "done" looks like]
- **Brief document:** [relative path to full brief]
## Personas
[Link to personas document]
- [Persona 1 name] — [one-line context]
- [Persona 2 name] — [one-line context]
- ...
## Design Principles
1. [Principle] — [what it means in practice]
2. [Principle] — [what it means in practice]
3. ...
## Taste Profile
- **Emotional target:** [2-3 words — e.g., "calm confidence", "playful warmth"]
- **Quality level:** [Prototype / Production / Flagship]
- **Key references:** [names/URLs]
- **Aesthetic principles:** [list]
- **Taste document:** [path to full taste profile]
_If no taste calibration was done, note: "No taste profile — craft evaluation uses general quality standards only."_
## Decisions Log
Append-only. Each entry records who decided, what, and why.
| Date | Agent | Decision | Rationale |
|------|-------|----------|-----------|
| [date] | design-strategist | Bottom tab navigation, 3 items | Minimises cognitive load per principle #1 |
| [date] | design-lead | Mint/sage palette, category colour coding | Warm, approachable, passes AA contrast |
| ... | ... | ... | ... |
## Open Questions
Things that need resolution. Remove when resolved (move decision to log).
- [ ] [Question — who needs to answer it]
- [ ] ...
## Artefact Index
Paths to key documents produced during the workflow.
| Artefact | Path | Status |
|----------|------|--------|
| Brief | [path] | Approved |
| Personas | [path] | Complete |
| Strategy | [path] | Complete |
| Plan | [path] | In progress |
| Heuristic evaluation | [path] | [Pending/Complete] |
| Synthetic test results | [path] | [Pending/Complete] |
| ... | ... | ... |
## Design Debt Register
Deferred findings from critique, accessibility review, heuristic evaluation, and synthetic user testing. Managed by `design-debt-tracker`.
_Items: 0 | Critical: 0 | Oldest: —_
| ID | Date | Source | Severity | What | Who is affected | Suggested fix | Status | Notes |
|----|------|--------|----------|------|----------------|---------------|--------|-------|
## Handoff Chain
Track which agent handed off to which. Each entry includes the conversational babble message that the agent wrote when handing off. These messages are shown to the user.
### [timestamp] design-strategist → design-lead
> "The core users are families with a new puppy, kids aged 8-14 taking the lead. Principle #1 says 'celebrate effort, not perfection' — so nothing should feel like a report card. The setup flow needs progressive disclosure. Over to you for the visual direction."
### [timestamp] design-lead → motion-designer
> "I've gone with frosted glass cards and a mint/sage palette. The progress ring is the hero moment — when it hits 100% it needs to feel like a celebration, not just a colour change. Keep it subtle everywhere else."
**🎨 User override:** "Use my existing design system instead of mint/sage. The tokens are in /tokens/colors.json."
### [timestamp] motion-designer → design-builder
> "Progress ring gets a 600ms spring fill. Checkboxes get 150ms bounce. Reduced-motion fallbacks swap to opacity fades."
### [timestamp] ...
Rules
- Every agent reads the design state before starting — if it does not exist, something is wrong. Go back to discovery
- Every agent appends to the decisions log when done — decisions that are not recorded did not happen
- Never delete from the decisions log — it is append-only. If a decision is reversed, add a new entry that supersedes it
- Open questions are removed only when resolved — the resolution goes in the decisions log
- The handoff chain is mandatory — every agent-to-agent transition is recorded with what was passed and what needs attention
- Keep it scannable — this file will be read by every agent. Tables and one-liners, not paragraphs
Show full SKILL.md (163 more words)Show less
Initialisation
When creating the design state for the first time (after discovery):
- Create
design-state.mdin the project root - Fill in the Brief section from the approved design brief
- Fill in Personas if they exist yet
- Fill in Design Principles if strategy has been done
- Start the Decisions Log with any decisions already made
- Add any known open questions
- Start the Artefact Index with the brief path
Updating After Agent Work
When an agent completes its work:
- Read the current design state
- Append new decisions to the Decisions Log (with date, agent name, decision, rationale)
- Resolve any open questions that were answered
- Add any new open questions that emerged
- Update the Artefact Index with any new documents produced
- Write the handoff babble message (2-4 conversational sentences addressed to the next agent)
- Add the babble to the Handoff Chain — this is shown to the user
- Update the "Last updated" line
© 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/design-state of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Design State 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 |
|---|---|---|---|---|---|---|
| Design State this skillOwl-Listener/designpowers | 251 | — | ~1.6k | 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 Design State
What does Design State do?
A skill your agent uses when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to. Design State is an agent skill from Owl-Listener/designpowers. Use when any Designpowers agent starts work or completes work — maintains the shared design state file that all agents read from and write to.
When should I use Design State?
Design State fits situations like: any Designpowers agent starts work; completes work — maintains the shared design state file that all agents read from and write to.
How do I install Design State in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill design-state -a claude-code`. Or copy the skill folder (skills/design-state in Owl-Listener/designpowers) into .claude/skills/design-state in your project. Claude Code loads it when a task matches its description.
How do I install Design State in Codex?
Run `npx skills add Owl-Listener/designpowers --skill design-state -a codex`. Or copy the skill folder (skills/design-state in Owl-Listener/designpowers) into .agents/skills/design-state in your project. Codex loads it when a task matches its description.
Can I use Design State 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 design-state -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-state, .gemini/skills/design-state, .github/skills/design-state and .opencode/skills/design-state in your project.
What does Design State need to run?
SKILL.md names no scripts, command-line tools or credentials: Design State is instructions for the agent only.
Does Design State 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 Design State 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 Design State use?
Design State 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 Design State use?
About 1.6k tokens (SKILL.md is roughly 6.6k 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 Design State?
Skills that share tags, products or a category with Design State: 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 Design State?
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.