PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-6-luna)
Token size
772
Example input
[topic]: Shipping a bootstrap SaaS feature in public every week [audience]: Solo SaaS founders and indie hackers who want a calm ship cadence without fake growth metrics [angle]: Build in public as a weekly ship log, not a hype launch thread [proof]: Ship cadence: one small feature or fix every Friday for the last 8 weeks. Qualitative lessons: cut scope before polish, write the changelog first, demo with one real user story. Revenue and follower counts: STAT_PLACEHOLDER. Product name: FILL_WITH_SPEC. [tone]: candid and practical
Example output
1) HOOK TWEET I shipped something small every Friday for 8 weeks on FILL_WITH_SPEC. No fake follower screenshots. Here is the calm cadence that stuck — and what I cut. 2) THREAD 1/ Cadence beat intensity. One feature or fix every Friday. If it was not demoable by Thursday night, I cut scope — I did not slip the day. 2/ Changelog first. Before code, I wrote 3 bullets: who it helps, what changed, how to try it. That stopped me polishing invisible work. 3/ One real user story in the demo. Not a feature tour. One person, one job, one before/after clip under STAT_PLACEHOLDER seconds when I had it. 4/ Public does not mean loud. I posted a short Friday note: what shipped, what I deferred, what I will try next week. No revenue flex. 5/ Revenue and follower counts stay out unless I can defend them. If I need a number, I use STAT_PLACEHOLDER until the dashboard is open. 6/ Scope knife: if polish took more than one evening, it waited. Ship the thin slice users can click, then iterate the next Friday. 7/ Feedback loop: I asked one active user a single question after each ship. Not a survey. One reply beat ten silent likes. 8/ After 8 weeks the habit mattered more than any single release. The product name on the thread is FILL_WITH_SPEC — swap it for yours before you post. 3) ENGAGEMENT CTA If you ship weekly too, reply with the one constraint that keeps you honest (time, scope, or demo). I will read every reply — no growth promises, just peer notes. 4) ALT HOOKS • 8 Fridays. 8 small ships on FILL_WITH_SPEC. Here is the weekly log template I reuse when I want progress without launch theater. • Build-in-public tip: write the changelog before the code. That one rule saved my Friday ship streak for 8 weeks. • Solo founders: a boring Friday ship beats a hype thread you cannot defend. My 8-week cadence, facts only. 5) TAGS #BuildInPublic #IndieHackers #SaaS #ShipWeekly #Bootstrap 6) COMPLIANCE CHECK Placeholders: STAT_PLACEHOLDER for demo clip length (seconds) and any revenue/follower figures — replace with dashboard facts or delete. FILL_WITH_SPEC for product name — replace with your real product. Confirm no invented metrics, followers, impressions, virality claims, or income guarantees. English only.
GPT

X Thread Writing Engine

Add to Cart
PromptBase Select
Get this prompt + 9 more with SelectFrom $14/mo · Cancel anytimeFrom $14/mo · Cancel anytime
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-6-LUNA
Tested icon
Guide icon
4 examples icon
Free credits icon
Turn a topic, audience, angle, proof, and tone into a ready-to-post X (Twitter) thread pack: hook tweet, 7–10 numbered thread tweets, engagement CTA, 3 alt hooks, tags, and a compliance check. Facts only — no invented followers, impressions, or virality claims. X threads only — not LinkedIn posts, not Instagram captions, not YouTube titles or Shorts scripts.
...more
Added 1 week ago
Report
Browse Marketplace