How the Build Journal works

The Build Journal is a private log of what you build. Every entry captures what you made, the prompts that worked, and what broke along the way. Over time it becomes your playbook: the next time you need a login page, a payment flow or a popup, you already have the steps that worked for you.

What goes in an entry

• Title and project. Name the feature, and group entries by project so you can filter them later.
• What I built and why. A few sentences on the feature and the problem it solves.
• Prompts that worked. Paste the prompts you gave Lovable, Claude, Cursor or another tool, with a note on why each one worked.
• What broke and the fix. Each problem you hit and how you solved it. This is the part you will thank yourself for later.
• Screenshots and links. Up to six screenshots and a link to the live app.

Who can see it

Entries are private. Only you and Lee can read them. Lee sometimes leaves a note on an entry with a tip or a fix; it shows at the top of the entry. You can share an entry when you want to; see Sharing an entry and the Bounty Wall.

Finding things later

Search covers titles, prompts and fixes, so a word like "webhook" finds every entry where you fought with one. Filter by project to see one app's full history.

XP and badges

Each entry with real content earns XP. Five entries earn the Field Notes badge and twenty earn Chronicler.

A good entry in ten minutes

1. Write two sentences on what you built and for whom.
2. Paste the one or two prompts that did the heavy lifting.
3. List what broke, even if the fix was small.
4. Add a screenshot of the finished screen.