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.
Profile →npx skills add aryaniyaps/lamina --skill lamina-systems --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lamina Systems ## Reference-loading protocol 1. Match the request's primary system question to one row below. 2. Open that linked reference before answering. Add another only when a second question materially changes the answer; do not preload the directory. 3. Start the response with `Using lamina-systems: <topic path(s)>` so the selected system lens is auditable. ## Topic index | System signal
What does the lamina-systems skill do?
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.
How do I install it?
Run `npx skills add aryaniyaps/lamina --skill lamina-systems --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aryaniyaps/lamina, a repository with 111 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.