ワンクリックで
init-design-config
Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | init-design-config |
| description | Initialize DESIGN-AGENTS.md config for the /design workflow, populated from project context. |
| disable-model-invocation | true |
| allowed-tools | Read, Grep, Glob, Write |
Initialize a memory-bank/DESIGN-AGENTS.md configuration file for the /design workflow, populated with values discovered from project context.
Check if memory-bank/DESIGN-AGENTS.md already exists.
If it exists, report to user and ask if they want to overwrite or abort.
Gather information from the project to populate the configuration:
Design System File:
**/design-system*.md, **/design-spec*.md, **/*-design*.mddocs/, agent-docs/, memory-bank/ directories[path/to/design-system.md - remove if none]Requirements File:
memory-bank/*requirements*.md, memory-bank/*REQUIREMENTS*.mddocs/*requirements*.md, **/PRD*.md[auto-detected from memory-bank/*requirements*.md]Existing Project Agents:
.claude/agents/ directory existsProject Type (for suggestions):
tsconfig.json → suggest TypeScript-related agentsapp.json with expo → suggest mobile-related agents.kiro/steering/tech.md for domain hintsCreate the DESIGN-AGENTS.md content:
# Design Agents Configuration
This file configures project-specific agents for the `/design` workflow.
## Configuration
Optional settings for the design workflow:
- design-system-file: [discovered path or placeholder]
- requirements-file: [discovered path or placeholder]
## Research Agents
Domain experts that gather information during Phase 2 (before design synthesis).
These agents run in parallel to research specific aspects of the problem domain.
Add entries as: `- agent-name: Brief description of expertise`
[If domain hints found from steering files, add suggestions as comments:]
<!-- Suggested based on project context:
- [domain]-expert-agent: Researches [domain] best practices and patterns
-->
## Review Agents
Additional reviewers beyond the universal agents that run during Phase 4.
These agents evaluate the design draft for project-specific concerns.
Add entries as: `- agent-name: Brief description of what it reviews`
[If existing project agents found, list them as suggestions:]
<!-- Existing agents in .claude/agents/ that could be added:
- [agent-name]: [description if available]
-->
<!-- Common review agents to consider:
- security-review-agent: Reviews for authentication, authorization, and data protection
- performance-review-agent: Reviews for performance bottlenecks and optimization opportunities
- accessibility-review-agent: Reviews for WCAG compliance and inclusive design
-->
If memory-bank/ directory doesn't exist, create it.
Write the generated content to memory-bank/DESIGN-AGENTS.md.
Report to the user:
## DESIGN-AGENTS.md Initialized
**Location**: memory-bank/DESIGN-AGENTS.md
### Discovered Values
- **Design System**: [path found | not found - placeholder added]
- **Requirements**: [path found | not found - will auto-detect]
### Next Steps
1. Review and update `memory-bank/DESIGN-AGENTS.md`
2. Remove placeholder comments for unused sections
3. Add project-specific research and review agents:
- Use `/add-design-agent` to create new agents
- Or manually add existing agents from `.claude/agents/`
4. Run `/design` to start the design workflow
### Universal Agents (always included)
The following agents run automatically for all projects:
- requirements-validation-agent
- software-engineering-agent
- simplicity-advocate-agent
- testing-strategy-agent
- ux-usability-agent
### Conditional Agents (auto-detected)
These agents are included based on project type:
[List which conditional agents will be included based on detection]
- [If TypeScript]: typescript-type-safety-agent ✓
- [If Expo]: expo-best-practices-agent ✓
- [If design system configured]: design-system-agent ✓
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.