Developer uses Claude Code agents to resolve 635 issues across 42 board games in single session

✍️ OpenClawRadar📅 Published: March 31, 2026🔗 Source
Developer uses Claude Code agents to resolve 635 issues across 42 board games in single session
Ad

A solo developer building a free multiplayer board game platform used Claude Code agents to systematically resolve hundreds of UI/UX issues across 42 different games in a single development session.

The Setup

The developer maintained approximately 800 issues in a local SQLite-based tracker, covering both backend Rust bugs (like field name mismatches between Rust and TypeScript) and frontend polish tasks. Examples included "Backgammon needs drag-and-drop," "Hearts needs card dim for invalid plays," "Shogi needs handicap support," and "Skat needs Ramsch mode."

Configuration files included:

  • CLAUDE.md with architecture rules
  • .claude/rules/ files covering actor model, game engine patterns, and E2E testing conventions

These rules auto-loaded every time Claude started working.

The Workflow

The developer ran four agents simultaneously, each handling a single issue from a different game to prevent file conflicts. Example agent assignments:

  • Agent 1: Fix backgammon drag-and-drop (#407)
  • Agent 2: Fix belote coinche bidding UI (#417)
  • Agent 3: Fix briscola field mismatches (#454-457)
  • Agent 4: Fix chess captured pieces display (#494)

Each agent would read relevant files, implement the fix, run svelte-check, mark the issue resolved, and commit. While these four ran in the background, the developer reviewed completed fixes, resolved any build errors, then launched the next batch.

What Worked Well

  • "One agent per issue, never batch" approach proved more effective than giving one agent multiple issues
  • Strict rules in CLAUDE.md (no any types, use data-ui attributes, backend as source of truth for field names) ensured consistent code
  • Claude understood both Rust game engine code and SvelteKit Canvas rendering equally well
  • Agents could read a Rust build_state_message() function and fix corresponding TypeScript handlers
  • Sound effects implementation was successful—Claude synthesized Web Audio API sounds (wood taps for Go, card snaps for Hearts, dice tumbles for Backgammon) without any audio files
Ad

What Went Wrong

  • When agents added new GameRule enum variants in Rust, they'd forget to update the exhaustive match in judge.rs
  • Occasional merge conflicts when two agents modified the same game.svelte.ts store file
  • Some agents over-engineered solutions—adding 200 lines when 20 would suffice
  • Train Dominoes tests broke three times because an agent changed round_scores from Vec<u32> to Vec<Vec<u32>> without updating all test assertions

The Results

  • 325 commits in one session
  • 635 issues resolved (all critical and high priority cleared from ~800 total)
  • 42 different games touched
  • Build maintained at 0 errors throughout (Rust + frontend)
  • Every game received: sound effects, board themes, move history, result screens, drag-and-drop where applicable

Lessons Learned

  • Should have run cargo test after every batch, not just cargo check—some compile-time-correct changes broke runtime behavior
  • Should have created shared components first for games with similar patterns (trick-taking card games, 4-player NESW layouts) instead of having each agent reinvent the wheel

📖 Read the full source: r/ClaudeAI

Ad

👀 See Also

SkiTomorrow.ai: A Ski Trip Decision Engine Built with Claude Code
Use Cases

SkiTomorrow.ai: A Ski Trip Decision Engine Built with Claude Code

SkiTomorrow.ai is a free web tool that scores 234 ski resorts worldwide based on live snow forecasts, travel distance, and cost, then provides personalized rankings. The developer built it entirely using Claude Code and shared specific workflow insights.

OpenClawRadar
How a Developer Used Claude Code with Linear and Discord for a Solo 30-Day Build
Use Cases

How a Developer Used Claude Code with Linear and Discord for a Solo 30-Day Build

A developer built a full-stack Pokémon VGC team report tool in 30 days using Claude Code as a pair programmer, integrated with Linear for ticket tracking and Discord for build notifications. The workflow involved automated ticket handling, type-checking gates, and a CLAUDE.md file for consistent AI instructions.

OpenClawRadar
Reddit user reports better results with Claude after changing prompting approach
Use Cases

Reddit user reports better results with Claude after changing prompting approach

A developer spent days struggling with multiple AI tools before finding success with Claude by shifting from search-engine style prompts to back-and-forth conversations with specific context about why approaches weren't working.

OpenClawRadar
Running an AI-Operated Store: Lessons from Ultrathink.art
Use Cases

Running an AI-Operated Store: Lessons from Ultrathink.art

The team behind ultrathink.art, an e-commerce store where every function is handled by AI agents, shares insights on treating agents like contractors rather than fancy autocomplete. Key differences include how you scope their work, what information you provide, and how you verify completion.

OpenClawRadar