Build one small part at a time

Break the job into parts

A component is a piece of the screen, such as a card, menu, or form. Reusing a component helps keep the same style and behavior in many places.

Give each part a clear job. A price card shows a service and price. A form takes a request. Avoid copying the same code into every page when one shared part would work.

Read the change

Ask which files changed and why. Look for edits outside your brief. Try the new part in preview. If it fails, share the error and steps that caused it.

Keep working versions. A small commit records a change in Git. It gives you a point to compare or return to. Saving a file, making a commit, and pushing to a Git host are separate steps.

Try these steps

1. Ask for one component with one clear job.
2. Review its files and test it in preview.
3. Save the working step before adding the next part.

A real-world example

Start with one service card. Next add a list of cards from data. Then add a form. Test each step. This is easier to fix than a whole app built in one huge request.

Ask AI for help

Copy this prompt into the tool you use. Fill in the blanks. Check what it gives you.

Build only this part: ___. Reuse the page’s current styles. Show changed files and a short test plan. Do not change other features.