Loading...
Loading...
Found 166 Skills
A cross-cutting cognitive mode for sitting with design problems before rushing to solve them. Part of the Intent design strategy system. Activates expansive brainstorming: hyperassociativity, beginner's mind, cross-domain pattern recognition, and suppression of premature idea-dismissal. Works alongside every Intent skill — strategize uses it to reframe briefs, blueprint to question structural assumptions, journey to rethink interaction models, and specify to stress-test specs. Trigger when the user invokes "expansive mode", "philosopher mode", "sit with this", "brainstorm", "explore this problem", or says things like "go weird with it", "don't filter yourself", "what connections are you not making", "think about this differently", or "I'm stuck". This is a reasoning protocol, not a persona — Claude's voice stays grounded but the cognitive process changes significantly.
Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
Create hierarchical mind maps using PlantUML @startmindmap syntax. Best for brainstorming, topic decomposition, study notes, and decision trees with automatic radial layout, left/right branches, and per-node styling.
Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".
Use when brainstorming, evaluating architecture choices, or comparing trade-offs where independent perspectives from different model families (Claude/Codex/Gemini) would surface blind spots
Use when the user wants to use Google Gemini for analysis, large files or codebases, sandbox execution, or brainstorming. Uses headless Gemini CLI scripts (no MCP). Triggers on "use Gemini", "analyze with Gemini", "large file", "sandbox", "brainstorm with Gemini".
ALWAYS use this skill before answering brainstorming, ideation, prompt crafting, or open-ended exploration requests. Transforms vague requests into actionable outputs via adaptive guided questioning — triages into Prompt Mode (craft/improve prompts), Explore Mode (brainstorm ideas), or Focused Mode (specific problem strategies). Trigger when user says: "brainstorm", "ช่วยคิด", "help me think", "I have an idea", "improve this prompt", "let's explore", "I want to build", "I'm thinking about", "brainstorm วิธี", "ช่วยคิดหน่อย", "อยากทำ", "ยังไม่รู้จะทำอะไร", "not sure about the approach", "help me figure out", "what should I". Also trigger for: side projects, career decisions, project planning, migration strategies, architecture decisions, cost optimization, or any request where the user hasn't decided direction yet and would benefit from structured discovery. Do NOT skip — this skill adapts depth automatically (2-7 questions) and produces BETTER results by asking targeted questions first.
This skill should be used when the user asks to "ideate on", "brainstorm an idea", "let's argue this through", "challenge my thinking", "help me refine this concept", "let's stress-test this", or needs a structured framework for collaborative idea generation, adversarial refinement, and convergence toward the best possible solution. Load this skill before running any ideation or brainstorming session.
Use this skill when the user needs help with personal writing — either starting a new piece from scratch (inspiration/brainstorming) or reviewing and polishing an existing article (proofreading/editing). Invoke immediately when: the user shares an article and asks for feedback, wants to improve their writing style, feels stuck on what to write, wants help structuring a travel piece/TIL note/personal essay, or asks to review Chinese writing quality. Trigger phrases: 帮我改文章, 检查一下, 润色, 校对, 不知道写什么, 帮我构思, 写游记, 记录 TIL, 写点什么. NOT for diary writing (use diary-assistant) or formal business communications.
Personalized brainstorming agent that generates sellable utility ideas (CLI, TUI, GUI, agent tools) tailored to the user's stack and niche, with persistent memory of past suggestions. Triggered by: /spark.
Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with bkit PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and applying YAGNI review before document generation. Use proactively when user mentions planning with brainstorming, intent discovery, exploring alternatives, or wants a more thorough planning process. Triggers: plan-plus, plan plus, brainstorming plan, enhanced plan, deep plan, 플랜 플러스, 브레인스토밍, 기획, 의도 탐색, 대안 탐색, プランプラス, ブレインストーミング, 企画, 意図探索, 计划加强, 头脑风暴, 深度规划, 意图探索, plan mejorado, lluvia de ideas, planificación profunda, plan amélioré, remue-méninges, planification approfondie, erweiterter Plan, Brainstorming, vertiefte Planung, piano migliorato, brainstorming, pianificazione approfondita Do NOT use for: simple tasks that don't need planning, code-only changes.
Use only when the user explicitly requests brainstorming, evaluating architecture choices, or comparing options where no single concern dominates