Chill
Load and apply evidence-first and changeset-scope before reassessing the approach.
Reassess the current approach and choose the smallest ordinary solution that meets the stated requirement.
Prefer existing code, dependencies, platform features, and established project patterns over new abstractions or custom machinery. Remove speculative flexibility, premature generalisation, unnecessary helpers, and work not required now.
Preserve complexity that is justified by concrete constraints, correctness, or evidence. Briefly state the simpler approach, then follow it if implementation was requested. Do not use simplification as a reason to discard requirements or widen the task.