Agent Skills

---

name: integration-e2e-testing

description: Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.

---

name: llm-friendly-context

description: Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

---

name: recipe-add-integration-tests

description: Add integration/E2E tests to existing codebase using Design Docs

---

name: recipe-build

description: Execute materialized task files in autonomous execution mode

---

name: recipe-design

description: Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval

---

name: recipe-diagnose

description: Investigate problem, verify findings, and derive solutions

---

name: recipe-front-adjust

description: Adjust an already-implemented UI in-session with verification against the design source

---

name: recipe-front-build

description: Execute materialized frontend task files in autonomous execution mode

---

name: recipe-front-design

description: Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval

---

name: recipe-front-plan

description: Create frontend work plan from design document and obtain plan approval

---

name: recipe-front-review

description: Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.

---

name: recipe-fullstack-build

description: Execute materialized fullstack task files with layer-aware agent routing

---

name: recipe-fullstack-implement

description: Orchestrate full-cycle implementation across backend and frontend layers

---

name: recipe-implement

description: Orchestrate the complete implementation lifecycle from requirements to deployment

---

name: recipe-plan

description: Create work plan from design document and obtain plan approval

---

name: recipe-quality-profile

description: Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.

---

name: recipe-reverse-engineer

description: Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow

---

name: recipe-review

description: Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.

---

name: recipe-update-doc

description: Update existing design documents (Design Doc / PRD / ADR) with review

---

name: requirement-convergence

description: Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.

---

name: subagents-orchestration-guide

description: Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.

---

name: test-implement

description: Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

---

name: testing-principles

description: Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.

---

name: typescript-rules

description: React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.