- Home
- /
- Categories
- /
- Debugging
Debugging
Find and fix bugs, error analysis
systematic-debugging
by mrtolkien
Use when encountering any bug, test failure, or unexpected behavior, before proposing
test-driven-development
by mrtolkien
Use when implementing any feature or bugfix, before writing implementation code
dispatching-parallel-agents
by mrtolkien
Use when facing 2+ independent tasks that can be worked on without shared state or
wallet-brc100-go
by b-open-io
This skill should be used when the user asks to "implement BRC-100 wallet in Go", "use go-wallet-toolbox", "Go BSV wallet", "BRC-100 Go implementation", or needs guidance on building conforming wallets using Go wallet-toolbox.
authentication-pattern
by igbuend
Security pattern for implementing authentication in software systems. Use when designing or reviewing authentication mechanisms, implementing login systems, verifying user identity, protecting system access, or addressing OWASP authentication flaws. Provides guidance on enforcers, verifiers, evidence providers, subject registration, credential management, and security considerations.
tpm-spec-verify
by ozten
Enrich a Phase Sepc/PRD with Quality Requirements (Q-nnn) and Acceptance Criteria (AC-nnnn). Use when user wants to add QA perspective, define test criteria, identify non-functional requirements, add verification steps, or prepare a Phase PRD for test planning.
pairwise-test-coverage
by apankov1
"Combinatorial testing with a greedy pairwise matrix generator. Covers all factor pairs in near-minimal test cases."
rust-senior-engineer
by mOdrA40
Senior/Lead Rust Developer dengan 20+ tahun pengalaman industri. Skill ini mengubah Claude menjadi ahli Rust yang sangat berpengalaman dengan keahlian dalam: (1) Arsitektur sistem yang scalable dan maintainable, (2) Docker containerization dan deployment, (3) Clean code dengan prinsip KISS dan pragmatic engineering, (4) Debugging expert-level dan identifikasi bug/crash proaktif, (5) Pengetahuan mendalam tentang library ecosystem Rust yang production-ready, (6) Code review dengan standar senior engineer, (7) Memory safety dan performance optimization. Gunakan skill ini ketika: bekerja dengan Rust/Cargo projects, containerizing Rust apps dengan Docker, membutuhkan code review berkualitas tinggi, debugging complex issues, merancang arsitektur sistem, atau membutuhkan guidance dari perspektif senior engineer yang pragmatis.
effect-ts
by teeverc
"Effect-TS (Effect) guidance for TypeScript. Use when building, refactoring, reviewing, or explaining Effect code, especially for: typed error modeling (expected errors vs defects), Context/Layer/Effect.Service dependency wiring, Scope/resource lifecycles, runtime execution boundaries, schema-based decoding, concurrency/scheduling/streams, @effect/platform APIs, Effect AI workflows, and Promise/async migration."
lookup-block-info
by b-open-io
This skill should be used when the user asks to "get block info", "lookup block by height", "block by hash", "block header details", or needs to retrieve BSV block information.
bunjs-docker-mastery
by mOdrA40
Senior/Lead Developer Bun.js + Docker dengan pengalaman 20 tahun. Skill ini digunakan ketika: (1) Membuat project Bun.js baru dengan Docker, (2) Code review dan refactoring untuk clean code, (3) Debugging complex issues, (4) Optimisasi performa dan scalability, (5) Arsitektur aplikasi production-ready, (6) Memilih library yang tepat dan terpercaya, (7) Setup CI/CD dan deployment. Trigger keywords: "bun", "bunjs", "bun.js", "docker", "typescript backend", "clean code", "scalable", "maintainable", "debugging", "performance".
stratum-v1
by b-open-io
This skill should be used when the user asks to "implement Stratum v1", "mining pool protocol", "JSON-RPC mining", "pool-miner communication", "mining.subscribe", or needs to build Stratum v1 mining infrastructure.
insecure-defaults-anti-pattern
by igbuend
Security anti-pattern for fail-open defaults (CWE-1188). Use when reviewing code that uses fallback values for secrets, credentials, or security settings. Detects applications that run with weak defaults when configuration is missing.
error-responses
by yanko-belov
Use when returning errors from APIs. Use when exposing internal errors. Use when error responses lack structure.
interface-segregation-principle
by yanko-belov
Use when designing interfaces. Use when implementing interfaces with methods you don't need. Use when forced to implement throw/no-op for interface methods.
React Framework - Quick Reference
by FortiumPartners
Version: 1.0.0 Last Updated: 2025-10-22 Status: Production Ready
Jest Test Framework
by FortiumPartners
Execute and generate Jest tests for JavaScript/TypeScript projects with support for unit, integration, and E2E testing
fail-fast
by yanko-belov
Use when handling errors. Use when tempted to catch and swallow exceptions. Use when returning default values to hide failures.
ExUnit Test Framework
by FortiumPartners
Execute and generate ExUnit tests for Elixir projects with setup callbacks, describe blocks, and async testing support
Cloud Provider Detection Skill
by FortiumPartners
Maintainer: Fortium Infrastructure Team
run-tests
by kenny-stacks
Run Clarity contract tests and diagnose common errors. Use when the user wants to run tests, check coverage, or debug test failures in a Stacks/Clarinet project.
error-boundaries
by yanko-belov
Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation.
Changelog Generator Skill
by FortiumPartners
Integration examples
ast-grep
by mauromedda
AST-aware code search and refactoring using ast-grep (sg). Use INSTEAD of grep/ripgrep for searching code structure. Finds functions, classes, patterns, anti-patterns across Go, Python, Bash, Terraform/HCL codebases. Triggers on "ast-grep", "sg", "find function", "find class", "find method", "find all usages", "where is X used", "search for pattern", "find anti-pattern", "code smell", "refactor pattern", "structural search", "AST search", "find error handling", "find imports", "find decorators", "find struct", "find interface", "search code", "locate function", "grep for function", "find definition". PROACTIVE: Use for ANY code search task; prefer over grep/ripgrep for code files.