azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

skills(brainstorming): make request-only, not auto-trigger

Browse Source 
Upstream description ("You MUST use this before any creative work...") would
auto-fire the brainstorming skill on routine feature/code work. Rewrote the
frontmatter description to invoke ONLY when the user explicitly asks to
brainstorm/design. Methodology body (incl. HARD-GATE) unchanged. Noted in SOURCE.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-06-16 19:59:22 -07:00
parent 6122efe98c
commit a073f66b92
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.claude/skills/brainstorming/SKILL.md
View File

@@ -1,6 +1,6 @@
---
name: brainstorming
description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
description: "Invoke ONLY when the user explicitly asks to brainstorm / shape an idea (e.g. 'brainstorm this', 'let's design X', '/brainstorming'). Turns a rough idea into a fully formed design/spec through collaborative one-question-at-a-time dialogue before implementation. Do NOT auto-trigger on routine feature/code work."
---
# Brainstorming Ideas Into Designs

1
.claude/skills/brainstorming/SOURCE.md
View File

@@ -10,6 +10,7 @@ Harvested from obra/superpowers (MIT, Copyright (c) 2025 Jesse Vincent) at commi
- No emojis were present in the source.
- Added a `NOTE (ClaudeTools)` block near the top recording that the optional visual brainstorming server was intentionally omitted and that this is imported as a methodology reference.
- No content was otherwise reworded; the brainstorming methodology is preserved as in the source apart from the normalization and the added note.
- **Trigger changed (ClaudeTools, 2026-06-17):** the upstream `description` ("You MUST use this before any creative work...") auto-fired on routine feature/code work. Rewrote it to **request-only** - the skill now invokes only when the user explicitly asks to brainstorm/design. The methodology body (incl. the HARD-GATE) is unchanged; it just no longer self-triggers.
## Omitted upstream tooling (intentional)
The optional visual brainstorming companion/server was NOT imported. Specifically, none of the following were fetched or included: