メニュー
Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook fits. Sensors and evals gate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Visual + UX design defaults for new UIs. Material Design 3, dark/light theme, modern type, Behance-grade polish, i18n (en, pt-BR, es), context-aware favicon. No emojis and no em-dashes; use MD3/modern icons instead. Apply when building something new. Project conventions in .claude/conventions/web.md override these defaults.
Re-install / upgrade harness-kit in the current project to the version bundled in the installed plugin. Run after /plugin update harness-kit fetches a newer plugin version.
Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and eval gates.
Install the harness-kit pipeline into the current project. Copies agents, slash commands, skills, hooks, and the status bar into the project's .claude/, plus AGENTS.md and CLAUDE.md at the repo root. Run after adding the harness-kit plugin from the marketplace.
Design a distributed rate limiter at scale, policy model, enforcement layers (edge/gateway/service), algorithms (token bucket, sliding window), hot keys, fail-open vs fail-closed, multi-region, shadow mode. Topic playbook from the System Design series EP (Rate Limit
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.
| name | design |
| description | Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook fits. Sensors and evals gate. |
| user_invocable | true |
Produce a System Design Doc for an arbitrary system. Follow guides/pipeline.md for retry and approval.
Ask once if missing: system in 1-2 sentences, scale target (users / QPS / data / latency SLO), internal vs web-scale, known constraints.
Route first. If the problem matches a topic playbook under
.claude/agents/system-architect/skills/{topic}/SKILL.md (e.g. search-engine), use that skill
instead, it carries a canned reference architecture. This generic skill is the fallback when no
topic fits.
Compute feature_id = {YYYY-MM-DD}-{slug}.
Read:
Generate the SDD: walk all 13 stages of the template. Every non-functional claim carries a number. Show back-of-envelope math. Name a trade-off per major choice. Mermaid for flow and architecture.
Save to .claude/runtime/outputs/architect/design/{feature_id}.md.
Sensors: sensors/design-structure.md, sensors/design-rigor.md. Evals: evals/design-quality.md.
After save reply: Design saved at {path}. Score: {N}/10. Then offer /system-design:review.
