Prompt packs for empty / error / loading states — stop shipping happy-path only

Description and use

<p>Agents are weirdly good at the happy path. Give them a Figma frame of a filled dashboard and you get a filled dashboard. Give them a “build a projects list” prompt and you get rows, avatars, and a neat toolbar.</p> <p>What you usually <em>don’t</em> get: the empty list on day one, the 500 that lands mid-scroll, or the skeleton that doesn’t jump when real data arrives. Those states are where users decide whether the product feels finished — and they’re the first thing agents skip unless you ask for them on purpose.</p> <p>So I stopped describing “the screen” and started shipping <strong>prom

Problem

<p>Agents are weirdly good at the happy path. Give them a Figma frame of a filled dashboard and you get a filled dashboard. Give them a “build a projects list” prompt and you get rows, avatars, and a neat toolbar.</p> <p>What you usually <em>don’t</em> get: the empty list on day one, the 500 that lands mid-scroll, or the skeleton that doesn’t jump when real data arrives. Those states are where users decide whether the product feels finished — and they’re the first thing agents skip unless you ask for them on purpose.</p> <p>So I stopped describing “the screen” and started shipping <strong>prom

Outcome

<p>Agents are weirdly good at the happy path. Give them a Figma frame of a filled dashboard and you get a filled dashboard. Give them a “build a projects list” prompt and you get rows, avatars, and a neat toolbar.</p> <p>What you usually <em>don’t</em> get: the empty list on day one, the 500 that lands mid-scroll, or the skeleton that doesn’t jump when real data arrives. Those states are where users decide whether the product feels finished — and they’re the first thing agents skip unless you ask for them on purpose.</p> <p>So I stopped describing “the screen” and started shipping <strong>prom

Evidence

Prompt packs for empty / error / loading states — stop shipping happy-path only

Source