crew

.NET backend stack conventions — MVC controllers, Razor server-side ownership, dotnet build specifics. Load when the resolved backend stack is dotnet. If the project also uses Optimizely CMS, also load `cms-optimizely`.

Node backend stack conventions — service framework conventions (NestJS/Express/Fastify), headless CMS/Graph client usage, npm/pnpm/yarn workspace awareness. Load when the resolved backend stack is node.

Optimizely CMS conventions — content types, blocks, IContentRepository, scheduled jobs, init modules. Composes on top of `backend-dotnet`; load additionally when the project references EPiServer.CMS/Optimizely.CMS.

Token/context discipline — process large data with code and surface only the answer, never read raw bulk output into context. Preload into agents that run verbose commands (tests, builds, log/data analysis). Use whenever about to read a large file, command output, or big API/tool response.

Reading a project's design tokens and reporting visual findings in token terms rather than raw pixels — where tokens live per system (CSS custom properties, Tailwind, SCSS, a tokens JSON, Figma variables), which of them survive to runtime, and how to map a measured value back to the token it should have been. Load when checking rendered UI against a design reference.

Core code-quality rules — YAGNI, KISS, DRY with judgment, small single-purpose units, clear naming, minimal-scope diffs. Preload into implementer agents and consult during any code review. Use whenever writing, refactoring, or reviewing code.

Conventions for decoupled/headless frontends — a React SPA (or Next.js) consuming Optimizely's Content Delivery API / Optimizely Graph (GraphQL) rather than Razor server rendering. Use for tasks involving a headless/decoupled Optimizely frontend, Content Delivery API or Optimizely Graph, or a React/Next.js SPA against a CMS. Load when the repo's frontend mode is "headless".

Next.js frontend stack conventions — App Router, Server/Client Components, data fetching (e.g. Optimizely Graph), npm build specifics. Load when the resolved frontend stack is nextjs.

React frontend stack conventions — React, Redux (slices/selectors), vanilla JS, HTML, SCSS/CSS, Vite/npm build specifics. Load when the resolved frontend stack is react.

Conventions for server-rendered frontends — a server template renders the page shell, with a client-side framework layered in as islands/widgets rather than a full SPA. Covers Razor (.NET/Optimizely) and Blade (Laravel). Next.js/RSC is not covered here — crew's mode vocabulary treats Next.js as headless (see frontend-nextjs) even though it server-renders. Load when the repo's frontend mode is "server-rendered".

Loop-mode discipline for orchestrated runs — recognize loop intent ("keep going until done", "loop this", "finish it", "clear all the stale ones", "bump everything SAFE"), offer to loop on open-ended work, and run to completion under explicit stop rules that always end at the run's terminal gate. Preload into orchestrator agents (crew's morpheus, keymaker); each defines its own bindings. Use whenever the user asks to keep going, loop, or finish the work without further check-ins.

ASD-STE-100 (Simplified Technical English) for operator-facing messages — short sentences, active voice, one term per thing, exact numbers. Preload into agents that report to the operator directly (plans, gates, summaries, blockers). Use whenever writing a message the operator reads to make a decision.

Cypress test conventions — e2e spec writing and component testing. Load when the resolved frontend e2e tool is cypress, or when cypress is the resolved frontend unit test tool.

Jest frontend component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running. Load when the resolved frontend unit test tool is jest.

Node backend test conventions — Vitest or Jest, detected by config file (vitest.config.* vs jest.config.*/package.json "jest" key). Load when the resolved backend stack is node.

Playwright e2e test conventions — spec writing, fixture/mock patterns, and running. Load when the resolved frontend e2e tool is playwright.

Vitest component/unit test conventions — test authoring with React Testing Library, mocking patterns, and running. Load when the resolved frontend unit test tool is vitest.

.NET backend test conventions — xUnit test authoring and running, integration tests for the .NET layer. Load when the resolved backend stack is dotnet.