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

Step	Action	Result
1	`/lamina-init <domain>`	Grounded product, actor, and persona knowledge
2	`/lamina-design <flow>`	Validated `GraphVersion` plus an implementation projection
3	Implement with your coding agent	App source in your existing stack
4	`/lamina-verify guest checkout at http://localhost:3000`	Behavioral findings backed by runtime evidence
5	Run a UI skill	Visual and interaction polish
6	Repeat the verification mission	Evidence that the 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 the accepted behavior findings first
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