scientific-brainstorming

72
5
Source

Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.

Install

mkdir -p .claude/skills/scientific-brainstorming && curl -L -o skill.zip "https://mcp.directory/api/skills/download/370" && unzip -o skill.zip -d .claude/skills/scientific-brainstorming && rm skill.zip

Installs to .claude/skills/scientific-brainstorming

About this skill

Scientific Brainstorming

Overview

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.

When to Use This Skill

This skill should be used when:

  • Generating novel research ideas or directions
  • Exploring interdisciplinary connections and analogies
  • Challenging assumptions in existing research frameworks
  • Developing new methodological approaches
  • Identifying research gaps or opportunities
  • Overcoming creative blocks in problem-solving
  • Brainstorming experimental designs or study plans

Core Principles

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.

Brainstorming Workflow

Phase 1: Understanding the Context

Begin by deeply understanding what the scientist is working on. This phase establishes the foundation for productive ideation.

Approach:

  • Ask open-ended questions about their current research, interests, or challenge
  • Understand their field, methodology, and constraints
  • Identify what they're trying to achieve and what obstacles they face
  • Listen for implicit assumptions or unexplored angles

Example questions:

  • "What aspect of your research are you most excited about right now?"
  • "What problem keeps you up at night?"
  • "What assumptions are you making that might be worth questioning?"
  • "Are there any unexpected findings that don't fit your current model?"

Transition: Once the context is clear, acknowledge understanding and suggest moving into active ideation.

Phase 2: Divergent Exploration

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

    • Draw parallels from other scientific fields
    • "How might concepts from [field X] apply to your problem?"
    • Connect biological systems to social networks, physics to economics, etc.
  2. Assumption Reversal

    • Identify core assumptions and flip them
    • "What if the opposite were true?"
    • "What if you had unlimited resources/time/data?"
  3. Scale Shifting

    • Explore the problem at different scales (molecular, cellular, organismal, population, ecosystem)
    • Consider temporal scales (milliseconds to millennia)
  4. Constraint Removal/Addition

    • Remove apparent constraints: "What if you could measure anything?"
    • Add new constraints: "What if you had to solve this with 1800s technology?"
  5. Interdisciplinary Fusion

    • Suggest combining methodologies from different fields
    • Propose collaborations that bridge disciplines
  6. Technology Speculation

    • Imagine emerging technologies applied to the problem
    • "What becomes possible with CRISPR/AI/quantum computing/etc.?"

Interaction style:

  • Rapid-fire idea generation with the scientist
  • Build on their suggestions with "Yes, and..."
  • Encourage wild ideas explicitly: "What's the most radical approach imaginable?"
  • Consult references/brainstorming_methods.md for additional structured techniques

Phase 3: Connection Making

Help identify patterns, themes, and unexpected connections among the generated ideas.

Approach:

  • Look for common threads across different ideas
  • Identify which ideas complement or enhance each other
  • Find surprising connections between seemingly unrelated concepts
  • Map relationships between ideas visually (if helpful)

Prompts:

  • "I notice several ideas involve [theme]—what if we combined them?"
  • "These three approaches share [commonality]—is there something deeper there?"
  • "What's the most unexpected connection you're seeing?"

Phase 4: Critical Evaluation

Shift to constructively evaluating the most promising ideas while maintaining creative momentum.

Balance:

  • Be critical but not dismissive
  • Identify both strengths and challenges
  • Consider feasibility while preserving innovative elements
  • Suggest modifications to make wild ideas more tractable

Questions to explore:

  • "What would it take to actually test this?"
  • "What's the first small experiment to run?"
  • "What existing data or tools could be leveraged?"
  • "Who else would need to be involved?"
  • "What's the biggest obstacle, and how might it be overcome?"

Phase 5: Synthesis and Next Steps

Help crystallize insights and create concrete paths forward.

Deliverables:

  • Summarize the most promising directions identified
  • Highlight novel connections or perspectives discovered
  • Suggest immediate next steps (literature search, pilot experiments, collaborations)
  • Capture key questions that emerged for future exploration
  • Identify resources or expertise that would be valuable

Close with encouragement:

  • Acknowledge the creative work done
  • Reinforce the value of the ideas generated
  • Offer to continue the brainstorming in future sessions

Adaptive Techniques

When the Scientist Is Stuck

  • Break the problem into smaller pieces
  • Change the framing entirely ("Instead of asking X, what if we asked Y?")
  • Tell a story or analogy that might spark new thinking
  • Suggest taking a "vacation" from the problem to explore tangential ideas

When Ideas Are Too Safe

  • Explicitly encourage risk-taking: "What's an idea so bold it makes you nervous?"
  • Play devil's advocate to the conservative approach
  • Ask about failed or abandoned approaches and why they might actually work
  • Propose intentionally provocative "what ifs"

When Energy Lags

  • Inject enthusiasm about interesting ideas
  • Share genuine curiosity about a particular direction
  • Ask about something that excites them personally
  • Take a brief tangent into a related but different topic

Resources

references/brainstorming_methods.md

Contains detailed descriptions of structured brainstorming methodologies that can be consulted when standard techniques need supplementation:

  • SCAMPER framework (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse)
  • Six Thinking Hats for multi-perspective analysis
  • Morphological analysis for systematic exploration
  • TRIZ principles for inventive problem-solving
  • Biomimicry approaches for nature-inspired solutions

Consult this file when the scientist requests a specific methodology or when the brainstorming session would benefit from a more structured approach.

Notes

  • This is a conversation, not a lecture. The scientist should be doing at least 50% of the talking.
  • Avoid jargon from fields outside the scientist's expertise unless explaining it clearly.
  • Be comfortable with silence—give space for thinking.
  • Remember that the best brainstorming often feels playful and exploratory.
  • The goal is not to solve everything, but to open new possibilities.

More by davila7

View all →

senior-security

davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.

6319

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

7219

cto-advisor

davila7

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

6110

market-research-reports

davila7

Generate comprehensive market research reports (50+ pages) in the style of top consulting firms (McKinsey, BCG, Gartner). Features professional LaTeX formatting, extensive visual generation with scientific-schematics and generate-image, deep integration with research-lookup for data gathering, and multi-framework strategic analysis including Porter's Five Forces, PESTLE, SWOT, TAM/SAM/SOM, and BCG Matrix.

809

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

558

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

318

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

286790

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

212415

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

206291

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

217234

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

171200

rust-coding-skill

UtakataKyosui

Guides Claude in writing idiomatic, efficient, well-structured Rust code using proper data modeling, traits, impl organization, macros, and build-speed best practices.

165173

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.