Prompt with intention → Vibe to Spec

1. Why prompts matter

The biggest gap between engineers who get good output from the model and engineers who don't is the prompt. Not the model. Not the temperature. Not which framework they're using. The prompt.

A vague prompt produces vague code. A precise prompt produces precise code. Most engineers write vague prompts and blame the model for the output. The fix isn't a better model. It's the skill of writing what you mean, before the model gets to start.

This is the skill that the four habits from chapter 5 keep pointing at. Specification clarity. The ability to state what you want in a way that a careful reader couldn't misinterpret.

2. What Vibe to Spec covers

[[vibe-to-spec]] is the deep dive on this skill. It's free. It's structured around worked examples from real engineering work — the kind of features you'd ship at a real company, not toy problems.

The course walks you from vibe-level prompts ("make a login page") down to specification-level prompts (the inputs, the outputs, the edge cases, the failure modes, the constraints, in a shape the model can act on). The worked examples show you the transformation step by step. You see the vague version, then the better version, then the spec-level version. You see what the model produces from each. You see the cost of the vagueness, in concrete output.

It's the next free course after this one.

3. Who should take it next

If you finished this course and want to start practicing the new skills concretely, [[vibe-to-spec]] is the right next step. It's especially useful if you're a junior or mid-level engineer working with the model day to day, or if you're learning to code and you want to learn alongside the model from the start.

It's less useful if you're already comfortable writing precise specifications. In that case, skip ahead.