react-testing
Testing patterns for Vitest, React Testing Library, and Jest. Routes to component, hook, and integration test examples.
tailwind-styling
Generate responsive, performant Tailwind CSS styles for React components. Use when styling components, building design systems, or implementing responsive layouts.
agent-teams
Guide for coordinating multiple Claude Code instances as a team using Agent Teams. Covers TeammateTool operations, spawn backends, communication, task coordination, hooks, and orchestration patterns. Use when building multi-agent workflows requiring inter-agent communication.
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
compound-learnings
Extract patterns from git history and session files, recommend artifacts (skill/rule/hook/agent) based on frequency thresholds
devils-advocate
Forces adversarial reasoning before committing to decisions. Triggers on architectural choices, approach selection, and planning phases to prevent premature commitment bias.
document-refinement
Use when reviewing brainstorms, plans, or PRDs for clarity and readiness before next workflow phase. Assesses documents for vagueness, gaps, and YAGNI violations.
learn
Extract cross-session patterns from git history, PRs, and handoffs, then recommend artifacts (skill/rule/hook/agent) based on frequency thresholds. Use when consolidating recurring patterns into durable artifacts. For single-session reflection, use `reflect` instead.
multi-agent-architecture
Patterns for designing multi-agent systems with Claude Code - job description method, shared folder communication, handbook consolidation, context management. Use when building complex agent orchestrations.
reasoning-verifier
Verify LLM reasoning using Reverse Chain-of-Thought (RCoT) to detect overlooked conditions.
reflect
Reflect on the current session and suggest AGENTS.md improvements based on user corrections, repeated feedback, and patterns observed during interaction. Use when ending a session to encode lessons learned. Don't use for cross-session learning from git history - use `learn` instead.
skill-archetypes
Four common skill archetypes with structure templates - CLI reference, methodology, safety/security, and orchestration. Use when creating new skills to select appropriate structure.
skill-design-philosophy
Core philosophy for designing Claude Code skills - when to use skills vs agents, the knowledge test, and what makes skills valuable. Use when deciding component type or evaluating skill quality.
skill-eval
Test and iterate on a skill using parallel eval runs. Spawns with-skill and baseline runs, grades results, and helps improve the skill based on feedback. Use when testing skill quality or iterating on skill improvements.
skill-grader
Evaluate skill test run outputs against expectations and extract implicit claims.
skill-structure
Skill file structure, naming conventions, directory layout, frontmatter requirements, and invocation control. Use when creating skill files or slash commands to ensure correct format and validation.
add-config-field
Add new field to .agents.yml config schema (updates init.md templates, version, migration)
fluff-detector
Detect human-oriented content in LLM artifacts. Flags attribution, personas, redundant explanations, marketing language, and decorative elements that waste tokens without improving LLM behavior.
skill-auditor
Audit installed skills across project, global, and plugin levels. Lists skills with line counts, identifies improvement opportunities (conciseness, clarity, overlap, token waste). Use when reviewing skill quality, finding bloated skills, or optimizing token budgets.
Page 4 of 4 · 169 results