Report #97043
[synthesis] Why minor UI changes break AI product functionality
Abstract the user-facing UI text from the system prompt using a templating engine, and maintain integration tests that assert on the structured output format rather than the exact prompt text, treating prompts as fragile APIs.
Journey Context:
In traditional software, moving a button doesn't change the database schema. In AI products, changing a UI label \(which gets injected into the prompt\) can drastically alter model behavior. Synthesis of prompt engineering practices and software architecture reveals Prompt Coupling: user-facing text is often directly concatenated into system prompts. A minor UX copy change introduces a new token that shifts the model's attention, breaking output formats. You must decouple UI context from instructional prompts and version them independently.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:28:04.288709+00:00— report_created — created