agentleFS
Sign inStart free
CloudChefCloudChef/atlasclaw-providers/skills/brainstorm/SKILL.md

brainstorm

Skill17 starsChanged 6 months agoApache-2.0View on GitHub

Generate ideas fast. Adapt depth and structure to what the user actually needs.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, team-polish and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 11 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 6 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 6 projects that use this

  • +8 more from CoralGame

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When user asks for ideas, generate immediately.

    line 8
  2. Distinctive:

    If context is missing, the ideas will show it — user will clarify naturally.

    line 10
  3. Distinctive:

    Don't force categories. Use structure only when it clarifies:

    line 34
  4. Distinctive:

    If user wants more: go deeper, wider, or different direction.

    line 43
  5. Distinctive:

    If user is silent: they got what they needed.

    line 44
  6. Very specific:

    Check modes.md for different brainstorm approaches.

    line 46
  7. Very specific:

    Check prompts.md for creative expansion techniques.

    line 47

“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

Default: Ideas First

When user asks for ideas, generate immediately. Don't interrogate first.

If context is missing, the ideas will show it — user will clarify naturally.

Adapt to the Request

SignalResponse
"Give me 5 ideas"5 ideas, simple list
"I'm stuck on X"3-5 angles to unstick
"Brainstorm names"10-20 options, varied styles
"Help me think through X"Explore, ask clarifying Qs
"What are my options?"Structured comparison

Match the energy. Quick request → quick response. Deep request → go deep.

Only Ask If

  • Request is genuinely ambiguous (not just incomplete)
  • You're about to invest significant effort
  • Constraints would completely change the output

One question max. Not five.

Structure When It Helps

Don't force categories. Use structure only when it clarifies:

  • Comparisons: Table with trade-offs
  • Many ideas: Group by theme
  • Recommendations: Highlight top pick with reasoning

Flat list is fine for most requests.

After First Round

If user wants more: go deeper, wider, or different direction. If user is silent: they got what they needed. Don't push.

Check modes.md for different brainstorm approaches. Check prompts.md for creative expansion techniques.

Related: For multi-perspective exploration, see diverge. For iteration, see loop.

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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free