agentleFS
Sign inStart free
VoTruongDanhVoTruongDanh/Skills-Agent/.cursor/skills/brainstorm/SKILL.md

brainstorm

Skill4 starsChanged 33 days agoMITView on GitHub

Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án.

We split this skill into the rules it gives an agent

16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    START: Read .ai-memory.md from project root.

    line 10
  2. Very specific:

    END: Update .ai-memory.md using Memory Compaction Rules with: problem, options considered, chosen direction, constraints, and new project …

    line 11
  3. Very specific:

    If brainstorm involves system architecture → read .kiro/skills/agents/agents/project-planner.md and apply its knowledge

    line 17
  4. Very specific:

    If brainstorm spans multiple domains → read .kiro/skills/agents/agents/orchestrator.md and apply its knowledge

    line 18
  5. Very specific:

    If brainstorm is about UI/UX → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge

    line 19
  6. Very specific:

    If brainstorm is about APIs/backend → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge

    line 20
  7. Distinctive:

    Before generating options, verify:

    line 23
  8. Distinctive:

    If any answer is unclear, ASK before proceeding.

    line 27
  9. Distinctive:

    Call out the most practical option and the boldest option.

    line 34
  10. Distinctive:

    Prefer practical ideas grounded in the current project.

    line 58
  11. Distinctive:

    Avoid pretending uncertain assumptions are facts.

    line 59
  12. Distinctive:

    If code context matters, inspect the repo structure first.

    line 60
  13. Distinctive:

    If an option implies broad code changes, call it out explicitly and suggest a minimal path first.

    line 61
  14. Distinctive:

    Always read and update the memory file.

    line 62
  15. Very specific:

    After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.

    line 65
  16. Very specific:

    All code snippets and example files referenced or produced by this skill must be UTF-8 encoded.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Memory Protocol

START: Read .ai-memory.md from project root. Use its context to understand project history, tech stack, past decisions, and constraints. If missing, note this and create it after completing this task. END: Update .ai-memory.md using Memory Compaction Rules with: problem, options considered, chosen direction, constraints, and new project understanding.

Goal

Help the user explore many realistic options before implementation.

Agent Routing

  • If brainstorm involves system architecture → read .kiro/skills/agents/agents/project-planner.md and apply its knowledge
  • If brainstorm spans multiple domains → read .kiro/skills/agents/agents/orchestrator.md and apply its knowledge
  • If brainstorm is about UI/UX → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
  • If brainstorm is about APIs/backend → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge

Socratic Gate

Before generating options, verify:

  1. What problem are we solving? (clarity check)
  2. What constraints exist? (budget, time, tech stack, team)
  3. Who are the users/stakeholders? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for project context.
  2. Restate the problem in one or two sentences.
  3. Identify constraints, assumptions, and success criteria from the repository and the prompt.
  4. Produce 3-7 strong options with pros, cons, complexity, and risks.
  5. Call out the most practical option and the boldest option.
  6. End with a recommended next step or implementation path.
  7. Update Memory — Save new understanding to .ai-memory.md.

Output format

  • Problem framing
  • Constraints
  • Options (3-7 with pros/cons/complexity/risk for each)
  • Recommendation (most practical + boldest)
  • Next step

Checklist

  • Problem clearly restated
  • Constraints identified from repo + prompt
  • At least 3 viable options generated
  • Each option has pros, cons, complexity rating
  • Practical and bold options highlighted
  • Next step recommended
  • Memory file updated
  • Clean code chuẩn (Standard clean code applied)
  • Cập nhật đầy đủ tất cả các file liên quan (All related files fully updated)

Rules

  • Prefer practical ideas grounded in the current project.
  • Avoid pretending uncertain assumptions are facts.
  • If code context matters, inspect the repo structure first.
  • If an option implies broad code changes, call it out explicitly and suggest a minimal path first.
  • Always read and update the memory file.

Quality Gate

After completing, read .kiro/skills/_scripts/checklist.md for cross-cutting quality checks.

Encoding

All code snippets and example files referenced or produced by this skill must be UTF-8 encoded. When applicable, include encoding: "UTF-8" in SKILL.md front-matter and ensure saved files use UTF-8 (no BOM).

Related Skills

  • /plan → read .kiro/skills/plan/SKILL.md — Turn chosen option into actionable plan
  • /create → read .kiro/skills/create/SKILL.md — Implement the chosen option
  • /orchestrate → read .kiro/skills/orchestrate/SKILL.md — Coordinate multi-domain brainstorm results

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free