Skip to catalogue

18

prompt as spec

Write the prompt as a ticket: objects, constraints, acceptance, what not to do. Not a mood.

What is prompt as spec?

A good prompt is a ticket, not a muse. Short, reusable, and when it fails you can point at the line that was ignored.

Why does prompt as spec matter when vibe coding?

“Make it nicer” cannot go red. Treat the prompt as spec, and a good turn can be saved as the next turn’s opening.

How do you do prompt as spec?

Four blocks: goal, constraints, acceptance, forbidden. Acceptance is a command or a test. When a turn works, commit that prompt into the repo.

How do you ask a model for prompt as spec?

Follow the ticket. Goal: … Constraints: … Acceptance: (command) must pass. Forbidden: … Do not embellish.

What goes wrong with prompt as spec?

Pasting the whole previous thread as the spec. Noise drowns the four blocks. Excerpt, do not dump.

adjacent