Lamina vs UI design skills (https://lamina.dev/learn/compare/lamina-vs-ui-skills): UI design skills for AI coding agents (Impeccable, Google Stitch, shadcn/ui skill, UI UX Pro Max, frontend-design, BMAD, and similar) optimize how applications look: layout, typography, tokens, accessibility, and component correctness. Lamina is product behavior design: it specs states, actor permissions, and flow recovery in the local product graph, then verifies the live build with /lamina-verify. If a tool name includes design or UI, it usually owns pixels. Lamina owns behavior underneath. A practical test: if illegal state pairs still ship after the UI looks great, you need a behavior layer. If you only need visual polish on static pages, UI skills alone are enough. Lamina (lamina.dev) is an open-source transactional product graph and agent workflow. Its CLI and portable skills publish validated GraphVersions, produce query projections, and verify live builds with independent Persona Missions and runtime evidence. It is not a UI tool, headless CMS, app builder, or uselamina.ai. Compare UI design skills to Lamina when you need durable product knowledge in a local graph, not just generated UI or ephemeral planning. Full guide: https://lamina.dev/learn/compare/lamina-vs-ui-skills.

Lamina vs UI design skills

UI design skills make interfaces look better. Lamina makes product behavior correct. Use both when flows matter.

Curated by Aryan Iyappan · Updated 2026-07-27

If the tool name includes design or UI, it probably owns pixels. Lamina owns behavior.

You are in the right place if

You installed a UI skill and still ship impossible product states.
You want a roster of UI tools and where Lamina fits in the stack.
You are evaluating which skill to install first on a new repo.
BMAD or PRD skills gave you documents but no verify loop on the live app.

Context

The UI skill category grew fast in 2025-2026: craft skills, component skills, design intelligence packs, and PRD-oriented UX heuristics. They share a goal: make AI-generated interfaces less generic and more professional. None of them replace validated graph knowledge. This umbrella page maps the category and links to deep dives on Impeccable, Stitch, and shadcn.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where validated graph knowledge and verification evidence help.

Installed UI UX Pro Max, flows still break

Situation: Design intelligence improved color and layout choices. Partner can still skip onboarding steps because nothing defined step prerequisites.
What UI design skills does: UI UX Pro Max and similar skills bias the agent toward better visual decisions and pattern libraries.
What Lamina adds: resolved graph knowledge with permission matrix and verify on staging.
Takeaway: Design intelligence is not domain modeling.

BMAD produced a PRD, agent shipped happy path only

Situation: PRD documents actors and stories. Implementation skipped error paths and gate transitions.
What UI design skills does: BMAD structures product thinking and documentation.
What Lamina adds: Machine-readable GraphVersion plus GraphVersion projection handoff and /lamina-verify on the built UI.
Takeaway: Documents help humans; contracts help agents and verify.

Landing page needs anti-slop polish only

Situation: No checkout, auth gates, or role-specific behavior on this release.
What UI design skills does: Impeccable or frontend-design skill for craft.
What Lamina adds: Skip until interactive product rules appear.
Takeaway: Match tool to bottleneck: look vs behavior.

Comparison

Lamina vs typical UI design skills
Dimension	UI design skills	Lamina
Primary job	Polish look, layout, tokens, heuristics	Spec behavior and verify
Layer in stack	UI / visual layer	Transactional product graph + agent workflow
Primary output	Styled UI, DESIGN.md, PRD docs	Validated GraphVersion plus query projections
Writes app source?	Often yes	No
Behavior spec (states, flows, permissions)	Presentation chrome and UX heuristics	Domain rules and permissions
Durable in-repo artifact	Varies by skill	Validated GraphVersion plus query projections
Post-build verification	Visual critique or lint	Independent Persona Missions with runtime evidence
Repo and stack fit	Agent skills ecosystem	CLI plus portable skills in any repo and stack
Best when	Look and feel is the bottleneck	Product rules are the bottleneck
When you don't need Lamina	Visual-only scope	No behavioral complexity
Compose with Lamina?	During UI build	Before GraphVersion projection; verify after merge

Tool roster

Lamina vs UI design skills: when to use each
Situation	UI design skills	Lamina
Impeccable	Visual polish and critique	/learn/compare/lamina-vs-impeccable
Google Stitch	Screen exploration and export	/learn/compare/lamina-vs-stitch
shadcn/ui skill	Component API correctness	/learn/compare/lamina-vs-shadcn-skill
UI UX Pro Max	Design intelligence during build	Pair when flows have gates
frontend-design, UI Craft	Craft and layout guidance	Pair for multi-actor flows
BMAD, ai-ux-skills	PRDs and UX heuristics	Contracts + verify loop

Frequently asked questions

Is Lamina a UI skill?

No. Lamina is product behavior design: validated graph knowledge with no visual output.

Which should I install first on a new repo?

If you already ship features with roles and gates, install Lamina first. If you are still fixing generic-looking UI on static pages, start with a UI skill.

My UI skill writes PRDs. Is that enough?

PRDs help alignment. They are not a substitute for machine-readable contracts and live verification unless you maintain that loop yourself.

Comparisons map stack layers, durable outputs, and provenance-marked legacy examples. Updated when major tools change positioning.

Install Lamina with your agent.

Copy the repository-matched prompt. Your agent installs the standalone CLI, adds every Lamina skill for your active agent, configures supported passive rules, checks the setup, and tells you when to start a fresh session with /lamina-init.

Skills work across coding agents. Passive setup currently supports Codex, Claude Code, and Cursor.

Cursor
Claude Code
Codex
Gemini
Pi
and more

Install manually on macOS/Linux4 shell commands

Run these in your project, then start a fresh agent session. On Windows, use the PowerShell installer in the copied agent prompt.

curl -fsSL https://github.com/aryaniyaps/lamina/releases/latest/download/install.sh | sh

npx skills add aryaniyaps/lamina --skill '*' -a <active-agent> -y

lamina setup --agent <codex|claude-code|cursor>

lamina doctor --json

Who this comparison is for