01
Give the repository durable design context
Use AGENTS.md for the method and STYLESEED.md for approved project decisions. Codex should not have to rediscover the visual system on every task.
Codex UI design guide
Make Codex carry design judgment across tasks.
Better UI comes from durable repository context, a reusable design workflow, and visible verification—not from asking for “modern and clean” one more time.
Short answer
AGENTS.md → grammar → STYLESEED.md → $ss-build → $ss-score → $ss-verify.
02
Choose the output grammar
Select a grammar for the user job and a surface adapter for the artifact. A product dashboard, marketing page, deck, and carousel need different composition rules.
03
Compile unfamiliar references
When references fall outside the built-ins, use $ss-reference to extract evidence-backed rules. Preserve relationships and judgment instead of cloning pixels.
04
Build with the saved decisions
Run $ss-build with real content. Components implement the selected hierarchy, rhythm, density, type, color roles, motion, and signature move.
05
Inspect code and actual pixels
Run $ss-score, fix the highest-value failures, then use $ss-verify to render required viewports. Repeat until both the code gate and the visible result hold.
How it maps to Codex
The method has an explicit home at every layer.
StyleSeed is independent open-source software, not an official OpenAI product.
Durable repository guidance
AGENTS.mdReusable Codex workflows
.agents/skills/ss-*Approved project decisions
STYLESEED.mdBuild the selected method
$ss-buildDeterministic code gate
$ss-score ≥80Rendered visual gate
$ss-verifyIntentional engine update
$ss-updateInstall and persist
One engine. Codex-native calls.
Installation and file changes stay user-controlled. Once approved, the repository context and project lock let later Codex sessions reuse valid decisions.
$ npx skills add bitjaru/styleseed
$ $ss-setup
$ $ss-build
$ $ss-score
$ $ss-verify
$ $ss-setup
$ $ss-build
$ $ss-score
$ $ss-verify
Repository-aware
AGENTS.md owns durable guidance.
Reusable
STYLESEED.md carries decisions.
Update-aware
Checks once and only when useful.
User-controlled
No install, update, or star is required.
Questions Codex users ask
Does StyleSeed work with Codex, not only Claude Code?
Yes. StyleSeed ships Codex-facing AGENTS.md guidance and exposes its ss-* workflows through the repository skill bridge. Codex uses $ss-* names while Claude Code uses /ss-* names; both read the same canonical design engine and project-local STYLESEED.md decisions.
How do I make Codex stop generating generic UI?
Give Codex a maintained design method before implementation: define the user job, choose a functional output grammar, save bounded visual decisions, use real content, then score the code and inspect rendered pixels. Aesthetic adjectives alone do not provide enough durable constraints.
Will later Codex sessions keep the same design decisions?
Yes, when setup writes the approved grammar, adapter, tokens, density, type, motion, and signature move to STYLESEED.md. Repository guidance tells later sessions to read that lock before visual work instead of inventing a new direction.
How does StyleSeed handle updates in Codex?
On the first StyleSeed use in a project, Codex may compare the local engine version with the public version endpoint. It only mentions $ss-update when a newer version exists, suggests it once, and never blocks the current task.
Will StyleSeed ask me to star the repository?
It may ask once, only after StyleSeed materially helped and the working result was visually verified. A star is optional and never affects access, output, updates, or support. The agent must not repeat or front-load the request.
Codex로 UI를 예쁘고 일관되게 만드는 법
저장소의 AGENTS.md에 디자인 방법을 두고, 프로젝트 결정을 STYLESEED.md에 고정한 뒤, $ss-score와 $ss-verify로 코드와 실제 화면을 함께 검사합니다. StyleSeed는 이 과정을 Codex가 다시 사용할 수 있는 작업 흐름으로 제공합니다.