research-methodology
Structured research using sophisticated query design, source vetting, and synthesis techniques. Use when conducting competitive analysis, market scans, historical investigations, or trend research.
What this skill does
# Research Methodology Structured approach to finding, vetting, and synthesizing information from diverse sources. Turns research questions into trustworthy, actionable findings through systematic query design, source evaluation, and cross-referencing. ## When to Use This Skill - Conducting competitive analysis or market scans - Investigating historical events, trends, or technical evolution - Fact-checking claims across multiple sources - Synthesizing research into structured deliverables (reports, tables, timelines) - Any research task that requires more than a single search query ## Quick Reference | Resource | Purpose | Load when | |----------|---------|-----------| | `references/search-strategies.md` | Query design, source vetting, fact verification, synthesis techniques | Starting any research task | --- ## Workflow ``` Phase 1: Scope → Define research objective, key questions, constraints Phase 2: Explore → Design queries, search broadly, capture sources Phase 3: Verify → Vet sources, cross-reference claims, assess credibility Phase 4: Synthesize → Organize findings into structured deliverables ``` --- ## Phase 1: Scope the Research Before searching, clarify the research objective: 1. **State the question** -- what exactly are we trying to learn? 2. **Define success criteria** -- what does a complete answer look like? 3. **Set constraints** -- time period, geography, domains, source types 4. **List hypotheses** -- what do we expect to find? (helps detect bias) 5. **Identify key terms** -- domain vocabulary, synonyms, related concepts ### Scoping Template ```markdown **Research Question**: [precise question] **Success Criteria**: [what constitutes a complete answer] **Constraints**: [time period, scope, source types] **Key Terms**: [domain vocabulary and synonyms] **Initial Hypotheses**: [what we expect, to check against later] ``` --- ## Phase 2: Explore Design multiple query variations and search broadly before narrowing: 1. **Create 3-5 query variations** per research question 2. **Search broadly first** -- cast a wide net with general terms 3. **Refine iteratively** -- narrow based on initial results 4. **Track what you searched** -- record every query for reproducibility ### Query Design Principles - Use exact-match phrases in quotes for precision - Exclude noise with negative keywords - Target specific timeframes for recency or historical depth - Vary terminology across queries to avoid vocabulary bias - Use domain-specific operators when available (site:, filetype:, etc.) ### Source Capture For each promising source, record: - URL and access date - Key claims with direct quotes - Author/publisher and their domain authority - Any noted biases or limitations --- ## Phase 3: Verify Vet sources and cross-reference claims before trusting them: 1. **Assess source authority** -- who wrote it, what are their credentials? 2. **Check recency** -- is the information current enough for the question? 3. **Detect bias** -- does the source have a commercial, political, or ideological interest? 4. **Triangulate** -- require 2+ independent sources for any key claim 5. **Seek primary sources** -- follow citation chains to the original data ### Confidence Rating | Level | Criteria | |-------|----------| | **Confirmed** | 3+ independent, authoritative sources agree | | **Likely** | 2 sources agree, no contradictions found | | **Uncertain** | Single source or sources disagree | | **Contested** | Credible sources directly contradict each other | --- ## Phase 4: Synthesize Organize findings into a structured deliverable: ### Standard Research Report Structure ```markdown ## Research Summary [1-2 paragraph overview of findings] ## Key Findings - [Finding 1] — [confidence level] - [Finding 2] — [confidence level] ## Detailed Analysis [Organized by theme or question] ## Source Credibility Assessment | Source | Authority | Recency | Bias Risk | Rating | |--------|-----------|---------|-----------|--------| ## Gaps and Limitations [What we couldn't determine and why] ## Recommendations [Next steps or actions based on findings] ``` --- ## Anti-Patterns - Do not rely on a single source for any key claim - Do not present uncertain findings as confirmed facts - Do not skip source vetting for convenience - Do not omit contradictory evidence -- always surface disagreements - Do not let initial hypotheses bias which findings you report
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.