27 small things that run in a browser tab. No install, no account, no build step. Open one and it runs. Next to each one is a write-up of how it was made, and the write-ups are the point: the section that matters is usually "the place it goes wrong", because that is the part nobody warns you about. 23 of them we wrote by hand. 4 were built by describing them in plain words, and for those we kept the actual transcripts — dead ends included. We keep the two lists separate.
Tines The single, secure environment for agents, apps, and automations.
Promoted
Maker
📌
Maker here.
These started as templates for our own tool, and the write-ups started
as internal notes — the kind you write after losing an afternoon to
something stupid.
A few examples of what's in them:
· Flat shading did nothing at all until we called toNonIndexed(). The
assistant helping us confidently reported that the triangles should
now be clearly visible. They were not. It could not see that it had
missed a step.
· A block tower passed its own stability check while visibly sliding
across the screen, because the check only tested "velocity < 0.6"
and a slow creep sails through that.
· An arm froze solid with nothing in the console, because floating
point handed acos() a 1.0000000002 and NaN went quietly down the
pipe.
One thing we were careful about: 23 of these we wrote by hand, and 4
were made by describing them to our tool. Calling a hand-written one
"built by typing one sentence" would be a lie, so they are in two
separate lists and each page says which it is. If you only came for
the second kind, that list is four long — we would rather say so than
pad it.
Everything is free to open and free to take. Happy to answer anything.