brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
replace-with-skill-name-using-hyphensUse when [describe triggering conditions, symptoms, or specific errors].
Independent GitHub snapshot · Automated classification · Original documentation governs
name: replace-with-skill-name-using-hyphens
[1-2 sentences explaining the core principle. What is the fundamental insight of this skill?]
[other-skill-name] instead.[Explain the mental model. Use a before/after code block or a small dot flowchart if the decision process is non-obvious.]
// ❌ Anti-pattern / Baseline failure
[Show the common mistake or naive approach]
// ✅ Best practice / Correct implementation
[Show the correct pattern]
[Clear, numbered steps for the agent to follow. Use imperative verbs.]
[A table for fast lookup of commands, syntax, or common operations.]
| Operation / Scenario | Syntax / Command | Notes |
|---|---|---|
| [Operation] | [Command] | [Note] |
[How to prove the implementation is correct (The GREEN phase). Agent must run these checks.]
[List specific rationalizations, shortcuts, or misunderstandings the agent might have. Address the "RED" phase baseline failures here.]
| Red Flag (Excuse / Mistake) | Reality / Fix (What to do instead) |
|---|---|
| "I'll just skip testing this time." | STOP. You must verify the behavior first. |
| [Mistake or excuse] | STOP. [Correct action] |