sgaabdu4

Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.

Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.

Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.

Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.

Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.

Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.

Interview one clear question before planning/building ideas, features, codebase maps, specs, UI flows, prototypes, or final plans.

Use for /he:implement; owner-first implementation after PASS, deterministic owner reuse, and lint/scanner/gate coverage.

Produce and approve one lean living Feature Brief after $he selects lifecycle work.

Route explicit lifecycle requests or genuinely complex or high-risk staged work through one living Feature Brief.

Design or review DESIGN.md, UI tokens, and component ownership.

Run deterministic project gates, including worktree readiness.

Prove browser/device behavior and visual evidence.

Execute an approved PLAN one demonstrable vertical slice at a time until the actual implementation is green.

Turn a verified process failure into narrow durable prevention without blocking normal product delivery.

Deliver one exact green Hard Eng snapshot through publish gates, authorized Git actions, and required CI.

Flutter Riverpod app architecture. Use before changing a Flutter app or package that uses Riverpod; skip non-Riverpod Flutter stacks and pure-Dart work without Flutter/Riverpod app context.

Appwrite backend development and operations. Use for Appwrite SDK work; any Appwrite CLI command or failure must route through the CLI safety branch.