project-guidelines-example
Example template for project-specific skill files covering architecture, patterns, testing, and deployment.
resilience-patterns
Circuit breaker, bulkhead, retry with jitter, graceful shutdown, health check patterns for production resilience.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
atomic-execution
Executes tasks in isolated states using atomic XML execution plans (GSD pattern).
micro-commit
Enforces strict, atomic commit hygiene. Splits large diffs into logical, revertible units.
circuit-breaker
Mandatory systemic pause when cumulative red flags exceed threshold. Forces disengagement across Trading, Spending, Relationships, Work, and Energy domains.
red-team-review
Bias-aware adversarial review for any artifact before shipping. 5-phase QA protocol with severity-weighted findings.
website-css
CSS architecture, design system, design tokens, utility classes, and styling patterns for AG product websites
technology-stack
Technology stack and architectural constraints. Use when choosing technologies, adding dependencies, or understanding zero-dependency requirements.
shared-base-extraction
Extracts duplicated properties, methods, and logic from sibling Blazor components into a shared intermediate base class. Covers identification of duplicated surfaces, base class creation, member migration, and @inherits directive updates. Use when three or more components share copy-pasted Parameter declarations, consolidating shared helper methods, or refactoring component inheritance hierarchies.
elixir-antipatterns
Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing. Trigger: During Elixir code review, refactoring sessions, or when writing Phoenix/Ecto code.
hexagonal-architecture-layers-java
Hexagonal architecture layering for Java services with strict boundaries. Trigger: When structuring Java apps by Domain/Application/Infrastructure, or refactoring toward clean architecture.
spring-boot-3
Spring Boot 3 patterns for configuration, DI, and web services. Trigger: When building or refactoring Spring Boot 3 applications.
ruthless-refactorer
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
skill-spawn
Research blockers and spawn new tasks to overcome them, updating parent task dependencies
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
write-an-adr
Write an Architectural Decision Record (ADR) to document a significant design choice. Use when user asks to write/create/document an ADR, or to record an architectural decision.
electrobun-teams
Use when orchestrating multi-agent Electrobun feature development. Explains the electrobun-feature-team architecture — UI agent (views, RPC contract) followed by backend agent (bun-side wiring) — the RPC contract handoff format, and how to run the team using CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
architecture-design
Use when designing new systems or significant features, evaluating architectural trade-offs, choosing between structural approaches, or when a task requires understanding system-wide design before writing code
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies