Builder Studio

Software that stays calm under real use.

I build practical tools, local-first systems, and AI-assisted products with a bias toward clarity, durability, and low-maintenance architecture.

Currently focused on: local AI workflows, durable product surfaces, and the bridge between software and physical-world making.

Why This Work Holds Up

Static-first by default

Plain HTML, CSS, JS, and small data files keep updates fast and maintenance calm.

Support surfaces are real

Products are backed by public support and privacy pages, not buried in app-store-only copy.

Local where trust matters

Offline-friendly behavior and local-first workflows are built in when reliability is part of the promise.

Selected Work

A curated slice of the studio

View all projects

Carpentry Companion (AU)

Practical Product

Offline-first carpentry study and workflow app with calculators, jobs, references, and published support surfaces.

AIStoryTeller

AI System

A local story workbench for long sessions where world state, voice, and writing stay in one coherent flow.

Hydrate

Utility

A bottle-first hydration tracker built around repeated daily use, local progress, and calm interactions.

Tuxborn Wiki Atlas

Reference System

A documentation and knowledge layer for a large modpack, shaped for fast route-finding and practical troubleshooting.

Publishing + Support Infrastructure

Studio System

A reusable static architecture for product pages, support routes, policy pages, and generated catalogs.

Security Research Website

Security Blog

A practical advisory site focused on scam awareness, risk patterns, and plain-language security notes.

Studio Approach

How I build

  • Clarity first: premium feel comes from hierarchy, rhythm, and fewer competing decisions.
  • Durability over novelty: systems should still be understandable after a long gap or handoff.
  • Local-first where it counts: trust improves when products stay useful with weak or no connection.
  • Small stacks, strong output: lightweight tooling and static publishing are defaults, not fallback modes.
  • Experiment with purpose: new ideas are welcome, but they need a path to shipped usefulness.

Writing + Journal

Field notes and working ideas

I keep quick observations in Notes, active tracks in Lab, and longer writing on the blog.