# Build brief — a focused alternative to SuperX

> **Verdict:** Partly, if you narrow it · **Buildability:** 50/100 · **Category:** Social Media
> **Source:** https://www.canitbevibecoded.com/superx
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from SuperX. Verify current pricing and capabilities before acting.

## Context

**SuperX** — AI content, smart scheduling, engagement tools, and analytics for growing on X. It currently costs $49/mo.

The personal core (a composer with an LLM writing in your voice, a slot-based scheduler, and basic analytics) is a contained build, exactly like every scheduler on this list. What you cannot one-shot: X's write API costs real money before your first post goes out, the 10M-post viral library and timing models are proprietary data collected over years, and the engagement automations live in rate-limit and ToS territory that a personal script will get wrong. Full disclosure: SuperX is built by the person who runs this site. The verdict got no mercy anyway.

This brief describes a focused, single-operator replacement for the part of SuperX that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Compose posts and threads with an LLM prompted on samples of your own writing, queue them into weekday time slots, publish via the X API, and pull your post metrics into a local dashboard.

- Draft, queue, and track content for the few networks you actually use.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Always-on box for the scheduler.

### Data and integrations

- Paid X API tier for posting.
- LLM API key for voice-matched drafts.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a personal X posting cockpit inspired by SuperX. Requirements:

- Node + Express + better-sqlite3, one localhost web app; no accounts, no
  telemetry, all keys in .env.
- A composer with an AI draft panel: send my topic plus 20 of my own past
  posts (pasted once into voice.txt) to an LLM API so drafts sound like me,
  with tone buttons for punchier, shorter, thread.
- Slot-based queue: weekday posting times in my timezone from a config
  file; drafts fill the next free slot, drag to reorder, pin to exact
  datetimes. Thread support with per-post character counters.
- Publish via the X API v2 with node-cron, marking rows sent or failed
  before posting so nothing double-posts. Be blunt in the README: posting
  needs a paid X API tier, and that bill exists before the first post.
- Pull my recent post metrics (impressions, likes, replies) on a daily
  cron into SQLite and render a simple dashboard: per-post table plus a
  30-day sparkline drawn as inline SVG.
- A fallback copy-to-clipboard button per queued post so the tool stays
  useful without paying X anything.
- Out of scope, and say so in the README: viral post libraries, optimal
  timing models, auto-DMs, lead generation, and multi-account. Those are
  data and ToS problems, not code.
- README: X developer app setup, which paid tier posting needs, and the
  LLM key.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- The 10M+ viral post library and niche inspiration feed.
- Algorithm-aware optimal posting times.
- Signal agents and lead generation.
- Auto-DM and engagement automation.
- The useful dataset is owned, accumulated, or expensive to reproduce.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [postiz-app](https://github.com/gitroomhq/postiz-app) — open-source social scheduling, the nearest self-host starting point

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/superx