Pair with UI skills

Lamina and UI design skills solve different problems. Use them together — Lamina owns product behavior, UI skills own how it looks.

Quick path

/lamina-init <domain> → domain charter
/lamina-design → behavior contract
Implement and /lamina-verify
UI skill pass → visual polish
/lamina-verify again → confirm behavior still holds

The split

Layer	Skill examples	Output
Behavior	Lamina	States, roles, flows, invariants, verification
Pixels	Impeccable, UI UX Pro Max, frontend-design	Typography, spacing, components, visual polish

Lamina never writes styling, colors, typography, or component libraries. UI skills never define permission matrices or state machines.

Recommended workflow


1. /lamina-init <domain>        → domain charter
2. /lamina-design <flow>        → implement.md (behavior contract)
3. Your agent implements         → app source from contract
4. /lamina-verify guest checkout at http://localhost:3000 → fix behavior gaps
5. UI skill pass                 → polish interface
6. /lamina-verify guest checkout at http://localhost:3000 → confirm behavior still holds

Compatible UI skills

Skill	What it adds
Impeccable	Design system enforcement, component quality
UI UX Pro Max	UX patterns, accessibility, responsive layouts
frontend-design	Visual design, typography, color systems

Why not UI skills alone?

UI skills polish how it looks. They do not:

Define permission matrices across actors
Specify state machines with recovery paths
Catch impossible states (cancelled + confirmed simultaneously)
Verify behavior on a live running app

That is Lamina’s job.

Conflict resolution

Advanced: If a UI skill changes behavior while polishing — adding a step, removing a gate, or altering a flow — re-verify immediately. Styling passes can accidentally break invariants.

When UI changes affect behavior:

Run /lamina-verify to catch regressions
If findings appear, fix behavior first (from fix.md)
Then continue visual polish
Re-verify after each significant UI pass

Example pairing

Design guest checkout with Lamina (after /lamina-init):


/lamina-design Guest checkout with hold, pay, cancel

Implement and verify. Then run your UI skill on the checkout page for visual polish. Re-verify with /lamina-verify to confirm behavior was not broken by styling changes.

Next steps

What is Lamina? — full comparison with UI skills
What to pair — broader pairing guide
Demo: HavenStay — behavior gaps UI skills miss