One platform, one login and one Admin for six business simulations, on a design system of its own.
Deployed and live in production.
Project facts
- Role
- Product design and direction. Built with AI coding sessions under my direction.
- Timeline
- September 2026
- Built with
- Figma
- Claude Code
- Storybook
- Stack
- React 18
- React Router 7
- TanStack Query
- zod
- Tailwind CSS 4
- Base UI
- Motion
- Storybook
- MongoDB
One Platform for Six Business Simulations
Stratagem runs business war games. Teams submit decisions each round, and an engine ranks them against each other. The old product was one admin copied four times inside a rail of iframes, with access that had a model but no screen, and a look scattered across 238 colour literals per client. The brief: a big change to the UI and the Admin first, with logic, formulas and inputs untouched. V2 answers with one platform, one Admin and one design system. It is deployed and live in production.
- One sign-in for staff, and a passkey alone for teams.
- Four copied admins and an iframe console, replaced by one Admin with 24 routes.
- Engine numbers never move by accident: replays are the proof.
- Designed by hand in Figma, built with Claude Code, and delivered as Storybook components.



One Admin for Every Simulation
A staff member chooses a simulation from a gallery, sets it up on one page, and hands out passkeys as a copy, a CSV or printed cards. From the simulation's page they start a round, watch each team submit live, and end the round, which computes it. Results come as a chart per winning metric, Excel reports and each team's decisions. Administrators also manage people, give access per application or per simulation until a date, and read an audit log written in words. The look stays light and flat, and covers play only on hover.
- One adapter reads all four modular servers; its contract test passed 105 of 105 steps.
- The front door: a passkey alone, looked up in five applications at once.
- Grants with dates, checked on every request and never deleted.
- Every Admin screen is assembled from the design system's Storybook components.











Banking: Run a Full-Service Bank
Each team runs its own copy of LIFE Bank, a fictional bank with four business units and thirteen products, in one shared market. A round is a fiscal year and holds 79 settings, plus up to 3 of 16 initiatives. Every change saves by itself and recomputes a live projection. Charts sit beside the decisions: a Revenue donut, an Account bar and expected charge-offs on loans. The engine places each team's value on a curve built from all the teams' values, and scores by rank on revenue, risk-adjusted profit and two satisfaction scores. Banking is the first player moved to the design system.
- 13 products, 79 settings a round, 16 initiatives.
- The frame, decisions, charts, statements and round flow are on the design system; some pages are still MUI.
- 405 player unit tests, and a 57-check play-through with none failed.











ET Prime: Run a Financial Group
Each team sits on the board of AABC Group, a fictional group with a commercial bank, an insurer and a private bank. Over three financial years it shapes 17 products in six segments, invests in operations and people, and picks initiatives. Each unit has its own industry's profit and loss model, and the group's statements are built from the three. The engine's rule is that accounting identities always hold, and they are written as named tests. The player is partly on the design system: the frame, the decisions and the charts have moved, while the group page and the statements are still MUI.
- 3 business units, 6 segments, 17 products, 107 input fields.
- Three profit and loss models, eleven cross-selling routes, and identities held by tests.
- Honest status: 53 server suites are quarantined, and the identity tests are not among them.






Product: Run a Consumer-Goods Company
The team leads Lumina, a fictional household-cleaning company with three brands. It starts with one product on sale and opens the rest through research and development. For each product it sets price, promotion, marketing and a share forecast, channel by channel, across Modern, Traditional and Online. The forecast sets production, and a team sells the smaller of what it produced and what was demanded, so over-forecasting leaves unsold stock. Each year closes with full statements, carbon cost included. Product's player is still on MUI: it moves to the design system after Banking and ET Prime.
- 3 brands, 6 products, 3 sales channels, and 78 inputs once everything is unlocked.
- Energy is enforced here: 100 points in round 1 and 110 after.
- "Product" on screen and "FMCG" in the data, so no number moves.






Mall: Run a Mall's Marketing Year
A two-round marketing game. Each team is the new Marketing Manager of a fictional flagship mall, with one fixed annual budget to split between a low season and a peak season. The team picks campaigns, funds four incentives and four channels inside each, and chooses a tenant strategy, all under an energy cap. Six figures come back, from Traffic to tenant satisfaction. In this game teams do not take shoppers from each other: competition is in the scoring, by rank on the six results. Mall's player is still on MUI. In the pictures its in-game brand is replaced with a neutral name.
- 9 campaigns, 9 inputs inside each, and at most 11 live inputs in round 1.
- Budget and energy are both enforced; a refused change flashes the budget bar red.
- Guarded by a byte-for-byte replay of a recorded session; the engine has no unit tests.

A Design System Built From Figma
The design system replaces MUI screen by screen, without breaking the running apps. Its 867 tokens come in three tiers and generate a locked theme: a class that is not a token generates nothing. On top sit 105 components, from buttons and tables to game parts such as the figures bar, the energy pill and decision tiles. The five chart types are drawn by hand, with no chart library, and each can be read by keyboard and by screen reader. 231 Storybook stories carry interaction tests and screenshot baselines. Figma is the spec, and the 39 places where the system departs from it each give a reason.
- 867 tokens, 23 text roles, 105 components, 231 stories and 211 screenshot baselines.
- Lint refuses raw colours, arbitrary values and MUI imports.
- The Admin has no MUI left; Banking and ET Prime are part way; Product and Mall have not started.



The Design, Built as Components
The design was crafted by hand in Figma. AI coding sessions with Claude Code then built it as real components, and the result lives in Storybook: one workbench where every part can be opened, tried in its states and reused. Its 231 stories show the components at work, and 147 of them run an interaction test when they open. An accessibility violation fails a story's test, and components and stories cite the Figma node they were measured from.
The Admin is built entirely from these components, and the Banking and ET Prime players are moving onto them. For a developer, a new screen starts from parts that already exist and already match the design.










Directing AI Sessions in Parallel
The design was crafted by hand in Figma, and the building was done by AI coding sessions. After a discovery session with twelve research agents, three sessions worked in parallel, each in its own worktree and owning its own folders. They coordinated through a log, a requests file and handover notes, and met at written contracts with tests. Hooks enforced my standing rules. I directed, decided, reviewed screens and approved merges. I also overrode: a wholesale player restyle and a dark Admin were both stopped at first look. The record keeps the slips too, such as a demo reset 32 minutes after a public link opened.
- 460 commits from import to last merge, in 5 days and 17 hours.
- Every check during the build was local: CI ran nothing from 24 September 2026.
- The recorded slips and overrides are part of the story, not hidden.

What I Did
Set the brief and three standing rules. Made the five decisions put to me on 24 September 2026; the other 46 of 51 ran on a recommended default. Held Figma as the spec. Reviewed the Admin screen by screen. Supplied a Figma frame for the sign-in page. Played the product and reported what was broken. Approved the merges. Presented it on 29 September 2026.
What the AI Sessions Did
Discovery with twelve research agents, the planning, and the building: the platform, the Admin, the design system, the server fixes and the local demo.
What Is Next
V2 is deployed and live in production. Next comes the rest of the players' move to the design system: ET Prime's group page and statements, then Mall and Product.








