Open one in a browser and play it. Nothing to install, nothing to download.
All of these are built under the same constraint: everything is generated in code. No downloaded models, textures, audio or fonts. Every wall, weapon, sound and sky in these pages is arithmetic that runs when the page loads, which is what gives them the look they have.
What this is
We are not a game studio.
A game is the hardest kind of software to fool yourself about. It runs at sixty frames or it does not. The thing you built is on screen or it is not. There is no partial credit and no writing your way out of it.
That is exactly why we build them. It is a gauntlet, and the gauntlet is the point. Making these runs one loop over and over: build it, render it, look at it, measure it, fix it.
More than twenty times in one of these games, something was written, believed, and never drew a single pixel. Rags on an enemy ten centimetres wide that put three pixels outside its silhouette. A gunsight modelled inside solid metal. A weapon so swallowed by its own muzzle flash you could not see the gun you were holding. Every one was found by looking at the artifact rather than reading the code that made it. Several were in the tests themselves, including one that could never have passed on any build ever made.
What comes out the other side is not really a game. It is a way of working that transfers to everything else we do here: build the thing, prove it exists, and never trust a green check you cannot deliberately make fail.
Playable now
A browser FPS built over one weekend. Three.js, no build step, every mesh and texture generated in code.
Controls: WASD, mouse to look, click to lock the pointer. Needs a keyboard and a real GPU; it will run on software rendering but slowly.