Open to roles · General Trias, PH
// full-stack, ai-assisted, reviewed by hand
I scope the work, AI drafts it, I ship what I'd put my name on.
Full-stack and game developer. I build with Next.js, Node, and Cloudflare, and write game systems in Unity. Katiwala and Bathala Studio are products I built end to end.
Executing: Task in
01 · intake
You describe the problem
A feature, a bug, a rule that changed. I need the actual problem — the solution is mine to design.
02 · scope
We agree on what "done" means
Edge cases, data model, what’s out of bounds. Most rework comes from skipping this, not from bad code.
03 · draft
AI writes the first pass
Boilerplate, the obvious cases, a working draft fast. I stay in the loop the whole time.
+ split_ratio: number | null
+ function splitBill(bill, ratio) {
+ return { unitA: bill*ratio, unitB: bill*(1-ratio) }
+ }04 · ship
I review, then it goes out
Every diff, line by line. If I can’t explain why a line exists, it doesn’t merge.
How I Work
What I hand off, and what I don't.
What AI drafts
- First-pass implementations from a written spec
- Boilerplate and repetitive refactors
- Test scaffolding
- Docs, comments, the obvious 80%
What stays with me
- System design and data modeling
- Auth, security, anything sensitive
- Anything expensive to undo — migrations, payments
- The final read on every single diff
How I scope
Before code, a written spec
What's in, what's out, what "done" looks like — written down first. Vague tasks produce vague code, AI-assisted or not.
How I review
Not "does it run" — "do I understand it"
Architecture, edge cases, anything I can't explain. That's what gets sent back, not accepted.
Featured Work
Selected projects, across web and games.
Showing 8 of 8 projects
Contact
Open to full-stack roles and contract work.
Ask me anything about the process on the Home tab — I mean it. Happy to walk through a real diff.