ReddRadar
Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
debugging-strategies
Use when troubleshooting bugs, analyzing stack traces, using debugging tools (breakpoints, loggers), or applying systematic debugging methodology across any technology stack.
MadAppGang/claude-code 248
-
universal-patterns
Use when implementing language-agnostic patterns like layered architecture, dependency injection, error handling, or code organization principles across any technology stack.
MadAppGang/claude-code 248
-
testing-strategies
Use when writing tests, setting up test frameworks, implementing mocking strategies, or establishing testing best practices (unit, integration, E2E) across any technology stack.
MadAppGang/claude-code 248
-
phase-enforcement
Evidence-based phase completion enforcement for /dev:feature. Use when orchestrating 8-phase feature development to ensure artifacts exist before phase completion, validation criteria are addressed, outer loops are enforced, and show-your-work requirements are met.
MadAppGang/claude-code 248
-
ui-implement
Patterns for implementing UI improvements based on design analysis.
Works with review documents from dev:ui-analyse or /dev:ui command.
Includes Anti-AI design rules and visual verification.
MadAppGang/claude-code 248
-
ui-design-review
Prompting patterns and review templates for UI design analysis with Gemini multimodal capabilities.
Use when conducting design reviews, accessibility audits, or design system validation.
MadAppGang/claude-code 248
-
ui-analyse
UI visual analysis patterns using Gemini 3 Pro Preview multimodal capabilities.
Analysis-only - no code changes. Use dev:ui-implement for applying improvements.
Includes provider detection, prompting patterns, and severity guidelines.
MadAppGang/claude-code 248
-
ui-style-format
UI design style file format specification with reference image support.
Defines the schema for .claude/design-style.md and .claude/design-references/.
Use when creating, validating, or parsing project design styles.
MadAppGang/claude-code 248
-
design-references
Predefined design system references for UI reviews. Includes Material Design 3,
Apple Human Interface Guidelines, Tailwind UI, Ant Design, and Shadcn/ui.
Use when conducting design reviews against established design systems.
MadAppGang/claude-code 248
-
auth-patterns
Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.
MadAppGang/claude-code 248
-
api-design
Use when designing REST or GraphQL APIs, defining endpoints, implementing pagination/filtering, handling API versioning, or establishing API documentation with OpenAPI/Swagger.
MadAppGang/claude-code 248
-
golang-performance
Use when profiling Go applications (pprof), running benchmarks, optimizing memory/CPU usage, or debugging performance bottlenecks in production Go code.
MadAppGang/claude-code 248
-
bunjs-architecture
Use when implementing clean architecture (routes/controllers/services/repositories), establishing camelCase conventions, designing Prisma schemas, or planning structured workflows for Bun.js applications. See bunjs for basics, bunjs-production for deployment.
MadAppGang/claude-code 248
-
bunjs-apidog
Use when creating OpenAPI specs for Bun.js APIs, integrating with Apidog, documenting endpoints with schemas, or automating API specification imports via Apidog REST API. See bunjs for basics.
MadAppGang/claude-code 248
-
database-patterns
Use when designing database schemas, implementing repository patterns, writing optimized queries, managing migrations, or working with indexes and transactions for SQL/NoSQL databases.
MadAppGang/claude-code 248
-
rust
Use when building Axum applications, implementing type-safe handlers, working with SQLx, setting up error handling with thiserror, or writing Rust backend services.
MadAppGang/claude-code 248
-
bunjs
Use when building Bun.js/Hono applications, implementing HTTP endpoints, setting up Prisma/SQLite, writing Zod validation, or using Bun's test runner. See bunjs-architecture for layered patterns, bunjs-production for deployment.
MadAppGang/claude-code 248
-
bunjs-production
Use when deploying Bun.js to production, containerizing with Docker, setting up AWS ECS/Fargate, implementing Redis caching, hardening security, or configuring CI/CD pipelines. See bunjs for basics, bunjs-architecture for patterns.
MadAppGang/claude-code 248
-
golang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
MadAppGang/claude-code 248
-
python
Use when building FastAPI applications, implementing async endpoints, setting up Pydantic schemas, working with SQLAlchemy, or writing pytest tests for Python backend services.
MadAppGang/claude-code 248
-
error-handling
Use when implementing custom error classes, error middleware, structured logging, retry logic, or graceful shutdown patterns in backend applications.
MadAppGang/claude-code 248
-
dingo
Use when working with Dingo meta-language for Go, implementing optionals/results, using generics shortcuts, or transpiling .dingo files to .go while maintaining Go compatibility.
MadAppGang/claude-code 248
-
tanstack-query
Comprehensive TanStack Query v5 patterns for async state management. Covers breaking changes, query key factories, data transformation, mutations, optimistic updates, authentication, testing with MSW, and anti-patterns. Use for all server state management, data fetching, and cache invalidation tasks.
MadAppGang/claude-code 248
-
shadcn-ui
shadcn/ui component library patterns. Covers CLI usage, installation, component categories, theming with CSS variables, dark mode setup, and integration with React Hook Form + Zod. Use when adding UI components, setting up design systems, or implementing forms with shadcn/ui.
MadAppGang/claude-code 248