Claude Code builds Drift Lane and starts a Unity port
@froessell used Claude Code to build Drift Lane in Three.js from a short PRD, then adjusted difficulty and controls through playtesting. A later Unity port remained a work in progress, not a shipped mobile release.
x.com
Original prompt
Shared by the source author. See source notes for context.
Core concept: An arcade drifting game where you navigate narrow, elevated tracks, avoid obstacles, and collect coins.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @froessell
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A playable browser drifting game and playtest-driven changes are reported by the poster. The follow-up reports a Unity port still in progress for intended iOS and Android distribution, not a shipped mobile release.
- Human involvement
- @froessell supplied the PRD, played the initial game and drove difficulty and control changes. The poster asked about engine choices and iterated on the UI draft. The account does not specify deployment permissions or app-store approval.
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
- The poster developed the concept with Codex and gave Claude Code a short PRD for an arcade drifting game.
- Claude Code built Drift Lane in Three.js, with a car asset from Tripo and Blender.
- The poster played the build and changed track difficulty, edge recovery and touch controls.
@froessell gave Claude Code a short product brief for Drift Lane, an arcade drifting game on narrow elevated tracks. Codex helped develop the concept, Claude Code built the browser game in Three.js, and the car asset came from Tripo and Blender. The initial playable result arrived "30 minutes later", reported by the poster, followed by "a few hours of iterating" while they did other things.
The poster then played the build and changed specific problems. Difficult early sections led to wider tracks and gentler corners. Instant death at the edge became a brief opportunity to steer back. Hard-to-hit directional buttons became a floating joystick. The account says the browser version runs on phone and desktop in portrait and landscape.
A later post describes a Unity port intended for iOS and Android. Asked to compare TopDown Engine and HighRoad Engine, Claude Code read the code and recommended neither because replacing the hand-tuned drift physics would change the feel. It instead ported the handling line by line. ChatGPT supplied a UI concept, Claude Design produced a draft through back-and-forth iteration, and Claude Code rebuilt the screens in Unity.
The follow-up explicitly calls that work a work in progress. It does not establish an App Store or Google Play release. The useful distinction is between a reported playable browser game, human-led playtesting and an unfinished mobile-oriented port. The prompt excerpt preserves the original concept rather than claiming to reproduce the entire brief.
Prompt
Original prompt
Source: X · @froessell
Frequently asked questions
Was Drift Lane actually playable in a browser?
The poster reports a playable browser game on phone and desktop, in portrait and landscape. This entry is based on the written account, not an independent playtest.
What did human playtesting change?
The poster widened tracks, softened early corners, added a chance to recover after grazing the edge and replaced directional buttons with a floating joystick.
Was the Unity version shipped on iOS and Android?
No shipped mobile release is established. The follow-up describes a Unity port intended for iOS and Android and explicitly says it is still a work in progress.
More details
Remaining steps
- In the follow-up, Claude Code inspected engine options, recommended preserving the existing drift handling and ported it line by line to Unity.
- The poster iterated on a UI draft with Claude Design after a ChatGPT concept; Claude Code rebuilt the Unity screens, with the port still in progress.
About this account
Claude Code implemented the browser game from a PRD. In the follow-up it read code, rejected proposed engine replacements to preserve handling, ported physics line by line and rebuilt Unity screens.
Original prompt excerpt: exact opening concept sentence from the published PRD, not the full brief. Full source-post text retained in evidence. Follow-up: https://x.com/froessell/status/2114310224391655453. Follow-up published 2026-10-25T10:56:54+00:00, checked 2026-10-27T08:27:49.926067+00:00 in supplied FxTwitter mirror JSON. It explicitly states work in progress; no shipped iOS or Android release is established. Attached media and browser gameplay were not independently reviewed. Source published 2026-10-19T11:52:20+00:00. Captured written post and author metadata checked 2026-10-27T08:27:49.926067+00:00 using supplied public FxTwitter mirror JSON, not a direct X page or independent execution. Results reported by the poster.
Credit: @froessell
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Codex · Three.js · Tripo · Blender · Unity · ChatGPT · Claude Design
Browser game · Game development · Unity port · Playtesting
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.