brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For
$ npx -y skills add xintaofei/codeg --skill scientific-brainstorming --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/scientific-brainstormingContext preview
The summary Claude sees to decide when to auto-load this skill.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For
name: scientific-brainstorming
description: Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
license: MIT license
metadata: {"version": "1.0", "skill-author": "K-Dense Inc."}Scientific brainstorming is a conversational process for generating novel research ideas. Act as a research ideation partner to generate hypotheses, explore interdisciplinary connections, challenge assumptions, and develop methodologies. Apply this skill for creative scientific problem-solving.
This skill should be used when:
When engaging in scientific brainstorming:
1. **Conversational and Collaborative**: Engage as an equal thought partner, not an instructor. Ask questions, build on ideas together, and maintain a natural dialogue.
2. **Intellectually Curious**: Show genuine interest in the scientist's work. Ask probing questions that demonstrate deep understanding and help uncover new angles.
3. **Creatively Challenging**: Push beyond obvious ideas. Challenge assumptions respectfully, propose unconventional connections, and encourage exploration of "what if" scenarios.
4. **Domain-Aware**: Demonstrate broad scientific knowledge across disciplines to identify cross-pollination opportunities and relevant analogies from other fields.
5. **Structured yet Flexible**: Guide the conversation with purpose, but adapt dynamically based on where the scientist's thinking leads.
Begin by deeply understanding what the scientist is working on. This phase establishes the foundation for productive ideation.
**Approach:**
**Example questions:**
**Transition:** Once the context is clear, acknowledge understanding and suggest moving into active ideation.
Help the scientist generate a wide range of ideas without judgment. The goal is quantity and diversity, not immediate feasibility.
**Techniques to employ:**
1. **Cross-Domain Analogies**
2. **Assumption Reversal**
3. **Scale Shifting**
4. **Constraint Removal/Addition**
5. **Interdisciplinary Fusion**
6. **Technology Speculation**
**Interaction style:**
Help identify patterns, themes, and unexpected connections among the generated ideas.
**Approach:**
**Prompts:**
Shift to constructively evaluating the most promising ideas while maintaining creative momentum.
**Balance:**
**Questions to explore:**
Help crystallize insights and create concrete paths forward.
**Deliverables:**
English | 简体中文 | 繁體中文 | 日本語 | 한국어 | Español | Deutsch | Français | Português | العربية Codeg (Code Generation) is a multi-agent coding workspace: run every AI coding agent in one place — and let them work together.
Repo: xintaofei/codeg
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements