Social mediaCAN I VIBECODE
posterly?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
posterly (poster.ly) is an AI-native social media scheduling platform for individuals, agencies, and AI agents. From one dashboard it publishes/schedules to LinkedIn, Instagram, X, YouTube, Facebook, Threads, TikTok, Pinterest, Google Business Profile, Bluesky, and Telegram (11 platforms live; marketing pages also cite 18). Built-in AI covers captions, image generation (Gemini/Nano Banana), and scheduling. Planning views: calendar, list, table, grid; agency content-plan boards offer client review/approval states, review-locked slots, drag-to-swap scheduling, and publishing approved story assets. Developer surface: REST API (POST /api/v1/posts with caption, account_id, media_urls, scheduled_at; accounts/media/analytics/webhook endpoints; Bearer auth; HMAC-SHA256-signed webhooks; ~100 create-post requests/hour/key), a hosted MCP server plus npm stdio package usable from Claude, ChatGPT, Cu
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for posterly, an AI-native multi-network social media scheduler. Core workflow: a user connects social accounts once, drafts a post (caption + optional media), optionally schedules a time and per-network variants, reviews it on a content-plan board, and the backend publishes it to every connected network through one unified queue. Requirements: user-facing — a dashboard with calendar/list/table/grid views; AI caption drafting and AI image generation via a pluggable model API; agency workspaces with draft/awaiting-review/approved states, review-locked slots, and drag-to-reschedule; webhook notifications on post lifecycle (created, publishing, published, failed). Technical — REST API (create post with caption, account_id, media_urls, scheduled_at; endpoints for accounts, media, analytics, webhooks; API-key auth; HMAC-signed webhook deliveries), a background job queue with retries and per-platform rate limiting (BullMQ + Redis), an MCP server exposing scheduling tools for agents, and a CLI for scripting/cron. Suggested stack: Node/TypeScript backend, Postgres for state, S3-compatible object storage for media; integrate at least two real platforms (e.g., X and Facebook via official APIs) and stub the rest with a documented adapter interface. Do not copy posterly's brand, logo, marketing copy, or UI. Out of scope: real billing multi-tenancy, native mobile apps, and production-grade scaling beyond a handful of networks. Deliver a README covering setup, env vars, OAuth/API-key flows, and the known limitations of each network integration.