Learning on Web Dev Open is free for all.

Build First > Prompting is a specRewrite six prompts
Phase 00Prompting is a spec25 of 434

Rewrite six prompts

Six wishes, rewritten as specifications. Fifteen minutes that changes how you write every prompt afterwards.

Build20 minAI pair

Rewrite each of these as a specification. Aim for four to eight constraint lines each. Avoid vague adjectives, include at least one prohibition, and include at least one number.

One: "make me a nice contact form." Two: "build a modern navbar." Three: "clean up this CSS." Four: "make it responsive." Five: "add some nice animations." Six: "make this look professional."

Number four is the interesting one. Responsive to what, at which width, changing to what layout? It is the most commonly typed prompt in web development and it says almost nothing.

For each rewrite, apply the test from two chapters ago: could two people disagree about whether the output satisfied this line? If yes, rewrite it again.

Then run two of them, before and after, and put both outputs in your repository. Those two pairs are your evidence, and they go in the checkpoint write-up.

Done when

  • All six rewritten as specifications
  • Every line is checkable, with no adjective that two people could reasonably interpret differently
  • At least one prohibition and one number in each
  • Two of the six actually run, before and after, with both outputs kept
  • A sentence on which pair surprised you most

Nobody marks this for you. It goes into your phase checkpoint, where a person does.

Build this in your own editor

This one runs on your machine rather than in the browser workbench. Work to the outcomes below, then come back and mark it complete.

You should now be able to

  • Turn a vague request into a checkable specification
  • Spot an adjective doing no work
  • Run the before and after and see the difference yourself
Ask the community

Loading…