About

I'm Hans Sep, a product manager at Fiery (print automation software). Outside of work, I've spent years building things the hard way—soldering ESP32 boards, configuring ESPHome, managing npm packages, setting up VNC and KVM for remote access. my.daybuilds.ai is where I share the implementation plans behind quick builds with AI coding assistants. I bring the domain knowledge. Claude writes the code. The real value is the structured thinking that connects the two.

My product philosophy: solve real problems, make it beautiful, make it fast, and lead. Every project here reflects that—whether it's an ESP32 presence sensor, a JobFlow Pro extension, or this very site.

What I Build

My focus areas span hardware (ESP32 sensors, IoT devices), software (Electron apps, JobFlow Pro extensions, MCP servers), and web (TypeScript backends, Astro sites). I care about the intersection of AI-assisted development and product quality—building things that are both functional and polished.

Why Share Plans?

With AI coding assistants, your users don't need your app anymore—they can build it themselves. But they do need good plans. Each project here includes the actual implementation plan I gave Claude, structured so you can copy it and adapt it for your own builds.

The Daybuilds Philosophy

Build time starts when it works for real. When I say a project took one day, I mean the time from first commit to "it's actually working." Continuous improvement code trickles after that don't count—the timer stops when the core functionality is live.

Good enough beats bulletproof. These projects aren't production-hardened enterprise systems, and that's intentional. I use code review skills and security evaluations to meet acceptable criteria—the code works, it's reasonably safe, and it solves the problem. Perfect is the enemy of shipped.

Domain knowledge in, code out. Every project here started with something I already understood—Bluetooth from years of ESP32 tinkering, clipboard behavior from remote access setups, npm workflows from daily use. Claude doesn't come up with the ideas or know what to build. I do. Claude writes the Swift, the Go, the C++ I can't write myself. And along the way I pick up new principles—RSSI signal processing, Kalman filtering, Matter over WiFi—without getting stuck on syntax. That's the real unlock: domain expertise plus AI lets you build in languages you've never learned.

No repo. No code. No comments section. I share plans for an audience of one. If you'd architect it differently—great. The plan is right there. Go build.

Claude Code Skills We Use Most

These builds rely heavily on Claude Code's specialized skills and workflows. Here's what actually shows up across projects:

  • /feature-dev:feature-dev - Guided feature development with codebase understanding and architecture focus. Write requirements, get implementation.
  • Plan mode - Structured implementation planning before touching code. Every project starts here.
  • /bishop - Dependency auditing and security scanning. I built this one—auto-detects package managers, flags vulnerabilities, recommends fixes.
  • /visual-explainer - Generates self-contained HTML visualizations for architecture diagrams, data flows, and technical explanations.
  • /handoff - Session continuity for multi-day builds. Creates detailed handoff plans so the next session picks up exactly where you left off.
  • /web-content - Clean web content extraction for research. Fetches readable markdown from any URL.

The Duration Subdomains

Connect

Find me on LinkedIn where I write about AI, product management, and print technology. Or send me a message directly.