Templates · Free

31 post templates for building in public.Free to use, and built from 2,000 posts that worked.

I built them from the 2,000 top build-in-public posts I could find on X: 117 builders, 250M views, January 2023 to November 2026.Each one is written for an AI agent to follow, so “the user” means you.

Progress.What you shipped.

Shipped

One feature or fix that works now, shown working.

When to use it
A feature, screen or fix goes from missing or broken to working on screen, or a merge or release closes it out.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[What works now, named concretely. One line.] [Why it exists: the pain or the request behind it. One line.] [Optional: one surprise, one number, or how long it took.]


Example

Moneta's menu now wraps the agent command instead of cutting it in half.

You were copying a line you couldn't read. Now it breaks after the && and the whole thing fits.

Ship log

Several small things shipped, as a short list.

When to use it
A day or week closes out three or more small fixes or features, seen working on screen, in merged pull requests, a release note or a closed issue list.
In the study
88 of the 2,000 top posts · 10.4M views
Platforms
X, Threads, Bluesky

Shape

[Shipped today on [product]:] - [item 1] - [item 2] - [item 3] [Optional: what's next, or one question.]


Example

Shipped on Moneta today:

- the menu wraps long agent commands instead of cutting them in half - dark mode's grey text passes contrast - About has a support address, and a person answers it

Before / after

One thing, two frames.How it looked or performed, and how it does now.

When to use it
The same screen, design, file or number appears early and late in the period and is visibly different.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[Before → after, in one line. Name what changed.] [What drove the change. One line.] [Optional: the measurable difference.]


Example

Moneta's dark mode, before and after.

The grey text was dimmer than it should be, and the two greys were in the wrong order. Both pass contrast now.

Weekly update

The week in a few lines.What shipped, what was hard, what's next.

When to use it
The end of a week, or the user asks for a recap of a date range.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

1. The week and its headline result, in one line. 2. What shipped: 2–4 items, concrete. 3. One number, if there's one on screen. 4. What was hard, or what didn't work. 5. One thing learned. 6. Next week, in one line.


Example

First week of Moneta.

Shipped: the menu bar app, onboarding, and a template library your agent fills in.

Hardest part: macOS forgetting the screen-recording permission after every rebuild.

Learned: if a permission depends on a signature, sign properly from day one.

Next: my own first week of summaries.

Timeline

Then and now, in dated steps.How far a project has come.

When to use it
summaries/ cover several weeks or months of one project and the same thing (a screen, a number, the product) visibly changed.Round dates suit it: 30 days in, six months, a year.
In the study
45 of the 2,000 top posts · 2.5M views
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[Date 1]: [state] [Date 2]: [state] [Date 3]: [state] Today: [where it is] [One line on what made the difference.]


Example

Tally:

March: a streak tracker only I used May: the first paying user August: 100 paying users, after the paywall moved to after the first streak Today: $2,000 MRR

What changed it: the yearly plan, and asking every new user one question.

Stories.What happened, and what you learned.

Lesson

One rule of thumb, earned from something that happened on screen.

When to use it
A session ends in a rule of thumb, such as an approach that worked after others didn't, or something you'd do differently.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The specific thing that happened. One line.] [What it cost: time, a rebuild, a user.] [The rule you'll follow next time.]


Example

Every rebuild of Moneta made macOS forget its screen-recording permission. That cost me an hour.

If your app needs a privacy permission, sign it with a real identity from the first build.

Lesson list

A numbered list of lessons from a stretch of work, a launch, or an event.

When to use it
A project, launch, month or milestone ends and summaries/ hold several separate lessons, or the user took notes at a trip or event.
In the study
66 of the 2,000 top posts · 8.5M views
Platforms
X, Threads, LinkedIn

Shape

[N] lessons from [building X / launching Y / a month of Z]: 1. [lesson, in one line] 2. [lesson] 3. [lesson] … [Optional: one closing line, or what you're doing about it.]


Example

5 things building Moneta taught me:

1. If your app needs a privacy permission, sign it properly from the first build. 2. Five onboarding screens lose more people than one. 3. A markdown file is easier to change than an app. 4. Look at every state of a screen at once. Bugs hide between them. 5. People already pay for an AI. Don't make them pay for a second one.

Bug story

A bug hunt told as a short story.Symptom, wrong guess, real cause, fix.

When to use it
A long stretch of errors, logs, a debugger, or repeated edits to the same file, ending in a fix.
Platforms
LinkedIn, X, Threads

Shape

1. The symptom, and how long it ate. 2. What you assumed was wrong. 3. What was actually wrong. 4. The fix, in a line. 5. What you'll check first next time.


Example

Moneta was running, the permission was on, and it still captured nothing.

I assumed the toggle in System Settings was broken.

It was pointing at an old build. Every unsigned rebuild gets a new identity, so the permission belonged to an app that no longer existed.

The fix: sign with a Developer ID and reset the entry once.

Next time I'll check what macOS thinks the app is before I check the app.

Failure

Something that didn't work, owned plainly.

When to use it
A revert, an abandoned branch or design, a plan that didn't happen, or a number that went the wrong way.
In the study
55 of the 2,000 top posts · 5.4M views
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The mistake, in one line.] [What you assumed, and what actually happened.] [What you changed.]


Example

Spent two weeks on a social feed for Tally. 3% of users opened it.

I assumed people wanted to compare streaks. They wanted to be left alone.

Removed it this morning.

Decision

A choice you made, and the option you turned down.

When to use it
Options are compared on screen, such as two designs, pricing pages, libraries, or a scope list with items crossed out.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The decision, in one line.] [The option you didn't take, and why.] [Optional: what would change your mind, or one question.]


Example

Moneta has no AI inside. Your own agent does the writing.

I could have shipped a model and billed for it. But people already pay for Claude or Codex, and a markdown file is easier to change than an app.

Origin story

Why you started, from the moment it began to where it is today.

When to use it
An anniversary of the project or of the first day in days/, a launch, or the user asks to tell how it started.
In the study
14 of the 2,000 top posts · 2.7M views
Platforms
X, Threads, LinkedIn

Shape

1. Where you were: [N] [years / months] ago you [quit, were stuck, kept hitting a problem]. 2. The moment it started: the problem you couldn't ignore. 3. What happened in between, in 2–3 real steps. 4. Where it is today, plainly. Users or revenue only if they're real and the user shares them. 5. Optional: what you'd tell yourself back then.


Example

For years I shipped things and posted about none of them. By the evening I couldn't remember what I'd done at 2 pm, and writing it up felt like a second job.

The problem wasn't writing. It was remembering.

So I built a Mac app that screenshots my work every minute and keeps it in a folder. My agent reads the folder and drafts the posts.

That app is Moneta.

Exit

You sold the product.What it was, how it started, what you learned.

When to use it
A signed acquisition, an escrow or transfer screen, or a marketplace listing that closed is on screen, or the user says they sold it.
In the study
125 of the 2,000 top posts · 14.6M views
Platforms
X, Threads, LinkedIn

Shape

[I sold [product]. The price, only if the user shares it.] [Where it started: [N] months or years ago it was [humble start].] [1–3 things you learned building and selling it.] [Optional: what's next.]


Example

I sold Tally this week.

Two years ago it was a weekend project to track my own reading streak. It ends with 4,000 paying users and a buyer who uses it every day.

What I'd tell myself at the start: charge earlier, and keep the code boring enough that someone else can run it.

Numbers.The numbers that moved.

Metrics

A number that moved, and what moved it.

When to use it
A dashboard, analytics, App Store Connect, Stripe, RevenueCat, download count or similar is on screen with a number that changed.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The number, and its change against the last period.] [What drove it. One concrete line.] [The cost, setback or caveat. One line.]


Example

Tally's trial-to-paid went from 4% to 7% this month.

The only change: the paywall now shows after the first streak, not on launch.

Refunds also went up a little. Watching that next.

Revenue

Revenue or MRR crossed a line, and the few things that moved it.

When to use it
Stripe, RevenueCat, Dodo, Gumroad, App Store Connect or a similar dashboard shows revenue or MRR crossing a round number or reaching a new high.
In the study
635 of the 2,000 top posts · 61.1M views
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[Product] crossed [$X MRR / $X in sales]. Say it plainly. [Where it started: $0 in [month], or [N] months ago.] What moved it: - [lever 1] - [lever 2] - [lever 3]


Example

Tally crossed $2,000 MRR this morning.

It was at $0 in March.

What moved it: - a yearly plan priced at eight months - the paywall after the first streak, not on launch - one forum reply that still sends people every week

Milestone

A threshold crossed, with what it took to get there.

When to use it
A threshold appears on screen, such as a first user, a round number of users, a version tag, or a store approval.For revenue, use revenue.
In the study
33 of the 2,000 top posts · 2.7M views
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The milestone, plainly.] [Where it started, or how long it took.] [2–3 things that actually got it here.] [Optional: thanks, and the next target.]


