A Native Command & Conquer Port Built by 'Claude Code (Anthropic's Claude, Fable Model)' Shows the Playbook: Sell AI-Assisted Legacy Code Porting, With a Public Engineering Log as Proof of Work.

A native, no-emulation port of a 2003 real-time strategy game to Apple Silicon Macs, iPhones, and iPads is not, on its own, a business idea.

But how it was built, and how it was proven, is.

What actually shipped

The README for the Generals-Mac-iOS-iPad repo says the port was "built as a human+AI collaboration: engineering by Claude Code (Anthropic's Claude, Fable model), directed and playtested on real devices by Ammaar Reshi."

The engine itself came from EA's GPL v3 source, ported through a rendering chain of DirectX 8 to DXVK to Vulkan to MoltenVK to Metal, built with CMake and Ninja, running on iOS through XcodeGen and custom DXVK patches.

None of that is the part worth stealing.

The part worth stealing

The README points to "the engineering log in docs/port/" as "the unedited record of how that worked" — specifically a PORTING_PLAYBOOK.md described as containing "every failure mode, root cause, fix," including a "bug archaeology" section investigating specific issues like minimap rendering and audio glitches.

That is the sellable artifact.

Most technical service providers hide the mess: the dead ends, the wrong fixes, the three days spent on a bug that turned out to be one line. This project published it as the credibility layer for the work itself.

The service to build

1. Find a client with a legacy codebase they still depend on but can't easily modernize — an old game, an internal tool built on a discontinued SDK, a desktop app nobody wants to touch.

2. Scope a fixed-bid port using an AI coding agent as the engineering layer, with a human directing the agent and doing the real-device verification, the same split described in the source repo.

3. Keep an unedited engineering log as you go — failure modes, root causes, fixes — the same structure the source project used.

4. Deliver the port privately to the client. Publish select, non-sensitive sections of the log publicly as your next piece of proof-of-work marketing.

5. Offer a retainer for post-port maintenance, since a fresh AI-assisted port is still new code that will regress against platform updates.

Why this works right now

Buyers of technical services are increasingly skeptical of "AI did this" claims with no evidence attached. A public, unedited engineering log — the exact format used in this port — is a direct answer to that skepticism. It turns the AI-assisted work itself into the marketing.

Bottom line

The interesting business lesson in this port isn't that an AI agent can help rebuild a 2003 game engine for modern hardware. It's that the team proved it by publishing "the unedited record of how that worked" instead of just the finished build.

Source: https://github.com/ammaarreshi/Generals-Mac-iOS-iPad/tree/main