Lint Roller

A tool that tidies AI-written code. Developer tools, 2026.

Your pointer is the roller.Drag across to roll.

One job.

Picks up what the AI shed.

Mags Olsen is a staff engineer in Minneapolis. She built Lint Roller on weekends to clean up after her own AI assistant, and 9,000 developers now use it. She was about to start charging teams, and the logo was an afternoon’s work: a dark page, a purple gradient, a hexagon, a rocket. She described the problem the same way every time: “It’s not broken. It’s just covered in fuzz.”

Client
Lint Roller: Mags Olsen, Minneapolis
Brief
Look like something a team will pay for, and still like something Mags made
We made
The mark, the pack, the used-sheet report, the docs, refill packs for release notes, stickers, a shirt and a real roller
Time
Nine weeks
Mags’s own page, before.

Built in a weekend. It worked, 9,000 people used it, and it looked like this.

A lint roller at the end of a clean stripe down the sleeve of a navy sweater, the rest of the sleeve covered in pale fuzz.
One pass, then peel.

The clean stripe.

The surface is covered in fuzz and the name sits in the one band a roller has just left. The clear space is the logo.

1.3× type height

The clean stripe: nothing sticks inside it. Ever.

0.5× inset

Where the name starts from the leading edge.

Real code specks

Recursive Mono, casual, slanted (-12°), 6% of type size and up.

On a peeled sheet
On the handle: the name alone
128 px
64 px
32 px
Smallest: just the stripe

Loose, then tidy.

Recursive, one family that runs from loose and slanted to upright and exact. Headlines arrive loose and are rolled tidy. The code face and the talking face are the same family.

Lint Roller / Recursive, one family from loose to exact

casual 0.00 · slant 0° · rolled tidy
Loose (CASL 1 · slnt -15°)Rolled tidy (CASL 0 · slnt 0°)

It’s not broken.

It’s not broken.

casual 1.00 · slant -15° · arrives

It’s not broken.

casual 0.75 · slant -11°

It’s not broken.

casual 0.50 · slant -7°

It’s not broken.

casual 0.25 · slant -3°

It’s not broken.

casual 0.00 · slant 0° · rolled tidy

The talking face and the code face are the same family, so the brand and the terminal never disagree.

$ lint-roller ./src --peel

It’s just covered in fuzz.

Navy, white, one red.

Sweater navy, because that is where lint shows. Sheet white. One handle red.

The Lint Roller at rest on the navy sweater: a white paper roll on a straight red handle, with the name in white along the handle.
  • Sweater navy#1B2947
  • Sheet white#F4F2EC
  • Handle red#E0382B
The roller at rest: sweater navy, sheet white, one handle red.
A lint roller with a red handle resting at the end of its clean stripe on a fuzzy navy sweater.
One pass.
The Lint Roller pack and three refill packs on a laundry shelf, among detergent and folded towels.

Sold from the laundry shelf.

A pack, and a refill for every release. The release notes are on the front.

Care instructions for code.

Eight symbols in one stroke, borrowed from the label inside a sweater. They are on the back of every pack and at the foot of every page of the docs.

  • Run on every commit.
  • Do not run on generated files.
  • Never bleaches. It takes only what nobody will miss.
  • Dry run first. Nothing changes until you say.
  • Then peel to apply.
  • Does not iron. Your formatting is your own.
  • Look over the sheets by hand.
  • Hang up old TODOs: ninety days, then they go.
A used sheet lying on navy wool, covered in the tokens it picked up: semicolons, TODOs, any, console.log.

The fuzz is real.

Every speck is a real line the tool took out: a stray semicolon, a TODO, an any, a console.log. After each run the report is a used sheet, and you can read what stuck to it.

Lint Roller / the report is a used sheet

214 things.
3 sheets.

Every speck on a sheet is a real line the tool took out. The bottom edge says which folder it rolled.

zsh — lint-roller

$ lint-roller ./src

src/billing/invoice.ts12 unused imports, 3 dead helpers
src/billing/tax.ts4 old TODOs, 1 console.log
src/auth/session.ts9 any, 2 @ts-ignore
src/auth/tokens.ts6 unused imports
src/legacy/report.js31 lines of dead code

… 33 more files, 146 things

214 things in 38 files. 1.8s. 3 sheets used.

Nothing was changed. Run again with --peel to apply.

Inside the terminal, nothing cute.

“I read that output forty times a day.”

Mags Olsen, who built Lint Roller on weekends.

Around the tool.

The docs, the stickers, the shirt.

What it picks up

Only things nobody will miss. If a line does something, it stays.

unused imports
import { x } from "./y" where x is never read
dead helpers
functions nothing calls, in files nothing imports
old TODOs
older than 90 days, with no name on them
notes to self
console.log, debugger, // fix later
Six round stickers: the mark on navy, 60 sheets on red, It’s not broken. It’s just covered in fuzz, a stripe of fuzz, Rolled before review, and --peel.
A folded navy T-shirt printed with the Lint Roller mark: the name in a clean band across a field of tiny code fuzz.
The shirt. Navy, because that is where lint shows.
A hallway by a front door: a navy sweater on a hook, a bag, keys, and a lint roller with a red handle on a bench.
You run it before you leave the house.

Everything, on one sweater.

Everything laid out square on the navy sweater: the pack, the three refill packs and the roller.

Fuzz in the terminal was our idea. Mags said no.

Zero on this line is one more dev tool with a purple gradient. A hundred is an actual lint roller on the desk.

Mags chose 52. The brand lives around the tool, and the tool stays quiet but for one last line: how many sheets it used.

We proposed 74. The laundry shelf everywhere, down to a little fuzz on every line of the terminal output.

Teams started paying in the first month. The roller on the desk became how people recommend it.

Set in Recursive, an open typeface. Every speck is real.

Next letter

Roll the rest, if you like.Drag across to roll.