Ship Shit Games

Building games with AI, in public

Ship Shit Games builds the DEADROT universe live with AI — a whole IP, many browser games, one bloody canon. Skills Pro and the studio tools are the system we use to move this fast.

Buy Skills Pro Play Deadrot

▼ scroll

7Game tracks

Public DEADROT builds with playable links, source, and readiness gates.

96Production sprites

Canon pixel assets synced straight from the live asset catalog.

134PRs shipped

Merged pull requests across the studio and DEADROT repos, all-time.

200Commits / 30 days

Commit pressure across both repos in the last thirty days.

$ latest shippedFull build log →

[PR]feat(scourge-survivors): elite wave affixes for Survivors breach surges2026-06-09
[PR]chore(tooling): test-path hygiene + gitignore cleanup2026-06-09
[PR]feat(game-kit): @deadrot/game-kit shared runtime (audio, juice, core)2026-06-09
[PR]docs(sessions): 2026-06-09 session 2 + ressources transcript memory2026-06-09

The games

Seven tracks. One war.

All games →

Scourge SurvivorsPlayable

Studio reality

AI floods. We ship.

The new bottleneck is not generation. It is taste, continuity, QA, deployment, and knowing what to cut before the build collapses under its own cleverness.

Idea flood

AI can hand you a hundred concepts before lunch. The hard part is choosing the one with enough teeth to ship.

Canon drift

Prompts, renders, lore, UI, and code drift unless the build has rules and a real source of truth.

Taste check

Automation without review makes louder slop. The system has to scope, build, inspect, and cut.

The build loop

Scope. Canon. Ship.

Ship Shit Games is the operating system we use to build DEADROT in public: scoped slices, canon-aware asset generation, agent workflows, and ruthless review loops.

01

Scope

Start with one promise, one aesthetic lane, and one public build target.

02

Canon

Keep assets, lore, prompts, and implementation tied to studio rules instead of one-off experiments.

03

Ship

Use agents for scaffolding, code, review, deployment, and session capture until the build is public.

DEADROT

War IP. Live build.

DEADROT is the browser-game IP we are building in public: war fronts, invasion pressure, hard factions, and the Scourge as parasitic host-takeover organisms, not generic monsters.

Play Deadrot See the war assets

Studio output

Games. Tools. Receipts.

This is not a content funnel pretending to be a studio. Each product is tied to what we are actually building, using, and publishing.

DEADROT

The browser-game universe we are building live: brutal canon, playable builds, source links, and finished-product gates.

See the games →

Skills Pro

The paid operating manual: production prompts, agent workflows, review loops, and updates from the live build. Early buyers get in at $29.

Buy the pack →

Asset pipeline

The generated game-art workflow, catalog rules, and assetgen tooling we dogfood on DEADROT.

See the assets →

Build log

The public record of what worked, what broke, and how the system changed after real shipping pressure.

Read the build log →

@shipshitdev/v0The scaffolder we ship every product with — Bun + Turbo monorepo, Next 16, Tailwind, shadcn, agent files. One command, a working repo.npx @shipshitdev/v0 →Agent skillsThe skill library that drives the studio — scaffolding, deploys, reviews, lore craft. The same ones we use daily.Browse the skills →Game boilerplatesVite + React + Three.js starters and the shared engine the games are built on. Clone, reskin, ship.See the repos →

Build log

The devlog should have an archive.

Substack is the right default for the newsletter because every issue can be email, public post, and receipt at the same time. The site stays the landing page; the archive carries the build history.

Email first

Short, useful dispatches from real builds: shipped slices, broken loops, prompts, and cuts.

Public record

Readers can link to posts instead of screenshots, and buyers can see the system getting sharper over time.