Debugging
Find and fix bugs, error analysis
reviewer-2-simulator
by GhostScientist
Critiques your paper draft as a skeptical reviewer would. Use when asked to review a paper draft, find weaknesses in a paper, prepare for peer review, anticipate reviewer criticism, or stress-test research before submission. Identifies weak claims, missing baselines, unclear explanations, and overclaims.
win
by medevs
Comprehensive thoroughness framework. Auto-invoked when planning features, implementing code, fixing bugs, writing tests, analyzing existing code, auditing features, reviewing architecture, or investigating issues. Forces systematic consideration of all edge cases, failure modes, error scenarios, security implications, state transitions, and hidden assumptions so nothing gets missed. Do NOT invoke for trivial changes like typos, renames, single-line fixes, adding imports, or updating config values.
programmatic-uikit-layout
by dagba
Use when building UIKit interfaces without storyboards, setting up Auto Layout constraints with anchors, creating reusable UI components, or encountering layout constraint errors and ambiguous layout warnings
research-question-refiner
by GhostScientist
Helps transform a vague research interest into a concrete, tractable research question. Use when asked to refine a research idea, develop a research question, scope a research project, or figure out what to work on. Walks through systematic refinement with feasibility analysis.
agentic-structure
by BackGwa
Collaborative programming framework for production-ready development. Use when starting features, writing code, handling security/errors, adding comments, discussing requirements, or encountering knowledge gaps. Applies to all development tasks for clear, safe, maintainable code.
Risk Assessment
by AmnadTaowsoam
Risk assessment is a systematic process of identifying, analyzing, and
test-specialist
by mamba-mental
This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.
smart-git-commit
by zlh-428
Create well-formatted git commits with conventional commit format and emoji. Automatically runs pre-commit checks (lint, build, docs), analyzes changes, suggests splitting when appropriate, and generates emoji-prefixed conventional commit messages. Use when creating commits in any repository to ensure consistent, professional commit history.
trading-bot-architecture
by SanctifiedOps
Design and build Solana trading bots - execution engine, position management, risk controls, and operational infrastructure. Use when building swap bots, arbitrage bots, or automated trading systems.
Websocket Patterns
by AmnadTaowsoam
WebSocket is a communication protocol that provides full-duplex communication
spec-feature
by weegigs
Feature specification workflow. Use when specifying new features to generate user stories with EARS acceptance criteria.
receiving-code-review
by martin-janci
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
dispatching-parallel-agents
by HJewkes
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
React Best Practices
by AmnadTaowsoam
React is a JavaScript library for building user interfaces using component-based
Nextjs Patterns
by AmnadTaowsoam
Next.js 14+ App Router is a powerful React framework with features including
golang-base-practices
by cexll
Go language best practices guide covering frameworks (Gin/Go-Kratos), ORM (GORM), database migrations (Goose), DDD project structure, error handling, concurrency patterns, testing (99% coverage target), and Lint tools. This skill should be used when writing, reviewing, or refactoring Go code to ensure best practices are followed. Triggers on Go project development, code review, performance optimization, or architecture design.
n8n-production-readiness
by RedcoatAsher
Dynamic tier system for right-sizing n8n workflow hardening. Use this skill on ANY n8n workflow request to determine appropriate validation, logging, and error handling levels. Adapts to user needs — from quick prototypes to mission-critical production systems.
5d-verify
by tapania
"Multi-layer verification of implementation against spec and intent. Use when: (1) After BUILD phase in 5D-SDD workflow, (2) Implementation is complete and needs validation, (3) User asks to 'test,' 'verify,' or 'check' the implementation, (4) Before considering a feature done. This phase catches errors at multiple levels and routes fixes appropriately."
common-anchor-errors-debugger
by SanctifiedOps
Troubleshoot frequent Anchor runtime errors: discriminator mismatch, constraint failures, account deserialization, and CPI issues. Use when tests or txs fail with Anchor errors.
Problem Framing
by AmnadTaowsoam
Problem framing is the critical first step before any implementation,
Systematic Debugging
by mamba-mental
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Python Standards
by AmnadTaowsoam
Python coding standards define best practices for writing clean, maintainable,
systematic-debugging
by martin-janci
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
test-driven-development
by martin-janci
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first