跪拜 Guibai
← All articles
Frontend · Artificial Intelligence · Design

Codex Takes the Design Wheel: A Hands-On UI Reskin of nvm-desktop

By 梦想很大很大 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

This workflow lets an AI handle the bulk of UI implementation on an existing app while the human reviews rendered pages and gives targeted visual feedback. The three-layer test setup turns the AI into a self-verifying contributor, cutting down the manual QA loop and making AI-generated design changes more trustworthy.

Summary

Codex, running GPT-6.1 Sol in Light mode, got a one-line brief: simple, modern, premium. No mockups, no spacing or color specs. The developer configured three skills (shadcn for components, UI UX Pro Max for design reference, and a custom comment skill), then let Codex produce a first pass. From there the loop was straightforward: Codex edits, the developer reviews the code, opens the actual page, and points out specific problems like crowding or visual imbalance.

The surprise was that Codex understood nvm-desktop's existing theme-switching system and tuned the design across themes, so changing themes didn't break the look. The author also added three layers of automated testing (Vitest in-memory, Playwright real-browser, and WebdriverIO E2E) so Codex could write and run its own test scripts after each change. The human still manually inspects pages for visual comfort and interaction smoothness.

Takeaways
— Used GPT-6.1 Sol in Light mode with no design mockup; the only brief was 'simple, modern, premium'.
— Configured three skills: shadcn for components, UI UX Pro Max (via `uipro init --ai codex`) for design reference, and a custom comment skill.
— Iteration loop: Codex makes a version, developer reviews code and opens the real page, then gives specific visual feedback for targeted fixes.
— Codex adapted to nvm-desktop's existing theme-switching system and kept visual consistency across themes.
— Added three testing layers: Vitest for in-memory logic/state, Playwright for real-browser interaction, and WebdriverIO for full E2E flows.
— The test setup lets Codex write and run its own validation scripts; the developer still manually checks the page and interactions.
— The author reported no controlled comparison of the three skills' contributions, but praised the theme adaptation and self-verification capability.
Conclusions

The human's role shifts from writing front-end code to acting as a design critic after seeing concrete output, which makes feedback much more specific than abstract style guidance.

Automated tests matter more when an AI is doing the implementation because they let the AI close its own loop, leaving the developer to focus on visual and UX judgment that tests can't capture.

The fact that Codex handled theme switching without explicit instructions suggests LLMs can infer and respect existing architectural constraints when given enough context, even in design work.

Concepts & terms
shadcn
A collection of React components that you copy-paste into your project rather than install as a package, giving full control over styling and behavior.
Codex Skill
A reusable instruction or configuration set that tells an AI coding agent how to handle specific tasks, like writing comments or applying design conventions, to make output consistent and reviewable.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