hypothesis-generation
Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.
What this skill does
# Scientific Hypothesis Generation ## Overview Hypothesis generation is a systematic process for developing testable explanations. Formulate evidence-based hypotheses from observations, design experiments, explore competing explanations, and develop predictions. Apply this skill for scientific inquiry across domains. ## When to Use This Skill This skill should be used when: - Developing hypotheses from observations or preliminary data - Designing experiments to test scientific questions - Exploring competing explanations for phenomena - Formulating testable predictions for research - Conducting literature-based hypothesis generation - Planning mechanistic studies across scientific domains ## Visual Enhancement with Scientific Schematics **⚠️ MANDATORY: Every hypothesis generation report MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.** This is not optional. Hypothesis reports without visual elements are incomplete. Before finalizing any document: 1. Generate at minimum ONE schematic or diagram (e.g., hypothesis framework showing competing explanations) 2. Prefer 2-3 figures for comprehensive reports (mechanistic pathway, experimental design flowchart, prediction decision tree) **How to generate figures:** - Use the **scientific-schematics** skill to generate AI-powered publication-quality diagrams - Simply describe your desired diagram in natural language - Nano Banana Pro will automatically generate, review, and refine the schematic **How to generate schematics:** ```bash python scripts/generate_schematic.py "your diagram description" -o figures/output.png ``` The AI will automatically: - Create publication-quality images with proper formatting - Review and refine through multiple iterations - Ensure accessibility (colorblind-friendly, high contrast) - Save outputs in the figures/ directory **When to add schematics:** - Hypothesis framework diagrams showing competing explanations - Experimental design flowcharts - Mechanistic pathway diagrams - Prediction decision trees - Causal relationship diagrams - Theoretical model visualizations - Any complex concept that benefits from visualization For detailed guidance on creating schematics, refer to the scientific-schematics skill documentation. --- ## Workflow Follow this systematic process to generate robust scientific hypotheses: ### 1. Understand the Phenomenon Start by clarifying the observation, question, or phenomenon that requires explanation: - Identify the core observation or pattern that needs explanation - Define the scope and boundaries of the phenomenon - Note any constraints or specific contexts - Clarify what is already known vs. what is uncertain - Identify the relevant scientific domain(s) ### 2. Conduct Comprehensive Literature Search Search existing scientific literature to ground hypotheses in current evidence. Use both PubMed (for biomedical topics) and general web search (for broader scientific domains): **For biomedical topics:** - Use WebFetch with PubMed URLs to access relevant literature - Search for recent reviews, meta-analyses, and primary research - Look for similar phenomena, related mechanisms, or analogous systems **For all scientific domains:** - Use WebSearch to find recent papers, preprints, and reviews - Search for established theories, mechanisms, or frameworks - Identify gaps in current understanding **Search strategy:** - Begin with broad searches to understand the landscape - Narrow to specific mechanisms, pathways, or theories - Look for contradictory findings or unresolved debates - Consult `references/literature_search_strategies.md` for detailed search techniques ### 3. Synthesize Existing Evidence Analyze and integrate findings from literature search: - Summarize current understanding of the phenomenon - Identify established mechanisms or theories that may apply - Note conflicting evidence or alternative viewpoints - Recognize gaps, limitations, or unanswered questions - Identify analogies from related systems or domains ### 4. Generate Competing Hypotheses Develop 3-5 distinct hypotheses that could explain the phenomenon. Each hypothesis should: - Provide a mechanistic explanation (not just description) - Be distinguishable from other hypotheses - Draw on evidence from the literature synthesis - Consider different levels of explanation (molecular, cellular, systemic, population, etc.) **Strategies for generating hypotheses:** - Apply known mechanisms from analogous systems - Consider multiple causative pathways - Explore different scales of explanation - Question assumptions in existing explanations - Combine mechanisms in novel ways ### 5. Evaluate Hypothesis Quality Assess each hypothesis against established quality criteria from `references/hypothesis_quality_criteria.md`: **Testability:** Can the hypothesis be empirically tested? **Falsifiability:** What observations would disprove it? **Parsimony:** Is it the simplest explanation that fits the evidence? **Explanatory Power:** How much of the phenomenon does it explain? **Scope:** What range of observations does it cover? **Consistency:** Does it align with established principles? **Novelty:** Does it offer new insights beyond existing explanations? Explicitly note the strengths and weaknesses of each hypothesis. ### 6. Design Experimental Tests For each viable hypothesis, propose specific experiments or studies to test it. Consult `references/experimental_design_patterns.md` for common approaches: **Experimental design elements:** - What would be measured or observed? - What comparisons or controls are needed? - What methods or techniques would be used? - What sample sizes or statistical approaches are appropriate? - What are potential confounds and how to address them? **Consider multiple approaches:** - Laboratory experiments (in vitro, in vivo, computational) - Observational studies (cross-sectional, longitudinal, case-control) - Clinical trials (if applicable) - Natural experiments or quasi-experimental designs ### 7. Formulate Testable Predictions For each hypothesis, generate specific, quantitative predictions: - State what should be observed if the hypothesis is correct - Specify expected direction and magnitude of effects when possible - Identify conditions under which predictions should hold - Distinguish predictions between competing hypotheses - Note predictions that would falsify the hypothesis ### 8. Present Structured Output Generate a professional LaTeX document using the template in `assets/hypothesis_report_template.tex`. The report should be well-formatted with colored boxes for visual organization and divided into a concise main text with comprehensive appendices. **Document Structure:** **Main Text (Maximum 4 pages):** 1. **Executive Summary** - Brief overview in summary box (0.5-1 page) 2. **Competing Hypotheses** - Each hypothesis in its own colored box with brief mechanistic explanation and key evidence (2-2.5 pages for 3-5 hypotheses) - **IMPORTANT:** Use `\newpage` before each hypothesis box to prevent content overflow - Each box should be ≤0.6 pages maximum 3. **Testable Predictions** - Key predictions in amber boxes (0.5-1 page) 4. **Critical Comparisons** - Priority comparison boxes (0.5-1 page) Keep main text highly concise - only the most essential information. All details go to appendices. **Page Break Strategy:** - Always use `\newpage` before hypothesis boxes to ensure they start on fresh pages - This prevents content from overflowing off page boundaries - LaTeX boxes (tcolorbox) do not automatically break across pages **Appendices (Comprehensive, Detailed):** - **Appendix A:** Comprehensive literature review with extensive citations - **Appendix B:** Detailed experimental designs with full protocols - **Appendix C:** Quality assessment tables and detailed evaluations - **Appendix D:** Supplementary evidence and analogous systems **Colored Box Usage:** Use the custom box envir
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.