Review and Finish

You pass this stage when you have a review score, one smallest fix applied, and proof you can explain.

What this is

This is the review and finish stage. You prove the visible build works, hold it up to the Review Mirror to score it against your plan, make the smallest useful fix, then capture proof.

The loop is:

Review -> pick smallest fix -> fix one issue -> retest -> proof

Why it matters

Shipping is not just generating code. You need to see problems, name them clearly, fix one thing at a time, and improve the page before you share it. One issue at a time keeps you in control and keeps the build understandable.

What to do

Quick-test the page

1. Open the preview and refresh.
2. Click every visible button or link.
3. Check the page on a narrow phone width.
4. Read the text out loud and remove confusing copy.

Hold it up to the Review Mirror

Ask AI to score the site against both saved files:

Review my current website against project-brief.md, design.md, and build-blueprint.md.

Score it:
- Goal match: /5
- Audience fit: /5
- Scope discipline: /5
- Design match (does it follow design.md?): /5
- Mobile clarity: /5
- Visual trust (no fake logos, stats, or cloned identity): /5

Then give:
1. What works
2. What drifted from the brief, design, or blueprint
3. What feels generic
4. What is missing
5. The smallest high-impact fix
6. A copy-paste prompt for that fix

If a design issue blocks clarity or taste, fix that one issue first.

Low scores are not failure. They tell you exactly where the smallest fix should go.

Fix one issue only

Fix only this one issue:

Issue:
[paste issue]

Use project-brief.md and build-blueprint.md as the source of truth.

Rules:
- Do not add new features.
- Do not redesign the whole website.
- Make the smallest useful fix.
- Explain what changed and what I should test.

Retest in the preview. Repeat the review/fix loop only if time allows.

Finish with proof

Capture your finish and explain it, including one line about your design choices:

My design inspiration was [...]. I borrowed [...]. I did not copy [...].

Follow Proof and Sharing, and for the strongest proof publish to GitHub and Vercel when time and accounts allow.

Common mistakes

• Reviewing and fixing several issues in one prompt.
• Calling the page done without testing mobile width.
• Adding a new feature instead of fixing the smallest issue.
• Redesigning the whole site during a fix.
• Finishing with no proof and no explanation.