A field guide to posting about AI-generated code and creative artifacts so people actually share them. Twenty-four rules, divided in two halves. Specific tactics, not vibes.
There are two kinds of posts that travel from this kind of project, and they obey almost opposite rules. The first is the tooling post — "look what I built, look at the engine." The second is the artifact post — "look what I got, look at the output." Most people mix them and lose both.
The first half of this playbook is for posts where the build is the story: AI demos, code-gen threads, "I shipped X in Y" posts, launches of dev tools. The second half is for posts where the output is the story: generators, creative experiments, artistic tools, identity-stamp content.
None of this is hypothetical. The thirty tools on this site were generated in an afternoon and deployed cold. We had every one of these decisions to make. Where it helps, the rules below point back to the worked examples.
AI demo posts live or die in the first three seconds. Your audience has seen five hundred of them this week. Your only job is to be the one that earns the screenshot. Twelve rules, in rough order of impact.
The first frame should be the running tool, not your face, not your prompt. The hook is look at this thing, not I built a thing. Save the meta for paragraph three.
A single screen recording, under fifteen seconds, no edits. Cuts read as polish; one take reads as real. If your demo needs editing to look good, the demo isn't ready — fix the demo, not the cut.
"$0.40 in API calls." "One prompt." "30 minutes." "30 apps in an afternoon." Cost is concrete social proof that the thing you did is reachable. Vague gestures at "AI helped me build" do not travel.
Reveal the prompt after the demo, like a magician revealing the trick. People love seeing the literal text. Reveal is a gift, and the gift is a retweet. Pinning the prompt in a reply also creates a natural reading order: demo, then proof.
The first frame of your video becomes the share image. Frame it like a poster: negative space, one clear focal point, no UI chrome bleeding in. Most demos lose the share because frame one is a dev console.
Quantity is content. "I built one tool" earns a hundred likes; "I built thirty tools in an afternoon" earns a quote-tweet from a venture firm. The ratio of effort to output is the part that travels.
The phrase peaked. Use the verb (built, shipped, generated, deployed), not the brand. By the time you're using the inside-joke phrase, it's already cringe outside the joke. This applies to every "X coding" / "X engineering" coinage on a six-month half-life.
The posts that travel make a stranger feel seen. "A tarot tool for witchtok" beats "an AI tarot tool". "For r/MechanicalKeyboards endgame builds" beats "keyboard tools". Specificity is signal; generality is noise.
"Just a quick experiment, not production-ready, sorry for the bugs" — the whole paragraph dies on contact. Confidence about your tools travels well; embarrassment does not. If something doesn't work, fix it or cut it. Don't pre-flinch.
Real URLs in the post. Skeptics check; believers share. Both vectors are good for you. A demo with no live link is a demo people quietly doubt. (Cloudflare Pages, vibes.diy, and any one-click deploy are all fine — the constraint is "click and use," not which service.)
"I deleted my Notion." "I cancelled my Figma sub." "This replaced my Webflow." The implied claim — this thing replaced a tool you respect — is what travels. Calibrate the boast to what's actually true, but the structure is reliable.
Controversy is a distribution vector. "Stop using Tailwind for this." "React is overkill for the kind of app you actually want to ship." A strong, wrong-on-purpose take gets quote-tweeted by everyone who disagrees, which is also content. Once per post, never twice.
When you build a tool that produces an artifact, the artifact is the post. The tool is the engine; the artifact is the vehicle. Most people get this backwards and post screenshots of the UI. Twelve rules for tools that produce sigils, charts, cards, generators, quizzes, and any other piece of expressive content the user wants to call their own.
Do not post a screenshot of your generator's interface. Post the thing it generated, full-frame. The UI is a means; the artifact is the message. If your tool's UI shows up in the share, you've already lost.
"Get your sigil." "Your moon mood. " "Your archetype." Beats "A generator anyone can use." Users share because the share IS self-expression — they're posting a piece of themselves, not your tool. The tool is incidental to the identity claim.
Daily horoscope. Sunday-night dread. Full moon. Mercury retrograde. NYE intentions. End-of-quarter dread. Your tool should hitch a ride on a rhythm already in the audience's calendar. Tools that ride existing rituals get adopted; new rituals almost never take.
"Your moon mood is…" not "Your astrological assessment is…". The vocabulary of the community is the signal of belonging. Generic clinical language sounds like an outsider trying to monetize the community — even when it isn't.
"Only black and gold." "Exactly seven lines." "Only emoji." Limits look intentional. A tool with one perfect look beats a tool with infinite mediocre ones. Constraint is also what makes outputs recognizable when they travel without context.
Wobbles. Marker textures. Misaligned masking tape. Hand-lettered captions. In the age of AI slop, the handmade look reads as luxury. If every screenshot from your tool looks like the same ChatGPT illustration, the screenshots blur into the background.
Can someone re-share your output by screenshotting one frame? If not, the frame isn't ready. Add a watermark, stamp the date, fix the composition. The frame is your distribution. Anything you wanted the viewer to know must be inside it.
People share results, not tools. Frame the artifact as something the user achieved, received, or was assigned — not something you offered them. The grammar of the share is the grammar of belonging.
If users can change one parameter and re-roll, you get a chain. Single-shot tools die after the first share; remixable tools propagate. The lever is small — a button labeled "another", a slider, a name field — but the compounding is large.
Every output should carry a tiny mark: URL, slug, watermark, sigil. When the screenshot travels, it should carry provenance. This is the difference between anonymous virality and traffic that finds you. Aggressive watermarks repel; tasteful ones convert.
Even a visual tool should produce one quotable line per output. "Your Mercury retrograde excuse: my Notes app ate it." A phrase is a piece of text people will type into their own posts; an image is a piece of text people won't. Phrases compound faster than pictures.
"What type of X are you." "Which Y archetype." Sorting is irresistible because it hands the user an identity stamp they can claim publicly. The bucket has to be flattering to most buckets — sorting people into one obvious winner kills sharing.
The thirty tools on this site are the worked example. Go check how each one obeys — or deliberately breaks — these rules at patron-saints.pages.dev.