菜单
How to think about design — product outcomes, system architecture, code structure, tradeoffs
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
| name | planner-design-k |
| type | knowledge |
| description | How to think about design — product outcomes, system architecture, code structure, tradeoffs |
| user-invocable | false |
Knowledge skill — Design thinking framework: product outcomes, system architecture, code structure, tradeoffs.
Start from the user, not the code:
When the change affects boundaries, data flow, or integration points:
Diagram first, prose second. Every system-level design must lead with visuals:
Required visuals (pick what fits):
┌─────────────────────────────────────────────────────┐
│ Component diagram — boxes, arrows, boundaries │
│ Data flow diagram — how data moves through │
│ Sequence diagram — who calls who, in what order │
│ State diagram — states and transitions │
│ Dependency graph — what depends on what │
└─────────────────────────────────────────────────────┘
Prose explains the why behind the diagram. No code snippets in design plans — describe interfaces and contracts in words or type signatures, not implementations.
When designing how code should be structured:
Prefer the boring obvious solution. Three similar functions is often better than a premature abstraction.
Every major decision should present 2-3 realistic approaches:
Frame as tradeoffs, not pros/cons lists. Every choice trades something for something else.