Can I vibe code Slack?
Where work talks: channels, DMs, and a decade of integrations.
A chat app is a classic tutorial build — websockets, channels, messages — and for a hobby group your vibe-coded version genuinely works. Slack the product is a different thing: the network already inside it. Your team, your clients, your community DMs, two thousand integrations, and everyone's muscle memory live there; a technically fine replacement with nobody in it solves nothing. Teams that actually want out don't DIY either — they move to Discord, or self-host Mattermost/Rocket.Chat and inherit mature software plus data ownership.
Build a private team chat for my small group (we're all agreeing to use it — say this matters in the README). Channels + DMs with real-time delivery over websockets, message history in Postgres, magic-link auth, presence dots, typing indicators, markdown with code blocks, emoji reactions, simple reply-in-thread, and full-text search. An incoming-webhook endpoint so my other vibe-coded tools can post alerts into channels (my Slack-integration replacement). PWA with web push notifications. Deployable on a host that supports websockets (Railway/Fly), Next.js front end.
A real-time chat for a small known group: channels, DMs, threads-lite, presence, and search — genuinely usable for a project team or friend group that agrees to live in it.
- Everyone-is-already-there — the entire point of a messenger
- 2,000+ integrations and workflow automations
- Mobile apps with reliable push notifications
- Search, retention, and compliance features orgs require
Messaging is a network good: the subscription buys presence in the room where your collaborators already are, and no feature list substitutes for occupancy.
A prompt is the first move, not the whole game. Course 01 teaches you to take a prompt like this one to a shipped, working app — reviewing, correcting, and steering the agent the whole way.
Start Course 01 →