On turning opinions into constraints

"Make it feel polished" is an opinion. Agents hear it all the time, and the output stays roughly the same because the sentence doesn’t constrain anything. A useful skill is that opinion forced into structure: when to activate, what to prefer, what to reject and how to know you’re done. Opinion is thin on its own Take a principle from the fluid UI work: Motion should feel physical. True, and still vague. A model can satisfy that sentence with a bounce easing, a 400ms fade or a spring, which means you can get three different products from one line of prose. The rewrite needs four answers before it becomes useful: when the rule applies, what the agent should choose by default, what it should refuse, and how it verifies the result. With those on the page, taste becomes something the agent can execute against instead of something it can nod at. The rewrite ladder Start with the opinion, then climb: # Vague Make interactive UI feel alive. # Trigger Use when building drawers, lists, hover…