Example

Tally has 100 paying users.

Seven months. The first 30 came from one forum reply. Most of the rest came after onboarding went from four screens to one.

Income report

The month's income, split by product or source, with costs.

When to use it
A month ends with revenue dashboards on screen during it, or the user asks for a monthly report.
In the study
31 of the 2,000 top posts · 5.7M views
Platforms
X, Threads, LinkedIn

Shape

[Total] in [month]. [Product or source 1]: [$] [Product or source 2]: [$] [Costs, if the user shares them]: [$] [What changed against last month, in one line.]


Example

$3,140 in October.

Tally for iPhone: $2,410 Tally for Mac: $590 Notion templates: $140 Costs: $212

The yearly plan carried the month. The templates barely sell now, and I've stopped updating them.

Process.How the work happens.

Behind the scenes

A raw look at how the work actually happens.

When to use it
A long stretch in one tool where the screen shows the real mess of the work, such as a canvas of variants, a busy terminal, notes, or a whiteboard.
Platforms
X, Threads, Bluesky

Shape

[What you're looking at. One line.] [Why it looks like this, or the unglamorous part nobody sees.]


Example

every state of moneta's menu panel, side by side in paper before launch. looking at all of them at once turned up a cut-off command line that i never saw one screen at a time.

Design detail

One small design choice on screen, and the reason behind it.

When to use it
A spacing, copy, icon, animation or layout change on screen that took real thought, and the reason is clear from days/ or the diff.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[The detail, named plainly: what it is and where it sits.] [What it looked like or did before, and what felt off.] [What you changed, and the reason in one line.]


Example

The delete button in Moneta's history list was red and sat next to the copy button.

I mis-tapped it twice in one afternoon.

Moved it behind a swipe and left only copy in the row. The list is calmer, and nothing gets deleted by accident.

Stack

The tools behind the work, each with a reason.

When to use it
The same few apps carry most of the day or week in days/, or the user asks what they use.
In the study
48 of the 2,000 top posts · 6.9M views
Platforms
X, Threads, LinkedIn

Shape

1. The kind of work, and the stack in one line. 2. One tool per line or post: what it does for you, and why it won over the alternative. 3. Optional: the one tool you'd drop, or what it all costs.


Example

What built Moneta this week:

Swift and a shell script. No Xcode project, one build command.

Paper, to see every screen state at once before launch.

Claude Code, to read the folder Moneta writes and draft the posts.

Ideas.What you think.

How-to

Steps that worked for you, written so someone else can follow them.

When to use it
A problem gets solved on screen with steps someone else could repeat, such as a setup, a config, a release process, or a workaround that finally worked.
In the study
31 of the 2,000 top posts · 2.0M views
Platforms
X, Threads, LinkedIn

Shape

[If you're [doing X / stuck on Y], do this:] 1. [step] 2. [step] 3. [step] [Proof: what it got you, from your own work.]


Example

If your Mac app loses its Screen Recording permission after every build, do this:

1. Sign every build with your Developer ID, not ad hoc. 2. Clear the stale entry once: tccutil reset ScreenCapture <your bundle ID> 3. Open the app and allow it again.

macOS ties the permission to the signature. Moneta kept it through every build after that.

Take

Your take on news in your field, or on advice everyone repeats, backed by your own work.

When to use it
News, a changelog, a policy change or a launch from a platform the user builds on is on screen and changes their plans, or their own numbers contradict common advice.
In the study
80 of the 2,000 top posts · 26.9M views
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[What happened, or what everyone says. One line.] [What most people take from it.] [Your take, and the proof from your own work: a number, a decision, a result.]


Example

Everyone says an AI product needs its own model.

Moneta has none. It keeps your workday in a folder on your Mac, and the agent you already pay for reads it.

A second model would only be a second bill.

Opportunities

Gaps you've spotted that someone should build, as a numbered list.

When to use it
Research is on screen, such as app store reviews, forum threads, competitor pricing, a notes file of ideas, or a pattern across customer requests.
In the study
7 of the 2,000 top posts · 2.0M views
Platforms
X, Threads, LinkedIn

Shape

[Why now: the change that makes these possible. One line.] 1. [idea]: [who it's for, and why] 2. [idea]: [who it's for, and why] 3. [idea]: [who it's for, and why] [Optional: which one you're building, or that the rest are free to take.]


Example

Agents can read files now, which makes a lot of small Mac apps worth building. Each one just keeps a good record:

1. A meeting recorder that saves markdown notes, so your agent can write the follow-ups. 2. A reading app that keeps highlights in a folder your agent can quote from. 3. A receipts folder your agent turns into a monthly expense report.

Moneta does this for your screen. The rest are yours.

People.The people you build for.

Ask feedback

One specific question about work in progress.

When to use it
Work in progress with two clear options on screen, or a nearly finished screen that needs a gut check.
In the study
15 of the 2,000 top posts · 507K views
Platforms
X, Threads, Bluesky

Shape

[What you're building, in a few words.] [The specific question, or A vs B.] [Optional: when you'll share what you picked.]


Example

Moneta's menu bar icon is a ring with a dot while it records, and an empty ring when paused.

Clear enough at a glance, or does it need colour?

Customer feedback

What a user told you, and what you changed because of it.

When to use it
A user's email, DM, review or support message is on screen, especially one that led to a change.
Platforms
X, Threads, Bluesky, LinkedIn

Shape

[What the user said, paraphrased.] [Why it mattered.] [What changed because of it.]


Example

A Tally user said streaks made them feel worse after one missed day.

Streaks now allow one skip a week.

Launch.The big day.

Launch

The launch post.Problem first, then what you built and where to get it.

When to use it
A release build, a store listing, a landing page or a launch checklist is on screen, or the user says it's launch day.
In the study
217 of the 2,000 top posts · 19.7M views
Platforms
LinkedIn, X, Threads, Bluesky

Shape

1. The problem, in the reader's words. 2. What you built, in one line. 3. How it works, in 2–3 lines, next to the screenshot. 4. Proof: a result from your own use or from beta users, only if it's real. 5. Where to get it. On LinkedIn, put the link in the first comment.


Example

You do real work every day and never post about it, because writing it up is a second job.

Moneta is a Mac app that screenshots your work every minute and keeps it in a folder. Your own agent reads that folder and drafts the posts.

$20 a year. No AI inside, no account, and your screen never leaves your Mac unless your agent sends it.

Link in the first comment.

Formats.Shapes for any post.

Tweet

One post about one moment from the day.The default build-in-public post.

When to use it
Any single moment worth sharing, when no more specific template fits better.
Platforms
X, Threads, Bluesky

Shape

[What I did, concretely, in one line] [Why it matters, what was hard, or what I learned. One line. Optional]


Example

Rebuilt Moneta's onboarding from 5 screens to 1. Pick a folder, grant one permission, done.

Every screen I cut was one more chance to quit.

Screenshot

The screenshot is the post.A few words at most.

When to use it
One frame explains itself at a glance, such as a finished screen, a chart, a terminal moment or a striking before/after.
In the study
79 of the 2,000 top posts · 28.9M views
Platforms
X, Threads, Bluesky

Shape

[The image.] [Optional caption, a few words: what it is, or one number.]


Example

[Image: every state of Moneta's menu, side by side in Paper]

Every state of Moneta's menu.

One-liner

One sharp line about building.No image, no thread.

When to use it
A realization, a small irony or a pattern the user noticed while working, short enough to say in one breath.
In the study
63 of the 2,000 top posts · 2.4M views
Platforms
X, Threads, Bluesky

Shape

[One line.]


Example

Half of shipping a Mac app is convincing macOS it's still the same app.

Thread

A short thread about a week, or one piece of work with a clear arc.

When to use it
The same piece of work shows up across several days and visibly changed from start to now.
Platforms
X, Threads, Bluesky

Shape

1. The hook: the result or the tension, in one line. Not "This week I…". 2. Where it started. What was wrong, missing, or ugly. Attach the first frame. 3–5. The turns. One post per real decision, attempt, or fix, in order. Say what changed and why. 6. Where it is now. Attach the latest frame. 7. What's next, or what I learned. One line. Optional.


Example

1/ Moneta's onboarding went from 5 screens to 1 this week.

2/ v1 explained everything: what it captures, where it saves, how the AI works. Nobody reads that.

3/ v2 cut it to permissions + folder. Still two decisions before anything happens.

4/ v3: pick a folder. That's it. The folder explains itself, and your agent explains the rest.

5/ The lesson keeps repeating: the app should do less and the file should do more.

LinkedIn

A longer reflective post about one piece of work and what it taught.

When to use it
A piece of work with a decision or lesson at its centre, worth explaining to peers.
Platforms
LinkedIn

Shape

[Opening line: a plain, specific observation or result. Short enough to show above "see more".] [2–3 short paragraphs: what I was working on, the decision or problem at the centre of it, and what I did. Concrete details from the screenshots.] [One line on what I took from it. A principle, not a slogan.] [Optional: one line on what's next.]


Example

I cut Moneta's onboarding from five screens to one.

Moneta is a small Mac app that screenshots your work every minute so your AI agent can turn your day into build-in-public posts. The first version of onboarding tried to explain all of that up front.

Every screen I added made sense on its own. Together they made people stop before anything had happened.

So the app now asks one thing: pick a folder. The folder holds a single markdown file, and whatever agent you already use reads it and explains the rest.

The more I build agent-first tools, the more the pattern holds: the app should do less, and the file should do more.

Essay

One long post.A hook, a short story, and what you took from it.

When to use it
A piece of work with a real story behind it, such as a hard week, a reversal, or a decision that cost something, that reads better in one piece than as a thread.
In the study
368 of the 2,000 top posts · 46.8M views
Platforms
X (long posts), LinkedIn

Shape

[Hook: one line with a surprising fact, number or turn. It has to work on its own above "show more".] [The story in short paragraphs: the setup, what got hard, the turn, where it landed.] [What you took from it. One or two lines.]


Example

Moneta has no AI inside, and that was the hardest call I made building it.

The obvious version was easy to picture: a model in the app, a bill that grows with every draft, drafts that appear on their own. Most tools like it work that way.

But the people I built it for already pay for Claude Code or Codex. A second AI bill to write about work the first one helped with felt wrong.

So Moneta does only the part a Mac app is good at. It screenshots your work every minute, reads the text on your Mac, and keeps both in a folder. Your own agent reads the folder and writes the drafts.

That made the app smaller and the price simple: $20 a year, with no AI bill on top. And the drafts get better whenever your agent does, without me shipping anything.

The best feature I cut was the one everyone expected.

Moneta keeps your workday on your Mac, and your agent picks the right template from it.

Buy Moneta · $20 a year