23 October 2026 · Design-system creation · Author sources inspected
Need a design system, or just a better screen?
Conditional fit: Try OpenDesigner when a new project needs reusable tokens and a written design system. If the project already has a system and you are fixing one screen, use its rules first. OpenDesigner's own instructions say not to start another interview for that job.
| Your job | Start with | Check |
|---|---|---|
| Create a shared visual system | OpenDesigner with product purpose, audience, existing assets and design preferences. | Review generated DESIGN.md, tokens, CSS and example states against your project. |
| Fix one screen in an existing system | The existing DESIGN.md, components, tokens and real content. | Render the named screen and its relevant empty, error and responsive states. |
The main skill file declares metadata version 0.1.0 and Python 3.10+ for its engine. It describes a short initial interview and generated DESIGN.md, DTCG tokens and CSS. Its install guide lists an eight-skill Claude Code plugin and a project-folder copy for Codex and other agents. The source is mutable; no commit or tagged release is pinned here. The repository's license file is MIT.
The author reports a Claude Code demo load and standalone engine test, but its guide says a Codex run was not recorded. We have not installed the skill or measured its effect on a frontend. A user's homepage account describes vague prompts leading to repeated redesigns before a concrete brief helped. That account does not test OpenDesigner.
Before adopting: verify the exact source revision, target agent loading, generated files and local edits. If you claim it improved a screen, compare the same project and brief without the skill and inspect the render and behavior separately.