Small tools for
stubborn problems.

I'm one developer in Jacksonville, FL. Half of what I build is open-source tooling for AI coding agents, the kind that makes them check risky work before calling it done and spend fewer tokens along the way. The other half is websites for local businesses that want the phone to ring.

Built because
I needed them.

Every one of these started as a problem I hit on real projects one time too many. Start with Bearpaws. It's free, like everything else here.

01

Bearpaws

Careful where it counts, quick everywhere else

Skills that judge each change by what could go wrong. Logins, payments and data deletes get tests and an independent review. Everyday edits skip all that.

See all 6 projects

Rules I
build by.

  1. Spend tokens on the code that matters.

    An agent needs your signatures and types. It doesn't need every line of boilerplate, so strip that out before it reaches the context window.

  2. Use what's already on the machine.

    A local binary or a short hook script usually does the job, and nobody has to sign up for another subscription.

  3. Show the work.

    If a tool changed something, you should be able to read what it did. That's why these leave plain logs and receipts behind.

Same care,
on a client's site.

When I'm not writing tools, I'm building websites for local businesses that need more calls and quote requests. This is the latest.

Precision Wraps Jax homepage section with a 3D food truck wrapped in the shop's black and red branding
Precision Wraps Jax on a phone, with the sticky call and quote bar

Precision Wraps Jax

Precision Wraps Jax is a vehicle-wrap shop in Jacksonville, and it needed a website that turns local searches into quote requests and phone calls. I designed and built it, and I still run it.

  • 14 service pages
  • Location pages
  • Quote-first layout
  • 3D wrap truck
Quote requests since launch
46
Average Google position
20 → 10
Organic traffic increase*
+247%
Visits from LLMs*
35

*Since the quote form launched in June 2026; traffic compares Jun–Sep with Feb–May.

Work with me.

There's no account manager. The person who answers your first email is the one who writes the code and launches it. Pick the option that fits and send a few lines about the problem, or read how a project runs first.

Websites that bring in calls.

For a local business whose site isn't bringing in work. I build around local search and the quote form, and I keep running it after launch.

  • Custom design and build
  • Service and location pages for local search
  • Quote forms and call buttons where customers look
  • Hosting, updates, and fixes after launch

See it live: Precision Wraps Jax

Email about a website

Coding agents that follow a process.

If your team already uses Claude Code or a similar agent, I'll set it up to plan and test before it calls anything done. It should burn fewer tokens getting there, too.

  • Bearpaws skills set up for your repo and stack
  • Context and token cost tuning with cubtoken
  • Hooks, review gates, and verification steps
  • A walkthrough so your team can maintain it

The tools behind it: Bearpaws and cubtoken

Email about agent setup