I18n
Apply when implementing or reviewing internationalization in a web project. Active when standards.json features.i18n is true, or i18next/react-i18next/next-i18next in package.json, or a locales/ directory exists. Detected but undeclared → INFO, not FAIL.
Forms
Apply when building mobile forms — field anatomy, keyboard types, autofill, validation timing, error display, focus, submission, multi-step, state preservation. Auto-invoke when writing form screens.
Extract Tokens
Extract the project's design tokens (color, type, spacing, radius, shadow, motion) from codebase or design inputs into one source-of-truth file. Run before any design audit — the audit needs the user's tokens to check against. Never imposes values.
Standards Config
Apply when setting up a new project or when project config (standards.json) is absent. Documents the standards.json schema, what each field activates, and disabled_rules transparency.
Api Design
REST API design principles — resource naming, HTTP semantics, status codes, pagination, errors, auth, rate limiting, versioning. Framework-agnostic.
Delegation Setup
Fast agent delegation with early compaction, forks, teams, and audit logging. Run /claude-setup-perf to automate all configuration in one pass. Covers: settings.json (env vars + hooks), CLAUDE.md (delegation policy), scout.md subagent, plus version checks. Requires Claude Code v2.1.32+ (teams) or v2.1.117+ (forks).
Design System
The shared design contract for any UI — web or mobile. Owns tokens, spacing, type scale, color system, elevation, radius, interactive states, motion, state design, dark mode, density, iconography, microcopy, accessibility (WCAG 2.2 AA cross-platform), and information architecture. Platform deltas and Tier-1 R-rules live in web-standards:design and mobile-standards:design.
Design
Apply on any web UI change — Tier-1 PASS/FAIL standards (WCAG, WHATWG, CSS specs, Bringhurst) plus web-specific design rules (responsive layout, chrome, theming, aesthetic coherence, brand moments). The shared contract (tokens, color, spacing, type, motion, states) lives in design-standards:design-system. Auto-invoke on components, styles, layout, or theme work.
Cross Stack Contracts
Apply when 2+ stacks communicate (Flutter+NestJS, Next.js+NestJS, any frontend+backend) — error shape, pagination, auth header, versioning at the boundary. Active when standards.json stacks[] has 2+ entries, or any code touches an external API boundary.
Accessibility
Apply when building Flutter UI — Semantics labels, 4.5:1 contrast, touch targets, no color-alone signals, text scaling to 200%, reduced motion, RTL via EdgeInsetsDirectional, focus indicators, screen-reader announcements. Auto-invoke on any interactive widget or form field change.
Websockets
Apply when implementing or reviewing real-time WebSocket features — connection auth, reconnection, event schema, room authorization. Active when standards.json features.realtime is true, or socket.io/ws/WebSocket is in the manifest AND used in source (`@WebSocketGateway`, `io()`, `new WebSocket()` — `ws` in the manifest alone proves nothing, many tools bundle it).
Engineering
Apply when writing or reviewing any Dart or Flutter code — reusability, single source of truth, no hardcoded values, centralized cross-cutting concerns, consistent error handling, data-pipeline verification, widget patterns. Auto-invoke on any Flutter code change.
Verify Changes
Apply after completing any delivery task before reporting done, and when the user asks to verify or audit changes across any stack. Adversarial, evidence-only — a prose assertion without a tool call is MISSED, not PASS.
Nextjs
Apply when writing or reviewing Next.js + React + Tailwind + shadcn — app router, Server Components by default, deep client boundary, CSS-variable tokens, shadcn base, React Query with structured keys, RHF + Zod, next/image + next/font, no barrel files, no any/as. Auto-invoke on changes under app/, components/, lib/.
Engine
Apply on every task, every stack — how the agent works, plans, makes claims, and writes code. Sections referenced as engine:work, engine:planning, engine:honesty, engine:minimize-code, engine:code-rules.
Nestjs
Apply when writing, reviewing, or auditing NestJS + Prisma code — module/controller/service/repository discipline, thin controllers, validated DTOs, repository-wrapped Prisma, consistent error shape, Prisma schema workflow, plus a production-concern audit (rate limiting, idempotency, webhooks, shutdown, health) via Detect → Check → Suggest. Auto-invoke on changes under src/.
Observability
Apply when adding logging, analytics, or crash reporting to a mobile app — one logger, structured events, level thresholds by build mode, crash hooks, PII discipline, consent. Auto-invoke on observability/logging/analytics code.
Aesthetic Coherence
Detect aesthetic mixing — a screen committing to two design languages at once (glass + neumorphism, bento + brutalist) is the #1 "assembled, not designed" tell. Scores each aesthetic's signals, flags mixed signatures, then hands per-aesthetic spec compliance to the audit engine. Use on a surface that feels "off" but passes token/contrast audits.
Production Readiness
Apply when auditing a Next.js app for production readiness — error boundaries, Suspense, optimistic UI, image optimization, metadata/OG/sitemap, CSP + security headers, analytics consent, Core Web Vitals, env-aware logging. Detect → Check → Suggest, never blindly enforces. Auto-invoke when reviewing app-level wiring, route config, or release readiness.
Pre Ship
Full quality gate before merge — lint, then all installed web standards. Narrow with "design" (design contract only) or "theme" (tokens/dark-light/hydration only).
App Audit
Run full Flutter app audit: pre-ship checks, design quality, screen states. Explicit command only.
Performance
Apply when building or reviewing web apps for performance — Core Web Vitals, images, fonts, bundles, caching, SSR/hydration. Auto-invoke when touching build config, image handling, or data fetching.