Development

Continuous frontend delivery loop — cycles subagents through test → diagnose → fix → review → re-test until E2E and review are clean. Use to develop, fix, harden, or finish a frontend feature/epic verified by tests.

Create or update Figma Code Connect template files (.figma.ts/.figma.js) that map Figma components to code. Use for Code Connect, Figma component mapping, design-to-code.

Develop, configure, and debug Fastify (Node.js/TypeScript) servers and REST APIs — routes, plugins, JSON Schema validation, hooks, auth, serialization, performance, deployment. Triggers: Fastify, server.ts, app.ts, fastify.config.

Disciplined diagnosis loop for hard bugs and performance regressions — reproduce → hypothesise → instrument → fix → regression-test. Use when asked to diagnose/debug, something is broken or failing, or a perf regression is reported.

Write a structured retrospective of a delivery-loop run (frontend-delivery-loop, backend-delivery-loop, or fullstack-delivery-loop) that judges what went well, what went badly, where time/roundtrips/tool calls were wasted and in which skill or agent, how the agents integrated, and the session id + trace file paths — then save it as a Markdown report for skill-evolution-factory to act on. Use this the moment a delivery loop finishes (or stalls), whenever the user says "retro", "post-mortem", "...

Explains Cypress tests (E2E and component) and how Cypress works — use to understand, review, or critique tests without editing code, even if the user only says "tests". For creating or fixing tests, prefer cypress-author.

Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.

Creates, updates, and fixes Cypress tests (E2E and component) — use to write, add, update, or fix failing/flaky tests, even if the user only says "tests". For explaining or reviewing without edits, prefer cypress-explain.

Organize CSS using BEM, SMACSS, and CSS-in-JS patterns. Use when building scalable, maintainable styling systems with proper naming conventions.

Create professional SVG logos, brand identities, icons, wordmarks, and visual marks — multiple concepts, layouts, and color variations. Use when asked to design a logo, brand identity, icon, or visual mark.

Core Web Vitals reference for measuring, diagnosing, and improving LCP, INP, and CLS page performance against Google's thresholds

Write and apply Conventional Commits — type(scope): subject, imperative mood, with body and BREAKING CHANGE footer when needed. Use when committing staged work or asked to write, review, or standardize a commit message.

React composition patterns that scale — compound components, render props, context providers, lifting state. Use when refactoring boolean-prop-heavy components or designing flexible, reusable component APIs (incl. React 19)

The bar for any code you write, edit, or review. Read these rules whenever you are writing or reading any code

Create beautiful visual art in .png and .pdf documents using design philosophy. Use when the user asks to create a poster, piece of art, design, or other static visual piece.

BullMQ Redis-backed job queues in Node.js/TypeScript — workers, delayed/repeatable jobs, flows, rate limiting, retries. Use for background jobs, job scheduling, or reliable async processing.

Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.

Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

Turn backend test ambiguity into one practical test packet — API/service/repo/auth coverage, fixture & seed/reset strategy, mock-vs-container choices, contract checks, and flaky-suite stabilization across local and CI.

Shared backend guide for Langfuse's Next.js/tRPC/BullMQ/TypeScript monorepo — tRPC routers, public REST endpoints, BullMQ processors, services, Prisma/ClickHouse access, Zod validation, and backend tests across web/worker/shared.

Design backend systems — REST/GraphQL/gRPC APIs, microservices, database schemas, auth, caching, message queues, scalability. Use when designing backend services, APIs, data models, distributed systems, or auth flows.

Continuous backend delivery loop — cycles subagents through test → diagnose → fix → review → secure → re-test until the suite, quality, and security gates are clean. Use to develop, fix, harden, or finish a backend feature/service/endpoint.

Analyze a codebase and generate Project_Architecture_Blueprint.md — detected stacks and architecture patterns, diagrams, layers, cross-cutting concerns, extension guidance. Use to document, map, or blueprint a project's architecture or keep it consistent.

Build inclusive, WCAG-compliant UIs. Use for a11y, screen readers, ARIA, keyboard nav, contrast, or accessibility audits.