Process of building a project from scratch with Antigravity (Solo Builder)

I share the process of building a project from scratch with Antigravity in the Solo Builder style - so that everything is clearest, the process is complete, so when you look back, you will know where you are. Solo Builder

1. Early AGENTS.md

This is Anti's "constitution" file — always loaded in context. At this step, I usually put the feedback style, techstack... here. For example:

• Always instruct manual testing after each phase/plan.
• Complex tasks that users have to do — if you can write a script, use a browser... let AI do it for you, then you should suggest it.

This file doesn't need to be beautiful, just a basic rule setup for AI. We'll circle back later.

2. Set up the docs folder

In this era, docs are mainly for AI to read people only read what they need. Files/folders in this folder:

• brief.md — wishes, ideas, project description: what is the project, what do you want. Write in natural language, for the reader.
• BRD.md — more detailed than brief: what functions are there, user personas, important technologies, important flows, do/don't.
• plans/ — all phases to complete the project. There is a master-plan.md that stores all phases + states, and name-phase.md files that record what to do, output expectations, testing instructions (of course, which phase to do, the detailed plan for that phase).
• CHANGELOG.md — saves changes after each function, bug fix, refactor... so that both humans and AI know where the project is.

Have an idea → talk to AI → brief → talk to AI → BRD → talk to AI → plans

3. AGENTS.md rework

This is enough project information. Tell the AI ​​to rely on the docs/ directory to recreate a professional AGENTS.md. Don't forget to add the CHANGELOG.md update trigger logic here. After each work, AI will have context thanks to this file.

4. Setup Kit, MCP, Rules, Skills, Workflow (if necessary)

Enough context to know what to do, now do a little research:

• Can I use Kit, which kit is suitable?
• What 3rd party do you use, does it have MCP? Install Context7 if you don't have it yet.
• Are there any rules that need to be followed?
• Are there any special/interesting skills for this project?
• Is there a process that goes back and forth to form a workflow?

A bit vague? Quick Q&A:

5. Anything else, let's set it up

Anything else that is necessary can be set up in this step, for example:

• Git
• Environment
• UI Design
• …

6. Phase by phase and infinite loop

Enough toys here, let's start coding (it's time to code). Each of my phases:

1. Pick task — see what needs to be done.
2. Plan — detailed plan, checklist, expectations, testing methods.
3. Review plan — is it reasonable? Update if necessary.
4. Execute — AI does; I go surfing Facebook, watching YouTube, or jumping to another project.
5. Review execution — read the AI ​​walkthrough, review git diff to see if there's anything unusual.
6. Test — tell AI to turn on browser test / write-run unit test / manual test (depending).
7. Update / fix / improve if necessary — AI is not always good right away; The vague things now have something to look at.
8. Review + Commit — review the diff more thoroughly, commit + push if necessary.
9. Repeat infinitely until the project is complete.

7. Overall review, release checklist, some small things

The project is done, let's do a few things before going into production:

• Review (by AI) to see if there are any problems, how the security is, refactor/improve whatever you want. Install or package your own skills for this if needed.
• Little things: favicon, OG photo, Google Analytics... etc.

8. Deploy

From here, it is beyond the scope of Antigravity.