调试
定位并修复问题，分析错误
react
mikkelkrogsholm
"React — JavaScript library for building user interfaces with components. Use when building with React or asking about hooks, state management, effects, Server Components, Suspense, or any React APIs, patterns, or configuration. Fetch live documentation for up-to-date details."
gdpr-dev
mikkelkrogsholm
"GDPR compliance for European developers. Use when building features that handle personal data: user registration, profiles, authentication, email sending, analytics, error tracking, payments, search indexes, background jobs, or any feature that stores, processes, or transmits information about people. Provides stack-aware gotchas, anti-patterns to avoid, and schema design principles. Does not ask questions — applies principles proactively based on what is being built."
sentry
mikkelkrogsholm
"Sentry — application monitoring platform for error tracking, performance monitoring, session replay, profiling, and alerting. Use when building with Sentry or asking about SDK initialization, error capture, tracing, source maps, sampling, PII scrubbing, tunneling, or integration with Next.js, Node.js, or other JavaScript frameworks. Fetch live documentation for up-to-date details."
fix-bug
mgiovani
"Fix bugs using test-driven debugging, root cause analysis, and comprehensive verification. Automatically activates when users want to fix a bug, debug an issue, resolve an error, investigate failing tests, or address problems in the codebase."
git-commit
mgiovani
Generate conventional commits following conventionalcommits.org specification.
ui-useframe
verekia
Sync UI elements outside the Canvas with the render loop using R3F v10's external useFrame.
critical-reasoning
andrewgleave
Apply critical rationalist epistemology (Popper, Deutsch) to evaluate reasoning, identify errors, and refine understanding. Use when the user explicitly requests help with reasoning - phrases like "help me think this through", "does this make sense", "any flaws in this", "what am I missing", "critique this", "is this reasoning sound", "stress test this idea", "devil's advocate", or any request to evaluate arguments, identify logical problems, or improve thinking. Also use when errors in reasoning are significant enough to materially affect the user's goals, even if not explicitly requested.
aio-ios-device-debug
aiocean
This skill should be used when the user asks to "debug on device", "deploy to iPhone", "get crash logs", "check device logs", "install on device", "run on phone", "pull crash report", "analyze crash", "why is my app crashing", "syslog", "device logs", "take screenshot", "capture screenshot", "screenshot from device", "device screenshot", or when debugging iOS app crashes on physical devices. Covers the full workflow from build, install, launch, log capture, screenshot capture, crash report extraction, and crash analysis.
faion-backend-systems
faionfaion
"Systems backends: Go, Rust, databases, caching."
aio-jira
aiocean
This skill should be used when the user asks to "create a Jira issue", "search issues", "update issue status", "add comment", "manage sprint", "link issues", "track time", or mentions jira, jql, sprint, story, epic, bug. Provides Jira operations through MCP tools for issue lifecycle management. Auto-installs the jira-mcp server if not configured.
rust-development
thrashr888
Rust development workflow with quality gates, testing, and iteration patterns. Use when developing Rust code, running tests, or iterating on Rust projects.
ai-code-cleanup
89jobrien
Remove AI-generated code slop from branches. Use after AI-assisted coding
receiving-code-review
izyanrajwani
Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.
dispatching-parallel-agents
izyanrajwani
Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
test-driven-development
izyanrajwani
Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
rust-best-practices
thrashr888
Rust coding best practices for idiomatic, efficient, and maintainable code. Use when writing Rust code, reviewing code, or learning Rust patterns.
golang-testing
89jobrien
Comprehensive Go testing patterns including table-driven tests, mocking,
tools-permission-fix
cuioss
Write operations for fixing and managing host-platform permissions - add, remove, consolidate, ensure, apply-fixes, executor migration, wildcard generation.
aio-debug
aiocean
This skill should be used when the user asks to "debug", "fix bug", "fixbug", "investigate error", "troubleshoot", "why is this broken", "not working", "failing test", "unexpected behavior", or encounters any bug, error, or test failure. Orchestrates systematic debugging with codebase understanding, code review, and quality verification for maximum fix effectiveness.
local-mainnet-debug
lodekeeper
Debug Lodestar beacon node issues by running a local mainnet node with checkpoint sync and engineMock. Use for investigating networking bugs, peer discovery issues, identify failures, metrics anomalies, or any behavior that needs real-world peer interactions without a full execution client.
git-commit
alpoxdev
'Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/git-commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping'
luau-type-expert
dig1t
Professional Luau type-checking and clean code specialist for Roblox development. Use this skill when: - Writing or reviewing Luau code that needs proper type annotations - Fixing type errors from luau-lsp or luau-analyze - Converting untyped Lua/Luau to strictly typed code - Designing type-safe APIs, modules, or data structures - Understanding Luau type system features (generics, unions, intersections, refinements) - Optimizing code for luau-lsp compatibility - Setting up --!strict mode compliance - Creating type definitions (.d.luau files) - Debugging "Type X is not compatible with Y" errors - Writing metatables with proper type support Triggers: "type error", "type annotation", "luau types", "strict mode", "--!strict", "type checking", "luau-lsp", "type mismatch", "generic type", "union type", "type narrowing", "type refinement", "type cast", "export type", "typeof"
systematic-debugging
izyanrajwani
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
aio-monitoring-observability
aiocean
This skill should be used when the user asks to "set up monitoring", "design metrics", "create alerts", "build dashboards", "calculate SLOs", "analyze performance", "compare monitoring tools", "migrate from Datadog", or mentions Prometheus, Grafana, Loki, OpenTelemetry, Four Golden Signals, RED/USE methods, error budgets, distributed tracing.