ReddRadar
Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
testing-frontend
Use when writing component tests, testing user interactions, mocking APIs, or setting up Vitest/React Testing Library/Vue Test Utils for frontend applications.
MadAppGang/claude-code 248
-
vue-typescript
Use when building Vue 3 applications with TypeScript, implementing Composition API components, setting up Pinia stores, or working with Vue Router. Covers script setup, composables, and reactive state.
MadAppGang/claude-code 248
-
react-typescript
Modern React 19+ patterns with TypeScript including function components, hooks, state management, TanStack Query integration, form handling with Zod, error boundaries, and performance optimization. Use when building React applications, implementing components, or setting up state management.
MadAppGang/claude-code 248
-
state-management
Use when choosing state management solutions, implementing global stores (Zustand, Pinia), managing server state (TanStack Query), or handling URL state in frontend applications across React and Vue.
MadAppGang/claude-code 248
-
tailwindcss
TailwindCSS v4 patterns with CSS-first configuration using @theme, @source, and modern CSS features.
Covers design tokens, CSS variables, container queries, dark mode, and Vite integration.
Use when configuring Tailwind, defining design tokens, or leveraging modern CSS with Tailwind utilities.
MadAppGang/claude-code 248
-
browser-debugging
Systematically tests UI functionality, validates design fidelity with AI visual analysis, monitors console output, tracks network requests, and provides debugging reports using Chrome Extension MCP tools. Use after implementing UI features, for design validation, when investigating console errors, for regression testing, or when user mentions testing, browser bugs, console errors, or UI verification.
MadAppGang/claude-code 248
-
tanstack-router
TanStack Router patterns for type-safe, file-based routing. Covers installation, route configuration, typed params/search, layouts, and navigation. Use when setting up routes, implementing navigation, or configuring route loaders.
MadAppGang/claude-code 248
-
css-modules
CSS Modules with Lightning CSS and PostCSS for component-scoped styling.
Covers *.module.css patterns, TypeScript integration, Vite configuration, and composition.
Use when building complex animations, styling third-party components, or migrating legacy CSS.
MadAppGang/claude-code 248
-
documentation-standards
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
MadAppGang/claude-code 248
-
task-routing
Use BEFORE delegating any complex task to a subagent. Contains the routing table that maps task patterns to the correct specialized agent. MUST be consulted before using the Task tool for delegation decisions. Trigger keywords - "delegate", "subagent", "agent", "research", "implement", "investigate", "debug", "architect".
MadAppGang/claude-code 248
-
brainstorming
Collaborative ideation and planning with resilient multi-model exploration, consensus scoring, and adaptive confidence-based validation
MadAppGang/claude-code 248
-
plugin-sdk-patterns
Unified patterns and templates for creating consistent Claude Code plugins. Use when creating new plugins, designing plugin architecture, implementing builder patterns, or standardizing plugin structure. Trigger keywords - "plugin SDK", "plugin template", "plugin pattern", "builder pattern", "plugin structure", "new plugin", "plugin architecture".
MadAppGang/claude-code 248
-
mcp-standards
MCP server standardization patterns for Claude Code plugins. Use when implementing MCP servers, designing tool interfaces, configuring MCP transports, or standardizing MCP naming conventions. Trigger keywords - "MCP", "MCP server", "MCP tools", "MCP transport", "tool naming", "MCP configuration".
MadAppGang/claude-code 248
-
test-coverage
On-demand test coverage analysis. Use when identifying untested code, finding test gaps, measuring coverage metrics, or improving test quality. Trigger keywords - "test coverage", "coverage report", "untested code", "test gaps", "missing tests", "coverage metrics".
MadAppGang/claude-code 248
-
audit
On-demand security and code quality audit. Use when checking for vulnerabilities, security issues, code smells, or compliance problems. Trigger keywords - "audit", "security check", "vulnerability scan", "code quality", "compliance", "security audit".
MadAppGang/claude-code 248
-
context-detection
Use when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g., React + Go).
MadAppGang/claude-code 248
-
test-driven-development
Use when writing production code. Enforces RED-GREEN-REFACTOR cycle: write failing test, make it pass, improve design. Prevents test-after development and ensures verified behavior.
MadAppGang/claude-code 248
-
systematic-debugging
Use when debugging failures, errors, or unexpected behavior. Covers root cause investigation, data flow tracing, hypothesis-driven debugging, and fix verification to prevent trial-and-error approaches.
MadAppGang/claude-code 248
-
agent-coordination-discipline
Use when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents. Covers delegation criteria, external-model patterns, task isolation, and agent selection strategies.
MadAppGang/claude-code 248
-
verification-before-completion
Use when claiming task completion or marking items as done. Covers completion evidence requirements, verification methods, and anti-rationalization patterns.
MadAppGang/claude-code 248
-
worktree-lifecycle
Use when starting isolated feature work or before executing implementation plans. Manages full worktree lifecycle from creation through cleanup with safety checks and error recovery.
MadAppGang/claude-code 248
-
optimize
On-demand performance and optimization analysis. Use when identifying bottlenecks, improving build times, reducing bundle size, or optimizing code performance. Trigger keywords - "optimize", "performance", "bottleneck", "bundle size", "build time", "speed up".
MadAppGang/claude-code 248
-
adr-documentation
Architecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision", "decision log".
MadAppGang/claude-code 248
-
sequence-best-practices
Email sequence design and optimization best practices
MadAppGang/claude-code 248