Product designer in Berlin. I learn what AI can and can't do by shipping things with it — each repo here is a finished, working tool, specced and built end to end with Claude Code.
The pattern is the same every time: write the spec first (PRODUCT.md, DESIGN.md), decide
where the model is allowed to be creative and where it absolutely isn't, then build. The
interesting output usually isn't the app — it's where the constraint had to go.
Case studies
| pour-pierre-case-study | A cocktail book built as a gift — design system, guardrails and suggestion engine |
| html-to-figma | Websites and HTML into editable Figma Auto Layout frames, styles and variables |
| onboard-board-game-teacher | Teaches a board game you own — built so the model never invents a rule |
| onboard-design-system | Tokens, components and a UI kit, packaged for a design agent to consume |
| talk-local-tts | Offline text-to-speech on macOS — no account, no key, no network |
| browser-speech-toolkit | Whisper and Kokoro in the browser; your audio never leaves the tab |
| klasse-live-subtitles | Live German → English subtitles, running entirely on your own machine |
| mallorca-trip-planner | Map-based travel planner for a phone held one-handed, with no signal |
| otto-walkies | A single-file iPhone web app, no build step and no dependencies, built for a dog |
| dedupe-ui | Duplicate file finder where every destructive default is the safe one |
Four of these exist because something needed to stay on my own machine — a transcript, a translation, a voice, a recipe. That constraint turned out to be a design brief, not a limitation.
Everything here is published for review, not for reuse.