调试
定位并修复问题，分析错误
systematic-debugging
rileyhilliard
Four-phase debugging framework that finds root causes before proposing fixes. Use when investigating bugs, errors, unexpected behavior, failed tests, or when previous fixes haven't worked.
preflight-checks
rileyhilliard
Detect and run project linters, formatters, and type checkers before committing or claiming completion. Auto-detects tools from project config files.
executing-plans
rileyhilliard
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
fixing-flaky-tests
rileyhilliard
Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation and resource conflicts. References condition-based-waiting for timing issues.
document-quality-standards
belumume
Use when creating or editing documents (DOCX, PDF, XLSX, PPTX) that need professional output. Adds visual verification, typography hygiene, and formula patterns.
three-best-practices
emalorenzo
Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.
techdebt
jh941213
기술 부채 정리 - 중복 코드, console.log, 사용하지 않는 import 등 검사 및 정리. 세션 종료 전 사용 권장.
dev.conventional-commits
kevinslin
Explain and apply the Conventional Commits specification for commit messages, including required format, types/scopes, breaking change notation, and examples. Use when asked to draft, validate, or review commit messages or when a repo wants Conventional Commits adoption.
gpui-entities
cnwzhu
Entity and context patterns for state management in GPUI. Use when managing component state, implementing entity lifecycle, handling subscriptions, or avoiding common entity access pitfalls.
gpui-elements
cnwzhu
UI element creation and composition with GPUI. Use when building element trees, creating custom components, implementing layouts, or working with conditional rendering.
napi-rs-node-bindings
pmcfadin
"Node.js bindings for Rust libraries using napi-rs. Use when working on Node.js/JavaScript bindings to Rust code, including creating or modifying napi macros and structs, converting types between Rust and JavaScript, handling errors across the FFI boundary, async/Promise patterns, building native modules, publishing to npm, testing binding code, or debugging binding issues. Tuned for CQLite (Cassandra CQL bindings) with feature parity tracking."
a-finding-is-not-a-fix-request
musterd-io
A review finding is REQUIRED only if the spec would have demanded it before anyone opened the diff — discovery adds information, not obligation. Four categories earn a block; everything else is a note that routes to the board under the finder's name, and complying with an out-of-scope REQUIRED is the failure mode, not the polite option. Use when reviewing a change, when a review has grown the work, or when a reviewer and an author are stuck.
napi-rs-node-bindings
pmcfadin
"Node.js bindings for Rust libraries using napi-rs. Use when working on Node.js/JavaScript bindings to Rust code, including creating or modifying napi macros and structs, converting types between Rust and JavaScript, handling errors across the FFI boundary, async/Promise patterns, building native modules, publishing to npm, testing binding code, or debugging binding issues. Tuned for CQLite (Cassandra CQL bindings) with feature parity tracking."
go-skills
llama-farm
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
investigate-report
zzstoatzz
Investigate the user report and fix it if you find it's a bug.
change
zzstoatzz
Deliver a feature or bug fix to plyr.fm end to end — branch, implement with tests, PR, self-review, merge to main (which deploys staging), and hand off for the production promote. Use whenever the user asks for a feature, a fix, a UX change, or says "open a PR for this".
autoskill
nicknisi
Analyze coding sessions to detect corrections and preferences, then propose targeted improvements to Skills used in the session. Use this skill when the user asks to "learn from this session", "update skills", or "remember this pattern". Extracts durable preferences and codifies them into the appropriate skill files.
git-commit
DauQuangThanh
Generates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions.
error-detective
AutumnsGrove
Systematic debugging and error resolution using the TRACE framework (Trace, Read, Analyze, Check, Execute). Use when debugging errors, analyzing stack traces, investigating failures, root cause analysis, or troubleshooting production issues.
backend-coding
DauQuangThanh
Expert backend development guidance covering Node.js, Python, Java, Go, API design (REST/GraphQL/gRPC), database patterns, authentication, caching, message queues, microservices, and testing. Produces production-ready, scalable, and secure backend code with industry best practices. Use when building APIs, implementing business logic, designing data models, integrating services, or when users mention backend development, server-side code, APIs, databases, or microservices.
twilio-api
tdimino
Use this skill when working with Twilio communication APIs for SMS/MMS messaging, voice calls, phone number management, TwiML, webhook integration, two-way SMS conversations, bulk sending, or production deployment of telephony features. Includes official Twilio patterns, production code examples from Twilio-Aldea (provider-agnostic webhooks, signature validation, TwiML responses), and comprehensive TypeScript examples.
go-code-audit
gopherguides
WHEN: User asks for a code quality audit, code review, or wants to find code smells, anti-patterns, or non-idiomatic Go code in their project. Also when asked "how good is this code?" or "audit my code." WHEN NOT: When the user wants to fix bugs, run tests, or just lint (use go-lint-audit for linting).
ceo
jordanhubbard
The human project owner and final authority. Does not write code or run
build-fix
gopherguides
"Detects project build systems and fixes compiler or generated-code failures until every detected build is clean. Use for active build errors; do not use for lint-only cleanup."