I direct AI agents to build real software. Then I publish exactly how.
I'm Adonias Micael, a product designer. Every build ships live, with its receipts. The recipe behind it costs one email.
Open the live demo: Live at keel-workspace.vercel.app
How it was made
- Model
- Claude Opus 5.5
- Build subagents
- 6
- Orchestrator
- 1
- Mobbin searches
- 57
- Design skills
- 11
- Agent time
- ≈ 4 h
- Reviews from me
- 1
7 h after the X postSep 24–25, 2026
- Views
- 25.5K
- Bookmarks
- 598
- Demo visitors
- 433
Keel's Today screen. Every company, person and number in it is fictional.
Keel, start to finish.
A revenue workspace where a sales team works alongside five AI agents. One brief at 06:00; live the same evening.
- 06:00
One brief goes in
The product, a fictional world whose numbers must agree, and the bar it had to beat.
- 06:05
The foundation agent
Design system, app shell, the whole dataset and the Today page. Done by 07:05.
- 07:10
Two agents in parallel
Records built the accounts table and record pages. Work & Crew built the delegation board and the agents.
- 08:00
One round of fixes
The orchestrating agent reviewed every page from screenshots and sent each agent its list.
- 08:05
First version done
Build and lint clean. Nothing posted yet.
- Afternoon
My one review
I looked at the first version and chose to build the two stub pages, People and Deals.
- 16:45
Three more agents
People, Deals, and a chart-and-color pass that gave every chart color one job. Done at 18:25.
- Evening
Live, then posted
Exported as a static site, deployed, and posted on X with the live link.
Left alone, an agent gives the average answer.
A page is a few hundred small decisions. Every one I leave open, the model makes for me, and it picks the most likely answer. So I give it better sources, not longer prompts.
Inputs
What I give it: a brief, the real words, a direction.
In Keel: One brief: the product, a fictional world, the bar to beat.
Sources
What it looks at: real products, not its own memory.
In Keel: 57 Mobbin searches, each logged with the app it came from.
Rules
What it follows: skills, written rules it loads when the task matches.
In Keel: 11 design skills, credited to their authors on the build page.
Get the recipe behind Keel.
The Build File is everything behind the build, ready to copy. The product stays open; the recipe costs one email.
The Keel Build File
Free. Copy any part of it, or download the whole file.
- The brief
- The single prompt that started it, word for word.
- The crew
- Six agents: what each owned, in what order, and the prompt they started from.
- The rules
- The foundation doc every agent read before building a page.
- The skills
- All 11 design skills with install lines, authors, and what each changed.
- The sources
- All 57 Mobbin searches, and what each one brought back.
- The rounds
- What every review caught, and the fix.
- Rebuild it
- The steps from an empty folder, with the screenshot tool the agents used.
Build something you'd put your name on.
An AI agent will write you the software. Making it something you'd run a business on is the work.
I build real projects with agents and publish each one: the brief, the references I hand them, how I check their work, and what the checks caught.
The YouTube channel