Typefully

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me a writing and scheduling tool that replaces Typefully — and read the obstacle first, because it is not code.

**Access to the platform is paid and gated.** Posting on somebody's behalf needs an approved application, and on the platform this product is built around, the API tier that allows meaningful use costs real money. The subscription absorbs that. Check today what an independent developer can actually get and what it costs, before writing anything — if the answer does not work, no amount of good software fixes it.

STACK
- Node 20+ with Fastify, server-rendered HTML
- SQLite through better-sqlite3, WAL mode
- A worker for publishing
- Caddy in front

WHAT IS WORTH BUILDING EVEN IF PUBLISHING IS NOT AVAILABLE
- The composer, the drafts and the preview. Writing a thread well is the hard part, and copying it out to post by hand costs ten seconds
- Say that plainly in the README: the writing half works regardless, and the publishing half depends on access you may not be able to get

THE DATA MODEL
- accounts: id, platform, handle, credentials_encrypted, token_expires_at, is_active, limits_json
- drafts: id, title, parts_json, created_by, created_at, updated_at, status
- posts: id, draft_id, account_id, scheduled_for, status, attempts, client_key, external_id, external_url, published_at, error
- parts: within the draft — an ordered list of pieces, each with its own text, media and character count
- media: id, path, sha256, kind, width, height, duration_ms, alt_text
- slots: id, account_id, weekday, time_local, position
- metrics: id, post_id, kind, value, collected_at — append-only
- clicks through your own short domain, which is the one number nobody can take away

THE COMPOSER, WHICH IS THE PRODUCT
- Write the whole thread in one plain text area, split by a delimiter. Not a form with a box per part — that is what every worse version does, and it makes editing the middle of a thread miserable
- A live character count per part, using the platform's own counting rules: a link often costs a fixed number regardless of length, and an emoji may count as two. Getting that wrong means finding out at publish time
- Automatic splitting of a long paragraph at a sensible boundary, offered rather than applied
- A preview that looks like the platform, at phone width, with each part as it will appear
- Alt text on every image, with an option to refuse scheduling without it
- Keyboard for everything, and autosave with no save button

PUBLISHING WITHOUT DUPLICATES
- The worker claims a post with a lease, publishes each part in order, and records the external identifier of each in the same transaction as its status
- A thread half-published is the specific failure to design for: if part three fails, the first two exist. Record what succeeded, retry only the remainder, and never restart the thread
- Idempotency: a timeout may still have published. Check by client key where supported, otherwise by searching the recent timeline
- Rate limits honoured, with the platform's own headers respected

THE QUEUE
- Slots per account per weekday; adding to the queue fills the next free one
- A calendar and a list of the next fortnight, drag to move, pause an account
- Best-time suggestions from your own past engagement, labelled as a weak signal from a small sample rather than a science

AFTER PUBLISHING
- Metrics collected on a schedule and appended, absent where the API does not provide them and shown as absent rather than zero
- Performance by format and length, with the sample size beside every comparison
- The distribution rather than the average, because social performance is heavily skewed and one post dominates a mean

OPERATIONS
- .env: DATABASE_PATH, STORAGE_PATH, BASE_URL, ENCRYPTION_KEY, SESSION_SECRET, platform client id and secret
- Migrations on boot, each once; tokens refreshed under a lock
- Nightly backup off the machine
- Health endpoint reporting the oldest due post and any expiring token

WHAT MATTERS MOST
The single-textarea composer and partial-thread recovery. The first is why the tool is pleasant; the second is what stops a failed publish from posting your thread twice.