crew

Plan and execute a feature through the morpheus orchestration flow

Push the crew's feature branch and open a pull request (host-agnostic)

Run consolidated review across code quality, security, and design conformance

Run pre-PR ship gate and return a go/no-go summary

Frontend e2e test author/runner (Cypress). Runs the suite and reports only failures. Invoked by the morpheus orchestrator. Not for standalone or automatic use.

Orchestrator for multi-agent feature work. Launch manually with `claude --agent crew:morpheus`. Plans work, delegates to specialist workers, synthesizes results.

Backend test author/runner (xUnit / integration tests for the .NET layer). Runs the suite and reports only failures. Invoked by the morpheus orchestrator. Not for standalone or automatic use.

Visual design-conformance verifier. Compares the rendered UI against a provided design reference (Figma export, image, or spec) using a browser-automation MCP (e.g. Playwright) when one is configured, and reports mismatches. Read-only on code. Invoked by the morpheus orchestrator. Not for standalone or automatic use.

Backend implementer for C#/.NET and Optimizely CMS (content types, blocks, IContentRepository, scheduled jobs, init modules), MVC controllers, and Razor views. Invoked by the morpheus orchestrator. Not for standalone or automatic use.

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.

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".

Conventions for server-rendered frontends — Optimizely/.NET MVC with Razor views and React used as mounted islands/widgets rather than a full SPA. Use for tasks involving Razor/.cshtml views, Optimizely/.NET MVC, display templates/IContentRenderer, or React mounted as islands/widgets. Load when the repo's frontend mode is "server-rendered".

4 hooks across 2 events