Your First Cursor Project

Choose a small task to learn the rhythm of completion, local edits and test-driven review. A large undefined feature often produces many changes that cost more to review than they save.

#1. Open a repository

Open a familiar local directory or an appropriate example repository. The source illustrates:

bashCopy
git clone git@github.com:voxelize/voxelize.git
cd voxelize
cursor .

You can also use the editor's Open command or cursor <path-to-project> after configuring its launcher.

#2. Try Tab completion

Start a function or comment:

jsCopy
function calculate

Inspect the suggestion before accepting it with Tab. The example is a typing exercise, not valid complete JavaScript. A precise name, signature or comment gives better direction than an ambiguous prefix.

#3. Make one inline edit

Select the function, open inline edit with the configured binding (commonly Cmd/Ctrl + K) and request:

textCopy
Make this function calculate Fibonacci numbers.

Review the changed implementation and any added imports. This gives you a bounded comparison between the request and the diff.

#4. Add and run tests

textCopy
Add tests for this function and run them.

Check whether the tests reflect the actual intended behavior rather than assumptions invented to make them pass. Where useful, write a failing test before implementing the missing behavior.

#5. Practice closing the loop

Evaluate instruction clarity, result correctness, change scope, naming and readability. The goal is controlled work, not the number of generated lines.

#Practice sequence

Pick one function/component, draft with Tab, make one inline change, add tests through chat/agent interaction, then inspect the final diff yourself. This demonstrates how the entry points complement one another.

#Next steps

• Tab completion
• AI Chat
• Multi-file editing