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 you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
Install Writing Design Plans
$ npx skills add Owl-Listener/designpowers --skill writing-design-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers writing-design-plans --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/writing-design-plans .claude/skills/writing-design-plans && 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 "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .claude/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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/writing-design-plansType 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 writing-design-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers writing-design-plans --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/writing-design-plans .agents/skills/writing-design-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .agents/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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 writing-design-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers writing-design-plans --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/writing-design-plans .cursor/skills/writing-design-plans && 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 "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .cursor/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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/writing-design-plans--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 writing-design-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers writing-design-plans --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/writing-design-plans .gemini/skills/writing-design-plans && 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 "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .gemini/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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 writing-design-plansInstalls 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 writing-design-plans -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/writing-design-plans .github/skills/writing-design-plans && 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 "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .github/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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 writing-design-plans -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 writing-design-plans --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/writing-design-plans .opencode/skills/writing-design-plans && 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 "writing-design-plans" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/writing-design-plans into .opencode/skills/writing-design-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-design-plans", 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
writing-design-plans- GitHub stars
- 251
- Token cost
- ~1k tokens
- SKILL.md length
- 395 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
- Works in 6 steps: Review Inputs → Identify Design Tasks → Order the Work → …
- You have a design brief
- SKILL.md covers When to Use, Process, Integration and Anti-Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Design Plans is an agent skill from Owl-Listener/designpowers. Use when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
Its SKILL.md is about 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
- You have a design brief
- Strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
Example prompts
- “/writing-design-plans”
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
Writing Design Plans loads about 1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 395 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). 395 words, ~1,019 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-design-plans/SKILL.md (or your agent's skills folder).- name
- writing-design-plans
- description
- Use when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
Writing Design Plans
A design plan breaks an approved design direction into discrete, reviewable tasks. Each task is small enough to evaluate clearly and specific enough that the result is predictable.
When to Use
- After design-discovery and/or design-strategy have produced an approved direction
- Before any implementation work begins
- When a design task is too large to complete and review in one step
Process
Step 1: Review Inputs
Gather:
- Design brief (from design-discovery)
- Strategy document (from design-strategy, if applicable)
- Personas (from inclusive-personas)
- Existing design system inventory
Step 2: Identify Design Tasks
Break the work into categories:
- Structure tasks — information architecture, page hierarchy, navigation
- Component tasks — individual UI components that need designing
- Layout tasks — how components compose into screens
- Interaction tasks — states, transitions, feedback patterns
- Content tasks — copy, labels, error messages, help text
- Accessibility tasks — specific inclusive design requirements per component
Step 3: Order the Work
Design work has natural dependencies:
Structure → Layout → Components → Interactions → Content → Review
↑ accessibility woven through each step, not a final phase ↑Order tasks so that:
- Foundation work (structure, layout) comes before detail work (interactions, content)
- Each task can be reviewed independently
- Accessibility is addressed within each task, not deferred
Step 4: Write the Plan
# Design Plan: [Feature/Project Name]
> **For agentic workers:** REQUIRED: Use designpowers:designpowers-critique to review completed work against this plan.
**Goal:** [One sentence — what this plan delivers]
**Design Direction:** [Reference to the design brief or strategy]
**Personas:** [Reference to personas this plan serves]
---
## Task 1: [Task Name]
**Files:** [Which files will be created or modified]
- [ ] Step 1: [Specific action]
- [ ] Step 2: [Specific action]
- [ ] Step 3: [Specific action]
**Accessibility check:** [What inclusive design criteria this task must meet]
**Verification:** [How to confirm this task is complete and correct]
---
## Task 2: [Task Name]
...Step 5: Task Sizing
Each task should be:
- 2-5 minutes of focused work — small enough to hold in your head
- Independently reviewable — someone can evaluate it without seeing everything else
- Specifically described — exact files, exact components, exact acceptance criteria
- Accessibility-inclusive — each task addresses its own inclusive design requirements
If a task takes longer than 5 minutes, break it down further.
Show full SKILL.md (147 more words)Show less
Step 6: Save and Review
Save to: docs/designpowers/plans/YYYY-MM-DD-<feature>-plan.md
Present the plan to the user. Walk through:
- Does the task order make sense?
- Are any tasks missing?
- Are the accessibility checks appropriate for each task?
- Is the scope right, or should anything be deferred?
User must approve the plan before execution begins.
Integration
- Called by:
design-discovery,design-strategy - Calls: Implementation begins via the relevant design skills (
ui-composition,interaction-design, etc.) - Pairs with:
designpowers-critique(reviews work against the plan)
Anti-Patterns
| Pattern | Problem |
|---|---|
| Tasks without accessibility checks | Every task affects the user experience. Every task has accessibility implications |
| Tasks that say "make it look good" | Vague tasks produce vague results. Be specific about what "good" means |
| Accessibility as the final task | By then it is too late. Accessibility is in every task |
| Plan without persona references | If you do not know who you are designing for, you cannot verify the design works |
© 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/writing-design-plans of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Writing Design Plans 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 |
|---|---|---|---|---|---|---|
| Writing Design Plans this skillOwl-Listener/designpowers | 251 | — | ~1k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 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 | 26 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 Writing Design Plans
What does Writing Design Plans do?
A skill your agent uses when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task. Writing Design Plans is an agent skill from Owl-Listener/designpowers.
When should I use Writing Design Plans?
Writing Design Plans fits situations like: you have a design brief; strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task.
How do I install Writing Design Plans in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill writing-design-plans -a claude-code`. Or copy the skill folder (skills/writing-design-plans in Owl-Listener/designpowers) into .claude/skills/writing-design-plans in your project. Claude Code loads it when a task matches its description.
How do I install Writing Design Plans in Codex?
Run `npx skills add Owl-Listener/designpowers --skill writing-design-plans -a codex`. Or copy the skill folder (skills/writing-design-plans in Owl-Listener/designpowers) into .agents/skills/writing-design-plans in your project. Codex loads it when a task matches its description.
Can I use Writing Design Plans 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 writing-design-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-design-plans, .gemini/skills/writing-design-plans, .github/skills/writing-design-plans and .opencode/skills/writing-design-plans in your project.
What does Writing Design Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Design Plans is instructions for the agent only.
Does Writing Design Plans 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 Writing Design Plans 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 Writing Design Plans use?
Writing Design Plans 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 Writing Design Plans use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Writing Design Plans?
Skills that share tags, products or a category with Writing Design Plans: 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 Writing Design Plans?
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.