Module 03 / Lesson 01
Design a status interface with UI UX Pro Max and tweakcn
Move beyond generic "AI slop" by enforcing real design tokens, accessible motion, and surgical component targeting.
A stressed user opens your status page on a mobile phone under bright sunlight to see if their service is down. If the AI generated low-contrast grey text, erratic animations, and overlapping badges, the user cannot find the answer. When you tell the AI "make the badge look better", it often rewires the wrong component and breaks the entire screen.
Read the narration transcript
The status is the first thing people need
A customer opens the status page to ask one question. Is Event Delivery down? The draft makes them scroll past a big gradient, a line of marketing copy, and three cards before they find the answer.
I bring the service name, visible severity, and latest update to the top. The customer should understand the state even if two colors look the same to them.
Use UI UX Pro Max to explore directions
UI UX Pro Max can suggest a design direction when you describe who uses the app and what they need to see. I use its current command-line package and choose offline mode for a local copy.
The brief asks for a quiet operations dashboard with legible numbers and no competing decoration. I choose the recommendations that serve this page and keep them in Design dot M D. Now the whole team can see what we picked.
Export tokens with tweakcn
In tweak C N I tune the theme and export CSS variables. These are named values the app can reuse. Operational needs a readable label and a distinct icon.
Degraded gets its own status token. I set that in the stylesheet and reuse it in the service card and incident view.
I check the outage label on both backgrounds. The app also uses aligned digits for uptime and timestamps, so the values are easy to compare.
Review the designed page at real sizes
Open the phone layout with a long service name and three different states. Is the affected service still obvious right away?
Check text contrast in both themes. Look for stray inline colors that defeat the shared rules. Next we’ll make the corresponding operator form respond clearly when it opens and closes.
The everyday problem
I open the status app during an incident. I need to know which service is affected and what changed since my last visit. The generated page puts a giant heading and three decorative cards above the status list. The list uses slightly different text for the same severity, and the outage row looks almost identical to an ordinary warning. It looks like a designed page until you need it for the job.
Start by sketching the operator’s and visitor’s first questions. Which services are affected? How severe is the problem? When did the team last update it? These are design requirements. Give those answers priority over decorative choices.
Why the agent got it wrong
A request for a “modern UI” leaves visual decisions open. An agent can easily invent a separate color, border radius, and font size for every component. The inconsistent treatment means people have to learn the interface again on every screen. One status displayed three ways is especially confusing when you only have seconds to scan it.
The best way to stabilize those decisions is to name their meaning. A token is a named value, such as a text color for a warning. Apply one status vocabulary with labels and icons. Then a layout change can move a badge without introducing a fourth representation of an incident.
The tool and technique
Use UI UX Pro Max to get a few directions by describing the app’s users and tasks. Try “service status operations dashboard with a public outage list.” A busy operations page needs calmer hierarchy than a marketing page. Choose a legible type scale and keep the status color for status, where it conveys information. Drop any suggestion that pulls attention away from Event Delivery.
Use an editor like tweakcn to explore a theme for shadcn components, or edit the project CSS variables directly. Theme values are an input to the design. Write the actual rules in DESIGN.md: keep the service name and state easy to scan, show a typed status label and icon, and use tabular digits for numbers that people compare.
Tabular digits keep numbers the same width, so times and percentages stay aligned as they change. For buttons, match the action with the outcome. “Publish incident update” tells an operator much more about what happens than “Submit.” Keep labels visible while the form is being filled in.
Use UI UX Pro Max for direction and tweakcn for tokens
Start from the public operations page: one affected service, one clear status, and the latest update. Ask UI UX Pro Max for a design-system draft, then decide which ideas fit the people using this page. Export CSS variables from tweakcn into src/app/globals.css and write the chosen rules in DESIGN.md. The next agent needs the decision and its reason.
# Example project setup after source review npx ui-ux-pro-max-cli init --ai codex --offline # Design-system search with the skill’s installed script python .agents/skills/ui-ux-pro-max/scripts/search.py "service status operations dashboard" --design-system -f markdown # DESIGN.md Use the status token for each known service state. Pair the icon with a visible label: Operational, Degraded, or Outage. Set tabular-nums on uptime percentages and incident timestamps. Label the operator action “Publish incident update”.
Check the same state on the public list and detail page in both themes. Inspect the label and contrast at phone width. Search component code for one-off colors that bypass status tokens.
On screen in the status app
Compare the illustrative fragments below. The first hard-codes a color and relies on its appearance. The second maps a known service state to a semantic token, visible label, and icon, while leaving the actual color values in src/app/globals.css. The status app’s default status is much easier to scan if operational, degraded, and major outage use consistent names everywhere.
Before accepting the exported theme, open the real service list in the app. Add a long service name and two incidents with nearly identical timestamps. Confirm the title remains readable and the timestamps line up. Try the theme on a second screen that uses the same states, so you discover whether the tokens still carry their intended meaning.
src/components/service-status.tsx
Before
<span className="bg-purple-600 text-white">{service.state}</span>After
<span className={statusStyles[service.state]}>
<StatusIcon state={service.state} aria-hidden="true" />
{statusLabel[service.state]}
</span>
<time className="tabular-nums" dateTime={updatedAt}>{updateLabel}</time>What to watch for
A generated theme can look right on the theme website and give poor contrast in your application. Actual colors depend on the surface, theme, and state. Check both light and dark modes if your app offers them. Avoid conveying severity through color alone. Text and icons still communicate when a user can’t readily distinguish two colors.
Keep the first implementation small. Export values you can review, check them into the project’s styles, and remove unrelated changes. An agent can find your conventions faster when the status mapping is in one place. You can still override the theme when a different surface requires it, with a clear reason.
How you know it worked
Open the actual status page and read three statuses without relying on color. Check text contrast against each background, resize until the longest service name wraps, and confirm that names still associate with their badges. Repeat on the log view or a recent incident. Compare timestamps and uptime values before and after the theme change.
Review the diff for hard-coded status colors that compete with the project tokens. Save one narrow and one wide view as evidence. The next lesson takes the same visual hierarchy into a keyboard-accessible form, so the better look also survives a real interaction.
Do one extra pass over a screenshot in grayscale. The severity label and icon should still tell you whether the service is affected. Then compare operational and degraded cards side by side. Make sure the title, affected service, and timestamp stay in the same place. That stable structure lets readers compare two rows without relearning the page. Save the theme tokens and evidence together so a reviewer can see where a design decision came from.