systematic-debugging
Methodical problem-solving workflow for debugging issues. Use when facing bugs, errors, or unexpected behavior that isn't immediately obvious.
Methodical problem-solving workflow for debugging issues. Use when facing bugs, errors, or unexpected behavior that isn't immediately obvious.
Systematic technical debt reduction and code optimization agent. Use when refactoring code, reducing complexity, eliminating code smells, improving performance, cleaning up unused code, or modernizing legacy patterns. Handles dependency updates, architecture improvements, and codebase health metrics.
Core development standards, patterns, and best practices for React and React Native projects. Use this when users need guidance on code quality (Biome, TypeScript), testing (Jest), project structure (Domain-Driven Design), React best practices (useEffect guidelines), or React Native development with Expo.
Specialized agent for determining the optimal placement of components and logic in a Next.js project based on the "Scope Scope Rule". It prevents tech debt by strictly enforcing modularity: local by default, shared only when necessary. Trigger: "Where to put component", "Structure components", "Scope rule", "Shared vs Local", "Move component".
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Provides systematic debugging methodology for thorough root cause analysis with evidence-based investigation. Use this skill when investigating code, analyzing bugs, tracing errors, or understanding unexpected behavior.
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
Comprehensive observability and monitoring workflow that orchestrates metrics collection, logging, distributed tracing, and alerting systems. Handles everything from monitoring architecture design and implementation to APM integration, anomaly detection, and incident response automation.
Next.js App Router development standards. Triggers when working with Next.js applications, Server Components, Server Actions, or App Router patterns.
Debug API 500 errors and unexpected responses. Use when mobile apps get server errors, when API returns wrong data, or when investigating failed requests. Checks server logs, common error patterns, and Prisma query issues.
This skill should be used when the user asks "where is this API endpoint implemented", "find the code for this route", "which file handles this endpoint", "map API findings to code", or needs to correlate OpenAPI spec paths with source code locations. Also use when creating fix plans for code-first API projects (NestJS, Fastify, Express) after running aip-review, or when user mentions "find my NestJS controller", "locate Fastify route handler", "Express route definition".
Identify dangerous-but-tempting API patterns in React/Next.js/Supabase. Finds "footguns" - APIs that look safe but fail silently or have dangerous defaults. Inspired by Trail of Bits methodology.
Use when reviewing plugin quality, auditing plugins, analyzing the marketplace, checking plugins against Anthropic standards, or evaluating plugin architecture - provides systematic analysis methodology with validation framework
This skill should be used when the user asks to "detect project type", "analyze this project", "create project profile", "what tech stack is this", "scan project structure", "what database does this use", or when autonomous development starts in a new codebase. Detects package.json, pyproject.toml, go.mod, Cargo.toml to identify the technology stack. Also detects database providers (Supabase, Firebase, Prisma, etc.) and MCP availability.
Performance optimization techniques for Svelte 5 and SvelteKit applications. Use when users ask about performance, optimization, slow rendering, bundle size, memory leaks, profiling, lazy loading, code splitting, or when diagnosing performance issues in Svelte applications.
45+ reglas de performance para React/Next.js desde Vercel Engineering
Audit frontend code for security, UX regressions, performance, and accessibility issues. Use when reviewing React, Next.js, Vue, Svelte, or any frontend code changes. Triggers on "audit frontend", "review UI", "check accessibility", "a11y audit", "frontend security", "UX review", "performance audit", "review components", "audit React".
JavaScript development patterns for Metalsmith plugins, browser scripts, and Node.js tooling. Triggers when writing JavaScript code, creating Metalsmith plugins, browser functionality, Nunjucks templates, or Node.js build scripts. Enforces functional programming patterns, ES6+ features, JSDoc documentation, dual ESM/CJS module support, and Mocha testing. No TypeScript.
Debug Vercel deployment issues for the CoinSite Astro project. Use this skill when deployments fail, when checking deployment status after pushing to GitHub, or when investigating runtime errors on the deployed site. Provides CLI-based debugging workflow for Astro + Vercel SSR deployments.
Provides structured information about the Aurora/NestJS project folder hierarchy, explaining the purpose and responsibility of each directory and key files. Trigger: When user asks about project structure, folder organization, "where is X", or navigating the codebase.
Analyse component dependencies and usage patterns in a Drupal/Twig component library. Use when user asks to find where a component is used, check if a component can be safely removed, audit component dependencies, find components using specific properties, or analyse impact of refactoring a component.