Skip to content
← toolbox Get in touch

Austin Pranger · skills and work

I build useful software with AI, from the first idea to a tool people actually use.

Developer, builder and project lead. I design, build, test and ship small, sturdy tools and sites, working side by side with AI agents, and I keep the whole thing organised enough that anyone can pick it up.

  • AI developer
  • Forward-deployed engineer
  • Project lead
  • Builder
  • Tech wizard
See the work Get in touch Open to projects, contracts and team roles.
50tools, sites and extensions built
24at beta or stable, in real use
5Chrome extensions
152commits in the toolbox repository
13weeks of steady building

Numbers are counted from the toolbox repository each time this page is built, not typed in.

01

Where I am strongest

What you can rely on me for.

01

Ships working software

Idea to something running, used and fixed. Dozens of tools, extensions and sites built and put in front of real use, several of them daily drivers.

02

Directs AI agents well

Briefs, constraints and checks that keep agents useful: written rules, task lists and decision logs so the work stays on course and anyone can take over.

03

Careful with people's data

Local-first by default, honest about what is saved, backups and restore built in, and automated checks that stop a change from breaking something people rely on.

04

Turns mess into a system

Takes a pile of ideas, notes and half-finished work and gives it a structure: clear status, next steps and a place for every decision.

02

Skills, and how deep they go

Levels are by evidence, not by feeling. Tap a level to filter.

  • Daily Used most days, in work that ships.
  • Shipped Used in something real and finished.
  • Working Can build with it, with the docs open.
  • Exploring Learning it now, and saying so.

AI and agents

  • Agentic development (Claude Code)Daily
  • Prompting and briefingDaily
  • Claude APIWorking
  • MCP connectorsShipped
  • AI agents with their own repoShipped
  • Local and cloud speech modelsExploring

Web and front end

  • HTML, CSS and JavaScript (no build step)Daily
  • Responsive, phone-first designDaily
  • Accessibility basics (keyboard, reduced motion, themes)Shipped
  • Canvas, SVG and animationShipped
  • Next.jsWorking
  • 3D in the browserExploring

Extensions and apps

  • Chrome extensions (Manifest V3)Shipped
  • Installable web apps (PWA, offline)Shipped
  • Browser storage (IndexedDB, localStorage)Daily
  • Import, export and backup designShipped
  • Android app packagingExploring

Back end and data

  • Node.js scripting and build toolingDaily
  • Serverless functionsWorking
  • Postgres (Neon)Working
  • Accounts and auth designExploring

Quality and delivery

  • Git and GitHubDaily
  • Deploying on VercelDaily
  • Automated tests (Node, Playwright)Shipped
  • Guardrail checks before every changeShipped
  • Licence and third-party recordsShipped

Project and product

  • Planning and breaking work downDaily
  • Specs, briefs and decision logsDaily
  • Client sites and handoffShipped
  • Research and documentationDaily
  • Video and showcase productionWorking
03

The tools I build with

My working stack, and how I actually use each part.

  • Claude Code

    My main builder: I direct it with written rules and task lists, and review what it produces.

    Daily
  • GitHub

    The home of everything, and the database for the toolbox itself.

    Daily
  • Vercel

    Automatic deploys for the toolbox and several standalone sites.

    Daily
  • Node.js

    Build scripts, checks and tests, with no framework in the way.

    Daily
  • Playwright

    Real-browser tests, including loading a real Chrome extension.

    Shipped
  • Neon (Postgres)

    Database for the tools that need accounts and shared data.

    Working
  • Next.js

    Full web apps with a login and a private database.

    Working
  • Chrome Extension APIs

    Tab saving, page changes, reading aloud and more, in Manifest V3.

    Shipped
04

What I build

Selected projects, with their honest status.

  • AI-assisted tools
  • Chrome extensions
  • Offline-first web apps
  • Client websites
  • Dashboards and planners
  • Explainers and visualisation
  • Research and content systems
  • AI agents
AI companion appin use

HiJinx

A planning and accountability companion for one person's day: a calendar, a short list of what matters now, and two Claude-powered guides, Ivy and Jinx. Used daily by its builder.

  • Next.js
  • Postgres
  • MCP
  • PWA
Browser toolsin use

