General-purpose React Testing Library guide with Vitest. Use when writing, reviewing, or setting up React component and hook tests. Covers project setup from scratch, RTL query priority, userEvent, async patterns, mocking strategies, and common anti-patterns. Applicable to any Vite + React project.
Safe, incremental refactoring of React UI applications. Use when restructuring components, extracting hooks, migrating state management, reorganizing file structure, or reducing technical debt in React code. Enforces behavior preservation, baby-step execution, and verification at every step.
Web application security best practices based on OWASP Top 10:2025. Use when reviewing code for vulnerabilities, implementing auth/authorization, handling user input, working with file uploads, managing secrets, or building API endpoints. Covers React, Express, MongoDB, and JWT security.
Use when investigating bugs, errors, or unexpected behavior. Activates when something is broken and needs diagnosis. Enforces root-cause analysis before any fix attempt.
Use when you have an approved design or feature spec and need to create a step-by-step implementation plan. Activates after brainstorming/design approval. Breaks work into small, verifiable tasks.
Two execution agents usable with or without a spec-driven workflow: implementer (build one task and self-verify) and test-writer (add or extend tests without changing production behavior).
Use proactively to implement ONE task/slice from an implementation plan (or one clearly scoped request). Discovers the project's stack and conventions before writing anything, applies whichever skills fit the task type, and self-verifies with the project's existing tests + typecheck before finishing. Safe to run in…
Use proactively to add or extend tests for existing code — backend services, domain/business logic, or UI components and hooks. Discovers the project's test stack and split conventions first, writes only test files, and self-verifies by running the suite + typecheck with pasted evidence before finishing.
Frontend engineering skill pack for React 19 + Next.js 15 (App Router): code architecture/placement, React best practices, and Next.js patterns. TypeScript now lives in typescript-skills; React Testing Library in testing-skills.
Code organization and architecture decisions for React 19 + Next.js 15 App Router (TypeScript). WHERE code lives, not HOW to write it. Covers: project folder structure, feature-based organization, component splitting rules, constants/utils/helpers/services placement, business logic separation, naming conventions…
Modern React best practices and anti-pattern catalog (2025-26). Use when writing, reviewing, or refactoring React components, hooks, and state management. Covers component design, state patterns, hooks misuse, performance, data fetching, and code organization.
Read-only research agent that locates, gathers, and fact-checks information from the codebase or the public web and returns it in a structured, cited format. Never edits files.
Read-only research agent. Finds information either inside this project (code, docs, config) or on the public internet, and returns it in a strict, structured format. Use when you need to locate, gather, or fact-check information without modifying anything. It never edits files and never runs deep-research.
Spec-Driven Development workflow: spec -> plan -> implement -> test -> verify -> retro. Ships the authoring and verification agents, the multi-agent retrospective skill, and the slash commands that drive the chain. Execution agents come from code-agents.
Use proactively when an agreed set of requirements (a spec, ticket, or clear request) needs a structured Implementation Plan before any code is written. Read-only architect that verifies the incoming requirements, flags gaps, recommends a better approach where it sees one, and maps the work onto the project's actual…
Read-only requirements-completion checker. Use after a feature is claimed done to verify every plan item / acceptance criterion is actually implemented — focus on completeness and traceability, not code quality.
Use proactively when a feature or change needs a written specification before any plan or code exists. Read-only-except-specs author for Spec-Driven Development — turns a request plus design sources (text, Figma links, screenshots, generated design skeletons, existing docs/plans, repo code) into a single concise spec…