Claude Skills by majiayu000

Research topics, verify facts, check historical accuracy, and validate technical details. Use when writing non-fiction, historical fiction, or any content requiring factual accuracy.

This skill should be used when the user asks about frameworks (React, Next.js, FastAPI, PydanticAI, Supabase, LiveKit, LlamaIndex, Tailwind, Zustand, etc.), when implementing new features, when expressing uncertainty ("how do I", "what's the best way", "should I", "is this right"), when designing solutions or architecture, or before committing to any implementation approach. Spawns a research sub-agent to query context7 (framework docs) and Perplexity (solution validation) in a separate conte...

Use this skill when you need to gather comprehensive documentation and best practices for frameworks, libraries, or dependencies in your project. This includes fetching official documentation, exploring source code, identifying version-specific constraints, and understanding implementation patterns.

APIキー不要の統合リサーチスキル。Claude Code組み込みのWebSearch/WebFetchを使用。他人に配布してもそのまま使える。

Technical research methodology using Context7, Exa, and Sequential Thinking for documentation, best practices, and complex investigations.

プロジェクト プロジェクトの機能(docs/features/)とリサーチ(docs/research/)文書を分析し、高収益/高LTV/低離脱達成のためのリサーチギャップを識別し、欠落したP0/P1リサーチを自動実行する。

Use when assembling strategic context - collects and filters research by topic with expiry management to prevent using stale data in decisions

Company due diligence, technology deep-dives, market analysis, and topic exploration for cyber•Fund investment decisions, content creation, and personal projects. Supports 3 intensity levels (quick/standard/deep) for speed-quality tradeoffs.

Git-aware skill for finding implementation patterns and retrieving story context from git history. Use when searching for similar implementations or understanding how a feature was built. To use this skill, you must have a story ID (e.g., "US-001-auth-login-admin"). Use research-user-stories skill to find the story ID.

Research a topic to make a comprehensive guide for the user.

Research best practices, guides, and libraries. Use when needing documentation, recommendations, implementation guidance, or library comparisons.

Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.

Use when asked to create a deep-research handoff bundle: do web research, codebase analysis, Gemini Oracle critique, and produce a prompt + context folder on Desktop for another AI agent (include a zipped archive of the bundle).

Use when user invokes /research command with any source — URL, GitHub repo, YouTube video, podcast, Reddit post, academic paper, documentation page, product site, local file, or empty. Processes and indexes research materials with raw source preservation and topic-level synthesis coalescing. Do NOT use for quick factual questions — use /explain instead.

Trace execution paths and document how code actually behaves. Use when you need to understand how features work, walk through code flows, explain component behavior, trace where data comes from, understand relationships between components, or audit for orphaned events and dead code.

Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability/security/maintainability analysis.

This skill should be used when the user asks to "brainstorm research ideas", "use 5W1H framework", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", or mentions research project initiation phase. Provides comprehensive guidance for research startup workflow from idea generation to planning.

Build a research definition and execute the study based on a Linear issue.

Deep research on a specific ingredient using the product-research MCP

Quick entry point for structured knowledge elicitation with epistemic tracking. PROACTIVELY activate for: (1) interviews and requirements gathering, (2) problem definition, (3) domain knowledge capture, (4) stakeholder elicitation, (5) assumptions surfacing. Triggers: "research interview", "elicit knowledge", "gather requirements", "define problem", "interview stakeholder", "capture domain knowledge"

Performs legal research for complex petitions using websearch tool. Provides statutes, principles, and argument frameworks without inventing citations.

병렬 리서치 오케스트레이션. 여러 소스(Context7, WebSearch, 코드베이스)를 동시에 탐색하여 기술 조사를 수행합니다. Use when researching libraries, APIs, best practices, or when comparing technical approaches.

Use this skill when external documentation, standards, or library comparisons are needed.

(ePost) Use when user asks to research, compare options, find best practices, or investigate a technology

Research when **getting it right matters**. When current information saves hours of debugging, ensures secure implementations, or guides you to the right abstraction—research first.

A tiered approach to answering research questions with clear stop rules, evidence capture, and escalation to Tavily/Playwright only when needed.

Use this skill when you need to search institutional learnings in docs/solutions/ for relevant past solutions before implementing a new feature or fixing a problem. This agent efficiently filters documented solutions by frontmatter metadata (tags, category, module, symptoms) to find applicable patterns, gotchas, and lessons learned. The agent excels at preventing repeated mistakes by surfacing relevant institutional knowledge before work begins.

Research a library and create comprehensive documentation in .claude/docs/libraries/.

Research a library and create comprehensive documentation in .claude/docs/libraries/.

Show statistics about the product research evidence library

Search and analyze research papers, find related work, summarize key ideas. Use when user says \"find papers\", \"related work\", \"literature review\", \"what does this paper say\", or needs to understand academic papers.

Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.

Research Literature agent for healthcare workflows.

Look up current research information using Perplexity Sonar Pro Search or Sonar Reasoning Pro models through OpenRouter. Automatically selects the best model based on query complexity. Search academic papers, recent studies, technical documentation, and general research information with citations.

Look up current research information using Perplexity's Sonar Pro Search or Sonar Reasoning Pro models through OpenRouter. Automatically selects the best model based on query complexity. Search academic papers, recent studies, technical documentation, and general research information with citations.

Document codebase as-is with thoughts directory for historical context

Research methodology and best practices for finding existing patterns

Use this skill when you need to conduct thorough research on a repository's structure, documentation, and patterns. This includes analyzing architecture files, examining GitHub issues for patterns, reviewing contribution guidelines, checking for templates, and searching codebases for implementation patterns. The skill excels at gathering comprehensive information about a project's conventions and best practices.

RPI Research Phase - Systematic codebase exploration with parallel agents and chunked output

When searching for authoritative sources for skills or validating existing source links.

Research Tanstack Query (React Query) patterns for server state management using Exa code search and Ref documentation

Research a topic and create a new note in the vault. Use this skill whenever the user wants to learn about a topic they don't know yet, investigate a question, explore an idea, or asks "what is X", "research X", "tell me about X", "I want to understand X", "look into X". Also triggers on /research. This is for BROAD research (web + vault) — for academic papers specifically, use /paper-discover instead.

Deep research and fresh perspective on current blockers. Use when stuck, for methodology validation, or auto-triggered during long optimization runs.

Analyzes codebase, searches documentation, investigates dependencies and architecture patterns

Research Zod validation patterns, schema design, and TypeScript integration using Exa code search and Ref documentation

Automatically activated when user asks "what's the best way to...", "how should I...", "what are best practices for...", or requests recommendations, industry standards, or proven approaches for implementing features

Use when the how is unclear; output is a chosen approach with evidence. **Prerequisites:** If what/why is unclear, use **discovering** skill first.

Generate a comprehensive resilience status report using all available MCP tools. Aggregates unified critical index, burnout Rt, early warnings, utilization, and defense levels into a single actionable dashboard.

Generate a comprehensive resilience status report using all available MCP tools. Aggregates unified critical index, burnout Rt, early warnings, utilization, and defense levels into a single actionable dashboard.

Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: \"resolve the open questions\", \"close the gaps in this spec\", \"research the open items\", \"finalize my spec\", \"make this spec implementation-ready\", \"answer the TBDs\". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved ...