Vibe Coding · Aula

Sendo específico

Prompts vagos geram código vago — seja concreto.

Sendo específico é uma aula grátis de Vibe Coding no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Vibe Coding, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Vibe Coding inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Vague In, Vague Out

AI builders like Cursor, Bolt and v0 are powerful, but they can't read your mind. When your prompt is fuzzy, the AI guesses — and its guess is rarely the app you pictured.

The fix is the single most valuable prompting skill: being specific. This lesson shows you how to turn a wish into a precise instruction.

Specific About What, Exactly?

You can add precision in four directions:

What — the exact feature or element
How it looks — colors, layout, size
How it behaves — what happens on click, on error
How much — counts, limits, ranges

Every detail you pin down is one fewer thing the AI gets wrong.

Specify the 'What'

Name the exact thing you want. 'A button' could be anything. 'A submit button labeled Save that appears under the form' leaves no doubt.

Vague:   "Add a button."

Specific: "Add a green 'Save Note' button below the textarea.
           When clicked, it adds the note to the list above."

Specify the Look

Design words like 'nice' or 'modern' mean different things to everyone. Give the AI concrete visual targets: colors, spacing, fonts, sizes.

You can even reference a known style — 'like Notion' or 'Apple-clean' — to anchor the vibe.

Vague:   "Make it look good."

Specific: "Use a clean white card on a light-gray background,
           rounded corners, soft shadow, and a single accent
           color of #7c3aed for buttons and links."

Specify the Behavior

Apps do things. Spell out what happens on each action — including the edge cases like empty input or errors. This is where vague prompts fail hardest.

Specific behavior:

"When the user clicks 'Add', take the text from the input,
 add it as a new list item, then clear the input.
 If the input is empty, do nothing and shake the input box."

Specify the Numbers

Numbers remove ambiguity instantly. How many items? What max length? What range? Give the AI real values instead of 'some' or 'a few'.

Here's a tiny function the AI might build from a numeric constraint — you can run it.

const MAX_LENGTH = 280;

function checkPost(text) {
  if (text.length > MAX_LENGTH) {
    return 'Too long by ' + (text.length - MAX_LENGTH) + ' chars';
  }
  return 'OK (' + text.length + '/' + MAX_LENGTH + ')';
}

console.log(checkPost('Hello world!'));
console.log(checkPost('x'.repeat(300)));

Replace Adjectives with Details

Watch out for slippery adjectives: fast, simple, clean, modern, professional, responsive, secure. Each one hides a decision you should make.

Whenever you write one, ask: 'what would that actually mean here?' — and write that instead.

Instead of: "Make it responsive."
Write:      "Stack the columns vertically on screens under 600px."

Instead of: "Keep it simple."
Write:      "One screen, no menu, three buttons max."

Specificity Beats Length

Being specific doesn't mean writing an essay. A short, precise prompt beats a long, fuzzy one. Pack meaning, not words.

Both prompts below are short — but only one will give you the app you imagined.

Fuzzy & short:  "Build a timer app."

Sharp & short:  "Build a 25-minute countdown timer with Start,
                 Pause and Reset buttons. Show MM:SS. Beep at zero."

Show, Don't Just Tell

When words get clumsy, switch to a concrete example. Paste a sample of the data, a row of a table, or a mini mock of the layout. Examples are the most specific thing you can give.

"Format each contact like this exactly:

   Ada Lovelace — ada@math.org — VIP

Name, then em-dash, email, em-dash, and a tag.
If there's no tag, leave off the last dash."

The Specificity Checklist

Before you hit enter, scan your prompt against this list:

Did I name the exact element/feature?
Did I give concrete colors/sizes if looks matter?
Did I describe what happens on each action and on errors?
Did I replace vague adjectives with real details?
Did I include numbers where they apply?

One pass over this list saves you three rounds of back-and-forth.

Don't Over-Specify Either

There's a balance. Pin down what you care about, and let the AI choose the rest. If you dictate every pixel, you slow yourself down and lose the AI's good instincts.

Rule of thumb: be specific about outcomes, flexible about implementation — unless implementation is the point.

Good balance:

"Make a contact form with name, email and message fields,
 and a Send button. Validate that email contains an '@'.
 You choose a tidy, accessible layout."

Quick Check

Which rewrite makes the prompt 'Make the app look modern' more specific and useful?

Recap: Get Concrete

Vague prompts give vague code. To get exactly what you pictured:

Name the exact what
Give concrete looks and numbers
Describe behavior and error cases
Trade vague adjectives for real details
Show an example when words fall short

Next: how to give the AI context about your files and goals so its code fits your project perfectly.

Perguntas Frequentes

A aula “Sendo específico” é grátis?

Sim — o texto completo de “Sendo específico” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Vibe Coding, atualize para CoddyKit PRO. O curso de Vibe Coding inclui 4 aulas no total.

O que vou aprender em “Sendo específico”?

Prompts vagos geram código vago — seja concreto. Você pratica Vibe Coding com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Vibe Coding?

Nenhuma experiência prévia é necessária. Vibe Coding no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Sendo específico”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Vibe Coding?

Sim. Cada aula de Vibe Coding inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

← Voltar para Vibe Coding