Depth for Vitest tests of front- React 19 SPAs when DOM, RTL, TanStack Query hooks, or TanStack Router route-tree tests are needed. USE WHEN: adding jsdom or testing-library, writing tsx render or renderHook tests, testing createMemoryHistory plus RouterProvider, Suspense UI, or React 19 act fixtures. DO NOT USE WHEN…
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…
Use when building Hono web applications or when the user asks about Hono APIs, routing, middleware, JSX, validation, testing, or streaming. TRIGGER when code imports from 'hono' or 'hono/', or user mentions Hono. Use npx hono request to test endpoints.
USE WHEN: editing Cursor/Claude agent config, rules, hooks, skills, MCP, subagents, slash commands, or dual-tree sync; or when asking how Claude vs Cursor instructions are laid out in this monorepo. DO NOT USE WHEN: implementing app features, Workers, or frontend UI unless the task is specifically about agent tooling.
Code and design review of this repo by domain - architecture, ci, code-quality, configuration, performance, security, seo, simplicity, tests, ui: one parallel reviewer subagent per selected domain, verified findings, one consolidated plan in chat with IDs to answer. USE WHEN: user runs /review, optionally with domains…
USE WHEN: updating locked agent skills from skills-lock.json, refreshing upstream skill content, or running npx skills update for project skills. DO NOT USE WHEN: adding new skills (use npx skills add with explicit approval), running bare npx skills update without skill names, or updating project-local skills that are…
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
UI/UX polish, component design, animation decisions, and Tailwind v4 patterns for making interfaces feel right. Use when reviewing, writing, or refactoring UI code involving animations, transitions, CSS transforms, gestures, Tailwind utility classes, or interactive component behavior. Triggers on tasks involving…
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
Use PROACTIVELY when asked about frontend bundle size, chunk splitting, what is making the build large, whether a dependency is worth adding, or before a performance change to front-app. Runs the existing analyze script and returns ONLY a ranked chunk summary - the verbose per-module build output stays out of the main…
Use PROACTIVELY to look up external library / framework / SDK / API documentation (Cloudflare Workers, the cf CLI, Wrangler, Hono, Zod) via the installed documentation MCP collector and the web, and return ONLY the distilled answer with citations. Delegate here whenever fetching docs would flood the main context with…
Use INSTEAD OF the built-in Explore agent for any "where is X / which files do Y / how is Z wired" question in this repo. Returns file paths and one-line excerpts, never file dumps. Read-only. Unlike Explore it already knows this monorepo's layout, its boundary rules, and which paths are deny-listed, so it does not…
Use INSTEAD OF the built-in Plan agent to design an implementation approach in this repo - new endpoint, new Worker, new package, schema change, refactor spanning workspaces. Returns a step-by-step plan naming real files. Read-only; proposes, never edits. Unlike Plan it already carries this repo's architectural…
Use PROACTIVELY before opening a PR or after a batch of edits: runs the repository verification gate (pnpm run ci:agent - lint, format, check-types, boundaries, test, build) and reports ONLY failures that need a decision. Read-only - never auto-fixes, never edits files, and keeps verbose OXC/TypeScript/runner output…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: