vibe coding · product building · automation · AI
I build tools for problems that annoy me, ideas that sound interesting, and projects that probably started with:
“Could this be done?”
Every project on this profile is vibe-coded. AI is my main implementation tool; I handle the idea, the specification, the architecture, the decisions, the tests, the iterations, and the part where I ask:
“Now fix this without breaking everything else.”
The original scope usually does not survive the first prompt.
Some started with “real quick.” “Real quick” is a product estimate, not a time estimate.
| Project | What it is | Technologies |
|---|---|---|
| Haumea | A multimodal AI workspace for conversations, studying, model comparison, and organized knowledge | Next.js, TypeScript, and Firebase |
| TelegramCloner | Clones and synchronizes Telegram channels, groups, and forums with checkpoints that survive interruptions | Electron, React, Python, and Telethon |
| HaumeaVoice (Tauri · Electron) | Two voice-typing implementations with global shortcuts, transcription, and refinement | Tauri, Rust, Electron, React, TypeScript, and Python |
| HaumeaStudies | Organizes study missions, mock exams, essays, mistakes, and review sessions | Next.js, TypeScript, and Firebase |
| AddictionLog | Tracks caffeine, alcohol, and habits, estimates active load, and shows patterns over time | React, TypeScript, Vite, and Firebase |
| Haumea Physique | Brings workouts, nutrition, measurements, exams, and physical progress into one personal dashboard | Next.js, TypeScript, and Firebase |
Smaller things. Some of them even respected the original scope.
- AI Exporters — exports Claude, Grok, and ChatGPT conversations to JSON or Markdown.
- MutualCheck — compares Following and Followers on X without handing your account to another service.
- InstagramReelsSpeed — adds playback speed controls to Reels through a userscript.
- HaumeaMC — a Minecraft KitPvP and lobby plugin; the smaller projects live in LastDeath, PingCheck, and NoAracnophobia.
- AprendizadoAntigo — my code dig site, from when centering a div was still a boss fight.
I do not claim to master all of them. I claim to have convinced each of them to cooperate at least once.
My goal is to maximize product per token.
So far, I have mostly achieved tokens per product.
The cycle ends when the product is finished — or when the context runs out.
| Metric | Result |
|---|---|
| Short prompts sent | statistically irrelevant |
| Context windows filled | too many |
| “Just one more feature” | has never been just one |
| Models consulted | yes |
| Tokens saved | future goal |
| Projects that started as a test | almost all of them |
You imagine it, I build it. If it works, it was engineering. If it doesn't, the context ran out.