design-brain
Skill2 starsChanged 10 months agoMITView on GitHub
设计大脑 - 合并: planner + architect-design 统一处理设计和规划工作: ┌─────────────┐ ┌─────────────┐ │ Component A │────▶│ Component B │ └─────────────┘ └─────────────┘ 原则:好的设计是演进出来的。保持简单,按需扩展。先规划后动手。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- GoodLadTom/design-brain-v2their own version, first seen Sep 6, 2026
- yapeepee/agent-harnessestheir own version, first seen Sep 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- GoodLadTom/design-brain-v2★ 1same name
- yapeepee/agent-harnesses★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/AGENTS.mdAGENTS.md
- template/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .claude/upstream/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- algorithmic-artSkill
- api-testerSkill
- brand-guidelinesSkill
- canvas-designSkill
- code-reviewer-123Skill
- design-auditSkill
- doc-coauthoringSkill
- docxSkill
- frontend-designSkill
- internal-commsSkill
- manus-kickoffSkill
- mcp-builderSkill
- my-skillSkill
- pdfSkill
- pptxSkill
- quality-guardSkill
- quick-fixSkill
- vercel-react-best-practicesSkill
- seo-optimizationSkill
- skill-creatorSkill
- slack-gif-creatorSkill
- technical-cofounderSkill
- template-skillSkill
- test-skill-nameSkill
- theme-factorySkill
- threejs-fundamentalsSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- web-design-guidelinesSkill
- xlsxSkill
The file
Files
Design Brain
设计大脑 - 合并: planner + architect-design
核心职责
统一处理设计和规划工作:
- 需求分析 - 理解和澄清需求
- 架构设计 - 系统设计、技术选型
- 实现规划 - 步骤分解、风险评估
工作模式
模式 1:快速规划(默认)
触发:一般任务
输出:简洁的实现步骤
耗时:< 2 分钟模式 2:深度设计
触发:--deep 或复杂架构决策
输出:完整设计文档
耗时:5-10 分钟快速规划流程
1. 理解需求(30s)
- 核心目标是什么?
- 有哪些约束?
2. 识别依赖(30s)
- 需要修改哪些文件?
- 需要什么外部包?
3. 制定步骤(1min)
- 分解为可验证的小步骤
- 确定步骤顺序深度设计流程
1. 需求分析(2min)
- 功能需求
- 非功能需求(性能、安全、可用性)
- 边界条件
2. 架构设计(3min)
- 组件划分
- 接口定义
- 数据流设计
3. 技术选型(2min)
- 框架/库选择
- 权衡分析
4. 实现规划(3min)
- 详细步骤
- 风险评估
- 测试策略输出格式
快速规划
# Plan: [功能名称]
## Goal
[一句话描述]
## Steps
1. [ ] [步骤 1]
2. [ ] [步骤 2]
3. [ ] [步骤 3]
## Files
- `path/to/file.ts` - [修改内容]
## Risk
- [主要风险] → [缓解策略]深度设计
# Design: [系统/功能名称]
## Overview
[背景和目标]
## Architecture
### Components┌─────────────┐ ┌─────────────┐ │ Component A │────▶│ Component B │ └─────────────┘ └─────────────┘
### Data Flow
[数据如何流动]
## Technical Decisions
### Decision 1: [名称]
- **Choice**: [选择]
- **Reason**: [原因]
- **Alternatives**: [备选方案]
- **Trade-offs**: [权衡]
## Implementation Plan
### Phase 1: [阶段名]
1. [ ] Step 1
2. [ ] Step 2
### Phase 2: [阶段名]
...
## Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
## Success Criteria
- [ ] 标准 1
- [ ] 标准 2设计原则
1. 简单优于复杂
能用简单方案就不要复杂化
避免过度设计
YAGNI - 不需要的就不做2. 最小变更
优先复用现有代码
避免不必要的重构
保持向后兼容3. 可测试性
每个步骤都可验证
定义清晰的成功标准
考虑自动化测试常用设计模式
| 场景 | 推荐模式 |
| 数据访问 | Repository |
| 业务逻辑 | Service Layer |
| 对象创建 | Factory |
| 算法切换 | Strategy |
| 事件驱动 | Observer |
| UI 组件 | Compound Components |
使用方式
# 快速规划(默认)
/plan
# 深度设计
/plan --deep
# 仅架构设计
/plan --arch原则:好的设计是演进出来的。保持简单,按需扩展。先规划后动手。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

