Capabilities
How I build reliable product tools.
A practical skill map for systems that need clear state, trustworthy signals, and enough technical depth to hold up in real use.
What I build
Areas of focus
Product engineering for messy systems
End-to-end product work where interface, logic, data shape, and real behavior need to evolve together.
- Scattered inputs into usable workflows
- Product iteration from actual use
- Clear boundaries around what the tool can and cannot know
Calm interfaces for dense information
Interfaces that make complex systems easier to scan without flattening away important context.
- Signal-first hierarchy
- Visible state and source confidence
- Progressive disclosure without hiding the next move
- Mobile surfaces that preserve the core job
Local-first and browser-native systems
Applications that keep important work close to the user when a server dependency would add friction or fragility.
- Browser-native compute and WASM when useful
- IndexedDB and local persistence
- Recovery paths for runtime uncertainty
- Offline-friendly workflow design
Operational tooling
Tools for managers and teams where continuity, speed, and clarity matter more than novelty.
- Scheduling and review systems
- Operational memory and handoff flows
- Audit trails and source-of-truth surfaces
- Reporting workflows that respect the real job
Tools
Stack
Primary
- Next.js
- React
- TypeScript
- Tailwind CSS
- IndexedDB / Dexie
- Stockfish / WASM engine integration
- Recharts / data visualization
Also used
- Firebase / Firestore
- Google Apps Script
- Microsoft Excel
- Photoshop
Best fit
Teams shipping complex tools where product judgment and implementation detail have to move together.