rhize-devflow

DevTools-protocol mechanics reference for the `chrome-devtools` MCP server, used by `/rhize-devflow:browser-qa` when that server is the active browser capability. Use when the user asks specifically about Chrome DevTools MCP tool names/parameters, connecting to a running Chrome instance, or MCP-level configuration/troubleshooting for that server — not for general "test in the browser" requests, which should go through `/rhize-devflow:browser-qa` instead.

Promote a completed feature or task branch through Rhize's repository-governed protected-branch workflow. Use when implementation is complete and the user says "push to main" or "push to dev and main", or otherwise explicitly asks to ship or promote the completed branch. Treat those phrases as authorization for the appropriate PR-based promotion sequence, not a raw push to a protected branch; preserve narrower user overrides and repository-specific release policy.

Enforce consistent data-mutation patterns across Next.js apps on Vercel with Supabase, Sanity, and Payload CMS — so cache tags, query keys, and revalidation stay aligned and data never goes stale. Use when the user reports "stale data", "not updating", "cache", "revalidate", "mutation", "optimistic update", "data is out of sync", "had to hard-refresh", or when reviewing React Query, Server Actions, Payload hooks, or Sanity writes. Scores mutations (9.0 warning / 7.0 critical), runs cross-layer validation, and generates fix plans via the read-only /rhize-devflow:mutation-check command (scoped, --all, and --fix-plan modes).

Foundational workflow patterns for large-codebase development — CodeGraph-first structural discovery paired with semantic impact mapping, component/function registry reuse, context hygiene, regression prevention, anti-pattern detection at write-time, and skill-refinement meta-patterns. Use when the user asks about "design patterns", "workflow optimization", "prevent regression", "anti-patterns", "dependency mapping", "impact map", "CodeGraph", "component registry", "why did this break again", or wants durable development guardrails. Reference layer that informs context-engineering and error-lifecycle-management; also encodes Boris Cherny's verify-first and worktree practices.

End-to-end production error lifecycle for Next.js/TypeScript on Vercel — triage, root-cause analysis, deployment correlation, and fix verification using Sentry, Vercel, and GitHub. Use whenever the user mentions an "error", "bug", "crash", "exception", "stack trace", "500/404", "timeout", "failed deployment", "production issue/incident", "memory leak", "bundle size", or something is "slow" or "broken" — and when correlating an error spike to a recent deploy or commit. Leads the operational response (Sentry+Vercel correlation, P0/P1/P2 severity, incident protocol); complements the official engineering:* and sentry:* skills.

Rhize-opinionated best practices for Sanity Studio config, schema design, GROQ queries, TypeGen, Portable Text, visual editing, page builder, image handling, localization, and next-sanity v11 integration. Use when working in a Sanity codebase — writing or reviewing defineType/defineField schemas, GROQ/defineQuery, Studio structure, stega/visual editing, or Sanity-powered Next.js frontends. Encodes Rhize conventions (named exports only, SCREAMING_SNAKE_CASE queries, model what things ARE) that layer on top of the official sanity:* plugin; defer to that plugin for exhaustive API reference, use this for Rhize house style and the Payload-vs-Sanity split.

Rhize conventions for instrumenting Next.js/TypeScript code with Sentry — exception capture (captureException), custom performance spans (startSpan), and structured logging (logger.fmt). Use when the user wants to "add Sentry", "capture exception", "add tracing/spans", "instrument" an API call or user interaction, or "set up structured logging" in app code. This is the write-the-code companion to error-lifecycle-management (which handles triage/RCA); for full per-framework SDK setup defer to the official sentry:* developer-kit skills and keep this for Rhize house patterns.

Safely simplify recent or explicitly scoped code changes by consolidating duplicated policy, removing accidental complexity, and eliminating unnecessary work without changing behavior. Use after implementation or before delivery when the user asks to simplify, consolidate, deduplicate, reduce complexity, apply React best practices, remove redundant state/effects, or review recent code for a cleaner solution. A verified no-op is valid; never expand into broad redesign or unrelated cleanup.

Classify changed regression tests as behavior, artifact, or structural contracts and produce or validate fail-closed, state-bound evidence metadata, including an explicit unavailable status while trusted test execution is not implemented. Use before review when tests changed, a change claims regression coverage, or someone asks whether a test actually protects behavior. Do not route data/cache mutation consistency requests here.