The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Embed the signup form on the homepage and the blog sidebar so new signups go into the same audience…
Execute — do the immediate task
+Embed the signup form on the homepage and the blog sidebar so new signups go into the same audience and receive the "newsletter" tag. Place the homepage form above the fold and the sidebar one on every blog post page. Verify the embedded code renders on mobile and that submissions show up in the audience within five minutes. Tell me if any CSS conflicts need a developer.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I hand the embed to the web developer, make the code easy to drop in: produce a…
Improve — make it easier to accept
+Before I hand the embed to the web developer, make the code easy to drop in: produce a mobile-friendly embed that won’t break site styles, include a short integration note for the developer about target container size and any CSS classes to avoid, and flag any steps that would slow approval from our freelance developer or the operations lead.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I embedded the signup form in the blog sidebar and the site layout shifted; the developer is…
Decide — diagnose the stuck moment
+Embed broke the site layout
I embedded the signup form in the blog sidebar and the site layout shifted; the developer is pushing back saying the widget’s CSS is clashing. I don’t know if I should override styles, ask for a sandbox, or switch to a plain HTML form. Which choice will minimize friction with the developer and keep the form responsive? Give the step I should take now and the one thing to test after deployment.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I keep running into developers to get embeds to behave, which delays launches. Is the recurring…
Become — change the pattern
+Every embed needs developer time
I keep running into developers to get embeds to behave, which delays launches. Is the recurring cost due to using complex embed types, inconsistent placement rules, or failure to standardize container styles? Recommend one change to our embed approach that reduces dev time and a short developer-facing style guide (3 rules) that will prevent future clashes.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other email marketing work people do in Mailchimp.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.