aryaniyaps/lamina-systems
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.
npx skills add https://github.com/aryaniyaps/lamina --skill lamina-systemsquestion materially changes the answer; do not preload the directory.
Using lamina-systems: <topic path(s)> so theselected system lens is auditable.
| System signal | Read | Adds |
|---|---|---|
| Need to map purpose, elements, relationships, stocks, flows, or delays | System Structure | a coherent system boundary before screen design |
| Local fixes recur, backfire, shift burden, or create unfair resource use | System Traps | named structural failure patterns and responses |
| Need to choose between copy/UI tweaks, information changes, rules, or goals | Leverage Points | intervention ranking by structural leverage |
| Outputs amplify or balance future inputs, especially with visible delay | Feedback Loops | reinforcing/balancing loops and oscillation risks |
| Need safe change under uncertainty or protection against rule regression | Evolutionary Rules | reversible choices, deferred commitment, and invariant rechecks |
Use the smallest sufficient reference set. Diagnose recurring behavior with
system traps + feedback loops, then use leverage points to choose an
intervention. Add evolutionary rules only when the question includes rollout,
reversibility, or future change.
Take aryaniyaps/lamina-systems from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.