design-patterns

To choose a design pattern for refactoring, select based on the underlying pressure and constraints rather than pattern names. This pressure-based pattern filtering ensures you apply the lightest pattern that fits the specific code relationship shape.

Require Guarantee Maintain Assert contracts are a contract-first interface shaping method. They define caller preconditions, implementation postconditions, invariants, and boundary assertions to prevent interface mismatches in component relationships.

Make nondeterministic agent loops deterministic by reframing them as state-machine transitions. Use external tool validation to gate transitions rather than relying on model self-assessment, treating the model as a compiler and the harness as a linker.

You should avoid using design patterns when a single-call solution works, favoring readable interfaces over clever abstractions. The principle of "no pattern over the wrong pattern" means stopping early if the constraint does not require complex relationship shaping.

Handle state-driven behavior branching by applying state-machine transition gating. Define explicit contract shapes and use external validation to enforce transitions, ensuring determinism matters are resolved without over-engineering the architecture.