Skip to content
Independent studio

Built to
come down

We make Wreckwing, a destruction game for Mac, and the engine it runs on.

WreckwingThe engine

Trilithon Games is a very small independent studio. We build our games and our engines almost entirely with Claude Code, Anthropic’s AI coding agent.

Work

A game and two engines

A gunship hovering over a rooftop as an office tower collapses into debris across the street
Game

Wreckwing

Fly a small gunship at street level through procedurally generated cities you can destroy.

Mac · Apple silicon · In development

See the game
A tower breaking apart in mid-collapse, its floors shearing into slabs above a city street
Engine

Trilithon Engine

Our own Swift and Metal engine on Jolt Physics, built around fracture, collapse and a deterministic simulation.

Mac · In-house · Not licensed

See what it does
A wrecking ball smashing through a stack of crates, in large pixels on a curved, scan-lined screen
Engine

Phosphor

Our indexed-color 2D engine, aimed at iPhone and iPad: a fixed grid of palette indices, deterministic physics and a CRT presenter on Metal.

iPhone and iPad · In-house · Not licensed

See what it does
Devlog

Latest posts

All posts
Studio note card reading Fact-checking the game, while writing about it, over a city street with a fireball beside an office tower
StudioStudio note

Fact-checking the game while writing about it

· 5 min

A night test scene at the peak of a blast's flare: two gray blocks on an open floor under a starry sky, lifted out of the dark, with a bright glow on the floor ahead
WreckwingDev journal

Darkening Wreckwing without losing the blasts

· 6 min

A park in a city seen from low over the grass: rows of white smoke puffs cross the lawn from the left and end at a fighter near the far edge, where the first missile has burst in fire
WreckwingDev journal

Finding why the new enemies felt soft

· 4 min

How we build

Designed here, built with Claude Code

We design our games and engines and direct the work, and Claude Code writes almost all of the code. Every devlog post says how it was made.

  1. 01

    We design and decide

    The game design, the engines’ architecture and the answers to hard problems. Each piece of work starts as an issue with a goal and a way to measure it.

  2. 02

    Claude Code builds it

    A Claude Code session writes the code, runs the measurements and drafts the devlog post.

  3. 03

    We review it

    Nothing ships or gets published until it has been reviewed. Every post says which session drafted it and who checked it.