用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/InugamiDev/ultrathink-oss --skill brainstorm命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
Unified design foundations — design system architecture, tokens, component specs, visual principles, creative vision, figma integration, plus brand design system loader (66 real brands via DESIGN.md). Absorbs design, design-system, design-systems, design-principles, design-router, creative-vision, figma, design-md.
Render, summarize, and present markdown documents and structured content in multiple output modes
Ultra UI skill - combines Google's DESIGN.md spec (machine-readable design tokens) with the ui-ux-pro-max knowledge base (91 styles, 161 palettes, 73 font pairings, 161 products, 104 UX guidelines, 25 chart types). Generates lint-clean DESIGN.md files, validates token references and WCAG contrast, exports Tailwind/DTCG tokens, and diffs design systems version-over-version.
基于 SOC 职业分类
正在显示 SKILL.md
| name | brainstorm |
| description | Structured ideation with constraint mapping, divergent exploration, and convergent selection |
| layer | hub |
| category | workflow |
| triggers | ["/brainstorm","brainstorm ideas","what are the options","how could we approach this","explore alternatives","think of ways to"] |
| inputs | [{"challenge":"The problem, question, or goal to brainstorm about"},{"constraints":"Hard constraints that solutions must satisfy (optional)"},{"preferences":"Soft preferences to guide selection (optional)"},{"quantity":"Number of ideas to generate (optional, default 5-7)"}] |
| outputs | [{"constraintMap":"Explicit map of hard constraints, soft preferences, and degrees of freedom"},{"ideas":"Ranked list of ideas with descriptions, tradeoffs, and feasibility notes"},{"recommendation":"Top 1-3 recommended approaches with reasoning"},{"nextSteps":"Concrete actions to move from ideation to execution"}] |
| linksTo | ["plan","research","scout"] |
| linkedFrom | ["plan","cook","team"] |
| preferredNextSkills | ["plan","research","scout"] |
| fallbackSkills | ["research"] |
| riskLevel | low |
| memoryReadPolicy | selective |
| memoryWritePolicy | selective |
| sideEffects | ["Produces ideation document in working memory","May invoke research for domain knowledge"] |
Generate diverse, well-structured ideas for solving a problem or approaching a challenge. This skill separates divergent thinking (generating options) from convergent thinking (selecting the best ones) to prevent premature optimization of the solution space.
The goal is not to find THE answer. The goal is to find the right set of options and make the tradeoffs visible so the best decision can be made.
Restate the challenge in precise terms. Often the way a problem is framed determines what solutions are visible.
Build the constraint map:
Identify the decision type:
Generate ideas using multiple lenses:
Lens 1: Direct solutions -- What is the most straightforward way to solve this?
Lens 2: Analogies -- How has this type of problem been solved in other domains?
Lens 3: Inversion -- Instead of solving the problem, what if we removed the conditions that create it?
Lens 4: Decomposition -- Can the problem be broken into subproblems that are each easier to solve?
Lens 5: Extreme positions -- What would the solution look like if we optimized for only ONE dimension (speed, simplicity, flexibility, cost)?
Lens 6: Existing solutions -- What off-the-shelf tools, libraries, or patterns already solve this?
Lens 7: Future-backward -- If this were already solved, what would the solution look like? Work backward from there.
For each idea, capture:
Do not judge during generation -- In this phase, quantity beats quality. Even "bad" ideas can spark good ones.
Filter by hard constraints -- Remove any ideas that violate hard constraints.
Score remaining ideas against soft preferences and practical criteria:
Rank ideas and identify the top 1-3 recommendations.
For each recommendation, provide:
plan to flesh out the chosen approach, or research to investigate unknowns.# Brainstorm: [Challenge Title]
## Challenge
[Precise problem statement]
## Constraint Map
### Hard Constraints
- [constraint 1]: [why it is non-negotiable]
- [constraint 2]: [why it is non-negotiable]
### Soft Preferences
- [preference 1]: [importance level]
- [preference 2]: [importance level]
### Degrees of Freedom
- [dimension 1]: [range of options]
- [dimension 2]: [range of options]
### Assumptions (worth questioning)
- [assumption 1]: What if this is wrong?
- [assumption 2]: What if this is wrong?
---
## Ideas
### Idea 1: [Name]
**Description**: [2-3 sentences]
**Tradeoffs**: Gains [X], gives up [Y]
**Feasibility**: [Low/Medium/High] — [brief reasoning]
**Constraints met**: [list]
### Idea 2: [Name]
...
### Idea 3: [Name]
...
(continue for all ideas)
---
## Comparison Matrix
| Idea | Impact | Effort | Risk | Flexibility | Score |
|------|--------|--------|------|-------------|-------|
| [1] | High | Medium | Low | High | ★★★★ |
| [2] | Medium | Low | Low | Medium | ★★★ |
| [3] | High | High | Med | Low | ★★★ |
---
## Recommendations
### Top Pick: [Idea Name]
**Why**: [reasoning]
**Key risk**: [main concern]
**First step**: [concrete action]
**Reconsider if**: [condition that would change this choice]
### Runner-up: [Idea Name]
**Why**: [when this would be the better choice]
---
## Next Steps
- [ ] [action 1] (via [skill])
- [ ] [action 2]
/brainstorm How should we handle real-time notifications in the app?
/brainstorm How to implement search functionality?
Constraints: Must use existing PostgreSQL database, no Elasticsearch, must support fuzzy matching
Preferences: Fast implementation over perfect accuracy
/brainstorm Should we use a monorepo or polyrepo for the new microservices?
/brainstorm Our API response times are over 2 seconds. What are our options for improving them?
Challenge: "How should we handle real-time notifications?"
Ideas generated:
Recommendation: Start with SSE + long-poll fallback (simplest to implement and sufficient for notification use case). Migrate to WebSocket only if bidirectional communication becomes needed.