Lint Roller

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

Your pointer is the roller.Drag across to roll.

The one idea

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 nine thousand developers now use it. Her logo took an afternoon. She was about to charge teams for it, and it looked like every other developer tool: a dark page, a purple gradient, a hexagon and 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 Lint Roller page: a dark page with a purple gradient, a hexagon logo, a rocket emoji and the headline Supercharge your workflow.
Mags’s own page, before.

Built in a weekend. It worked, nine thousand 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 mark

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.

The Lint Roller mark and its one rule: the name in a clean band across a field of fuzz, the band 1.3 times the size of the type and the name starting half the type size in. Below it, the mark on a sheet, on the red handle, as a bare stripe and at 128, 64 and 32 pixels.

The type

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.

Recursive set five times in a column, from loose and slanted at the top to upright and exact at the bottom, each with its settings beside it, and under them the line: the talking face and the code face are the same family.

It’s just covered in fuzz.

The color

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.

Three used sheets on navy, each covered in the tokens it picked up, 80, 80 and 54 things, and under them the line: 214 things. 3 sheets.
The terminal output: the command, five files with what was found in each, and the last line, 214 things in 38 files, 1.8 seconds, 3 sheets used. Nothing is decorated.

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.

The new docs site: a navy banner of fuzz with the name, a side menu, and the page What it picks up, with a list of what the tool removes and a row of the eight care symbols at its foot.
A refill’s page in the docs: Refill 2.4 in large type, the three release notes, the install line and the row of eight care symbols at its foot.
The docs on a phone: the navy banner of fuzz with the name, the page What it picks up, and the row of eight care symbols at its foot.
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.

We proposed. Mags decided.

At one end of the line, a tool that looks like every other tool. At the other, a lint roller on the desk.

  1. We proposed

    The laundry shelf everywhere, the terminal output included: rolled headings, a sheet counter, a little fuzz on every line.

  2. Mags argued

    “Nothing cute inside the terminal. I read that output forty times a day.”

  3. Mags decided

    The brand lives around the tool. The tool stays quiet. We kept the one thing she liked from our pitch inside it: the last line says how many sheets it used.

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 letterStoop