Skip to content
>devspeak
← glossary
patternCommunication Patterns

Preserve existing behavior

Tell the agent that everything that works today must keep working exactly the same way, except for the specific thing you asked to change.

a bit more technical

Treat all current user-visible behavior outside the requested change as a requirement, including quirks users may rely on. Changes should be additive or tightly targeted, and verified against existing tests or manual checks.

picture it

Asking a tailor to shorten your sleeves. You expect the same jacket back with shorter sleeves, not a new collar and different buttons too.

✗ instead of
add date sorting to the recipes page, make it better
✓ try
Add a date sort option to the recipes page. Preserve existing behavior: alphabetical stays the default and pinned favorites stay on top. List anything that would behave differently before changing it.
why it matters

Agents sometimes improve things you didn't ask about: defaults, error messages, sort orders, validation rules. Users notice even small changes. Saying this turns current behavior into an explicit rule.

what your agent might say
agent
Added date sorting. Existing behavior is preserved: alphabetical is still the default, and pinned favorites stay on top. The existing list tests still pass.
how you might use it
you → your agent
Add date sorting to the recipe list. Preserve existing behavior: alphabetical stays the default and pinned recipes stay on top. Tell me if anything else would change.
common mistake

Assuming the agent knows which current behaviors matter. It can't read your users' minds. Name the behaviors that matter most.

builds on