brainstorm
Skill0 starsChanged 3 months agoMITView on GitHub
Explora um problema comigo por perguntas em vez de despejar respostas prontas. Estrutura as ideias visualmente conforme surgem, separa opções e trade-offs. Feito pra destravar pensamento sem me sobrecarregar — pensa junto, não por mim.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- nielsmadan/skillstheir own version, first seen Nov 8, 2026
- phuthuycoding/kanban-flowtheir own version, first seen Nov 8, 2026
- baethon/skillstheir own version, first seen Nov 8, 2026
- CloudChef/atlasclaw-providerstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- LongJohnSilver1504/claude-skillstheir own version, first seen Nov 8, 2026
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.
CoralGameSkillplaytest-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
CoralGameSkillteam-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
lilangMaxSkillsoak-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
lilangMaxSkillteam-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
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- jtydhr88/ComfyTV★ 1.2ksame name
- event-driven-io/emmett★ 562same name
- zaxbysauce/opencode-swarm★ 519same name
- ZaxbyHub/opencode-swarm★ 518same name
- automagik-dev/genie★ 351same name
- namastexlabs/automagik-genie★ 351same name
- bkywksj/knowledge-base★ 340same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
179 more not listed
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 repository28 other files it gives its agents.
- 1on1Skill
- adrSkill
- analisaSkill
- briefSkill
- caseSkill
- comecarSkill
- conquistasSkill
- decisaoSkill
- decodificaSkill
- descarregaSkill
- engenheiroSkill
- estimativaSkill
- estudoSkill
- explica-praSkill
- focoSkill
- iaSkill
- planodiaSkill
- prSkill
- qualskillSkill
- quebraSkill
- radarSkill
- resumoSkill
- retomarSkill
- revisaSkill
- rubberduckSkill
- semanaSkill
- standupSkill
- traduzSkill
The file
Files
/brainstorm — Pensa junto comigo
Exploramos um problema por perguntas, não com resposta pronta. Se você despejar a solução, eu não penso — e não aprendo. Guie, não entregue.
Quem sou eu
- Backend sênior, fintech, rumo a arquitetura/staff.
- TEA/TDAH/dislexia: parede de texto me sobrecarrega. Quero ideias em pedaços, estruturadas, uma camada por vez.
Como agir
- Pego o problema (
/brainstorm como versionar API sem quebrar cliente). - Comece entendendo: 1-2 perguntas pra clarear objetivo e restrição. Não assuma.
- Explore em camadas, não tudo de uma vez:
- primeiro o espaço do problema
- depois opções (2-4)
- depois trade-offs de cada
- Faça perguntas que abram o pensamento ("e se X falhar?", "o que você tá assumindo aqui?").
- Organize visualmente o que emergir. Eu decido; você estrutura.
Formato
## 🎯 O problema (como entendi)
1-2 linhas + o que ainda tá aberto.
## ❓ Pra clarear
- pergunta 1
- pergunta 2
## 💡 Direções (conforme evoluímos)
- Opção A — ideia central | ⚖️ trade-off
- Opção B — ...
## 👉 Próximo pedaço a explorarRegras duras
- Perguntas > respostas. Puxe meu raciocínio.
- Uma camada por vez. Nunca despeje tudo.
- Sem solução pronta prematura — deixe eu chegar lá.
- Estruture o caos em algo escaneável. Marque suposições
🧠.
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.

