lamina-systems
From the author
Reason about causal product systems and change over time. Use when mapping stocks, flows, delays, purposes, or interconnections; diagnosing reinforcing or balancing feedback; recognizing recurring traps; finding high-leverage interventions; or deciding how rules can evolve safely. Use lamina-product-behavior for one workflow's authoritative states, prerequisites, and consistency rules.
Install
npx skills add aryaniyaps/lamina --skill lamina-systems -a claude-code
Installs to .claude/skills/lamina-systems/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- lamina-product-behavioraryaniyaps/laminaDefine authoritative runtime product truth across actors and views. Use when modeling domain behavior, setting product density, specifying side effects, protecting invariants, choosing consistency guarantees, handling retries or concurrent actions, defining time semantics and prerequisites, drawing ownership boundaries, or keeping views coherent. Use lamina-systems for causal loops and change over time, and lamina-ux for interaction expression.Design★ 120
- lamina-product-discoveryaryaniyaps/laminaFrame product problems and decide what to build. Use when establishing business context, aligning actors with conflicting goals, discovering or prioritizing features, defining traceable requirements, comparing consequential tradeoffs, or recording a product decision. Use lamina-ux for interaction details and lamina-product-behavior for authoritative runtime rules.Design★ 120
- lamina-uxaryaniyaps/laminaDesign understandable and accessible product interactions. Use when shaping workflows, information architecture, navigation, interface copy, forms, controls, empty states, onboarding, feedback, error recovery, progressive disclosure, discoverability, accessibility, trust, group dynamics, or interaction edge cases. Use lamina-product-behavior for authoritative state rules and lamina-evaluation to judge a built product.Design★ 120
- lamina-evaluationaryaniyaps/laminaJudge product usability and evidence quality. Use when running Persona-based walkthroughs on a built product, planning an expert heuristic review, defining evidence-backed success metrics, or checking quantitative claims without inventing measurements. Use lamina-research to plan or synthesize evidence collection and lamina-ux to design interaction behavior.Design★ 120
- lamina-researcharyaniyaps/laminaPlan and synthesize evidence-grounded product research. Use when deciding what evidence is needed, designing actor walkthroughs, grounding claims in a repository or live product, analyzing user-provided references, modeling users and tasks, or communicating findings without inventing data. Use lamina-evaluation instead to judge a built product, and lamina-ux to design interaction behavior.Science★ 120
- laminaaryaniyaps/laminaRoute ordinary product implementation and explicit Lamina lifecycle requests. Use passively after initialization for changes to product behavior, flows, permissions, states, failures, or UI; skip purely mechanical maintenance.Design★ 120
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in