Agentic systems

Halaska OS

Keep the bar high after I step back

The kit your team and your AI tools build from

Your team ships with AI every day. Without a system to work from, every tool invents its own buttons, colours and patterns, and the product slowly drifts. I build Halaska OS alongside your product: the standards, decisions and taste your people and your AI tools work from.

Our foundation of product design rules underneath. Your company’s taste on top. Everything that gets made, by a person or an AI tool, comes from the same source.

The problem

AI tools are fast. They have nothing to work from.

Ask an AI tool for a screen and you get a reasonable screen. Ask five times and you get five different products.

The decisions that make your product yours live in people’s heads, old Figma files and chat threads. An AI tool can’t read any of that, so it falls back on the average of everything it has seen.

Halaska OS gives it something better to read.

What’s inside Halaska OS

Two layers.

The foundation
How good digital products work, written as rules. It’s the same for every company and I keep improving it.

Your layer
Who you are, what you sound like, what you look like, and where you do things differently. It’s written with you, for your company only.

One rule between them
Where the two disagree, your layer wins.

Two layers.

The foundation
How good digital products work, written as rules. It’s the same for every company and we keep improving it.

Your layer
Who you are, what you sound like, what you look like, and where you do things differently. It’s written with you, for your company only.

One rule between them
Where the two disagree, your layer wins.

The foundation

20+ years of product design, written down.

More than 300 rules. Each one has a reason, a wrong example and a right one, so a person can learn from it and an AI tool can follow it.

Usability. The basics every screen is checked against.
Behavioural science. Design changes what people do. I rate the evidence behind each technique and set an ethical line, so your product earns its results honestly.
AI behaviour. What an AI feature should do alone, what it should ask first, and how it shows its reasoning.
Every state of every screen. Loading, empty, failing, offline. The parts AI tools skip.
Interface writing. Every button, error and empty screen, to one standard.
Websites by type. Different rules for a software site, an AI product site and a crypto or fintech site, including the legal limits.
Accessibility and quality. The current standard, a fixed review order and automated checks.

You don’t pay me to work this out again. It’s there on day one.

20+ years of product design, written down.

More than 300 rules. Each one has a reason, a wrong example and a right one, so a person can learn from it and an AI tool can follow it.

Usability. The basics every screen is checked against.
Behavioural science. Design changes what people do. We rate the evidence behind each technique and set an ethical line, so your product earns its results honestly.
AI behaviour. What an AI feature should do alone, what it should ask first, and how it shows its reasoning.
Every state of every screen. Loading, empty, failing, offline. The parts AI tools skip.
Interface writing. Every button, error and empty screen, to one standard.
Websites by type. Different rules for a software site, an AI product site and a crypto or fintech site, including the legal limits.
Accessibility and quality. The current standard, a fixed review order and automated checks.

You don’t pay us to work this out again. It’s there on day one.

Your layer

The foundation makes the work correct. Your layer makes it yours.

Strategy. Who it’s for, why they pick you, and what you won’t build.
Voice and messaging. What you say, how you sound, and what counts as proof.
Art direction. One idea, and the colour, type, motion and imagery that follow from it.
Product priorities. The few things people come to do, and what gets out of the way.
Your exceptions. The places you break my defaults on purpose, with the reason.
Decisions. Every call, who approved it and why.

The foundation makes the work correct. Your layer makes it yours.

Strategy. Who it’s for, why they pick you, and what you won’t build.
Voice and messaging. What you say, how you sound, and what counts as proof.
Art direction. One idea, and the colour, type, motion and imagery that follow from it.
Product priorities. The few things people come to do, and what gets out of the way.
Your exceptions. The places you break our defaults on purpose, with the reason.
Decisions. Every call, who approved it and why.

It works in the tools you already have

Plain files. No new platform to learn and nothing to log into.

Built for AI tools. Claude Code, Cursor, Lovable. The kit tells each tool what to read for the job in front of it, and when to stop and ask.

Readable by people. A new hire can read it on day one.

A kit has to prove that it works

Tested. I give a fresh AI agent a set of tasks with nothing but your kit. It passes only if the output would ship without edits.

Governed. Changes go through approval and land in the decision log. Nobody quietly undoes a call that was made for a good reason.

Versioned. When I improve the foundation, your kit can move to the new version. Your layer stays untouched.

Tested. We give a fresh AI agent a set of tasks with nothing but your kit. It passes only if the output would ship without edits.

Governed. Changes go through approval and land in the decision log. Nobody quietly undoes a call that was made for a good reason.

Versioned. When we improve the foundation, your kit can move to the new version. Your layer stays untouched.

How I build it, alongside the real work

It’s built in three stages, while I design your product, not as a separate project.

Capture. In the first weeks I write down your strategy, voice, brand and product decisions, on top of my foundation of product design rules.

Wire in. I connect it to the tools your team already uses, add the skills and checks that keep output on standard, and prove it on real work: a flow, a page, a launch.

Hand over. Your team works AI-first with it every day. You run it yourselves, or keep me on to maintain it and produce work through it.

We build your kit in sprints. Each sprint produces something real, such as a brand, a website or a product flow, and sharpens the kit behind it.

At the end you run it yourselves, or keep us on to maintain it and produce work through it.