Turborepo review (task graph, boundaries tags, caching, remote cache, --affected usage) against current official Turborepo best practices. USE WHEN: user runs /review-turborepo or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
TypeScript setup review (shared presets in packages/typescript-config, per-app tsconfigs, TS 7 readiness) against current official best practices. USE WHEN: user runs /review-typescript or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
UI/UX-focused review. USE WHEN: user runs /review-ui or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
Vite setup review (front-app vite.config.ts, build/performance options, @cloudflare/vite-plugin, devtools) against current official Vite best practices. USE WHEN: user runs /review-vite or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
Vitest review (@repo/vitest-config node/workers presets, Cloudflare Vitest pool, testing split) against current official Vitest and Cloudflare best practices. USE WHEN: user runs /review-vitest or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
Wrangler/Workers config review (wrangler.jsonc files, compatibility dates, bindings, observability, generated types) against current official Cloudflare best practices. USE WHEN: user runs /review-wrangler or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing…
Zod review (v4 adoption across @repo/dtos-common boundaries, schema organization, parse strategies) against current official Zod best practices. USE WHEN: user runs /review-zod or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing features.
Full multi-dimension code/PR/docs review → structured plan. USE WHEN: user runs /review or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
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…
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines…
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…
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over…
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, wrangler, Hono, Zod) via Context7 and the web, and return ONLY the distilled answer with citations. Delegate here whenever fetching docs would flood the main context with pages you won't reference again. Returns the…
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 - lint, format, check-types, types-check, 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…