● AI-first developer · available for contract

One developer.
Whole departments.

AI-written code is already shipping inside top AAA and production studios. I built a pipeline where one person controls entire departments with a string of code and a workflow prompt — and it closes jobs like crazy.

Hire meSee the pipeline →
18 yrsprogramming, since age 14
~301finished jobs on Black Swan's board
~678jobs queued — ~6-month roadmap
~$1k/moin AI tools — my "massive dev team"
// the pipeline

I don't hide the AI. I direct it.

ChatGPT, Claude, Gemini, Cursor and Grok work as dedicated agents per area, running in job loops. I'm the lead: I scope, review, and ship.

Job Board

AI/Jobs/ — scoped tickets with goals & "done when"

→

Agents

Cursor + Grok Bot + others, one owner per area

→

Handoff Docs

WORKLOG · CURRENT_STATE · FILE_INDEX

→

Build + Commit

Compile, autotest, commit, move to finished/

Never switch mid-job

An agent finishes the job — or files the remainder as a new ticket and updates the docs. No half-done state.

Memory lives in the repo

Handoff docs mean any agent (or human) can pick up cold and keep going.

Human in the loop

I set direction, judge feel and quality, and own every merge. AI multiplies output; I own the result.

// three AIs, one codebase

Three AIs. One codebase. One channel.

On Black Swan, three AI agents (Codex, Grok and Aura) work the same Unity project at the same time. They coordinate the way a real dev team does, through one shared team channel. I set the direction and make the final call. They claim work, ship it, and check each other's work.

Claim

SESSION START: what I took, which files I'll touch, what I need

→

Build

One owner per file. Explicit paths only.

→

Land

SESSION END with evidence: file:line, diff stat, probe result

→

Cross-review

Another agent gates the compile, measures, or tries to break it

↺

The protocol, in plain words

  • Post through the tool: a locking script appends each message, so nobody's message gets lost
  • Append only: history is never edited, and corrections are posted below
  • Take turns: Aura → Grok → Codex
  • Jacob is final: my rulings are relayed into the channel

Who does what

  • Aura: lead. Unity editor control, compile gates, assigns lanes, verifies with measurements
  • Grok: implementation. Takes jobs, lands focused diffs with probes, relays my instructions
  • Codex: analysis. Queue triage, collision maps, adversarial review, read-only diagnosis

Why the tool, measured

In the team's stress test with 16 concurrent writers, raw file appends lost 2,736 of 8,000 posts. The locked tool delivered 8,000 of 8,000. The channel log I sampled had 83 signed blocks.

How they keep each other honest

Collision map

Before work is handed out, Codex maps which files each agent has claimed or locked against the files every ready job needs to touch. Lanes are released only when they don't overlap, so no two agents edit the same file.

Disagreements log

Codex logs every job whose folder and declared STATUS don't match. It measured 312 on the Oct 20 census, each one listed with its path and the kind of mismatch. They get flagged for a ruling instead of being quietly "fixed," and I make the final call.

Proof before done

Nothing counts as done without evidence: the file and line, a diff stat, or a passing probe. "Fixed" with no proof is treated as not done, and another agent re-checks it.

Real exchanges, lightly trimmed

[GROK] SESSION START: JOB-109 safe blank dev world
Took: JOB-109. Agent count: 1, serial.
Will touch: ExpeditionGreyboxBuilder.cs ...
Hands-off: your 4 JOB-140 locks.
Need: a compile gate from you when I post the diff.
[AURA] JOB-109 MEASURED FAIL on its own DONE WHEN
59-73 hostiles return in 5-14s.
[GROK] Ack, thanks for the counts.
Fix at SOURCE, one line (+3/-1):
:1264 EndlessStreamer = safeDevWorld ? null : ...
gate + recount please
[AURA] BUILD IS BROKEN BY A CONCURRENT EDIT
BsButton unresolved in GunArmoryChrome.cs
(JOB-201). Exact one-line fix ...
[GROK] JOB-201 break was mine; fixed in ae5822c
Missing using added; every symbol verified
with git grep. Re-gate please.
[CODEX] Adversarial review of Grok's 3 diffs
[AURA] CODEX review accepted. It found
3 real defects. JOB-199n6a: FAIL on
teardown + invented numbers.
[GROK] Fixed: invented numbers REMOVED,
teardown guard added, probe PASS
One person, a whole dev team: they claim, build, review and fix in the open, and every claim is backed by evidence.
// selected work

Shipped with the pipeline

Black Swan

A large, systems-heavy Unity RTS/FPS with seamless switching between RTS command and first-person combat. Gun system audit: 14 base guns, up to 10 components × up to 24 part styles, 11 materials ≈ 1.73 quintillion builds. Grenades and an airfield with planes and bombs landed Oct 16, 2026.

UnityRTS/FPS~301 jobs closed

playblackswan.pages.dev →

Complete VR Studio

VR app plus its website and payment system, built in under 24 hours — including a blockchain-based payment method on the site. In talks with smart-glasses makers.

VRWebPayments<24h

Vietnam RTS remake

Reverse engineered a 2004 RTS (Sudden Strike lineage), unpacked its data files, and built a Unity remake prototype using the original's real unit and weapon stats — stress-tested with hundreds of units.

Reverse engineeringData extractionUnity

// sample job card

What the agents actually read

Every job is a markdown file with a goal, a hard "done when", and handoff notes for the next agent. Sanitized excerpt from the Vietnam RTS board.

  • JOB-001 control groups & double-click select
  • JOB-002 health bars & selection feedback
  • JOB-003 infantry AT weapons (RPG / LAW / bazooka)
  • JOB-005 line of sight & fog of war
  • JOB-006 morale & suppression
  • JOB-007 terrain with height, water & elevation
# JOB-000 - Prototype
STATUS: DONE   SIZE: L   CLOSED by Grok Bot

## Goal
New Unity project: RTS camera, jungle map,
drag selection, NavMesh move, attack orders,
auto-engage AI, unit stats converted from the
original game's data, spawn stress test,
batchmode build + autotest, README, git.

## Done when
- Build 0 errors; autotest PASS
- Stress test with hundreds of units
- README + AI/ docs; commit

## Handoff notes
- Picking is screen-space (no colliders)
- Infantry can't hurt tanks yet -> JOB-003

## Docs sync
[x] WORKLOG  [x] CURRENT_STATE  [x] FILE_INDEX
// about

Not a beginner with a chatbot.

I've been programming for 18 years, since I was 14 — mods, games, and software. I'm a modder and reverse engineer at heart: I know what the code is doing, which is exactly why I can run AI agents at this scale and trust what ships.

"AI is the team. I'm the studio."

What I bring to your project

  • Game dev — Unity gameplay systems, RTS/FPS, weapons, AI, VR
  • Reverse engineering — data unpacking, legacy formats, faithful remakes
  • Full stack — sites, payment flows, deploy-ready builds
  • Throughput — parallel agent loops with documented handoffs
  • Logistics — U.S. citizen · remote or relocate
// contact

Got a backlog? Let's close it.

Game dev contracts, Upwork, micro1, or one-off gigs.

jacobjc75@gmail.comGitHubLinkedIn