Build Sessions
2 runs · Opus 4.6
ManyHands-Slack
Two orchestration runs. First, a full Slack clone built from scratch. Then, a second run extending it with WebRTC video calling, screen sharing, and persistent huddles. Click between sessions to explore the prompt conversations that started each build.
The original build — a full production-grade Slack clone with channels, threads, real-time messaging, file uploads, user presence, and search. Launched cold from a single prompt.
manyhands — prompt session — SlackClone
COMPLETED
YOU
Use manyhands to make Slack, all of it.
AI
That's an ambitious project! Let me get the ManyHands prompt template to structure this properly.
AI
AI
Great, I have the template. Let me draft a comprehensive spec for this. A couple quick questions first:
AI
YOU
User has answered your questions: "What tech stack do you prefer for this Slack clone?"="Next.js + PostgreSQL (Recommended)", "What scope feels right? 'All of Slack' is enormous - how far should we go?"="Full Slack clone". You can now continue with the user's answers in mind.
AI
Full send it is. Let me draft the complete spec.
AI
AI
That's a ~400-line spec covering the full Slack experience. Here's what's included:
Scope: 25 core features across auth, workspaces, channels, messaging, search, notifications, and more.
Tech stack: Next.js 14, TypeScript, Tailwind + shadcn/ui, PostgreSQL/Prisma (SQLite for dev), Socket.IO, NextAuth, Tiptap rich text editor, Zustand.
Shared contracts defined upfront:
▸Full Prisma database schema (15 models)
▸Socket.IO event contracts (both directions)
▸REST API endpoints (~40 routes)
▸Zustand store shape
▸Complete directory structure
4 milestones: From "two tabs exchanging messages" → full Slack experience with polish.
Out of scope: Video calls, Slack Connect, apps/bots, workflow builder, Canvas/Clips.
Ready to launch?
AI
🚀Orchestration Launched
Build Complete