hard-eng

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.

Resolve material decisions with evidence-first questions when explicit or delegated by $he-plan.

Prove whether failures share one recurring root cause.

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

Design or review behavior tests, QA coverage, TDD, or mutation strength.

Find reproducible root causes for bugs, flakes, failures, or regressions.

Verify current repository, vendor API, or library facts before a decision.

Design or review terse, predictable agent skills.

Review branch, PR, commit, or WIP diffs against repository standards and intended behavior.

Design or review module boundaries, public APIs, ownership, abstractions, wrappers, or test seams.

Review owned code or proposed changes for auth, data, secret, dependency, injection, or LLM security risks.

Investigate or remediate Sentry issues through the installed `sentry` CLI.