ProofKit

Browser extension

Type your resume once. Fill every application form with it.

The ProofKit Resume Filler is a small extension with two buttons. Save your builder draft into your browser, then open any application form and fill the matching fields from it. It makes no server calls at all - the draft lives in your browser storage, the fill happens in the tab you are looking at, and nothing is submitted until you submit it yourself.

Works in Chrome, Edge, and Brave. Not on the Chrome Web Store yet - you sideload the zip (two minutes, steps below).

Install

Four steps, no account needed.

1Unzip the download into a folder you will keep - for example Documents\proofkit-filler.

2Open chrome://extensions (or edge://extensions, brave://extensions) and switch on Developer mode.

3Load unpacked and pick the unzipped folder - the one containing manifest.json.

4Pin the icon, open your builder tab, click Save my builder draft, then open an application form and click Fill this form.

What it is

Two buttons, zero phone-home.

01

Save my builder draft

Reads the draft you typed in the builder from that tab’s browser storage and copies it into the extension’s own storage. No account, no network call.

02

Fill this form

Matches the page’s input fields by label, placeholder, name, and autocomplete hints, fills the first match per section, and reports how many it filled. You review and submit.

03

Nothing uploaded

Both steps are pure browser work - read the source: popup.js and fill.js contain no fetch calls at all. Permissions are storage, activeTab, and scripting.

What this is - and isn’t. It fills simple form fields; it does not auto-submit, does not learn your answers, and will not handle complex multi-entry ATS sections perfectly - count on reviewing what it wrote. It is not on the Chrome Web Store yet: sideloading means Chrome will show a “developer mode” notice, and the extension will not auto-update. We would rather ship the source you can read than a listing you cannot.

Chrome Web Store

Publish-ready package, one owner step left.

The extension ships as a proper Manifest V3 package: real PNG icons (16/48/128), a tightened description, a homepage URL and an offline flag. The store listing copy, the single-purpose description and the privacy disclosure are already written and live in the package as store-listing.txt - paste them into the developer dashboard and you are done.

  • Ready: manifest V3, icons, permissions limited to what the filler uses, no remote code, no analytics, no background mining.
  • Ready: listing copy, category, support URL, privacy policy URL (/legal) and the disclosure the store asks for.
  • Owner step (one time, about five minutes): pay the one-time $5 developer registration at the Chrome Web Store console, then upload extension.zip. That needs your Google account and your card - we cannot do it from here.
  • Before upload: rebuild the zip from the extension folder with manifest.json at the ZIP root, and take the store screenshots yourself on a real application form.

Until it is listed, the sideloadable package works exactly the same: load it unpacked or install the zip with developer mode on.

Want the whole product on your desktop?

The extension fills forms. For the builder itself as a desktop app - its own window, a dock icon, offline drafts - see ProofKit on your desktop.

Questions

What people ask about the filler.

Where does my draft go?
Into your browser’s extension storage on your machine. Clearing it (removing the extension or clearing site data for it) deletes it. There is no ProofKit account, no sync, and no server involved.
Why does it ask for all-sites permission?
The fill button has to run on whichever application site you are looking at - Workday, Greenhouse, a plain HTML form - so the scripting permission covers the tab you are on. It only acts when you click the button.
Will it submit applications for me?
No, and that is deliberate. It fills fields, tells you how many it filled, and stops. What you send, where, and when stays under your hand.

One draft. Every form.

Build it once in the builder, carry it in your browser, fill and review on every application.