Lamina information architecture
Skill aryaniyaps/lamina/skills/lamina-information-architecture
Headless Product Design skill for AI coding agents | Design how it works, verify what you ship.
npx -y skills add aryaniyaps/lamina --skill lamina-information-architectureAssembled 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
Entity organization and retrieval — how actors find domain objects in screens and nav. Use when IA mirrors files or tables instead of tasks.
SKILL.md
2.0 KB, 344 tokens by cl100k_base, as published. Nobody here has run it
Information Architecture (agent-native)
Organize entities[] for actor retrieval — recency, search, hierarchy — not filesystem or schema shape.
Contract encoding
- Entity list drives nav sections and
surfaces[]groupings - Retrieval patterns per entity type: list, search, timeline, facets — in screen spec
entities[].relationshipsinform parent/child nav — not foreign keys in UI copy
Frameworks
- Unified object model: actors manipulate domain objects (tickets, exams), not paths or tables.
- Retrieval: recency + search + visual browse — match how actors remember work.
- Auto-persist: no "save?" anxiety — session/history scenarios if undo needed.
Design checklists
- IA follows task analysis operations, not org chart.
- Recent/frequent objects promoted on dashboard screen.
- Search across entity attributes actors know (name, date) — not internal ids.
- Deep hierarchy only for rare admin paths.
- Entity rename in domain → nav label update in same contract pass.
Verify checks
- Actor walk: find entity by primary retrieval path on live product.
- "Where did it go?" after create operation → finding if contract promised visibility.
Anti-patterns
- Exposing file paths, table names, module ids to actors.
- Folder drilling as only retrieval path.
- IA copied from database ERD without task mapping.