"Full-stack" gets read as half front-end, half back-end. For me it just means I can never sit still on one layer. I want to build something from scratch and watch it go from a blank screen to something that actually runs, database, API, UI, and deployment included. Preferably with a different stack every time, because apparently I can't use the same tools twice without getting bored.

Artui
For my bachelor's thesis I built Artui, a React component library built around developer experience and accessibility. Instead of running a WCAG audit after the fact that nobody reads anyway, Artui surfaces accessibility violations right away, either as TypeScript compile-time errors or as runtime warnings, depending on how strict you want to be. It grew a shadcn-style CLI on top, so you copy components straight into your project instead of installing a package, plus an MCP server that exposes component metadata to AI coding assistants. That way a tool like Claude actually knows a component's props and accessibility rules before it suggests any code.

Odyfeed
Odyfeed is my small obsession with Solid Pods, linked data, and ActivityPub. The idea: rewrite the Odyssey as a Twitter-style feed, where every character gets their own Solid Pod and posts get pushed around through ActivityPub, the same way the actual fediverse works. Odysseus posting from Troy, Penelope replying, Poseidon throwing in a jab somewhere along the way. Mostly for fun, but also a good excuse to play with decentralized protocols without it feeling like another dry class project.