calmdownoscar

An idea, a few tools, one shared memory — roughly how a concept becomes a final result.

Awaiting Review · App Store

Wedding Concierge

A calm planning companion for couples, guests, and the tiny decisions that somehow become the whole week.

Web Planning
nuptia.wedding
Being Reworked

ClearSpace

A faster, friendlier home for your photos. Sort shots into albums Instagram-style, swipe the junk into the trash, and clear it out in batches.

iOS Photos
In Progress

Architecturally

Sketch-first architectural design. Draw rough strokes on an iPad and get clean floor plans, a live 3D model, and — soon — AI-rendered visuals, all from the same building data.

iOS Design
Open Source · App Store Soon
Unli Rice app icon

Unli Rice

A persistent memory layer for AI agents. Claude, Gemini, Codex, and every other tool you connect read and write into the same notes over MCP, so nothing gets re-explained and no thread is ever really lost.

macOS MCP Memory
Non-administrative iOS Account Idea Gemini Prompt Figma Claude Unli Rice Codex / Antigravity GitHub Vercel Final Result becomes one of the apps above ↑

The diagram above isn't decoration — it's genuinely how everything here, including this website, gets made. Different tools at every step, all pointed at one goal: to bring an idea to life.

One pipeline, every time

Every idea travels the same road: brainstormed into a prompt, specced out, planned, built, pushed to GitHub, and shipped. Tools get swapped as better ones appear, but the road never changes — so no project ever depends on any single tool staying the best.

Each tool has one job

Gemini turns a rough idea into a proper prompt. Claude does the careful thinking — architecture, plans, reviewing the work. Codex and Antigravity write most of the actual code. Nobody does everything; splitting the work this way is what gets things finished.

One shared memory

Unli Rice in the middle of the diagram is what holds it together: persistent memory — what's decided, what's next, where I left off. Every tool reads it before starting and updates it when done, so I never re-explain anything, and switching tools mid-task costs nothing.

Built between naps

All of this runs on borrowed time — the gaps between changing diapers and Oscar's naps. That's exactly why the pipeline exists: I can put work down mid-thought, and days later any tool can pick up the thread right where it was left. The goal from here is to hand off more and steer less — walk away, come back to see it finished.