.dotfiles

Design or review REST APIs, define endpoints, request/response schemas, or evaluate API contracts. Use when the user is designing a new API, reviewing an existing one, or asking about HTTP conventions.

Perform a structured code review. Use when the user asks to review code, check a PR, audit a file, or validate an implementation against best practices.

Systematically investigate and fix bugs, errors, or unexpected behavior. Use when the user reports a bug, shares an error/stacktrace, or asks why something isn't working.

Write or improve technical documentation. Use when the user asks to document code, write a README, generate API docs, write a technical spec, or explain how something works for other engineers.

Improve the internal structure of code without changing its behavior. Use when the user asks to clean up, refactor, simplify, or reduce complexity in existing code.

Review code or configuration for security vulnerabilities. Use when the user asks to audit security, check for vulnerabilities, review auth logic, or validate input handling.

Implement tasks from the change, writing actual code following the specs and design. Trigger: When the orchestrator launches you to implement one or more tasks from a change.

Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.

Create technical design document with architecture decisions and approach. Trigger: When the orchestrator launches you to write or update the technical design for a change.

Explore and investigate ideas before committing to a change. Trigger: When the orchestrator launches you to think through a feature, investigate the codebase, or clarify requirements.

Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend. Trigger: When user wants to initialize SDD in a project, or says "sdd init", "iniciar sdd", "openspec init".

Create a change proposal with intent, scope, and approach. Trigger: When the orchestrator launches you to create or update a proposal for a change.

Write specifications with requirements and scenarios (delta specs for changes). Trigger: When the orchestrator launches you to write or update specs for a change.

Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.

Validate that implementation matches specs, design, and tasks. Trigger: When the orchestrator launches you to verify a completed (or partially completed) change.

Vercel AI SDK 5 patterns. Trigger: When building AI chat features - breaking changes from v4.

Clean Code principles for readable, maintainable software. Trigger: When writing code, refactoring, or reviewing pull requests.

Conventional Commits specification and Keep a Changelog best practices. Trigger: When creating commits or updating CHANGELOG.md.

Django REST Framework patterns. Trigger: When building REST APIs with Django - ViewSets, Serializers, Filters.

Grails 5 framework patterns and best practices. Trigger: When working with Grails 5 applications - controllers, services, GORM, domains.

Test-Driven Development workflow for Grails applications with Spock. Trigger: When implementing features, fixing bugs, or refactoring in Grails projects.

Next.js 15 App Router patterns. Trigger: When working with Next.js - routing, Server Actions, data fetching.

Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.

Reviews GitHub PRs and leaves human, direct comments. Trigger: When user asks to review a PR, check a PR, or gives a PR URL.

Pytest testing patterns for Python. Trigger: When writing Python tests - fixtures, mocking, markers.

React 19 patterns with React Compiler. Trigger: When writing React components - no useMemo/useCallback needed.

Security-first development practices (Shift-Left Security). Trigger: When handling user input, authentication, data storage, or API design.

SOLID principles for object-oriented design. Trigger: When designing classes, refactoring code, or reviewing architecture.

Spock testing framework for Groovy and Java applications. Trigger: When writing tests with Spock - specifications, mocking, data-driven tests.

Tailwind CSS 4 patterns and best practices. Trigger: When styling with Tailwind - cn(), theme variables, no var() in className.

Test-Driven Development workflow for any project (UI, Backend, API). Trigger: ALWAYS when implementing features, fixing bugs, or refactoring - regardless of component. This is a MANDATORY workflow, not optional.

TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.

Vitest testing patterns with React Testing Library. Trigger: When writing unit tests - AAA pattern, mocking, async testing.

Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.

Zustand 5 state management patterns. Trigger: When managing React state with Zustand.

Creates new AI agent skills following the Agent Skills spec. Trigger: When user asks to create a new skill, add agent instructions, or document patterns for AI.

Syncs skill metadata to AGENTS.md Auto-invoke sections. Trigger: When updating skill metadata (metadata.scope/metadata.auto_invoke), regenerating Auto-invoke tables, or running ./skills/skill-sync/assets/sync.sh (including --dry-run/--scope).

Creates GitHub PRs following the Chained PRs workflow pattern. Trigger: When user asks to create a PR for a feature with sub-tasks, chained PR, or stacked PR workflow.

Implement tasks from the change, writing actual code following the specs and design. Trigger: When the orchestrator launches you to implement one or more tasks from a change.

Sync delta specs to main specs and archive a completed change. Trigger: When the orchestrator launches you to archive a change after implementation and verification.