tworkflow

Use when context usage needs checking or a compact/clear decision is due — a context warning or usage figure appears, the user asks whether to compact or clear, the session shows degradation (re-read files, repeated corrections, forgotten constraints), or a dev-workflow phase boundary is reached (step committed, review or QA report delivered).

Structured development loop — plan, implement in small commits, review with three fresh-context lenses, QA with a visual screenshot step. Use when the user asks to plan a feature, scope a change, review a branch or diff, run QA or visual QA on the app, or implement any multi-file feature, migration, or behavior change — also when they ask "what's the process" for shipping. Not for trivial fixes (typos, copy, dependency bumps) or single-file changes; handle those directly.