Pixii
All of Pixii’s design on one system, built for the age of AI.
- Client
- Pixii, battery energy storage, Norway
- Through
- Glitch Studios
- Role
- Designed and built the system
- Year
- 2026
- Built with
- Claude and Claude Code, on Radix
The architecture
One foundation holds the brand: colour, typeface, wordmark, rules and voice, and the brand portal holds the pictures. Two surfaces are compiled from the foundation, one for screens and one for decks, with marketing web and datasheets to come. They are built into the component package and the deck pipeline, which lints, renders, refuses and previews, and they land as screens, decks and the portal that people, code and AI all read.
Concepts
Concepts made from the same system: a landing page, a product page, the product family, a phone app and social posts. Colours, type, rules and the product drawings come from the system, and the photos from Pixii’s brand portal.
The work
Pixii’s staff were already making decks and dashboards with AI. The brand lived in guidelines, PDFs and old decks that did not agree, and every person and every AI read them differently. Pixii had as many brands as people using AI.
When everyone designs, a guideline is not enough. So I turned the brand into one system that all of Pixii’s design is made from. Colour, type, layout and voice are decided once, and written so that people, code and AI all read the same thing.
Decks, product screens and AI tools are three places where that one system shows up. Anyone at Pixii can ask Claude for a presentation. The AI decides what to say, the system decides how it looks, and a deck that breaks the brand never comes out. The same system dresses the product screens. Because the brand lives in the system and not in the parts, I could take a proven open-source library (Radix) instead of drawing every button: about fifty parts in days. The colour scales are built on how the eye sees light (OKLCH), so every palette Pixii adds later comes out balanced without hand tuning. And whatever AI tool or developer Pixii uses next starts from the real brand.
One source also means one place to fix: feedback becomes a rule for every deck and screen within a day.
Pixii’s staff now make their own decks and are happy with them. The screen system is delivered, and the team is already building on it.
Before this, Pixii had tried again and again to get on-brand presentations out of AI, and every attempt had failed. At the first review, when the decks came out right:
“It’s a relief to see that it actually is possible to get some control of this monster.”
The system
The elements of the system, drawn from its own tokens: colour, type, status, icons and the wordmark. Every value here is the value the code and the decks use.
A deck, made by the system
Four slides from one short plan, rendered without a hand on them. Every picture came from Pixii’s brand portal: the cover photo, a site photo in a box shaped to it, three packshots matched by product name, and the closer.
The deck and the portal
How a slide gets its pictures. The plan names the products; the renderer looks each one up in the brand portal’s catalogue, takes the transparent packshot, and refuses any picture that is not a catalogue line. Right, the three entries the slide pulled.
Screens
A fleet platform demo built on the same system, in light and dark, with demo data. Every table, chart and control comes from the one package.
The template
The problem to solve for decks: made with AI, they had to keep Pixii’s own PowerPoint template exactly. Left, slides from Pixii’s own deck. Right, the same layouts made by the system, with the right product photo pulled from Pixii’s brand portal.
The portal
The brand portal. Colour, type, the wordmark, the rules and the live components, in one place that people, code and AI all read.