Why I'm building PerfectPolaris

I started writing PerfectPolaris the weekend after a project review where I’d spent the previous Friday running the same naming audit by hand for the third time that month. Different folders, same Python in a different shape, same set of issues. By the third pass it was hard to argue that the audit was the problem. The problem was that I kept writing the audit instead of getting on with the work the audit was supporting.

So I built a thing that ran the audit, and then ran the next audit, and then ran a quick fix on the things the audit had found. It wasn’t impressive. It was 200 lines of Python and a chat panel that called my Anthropic key. But it cut a Friday into 20 minutes, and the next time I needed a one-off tool I asked the panel to write it instead of opening PyCharm.

That’s the whole pitch. There’s nothing on this site that I haven’t personally needed at three in the morning during a build.

What I keep noticing

Every team I’ve worked on — at studios from indie to AAA — has the same shape of waste. It looks like this:

• A tech artist writes a script that does X. It gets used six times, then forgotten, then re-written by someone else two months later.
• A producer asks for a report. The report takes a day to assemble. Next quarter, the report is asked for again. It takes a day, again.
• A naming convention gets agreed in a meeting. It’s enforced manually by whoever opens the file last. Drift sets in by week two.
• A material gets parameter-bombed in a hurry. Six months later, nobody knows which parameters matter and which were left over from a debugging session.

The common thread is that the fix to each of these is a script. The script never gets written, or it gets written and lost. PerfectPolaris is the place those scripts live, and the place they get written when you need them.

What this is not

It’s not a chat panel that hands you snippets to paste somewhere else. There are plenty of those, and they’re useful in their place, but they leave the actual work — running, checking, committing — to you. PerfectPolaris runs the work, shows you the diff, and waits for your sign-off.

It’s not a black box. The Python it generates is plain Python. You can read it, modify it, save it as a project tool, share it with the team. The AI part is a fast way to write the script you would have written yourself. The script is what does the work.

It’s not a replacement for skill. It runs your audits, against your conventions, with your approvals. The taste — what’s worth fixing, what’s worth leaving alone, what’s worth shipping — stays with you.

What’s next

I’m running early access at £1.99 a month for individuals and £4.99 a month for teams of up to five. Those prices stay locked in for as long as you keep the subscription active, regardless of where the price goes when it leaves early access. I’d rather have ten thousand developers using it cheaply than a hundred using it grudgingly.

If you want to follow along while it grows, this devlog is where the working notes go. Next post: what 50 levels’ worth of lighting audits looked like, and what they taught me.