Halaska OS

The design system and toolkit I leave behind, so your team and its AI tools keep shipping on brand after I step back.

The problem it solves

Your team already builds with AI. Out of the box, the tools make up their own buttons, colours and patterns, and everything they touch drifts off brand. More prompting doesn't fix that. Writing the decisions down where agents can read them does.

What it is

The operating system for your product's design: the rules, components, principles and past decisions, kept as plain files that both people and AI tools read. I bring a base system with 20+ years of design judgement built in, then we layer your brand on top: your taste, your voice, the decisions that make you different.

What's inside

• Your design system in code: colours, type, spacing and components, each with clear usage rules.
• Your principles and decisions in plain words: what you chose, what you rejected, and why.
• Prompts, skills and workflows for the tools you already use, like Claude and Cursor.
• Checks that keep agent output on standard, so speed never costs you quality.

How it works

It builds up as a side effect of the work, not as a separate project. Every flow we design and every component we code gets its decisions written back into the system, so it ends the engagement knowing your brand, your components and your standards. Every launch makes it smarter.

What you keep

The whole thing. Everyone on your team, and every AI tool they use, produces work that looks and reads like your best designer made it. Take it and run with it, or keep me on to look after it. This site is built from the same kind of files, which is the point.