Promptles
Clarity

Name Things Precisely

Use exact names from the code so Claude knows what to change.

Computers store information in named containers called variables. When you prompt Claude Code, use the exact variable and file names from the code so it knows exactly where to look and what to change. Saying 'the user variable' is vague; saying 'the username variable in app.js' is precise.

Where you'll practice this

2 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.

  • Name That Variable

    You're working on a small JavaScript app that tracks a user's score in a game. Right now the score is stored in a variable called `s`, which is confusing. Your team wants it renamed to `playerScore` so the code is easier to read. The file is `game.js`.

  • A Branch of One's Own

    You're on `main` and about to start work on a new feature: a dark-mode toggle for the settings page. Your team's convention is to do all feature work on a branch named `feature/<short-description>` and never commit directly to `main`. You want Claude Code to create and switch to…

Other principles in Clarity