SMF·SUPERX
Can a prompt replace SuperX?
Social media — X growth platform
Exhibit tracking slip
Verdict
The personal core — a composer with an LLM writing in your own voice, a slot-based scheduler, basic post-metrics tracking — is a weekend build, the same as every other social scheduler in this catalogue. What isn't buildable: X's write API costs real money before your first scheduled post even goes out, the viral-post library and timing models are proprietary data collected over years, and engagement automations sit in rate-limit and terms-of-service territory a personal script will get wrong.
Exhibit A — The prompt
Received on30.07.2026Build a personal X posting cockpit: a composer with an AI draft panel that sends your topic plus a sample of your own past posts to a model API, so drafts sound like you, with a couple of tone options (punchier, shorter, thread). Build a slot-based queue — preferred weekday posting times from a config file — where drafts fill the next free slot, can be reordered, or pinned to an exact time; support threads with a per-post character counter. Publish on a scheduled loop through the X API, marking each post as sent or failed before it actually posts so nothing double-fires. Pull your own recent post metrics (impressions, likes, replies) on a daily schedule into a simple dashboard: a per-post table and a rolling trend line. Add a copy-to-clipboard fallback per queued post so the tool stays useful without paying for API write access.
Do not build a viral-post library, optimal-timing models, auto-DM or lead-generation features, or multi-account management — those are data and terms-of-service problems, not code, and pretending otherwise wastes real effort. Be blunt in the README that posting through X's API needs a paid tier, and that cost exists before your first scheduled post goes out.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 a large viral-post library and niche inspiration feed
- B.2 algorithm-aware optimal posting-time models
- B.3 engagement automation and lead-generation tooling
- B.4 in-feed browser-extension analytics
- B.5 multi-account management
Prior art
Exhibit C — Why people still pay: proprietary data + platform API costs
X's API meters every write before your first post goes out, so the DIY version starts with a monthly API bill and none of the product. What actually grows an account — knowing what performs in your niche, and when — comes from data collected and modeled over years, not from code you can regenerate.
Questions
Can I import my existing SuperX queue and drafts?
Not automatically — there's no structured export of scheduled drafts. Recreating an active queue by hand is realistic, since it's rarely more than a handful of pending posts.
Will it work on my phone?
The composer is a responsive web page, usable on a phone for drafting, but there's no dedicated app, and paying for and configuring X's API access is a desktop-and-developer-console task either way.
What does it actually cost to run?
Hosting plus LLM API usage per draft, typically a few cents — the real cost is X's own paid API write tier, which exists before the first scheduled post goes out and can exceed the flat subscription price depending on volume.
What's the one thing that genuinely doesn't survive the rebuild?
The data. Knowing what performs in a given niche and when to post it comes from years of collected engagement data across many accounts; a personal script only ever has visibility into your own account's numbers.
Related tools
Receipt