Adding New Features
Swipe to show menu
You know how to make small changes. This chapter is about what to do when the feature you want to add is more substantial.
The approach is simple: treat it like a mini version of how you started the whole project. Plan first, then build.
Why bigger features need a plan
Small changes like updating a colour or tweaking a field can be done with a direct prompt. But when a feature involves multiple files, new logic, or changes to how the app behaves, jumping straight to building often creates problems.
Going back to plan mode first means Claude Code thinks through what needs to change before it touches anything. You get to review that plan and catch anything that does not match what you wanted before a single line of code is written.
Treat every significant new feature like a mini project. Plan it, approve it, then build it.
The process
Click the model selector in Claude Code and switch to Plan Mode. This tells Claude Code to think through the implementation and return a plan rather than immediately writing code.
You do not need to be perfectly specific at this stage. Describe the feature in plain English. Claude Code may ask clarifying questions. If it does, answer them. If it does not, read through the plan carefully before approving.
Check that what Claude Code is proposing matches what you actually want. Look at which files it plans to create or modify. If something looks off, tell it before approving.
Once the plan looks right, approve it and switch back to a normal session. Claude Code will build the feature out from there.
Try the feature in your browser as soon as it is done. Does it behave the way you expected? If not, write a specific follow-up prompt describing the one thing that needs adjusting.
Thanks for your feedback!
Ask AI
Ask AI
Ask anything or try one of the suggested questions to begin our chat