Next steps

Your site is live, and it's yours. Here is how to keep building at home, and how to keep learning with your agent.

Add an Optional module

An Optional module is one more section for your site: YouTube videos, podcasts, a blog, resources you recommend, or project ideas. Each entry is a link, shown as a card below your CV. Fast in the room? Add one now. Otherwise, at home.

1. Start a fresh chat and check the model, as in every Role.
2. Ask for the section you want, for example:

Agent chat

Add a YouTube section to my portfolio.

Or ask for podcasts, a blog, resources or project ideas in the same way. The agent asks you for each entry: a title, a link and, if you like, a sentence about it. It writes them into your content file and shows you the new section in the preview.

The same kind of chat adds a widget: your events and talks, certifications, a dated "Now" list, a few numbers, or a project told as a case study. For example: "Add my certifications to my portfolio."

3. Publish it: start a fresh chat and type:

Agent chat

Start the Ops step.

Keep editing at home

Your repo, your skills and your agent rules come home with you. To change your content, edit site/content.json in Antigravity IDE, or ask the agent in a fresh chat, for example:

Agent chat

Change my headline in site/content.json to "Frontend developer who builds fast, accessible sites". Then run node tools/check-content.mjs.

Then publish with Ops, as above. Leave the Analyst out of small changes: it rewrites the whole content file, so the Optional modules you added would be gone.

To see your changes before you publish, start the preview in the terminal of Antigravity IDE (menu Terminal → New Terminal):

Terminal · same on Mac, Windows and Linux

node tools/preview.mjs

It prints an address such as http://localhost:8000. Open it in Chrome. The preview keeps that terminal busy until you stop it with Ctrl+C, also on a Mac.

Publish without the agent

Open a second terminal with Terminal → New Terminal, or stop the preview with Ctrl+C first. Then paste these commands one at a time (Cmd+V on a Mac, Ctrl+V on Windows, Ctrl+Shift+V on Linux), press Enter after each, and read what it prints before the next.

First, see what would be published. Read the list as Ops did: only files in site/, and maybe design/brief.md or docs/spec.md. Move anything private out of the folder first.

Terminal · same on Mac, Windows and Linux

git status

Add the changes:

git add -A

Save them in a commit:

git commit -m "Update my portfolio"

Send them to GitHub:

git push

Wait until the new version is online:

node tools/live.mjs

Done when it prints Your site is live.

Tip: a shorter address

Want an address without /portfolio/ at the end, such as https://YOUR-USERNAME.github.io/? Rename your repo:

1. In your repo on GitHub, open Settings. Under Repository name, rename portfolio to YOUR-USERNAME.github.io, with your own username, and click Rename.
2. In Antigravity IDE, start a fresh chat and tell the agent:

Agent chat

I renamed my repo on GitHub to YOUR-USERNAME.github.io. Update the remote of my local repo to the new address.

3. Publish once with Ops. Your site then lives at the shorter address.

Your next project

• Use the flow on your next project. Plan with a spec, split the work into small tasks, give each task a fresh chat, and check every result. The pages under Going deeper show how: Spec first, Context and subagents, Prompting in practice and Recovery toolkit.
• Track the work in GitHub issues. Write each small task as an issue in your repo, then let the agent take one issue per fresh chat. Matt Pocock's skills for coding agents automate this flow. Install and use them.
• Learn to read code. The agent writes faster than you, but you decide what is good. Knowing HTML, CSS and JavaScript lets you judge its work and keep your site easy to maintain.
• Add tests. Ask the agent to write a test that fails first, then make it pass. A test is evidence you can run again tomorrow.
• Stay current yourself. Modern Web Guidance is open source: GoogleChrome/modern-web-guidance. Read the guides your agent read today.

Learn with your agent

Your agent is also a teacher. Don't leave with code you can't read: ask it about anything it built, in a fresh chat.

Agent chat

Explain site/index.html to me.

It explains the file in plain words, points to the lines, and asks you one question to check you got it. It changes nothing. Ideas work too: Explain dark mode to me.

At the end, let it write down what you did and why. It saves the story of your site, Role by Role, in docs/recap.md in your repo:

Agent chat

Write down what we did and why.

Remember it next week

What you only read today fades fast. Trying to recall it, even badly, makes it stick. Three short prompts for later: