with one click
add-design-agent
Create a research or review agent for the /design workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Create a research or review agent for the /design workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add terms, context, or instructions to Shama voice-to-text files for clipboard mode (Ctrl+Opt+Space) or shell-command mode (Ctrl+Opt+S), at project or global level.
Initialize Shama voice-to-text config for the project — create voice.json, voice-vocabulary.md, voice-context.md, and register the project in Shama's registry.toml.
Reflect on codebase navigation effectiveness at end of conversation. Surfaces dead ends, inefficiencies, missing context. Does not write files — pair with /kiro:steering-custom to persist.
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
| name | add-design-agent |
| description | Create a research or review agent for the /design workflow. |
Create a new project-specific design agent that integrates with the /design workflow.
$1: Agent type (optional) - "research" or "review"
$2: Agent name (optional) - Name for the agent (will be suffixed with -agent)If $1 is not provided or not "research" or "review", ask the user:
Use AskUserQuestion with:
Use AskUserQuestion to gather:
Question 1: Agent Name
$2 was provided, skip this question and use $2Question 2: Domain/Expertise
Question 3: Key Responsibilities
Use the plugin-dev:agent-development skill to create the agent.
Provide this context to the skill:
Create a design workflow agent with these specifications:
**Type**: [research|review]
**Name**: [agent-name]-agent
**Domain**: [user's expertise description]
**Responsibilities**: [user's selected/described responsibilities]
**Requirements**:
1. Frontmatter must include:
- name: [agent-name]-agent
- description: Use this agent when [appropriate triggering conditions based on type and domain]
- model: sonnet
- color: [choose appropriate color - not already used by universal agents: magenta, gray, blue, red, cyan, yellow, orange]
- tools: Read, Grep, Glob, Write [add WebSearch, WebFetch if research agent]
2. System prompt must include:
- Clear role description as [research expert | reviewer] in [domain]
- Core responsibilities (3-5 items based on user input)
- Process/methodology for [researching | reviewing]
- Output format following design workflow conventions:
For RESEARCH agents:
```markdown
# [Agent Name] Research
## Executive Summary
[2-3 sentences on key findings]
## Key Findings
### [Finding 1]
- Observation
- Implications
- Recommendation
## Recommendations
[Prioritized list]
## Tradeoffs and Alternatives
[Options considered, why recommendations chosen]
## References
[Sources consulted]
```
For REVIEW agents:
```markdown
# [Agent Name] Review
## Summary
[1-2 sentence assessment]
## Critical Issues
### [Issue 1]
- Location: [where]
- Problem: [what]
- Impact: [why it matters]
- Recommendation: [how to fix]
## Major Issues
[Same format]
## Minor Issues
[Same format]
## Suggestions
[Nice-to-haves]
## What's Working Well
[Positive aspects]
```
3. The agent will be saved to: .claude/agents/[agent-name]-agent.md
Save the generated agent file to .claude/agents/[agent-name]-agent.md.
Create the .claude/agents/ directory if it doesn't exist.
Check if memory-bank/DESIGN-AGENTS.md exists.
If it doesn't exist:
${CLAUDE_PLUGIN_ROOT}/resources/design-agents-template.mdIf it exists:
- [agent-name]-agent: [brief description of expertise]Report to the user:
## Design Agent Created
**Agent**: [agent-name]-agent
**Type**: [Research|Review]
**Location**: .claude/agents/[agent-name]-agent.md
**Added to**: memory-bank/DESIGN-AGENTS.md
### Next Steps
1. Review the agent at `.claude/agents/[agent-name]-agent.md`
2. Customize the system prompt if needed
3. Run `/design` to use the new agent in your design workflow
The agent will automatically be included in:
- [If research]: Phase 2 (Research) of new design workflows
- [If review]: Phase 4 (Review) of both new design and iteration workflows
.claude/agents/ cannot be created, report error and suggest manual creation