744건 · 관련도순
Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates scientifically sound inclusion and exclusion criteria for Meta-Analysis based on a given title or keywords. Use when user wants to design eligibility criteria for a systematic review or meta-analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Screens research papers based on title/abstract and inclusion criteria, providing a structured Yes/No/Maybe decision. Use when you need to filter literature for meta-analysis or systematic reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write comprehensive literature reviews for medical imaging AI research. Use when writing survey papers, systematic reviews, or literature analyses on topics like segmentation, detection, classification in CT, MRI, X-ray, ultrasound, or pathology imaging. Triggers on requests f...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically maps mechanism evidence for a disease from molecules to pathways, cell types, tissues, biological consequences, and clinical phenotypes. Always use this skill when a user needs a layered mechanism evidence chain rather than a flat summary or immediate gap analysis. Formal literature citations must be real and verifiable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resolve defects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose software failures using observability data, ranked hypotheses, and targeted instrumentation. Use when the cause is unclear or an issue requires systematic investigation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically fix all failing tests after business logic changes or refactoring
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iterative PDCA cycle for systematic experimentation and continuous improvement
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematic Fishbone analysis exploring problem causes across six categories
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", or "test this app" on mobile. Produces a structured report with reproducible evidence: screenshots, optional repro videos, and detailed steps for every issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-agent research orchestration: split a research goal into parallel sub-goals, run each via headless `claude -p` subprocesses, aggregate results into a polished report file. Use for systematic web/document research, competitive or industry analysis, batch link/dataset processing, and long-form evidence synthesis. Triggers: "深度调研", "deep research", "wide research", "多 Agent 调研", "系统调研".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI DevKit · Systematic structural or multi-file refactors across any stack while preserving behavior and public contracts. Use for reorganizing modules, boundaries, naming, APIs/contracts, staged refactor plans, or refactor risk review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component, function, or line is faulty. Covers binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions across TypeScript, SQL, and bash.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.