Lamina empty states
Headless Product Design skill for AI coding agents | Design how it works, verify what you ship.
npx -y skills add aryaniyaps/lamina --skill lamina-empty-statesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Empty and zero-data UX in scenarios — first productive action when domain collections are empty. Use when collection_empty scenarios are missing.
SKILL.md
1.7 KB, as published. Nobody here has run it
Empty States (agent-native)
Empty domain state is a scenarios[] category empty — not an afterthought in implementation.
Contract encoding
scenarios:
- id: no-tickets-yet
category: empty
trigger:
when: collection_empty
entity: hall_ticket
screen_id: ticket-list
ux: empty_state
primary_action: view exam schedule
copy: No tickets yet — tickets appear after payment confirms.
Design checklists
- Every list/dashboard screen has
collection_emptyscenario or explicit "always populated" invariant. - One primary CTA toward first productive workflow step.
- Explain what will appear after actor acts — not just "no data".
- Distinguish empty vs error vs loading in
uxfield. - No fake data without label.
Verify checks
- Actor walk with zero-data fixture or fresh account.
- Empty state copy matches contract; CTA completes onboarding workflow.
Anti-patterns
- Bare table with no rows and no guidance.
- Feature tour modal instead of one clear action.
- Empty state missing from contract — implementer guesses.