Developer Uses Claude Code to Build SetForge Web App for Band Management
A developer who recently joined a band used Claude Code to build SetForge, a production web app for managing band song libraries and setlists. The developer described the problem to Claude Code and didn't write the architecture or scaffold the project - just described what was needed.
Key Features Built with Claude Code
The resulting React app, deployed to Vercel and available at setforge.live, includes:
- Jam Set: Import your library, share a collab link with bandmates, and SetForge finds songs you all know to build a starting set from the overlap
- Excel/CSV import: Uses SheetJS with flexible column mapping and deduplication logic
- Flow scoring: Grades setlists with 60% transition score (energy + key distance) + 40% arc score. Checks if peaks land in the right window and if you close strong. Only appears when songs are tagged
- Auto-arrange: 5 modes: Wave, Slow Build, Front-loaded, Smooth Keys, Drama Arc. Segment-aware, respects Opener/Closer category tags, undo via toast
- Gig Mode: Full-screen per-song view with lyrics pulled live from lrclib.net with auto-scroll, break countdown timer, speed control
- Collab links: Bandmates edit the same setlist in real time via /c/:token. No auth, no accounts - the UUID is the "account"
- Smart paste parser: Handles raw UG favorites dumps, messy "Artist - Title" lists, tab URLs. Deduplicates against existing library automatically
- Print view + CSV export
Developer Insights on AI-Assisted Development
The developer, who manages a UX team professionally, noted that while Claude Code quickly built and deployed the scaffolding and features, the refined experience required human intervention. Micro-interactions that were technically correct but awkward on an iPhone mid-gig, or drag behavior that works but doesn't respond the way a hand expects, only surfaced when real people used the app in context.
The developer found they weren't spending less time on UX, but spending "better, more productive time" on it - validating intent rather than debugging layout logic or pixel alignment. Questions like "Does this gesture feel like what the user means?" and "Does this flow match what a musician needs at 9pm on a dark stage?" became the focus.
The developer concluded: "Claude builds the thing. It does not feel the thing. AI is removing the barrier to entry - the parts of the job that were never the valuable part. The judgment about what a user actually experiences is still entirely human and that's the part that makes something worth using."
📖 Read the full source: r/ClaudeAI
👀 See Also
Using Lava's MCP Gateway with Claude Code for Low-Cost Content Workflow
A user connected Lava's MCP gateway to Claude Code and accessed research tools like Exa, Serper, and Tavily without accounts or API keys, creating a social media content workflow for $0.03.
State Machine Approach for Coordinating Multiple AI Agents
The team at ultrathink.art found that coordinating multiple AI agents requires explicit state transitions, heartbeat timeouts, retry limits, and task chaining rather than traditional message queues. They implemented mandatory quality gates between agent handoffs to prevent garbage output.
Building a 13-Agent Claude Team with Peer Review Workflow
A developer built a 13-agent Claude system where AI agents review each other's work, run on scheduled heartbeats, and track everything in a database for marketing automation.
Agentic Coding Fatigue: Why More Agents Won't Save You
Sid's blog post argues that agentic coding compresses the normal ebb and flow of development, forcing developers into a constant cycle of decision fatigue and burnout. The solution isn't more agents—it's better verification, but building that is a catch-22.