Chrome extensions

A small family of extensions: DustyTab saves and rates tabs, Murmur reads highlighted text aloud, MeTube quiets YouTube, and Reframe splits claude.ai into conversation and message box.

  • Manifest V3
  • JavaScript
  • Playwright
See it
Writing appin use

Writer

A distraction-free writing surface with live formatting: just text and a cursor. Developed in its own repository.

  • JavaScript
  • Single-file app
Research notebooklive

Commonplace

A public research notebook with its own protocol for how topics are researched, sourced and kept honest. The biggest topic is AI.

  • Static site
  • Markdown
  • JSON feeds
See it
Browser toolin use

Render Desk

Renders showcase videos on your own computer instead of in the cloud: pick what is queued, press Render, get a zip to commit back.

  • WebCodecs
  • Canvas
  • JavaScript
See it
Content systemin progress

Content Index

Everything published online in one searchable, filterable list, with a podcast page and an import format for adding entries in bulk.

  • Postgres
  • JavaScript
  • Import pipeline
See it
AI agentin progress

Mira

A semi-autonomous, openly-AI agent with her own repository, site, blog and public roadmap, who studies the work and builds a paper trail around it.

  • Agents
  • Next.js
  • Git
See it
Capture and planningin progress

Loopy and Loom

Loom captures an idea from any device; Loopy shows every open loop. Linked between phone and PC with live updates, and a first project with an outside database.

  • Realtime sync
  • Web app
See it
Explainersin progress

Lens

A gallery of explainer animations, simulations and 3D models for ideas that are hard to put into words, built so every piece can be embedded on any site.

  • Canvas
  • Simulation
  • Embeds
Websitesdelivered

Client websites

Sites built for other people, such as Memento Magicka for Holly Hamel, designed with them and handed over to run on their own.

  • HTML and CSS
  • Design
  • Handoff
Planning toolin use

Renaissance Faire Tracker

Themed weekends, prices, overlaps, drive times and a map across a nationwide directory of faires, LARPs and immersive events.

  • JavaScript
  • Maps
  • Filters
See it

Also in the workshop

  • Experience•ographyCommunity platform
  • LatticeDashboard
  • ArtiAI service
05

How I think and work

The skills that sit underneath all the others.

Organisation

The repository is the proof.

Every project here keeps the same small set of files: rules for whoever works on it, a live task list with a clear next step, and a log of decisions with the open questions marked for me. A person or an AI agent can open any of them cold and carry on where the last one stopped. That habit is what lets me run dozens of projects without losing the thread.

Ideation

Lots of ideas, honestly sorted.

I try ideas quickly, as mock-ups and prototypes, and then sort them without sentiment: what is real, what is an experiment, what is on hold. The toolbox shows that sorting in public, with status labels that say what is finished and what is not.

Working with AI

Direction, not just prompts.

I treat AI agents as capable colleagues who need a good brief. I write the rules they work under, give them tests and checks to prove their work, review what they produce, and keep a record of what was decided. I know where they are strong, where they need watching, and when to do it by hand.

Judgment and care

Protect what people rely on.

I build the safety nets before they are needed: backup and restore, checks that fail loudly if a change would break a bookmark or lose data, plain-words records of licences, and labels that never oversell what a tool can do.

  1. 1Idea

    Capture it fast, decide if it is worth building.

  2. 2Brief

    Write down the goal, the rules and what done looks like.

  3. 3Build

    Work with agents in small, checkable steps.

  4. 4Prove

    Tests and guardrail checks before anything ships.

  5. 5Ship

    Deploy, use it, and be honest about its status.

  6. 6Learn

    Write down what worked so the next one starts ahead.

06

What I am, and what I am not

Plain about where I am strong and where I am still growing.

How I build

  • I direct AI agents to write most of the code, and I am accountable for the result.
  • I am strongest at turning an idea into a finished, tested, well-documented tool.
  • I am newer to large-scale systems, deep back-end work and team-scale code review.

Still learning

  • Accounts and auth design
  • Android app packaging
  • 3D in the browser
  • Working inside a larger engineering team

Let's build something

Have a project, a problem, or a team that could use someone who ships? Send a short note about what you need and when.

Email me iam.austinpranger@gmail.com