В каталоге 182 820 навыков в 14 категориях.
Generate a comprehensive MacBook system health report. Use when Rick asks about system status, performance, or space.
deeply review a system/architecture area and propose a simplification plan (Elon’s Algorithm).
Review the skill development ecosystem itself - assess ecosystem health, identify systemic issues, evaluate toolkit effe...
Capture and verify screenshots of runtime apps, browser apps, Figma nodes, and the Windows desktop or individual desktop...
Documentador Oficial e Wiki Viva do Sistema Super Cartola. Professor do sistema que EXPLICA como funciona baseado no cód...
Use for full system-state snapshot + diff + HTTP:8898.
Unified documentation and context preservation: spec folder workflow (levels 1-3), template enforcement, validation, Spe...
Handle disk pressure, critically low storage, safe storage limits, and storage cleanup mode by inspecting disk usage and...
System 테스트 작성 및 실행. pytest 기반, docker-compose.acceptance.yml 필수, 4단계 순서(infra→component→integration→scenarios). 네이밍 test...
Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming po...
Provides guidance on new System.Text.Json APIs introduced in .NET 11. It covers typed JsonTypeInfo access via GetTypeInf...
Set up and maintain design token architecture and foundation scales. Use when defining spacing, radius, edge, shadow, z-...
Restore system responsiveness via safe, ordered process cleanup and agent-swarm hygiene.
대화형 System-wide Refactoring — 변경 파일에서 Extract Method·Domain Logic 이동·Pull Up 등 클래스 경계를 넘는 구조 변경 후보를 찾아 승인 후 기법별 커밋으로 적용....
System 2 attention mechanisms for deliberate, slow reasoning in transformer
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root...
系统采样算子。按照固定间隔从数据中进行系统采样，适用于时间序列数据或需要均匀分布样本的场景。 当用户提到系统采样、等距抽样、按间隔取样、均匀抽样等需求时使用此skill。 即使用户没有明确说出"系统采样"，只要任务涉及从有序数据中按固定步长...
Structured code review framework using Conventional Comments for clear, actionable feedback.
4-phase code review: UNDERSTAND, VERIFY, ASSESS risks, DOCUMENT findings.
4-phase code review methodology: UNDERSTAND changes, VERIFY claims against code, ASSESS security/performance/architectur...
Systematic debugging methodology - scientific approach to finding and fixing bugs using hypothesis testing, isolation, a...
This skill should be used when the user mentions "debugging", "troubleshooting", "bug", "error", "issue", "not working",...
Structured debugging methodology using hypothesis-driven investigation, log analysis, and bisection to isolate and resol...
Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical i...
四阶段调试方法论和根本原因分析。在调查bug、修复测试失败或排查意外行为时使用。强调在根本原因分析之前不要进行修复。
Use when diagnosing a bug, failure, flaky test, performance regression, unexpected behavior, or error recovery path. Do...
4-phase root cause debugging: understand bugs before fixing.
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when m...
Systematic debugging framework for any bug, test failure, or unexpected behavior. Use BEFORE proposing fixes. Triggers:...
Debug Godot issues systematically using AgentBridge — use instead of guessing whenever an error, crash, or unexpected be...
This skill should be used when encountering any bug, test failure, or unexpected behavior. It requires finding root caus...
Trigger: debug, debugging, root cause, root-cause analysis, why does this fail, intermittent failure, shotgun fixes. Roo...
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first...
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is...
Step-by-step debugging workflow: reproduce the bug, isolate the failing component, trace to root cause, apply a targeted...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
[Debug] Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framewo...
Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever somethin...
This skill should be used when the user asks to "debug this issue", "find the root cause", "investigate the bug", "syste...
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or afte...
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Debugging sistemático - Análise de root cause em 4 fases
ONLY USE THIS SKILL UPON USER/HOOMAN REQUEST TO USE EXACTLY THIS SKILL, ONLY RUN ON HOOMAN [OK]. Use when encountering a...
Explicit `/systematic-debugging` reference for a structured root-cause audit. Use only when the user requests this workf...
Use for any bug, failing test, build/runtime failure, unexpected behavior, or performance regression; require reproducti...
Root-cause one known bug: reproduce, trace, fix, verify.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuri...
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation BEFORE proposing f...
Diagnose a concrete software bug or incident from symptoms, logs, failed tests, or code; verify the cause and, when aske...
Proceso riguroso de cuatro fases para diagnosticar y corregir errores, priorizando la investigación de causa raíz y limi...
Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes
Use when encountering any bug, test failure, or unexpected behavior. ALWAYS find root cause before attempting fixes. Sym...
Use when investigating a bug, test failure, crash, or unexpected behavior, before proposing or applying a fix.
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without...
Systematic root-cause debugging with structured triage. Use when tests fail, builds break, behavior doesn't match expect...
Diagnose bugs, failing tests, flaky behavior, build failures, and unexplained performance regressions through reproducti...
Find the root cause of a bug before writing any fix.
Four-phase debugging process - root cause first, then fix. Use when encountering bugs or unexpected behavior.
（中文）Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
When something breaks, the instinct is to start changing code — adding logs, tweaking values, commenting things out. Thi...
遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行
Use on any bug, test failure, or unexpected behavior, before fixes.
Use when encountering any bug, test failure, or unexpected behavior, BEFORE proposing fixes. Four phases — no fixes with...
Use for bugs, test failures, or unexpected behavior needing root cause
Systematic debugging process for any error, test failure, or unexpected behavior. Investigate root cause BEFORE proposin...
Four-phase debugging framework for any technical issue. Use when encountering bugs, errors, or unexpected behavior. Prev...
Beginner-friendly reverse-engineering workflow for Systematic Debugging. Use it to collect evidence, choose static or dy...
Structured debugging workflow adapted for Compiler Driven Development in scala-ts. Use when fixing bugs, investigating w...
Use to find the cause of a failure when it is unclear, after a fix did not hold, or for a flaky or production-only failu...
Use when a failure cause is unclear, an attempted fix failed, or flaky behavior needs investigation. Handle obvious loca...
Apply whenever the task is diagnosing a bug, a failing test, or unexpected behavior — even if the user only says "fix it...
Four-phase debugging framework for any technical issue. Prevents random fix attempts
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or trouble...
Use when encountering any bug, test failure, crash, or unexpected behavior in mobile applications — before proposing fix...
Structured 4-phase debugging process — reproduce, isolate, hypothesize, verify — that finds root causes before attemptin...
Use when encountering any bug, test failure, unexpected result, or failed replication - before proposing fixes or explan...
Methodical problem-solving workflow for debugging issues. Use when facing bugs, errors, or unexpected behavior that isn'...
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging co...
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. U...
Use when encountering bugs or unexpected behavior. Methodical approach to identify root cause: Reproduce → Isolate → Ide...
Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the...
Find and repair unresolved root causes.
Apply structured debugging techniques to find and fix bugs efficiently. Use when the user reports a bug, encounters unex...
4-phase root cause investigation methodology for bugs and unexpected behavior. Use when tests fail, errors occur, behavi...
当遇到任何 bug、测试失败或非预期行为时，在提出修复方案之前使用
Root-cause debugging in four phases: investigate, analyze, hypothesize, implement. Iron Law -- no fixes without root cau...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Turkish triggers: sistemati...
Optional structured debugging for unclear root causes, repeated failed fixes, or cross-module faults. Use when requested...
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use fo...
Processus de debugging systématique une fois la cause identifiée. MANDATORY pour bug fixing. À utiliser lors de correcti...
Disciplined development workflow that prevents incomplete implementations, silent fallbacks, and hallucinated code. Use...
Use Sherpa's systematic development workflow for general coding tasks. Activates when starting development work, adding...
Systematic literature review across multiple arXiv papers.
当用户需要做系统综述/文献综述/related work/相关工作/文献调研时使用：AI 自定检索词，多源检索→去重→AI 逐篇阅读并评分（1–10分语义相关性与子主题分组）→按高分优先比例选文→自动生成"综/述"字数预算（70% 引用段...
系统化问题解决与优化流程（领域无关）：量化基线→全量列问题→根因分类→结构性方案（拒绝临时补丁）→借鉴同类方案→归纳取舍→展示计划确认实施→实施→验证生效→度量闭环。核心原则：规则/流程存在≠被执行，能落到"无法绕过的机制"就不写建议；优化...