architecture-simplification

Add a pattern only when a concrete trigger exists: Adapter for external boundaries, Strategy for three or more interchangeable behaviors, Repository for persistence boundaries, and Factory for platform-specific construction. Without a trigger, use a plain function.

Trace the workflow from entry point to core behavior, assign one primary role per touched file, and identify the true boundary such as DB, HTTP API, or filesystem. Then choose the smallest design, starting with reusing existing code before extracting helpers or abstractions.

Use the Repository pattern only at a persistence boundary where data storage is abstracted from business logic. If no real persistence boundary exists, a plain function keeps the design smaller and easier to test.

Classify each piece of state by its owner: server cache in Query, shared client state in Zustand, shareable UI state in the URL, component-local state in React, persistent data in the DB, or data owned by an external system.

The workflow relies on judgment when tracing workflows and naming module roles, so results depend on how accurately boundaries are identified. It guides decisions but does not enforce them automatically in code.