helix-web

HELIX web/frontend operator flow — owns the application surface a customer interacts with: site/app deploys, page perf, RUM/web monitoring (page errors, conversion funnel), and frontend release ops. Engage ONLY when the prompt names an explicit web/app-deploy verb (deploy/ship a feature to production, publish a build, add monitoring for a user-facing flow like checkout, optimize page performance). Do NOT engage on product-shaped asks ("plan the change", "the PRD says…") — DEFER to the `helix` product flow first; it frames the work and surfaces helix-web as a cross-flow prerequisite. Do NOT engage on infra-shaped verbs (terraform/tofu, CI runners, secrets, provider credentials) — DEFER to helix-infra. Do NOT engage on data-shaped verbs (backfill, ingest, schema migration) — DEFER to helix-data. Honor explicit operator prefix (/helix-web ...) and env override (HELIX_METHODOLOGY=helix-web) — stay silent otherwise.

By DocumentDrivenDX schedule Updated 6/7/2026