Skip to content
Back to skills

Lamina Systems

ASecurity

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.

  • 115 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add aryaniyaps/lamina --skill lamina-systems --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lamina Systems?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lamina Systems
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aryaniyaps-lamina-systems/badge)](https://www.skillsdirectory.com/skills/aryaniyaps-lamina-systems)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lamina-systems
description: "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."
---

# 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 | Read | Adds |
|---|---|---|
| Need to map purpose, elements, relationships, stocks, flows, or delays | [System Structure](references/system-structure.md) | a coherent system boundary before screen design |
| Local fixes recur, backfire, shift burden, or create unfair resource use | [System Traps](references/system-traps.md) | named structural failure patterns and responses |
| Need to choose between copy/UI tweaks, information changes, rules, or goals | [Leverage Points](references/leverage-points.md) | intervention ranking by structural leverage |
| Outputs amplify or balance future inputs, especially with visible delay | [Feedback Loops](references/feedback-loops.md) | reinforcing/balancing loops and oscillation risks |
| Need safe change under uncertainty or protection against rule regression | [Evolutionary Rules](references/evolutionary-rules.md) | reversible choices, deferred commitment, and invariant rechecks |

## Working rule

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.

Files in this skill

  • SKILL.md2 KB
  • references/evolutionary-rules.md1.9 KB
  • references/feedback-loops.md2.2 KB
  • references/leverage-points.md1.7 KB
  • references/system-structure.md2.9 KB
  • references/system-traps.md2.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.