How to use Claude to build a social media platform
A developer used specifications, Claude Code implementation, and Codex review to ship a social media management platform in three weeks, while manually addressing difficult integrations and operational logic.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Using [specifications], [architecture document], and [style guide], plan [social media platform]. Separate parallel tasks from dependencies, implement [selected backend and UI scope], and have [review agent] challenge security and correctness. Flag integration uncertainties for manual investigation.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- JanSchu
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports shipping an AGPL-3.0 social media platform in three weeks with twelve first-party integrations, while describing substantial manual work and AI-generated failures.
- Human involvement
- The author planned the work and manually handled difficult integration, orchestration, security, and UI issues; some tenant bugs passed tests.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Write detailed specifications, architecture documentation, and a style guide.
- Separate parallel implementation tasks from tasks with merge dependencies.
- Use Claude Code for planning and initial backend and UI implementation.
The author reports shipping a production social media management platform in three weeks using Claude Code and Codex. Before coding, they wrote detailed specifications, an architecture document, and a style guide. They divided the specifications into tasks that could run across parallel agents and dependent tasks that needed to merge first.
Claude Code with Opus 4.6 handled planning and the initial backend and UI implementation. Codex 5.3 then challenged implementations, surfaced security issues, and found bugs. The author reports useful results with Django CRUD, documented provider APIs, Tailwind layouts, HTMX interactions, test generation, and cross-file refactoring.
Several areas needed substantial human intervention. Both tools repeatedly mishandled TikTok's upload flow. Multi-workspace permission bugs leaked data across tenants despite passing tests. OAuth edge cases and background orchestration required manual work. UI consistency and reachable flows also consumed significant effort.
The delivered project is open source under AGPL-3.0 and includes twelve first-party platform integrations, approval workflows, encrypted credentials, and a unified inbox.
Who it's for: Experienced developers able to specify architecture, investigate security failures, and finish integration details themselves.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · JanSchu
Frequently asked questions
How were Claude Code and Codex assigned different roles?
Claude Code with Opus 4.6 planned and built the first backend and UI pass. Codex 5.3 challenged implementations, identified security issues, and caught bugs.
Which parts still required manual implementation?
The author reports manual work on OAuth edge cases and background orchestration, alongside difficulties with TikTok uploads, tenant isolation, and UI usability.
More details
Remaining steps
- Use Codex to challenge implementations and identify bugs and security issues.
- Manually address OAuth, background orchestration, and usability problems.
About this account
Agents implemented substantial portions of the platform from prepared specifications and reviewed the resulting code, with tasks divided by dependencies.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47749688. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: JanSchu on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Codex · Django · HTMX · Tailwind CSS · PostgreSQL · Docker Compose
Spec-driven development · Code review · Social media
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.