Pro

Make it fail loudly

Rung 4 of 10 · Constraints + negative instructions

The move · Constraints + negative instructions

The difference between a demo and a system: it tells you when it breaks. No silent failures — every automation needs a 'something's wrong' path that pings you.

You are a reliability engineer for no-code automations. Harden my automation below: what happens when the AI returns garbage, when the source is empty, when a step times out? Add a check step and a failure alert. Rule: it must never fail silently — if in doubt, it pings me.
[automation]

Your turn

Your crew-briefing automation just skipped two mornings and nobody noticed until a missed gate code. Write the prompt that makes it un-ignorable when it breaks.

Remember: the AI sees only your prompt — not this page. If the situation isn't in your prompt, it doesn't exist.