topaz

Use when running behavior-preserving refactor, de-slop, hard-cut, or code refinement passes; deciding whether a code change is earned; separating structural fixes from style churn; preserving domain complexity; validating package-local gates; and knowing when a coherent coding pass is complete.

Decide whether a software task is code time or not code time, then execute with evidence-backed restraint. Use when asked to optimize, refactor, clean up, harden, review, fix, or improve code; when a request could tempt speculative edits; when deciding whether to patch now, measure first, report findings only, or stop because the change would weaken correctness, contracts, security, or maintainability.

LobeHub Zustand store conventions. Use when editing src/store, store slices, public/internal actions, dispatch actions, flattenActions, optimistic updates, selectors, maps, or class action migration.