CLAUDE
01Agent
When creating custom agent files in .claude/agents/, the YAML frontmatter format matters.
Claude Code plugin marketplace with 18 commands, 24 agents, and 33 coding rules
Agent
When creating custom agent files in .claude/agents/, the YAML frontmatter format matters.
Agent
Use when reviewing architecture, checking design patterns, auditing dependencies, or catching structural problems before they multiply.
Agent
Use when completing tasks autonomously, working independently, delivering PR-ready code, or needing end-to-end implementation without supervision.
Agent
Use when scanning for code pattern inconsistencies - prop naming, implementation approaches, boolean conventions, import patterns, deprecated usage.
Agent
Use when reviewing comments, checking docstrings, auditing documentation accuracy, or finding stale/misleading comments in code.
Agent
Use when debugging errors, investigating failures, finding root causes, or tracing unexpected behavior to its source.
Agent
Use when reviewing frontend design, checking UI quality, auditing visual consistency, or verifying responsive behavior across viewports.
Agent
Use when reviewing UX, user experience, interfaces, user-facing features, or need empathy/design perspective on code changes.
Agent
Use when reviewing error handling, finding silent failures, checking try-catch patterns, or ensuring errors surface properly with actionable feedback.
Agent
Use when writing commit messages, creating PR descriptions, naming branches, or needing git messages that explain why changes were made.
Agent
Use when choosing libraries, evaluating npm packages, deciding build vs buy, researching technology choices, or comparing library options.
Agent
Use when reviewing for logic bugs, edge cases, off-by-one errors, race conditions, or finding correctness issues before users do.
Agent
Use when finding, downloading, or fetching service logos, brand icons, official SVG assets, or adding integration logos.
Agent
Use when reviewing mobile UX, checking responsive design, testing touch interactions, or verifying mobile layouts work on phones and tablets.
Agent
Use when reviewing logging, checking error tracking, auditing monitoring patterns, or ensuring production issues are debuggable at 3am.
Agent
Use when reviewing performance, finding N+1 queries, checking algorithmic complexity, or catching efficiency problems before production.
Agent
Use when writing prompts, creating agent instructions, designing system prompts, or crafting LLM-to-LLM communication.
Agent
Use when scanning for dead-end error paths - errors without retry, failures without recovery options, places where users get stuck when things go wrong.
Agent
Use when reviewing for production readiness, fragile code, error handling, resilience, reliability, or catching bugs before deployment.
Agent
Use when reviewing security, checking for injection flaws, auditing authentication, or finding OWASP vulnerabilities before attackers do.
Agent
Use when auditing SEO, improving search rankings, implementing structured data, or optimizing for organic traffic and Core Web Vitals.
Agent
Use when simplifying code, reducing complexity, eliminating redundancy, or making code more readable without changing behavior.
Agent
Use when reviewing code style, checking naming conventions, auditing project patterns, or ensuring consistency with codebase conventions.