调试
定位并修复问题，分析错误
observability-design
rsmdt
Monitoring strategies, distributed tracing, SLI/SLO design, and alerting patterns. Use when designing monitoring infrastructure, defining service level objectives, implementing distributed tracing, creating alert rules, building dashboards, or establishing incident response procedures. Covers the three pillars of observability and production readiness.
ui-testing
alinaqi
Visual testing - catch invisible buttons, broken layouts, contrast
nodejs-backend
alinaqi
Node.js backend patterns with Express/Fastify, repositories
android-java
alinaqi
Android Java development with MVVM, ViewBinding, and Espresso testing
iterative-development
alinaqi
Ralph Wiggum loops - self-referential TDD iteration until tests pass
base
alinaqi
Universal coding patterns, constraints, TDD workflow, atomic todos
flutter
alinaqi
Flutter development with Riverpod state management, Freezed, go_router, and mocktail testing
supabase-node
alinaqi
Express/Hono with Supabase and Drizzle ORM
ticket-craft
alinaqi
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing
code-review
RTGS2017
代码审查和质量分析技能。用于审查代码、发现潜在问题、提供改进建议。当用户请求代码审查、代码质量分析或最佳实践建议时使用。
linux-phone-porting
angelwzr
Use for every hardware bring-up / debug session when porting mainline Linux to a phone. Enforces evidence-first debugging - capture device logs, then research across mainline, the vendor kernel, postmarketOS, Halium/UBports, Mobian and NixOS - before writing or flashing any fix. Requires an already-unlocked bootloader; locked devices are out of scope.
ccs-delegation
kaitranntt
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via ccs {profile} -p "task" or ccs {profile}:continue, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
behavioral-product-design
RefoundAI
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
dogfooding
RefoundAI
Help users implement effective dogfooding practices. Use when someone is trying to get their team to use their own product, designing internal usage programs, or building user empathy through personal product use.
bug-localization
ArabelaTso
Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis. Analyzes stack traces, error messages, failing tests, and code patterns to pinpoint buggy functions, classes, files, or modules with confidence rankings and supporting evidence.
counterexample-generator
ArabelaTso
Generate concrete counterexamples when formal verification, assertions, or specifications fail. Use this skill when debugging failed proofs, understanding why verification fails, creating minimal reproducing examples, analyzing assertion violations, investigating invariant breaks, or diagnosing specification mismatches. Produces concrete input values, execution traces, and state information that demonstrate the failure.
code-generation
romiluz13
"Internal skill. Use cc10x-router for all development tasks."
reviewing-dependencies
bitwarden
This skill should be used when the user asks to "review Dependabot alerts", "check for vulnerable dependencies", "audit third-party packages", "assess supply chain risk", "run Grype scan", or needs to evaluate dependency health, transitive risk, or supply chain security.
Papyrus Frontend Audit (crates/pex + crates/papyrus)
matiaszanolli
"Deep audit of the Papyrus compiler frontends — .pex reader + 5-phase decompiler (Champollion port, crates/pex) and the .psc lexer/Pratt parser (crates/papyrus): untrusted-input bounds, decompiler soundness, depth caps"
Fix Issue Pipeline
matiaszanolli
"Fetch a GitHub issue, investigate, plan, implement, test, and commit the fix"
avoiding-false-positives
bitwarden
Use this skill when validating ANY potential code review finding. Apply BEFORE classifying to verify the finding is real; can you trace incorrect behavior, is it handled elsewhere, and are you certain about framework semantics? If any answer is no, DO NOT create the finding.
Flow Tracer
matiaszanolli
"Trace a data flow through the engine — from ECS to GPU or from file to entity"
posting-bitwarden-review-comments
bitwarden
Use this skill when posting inline comments to GitHub pull requests. Apply when formatting comments following Bitwarden engineering standards with severity emojis, clear explanations, and actionable suggestions. Use after findings are classified and ready to post. DO NOT USE when posting summary comments.
monitoring-observability
Logos-Liber
Prometheus, Grafana, CloudWatch, Azure Monitor, Stackdriver, logging, alerting, and SRE practices