Lamina Product Behavior Agent Skill
Define 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/aryaniyaps/lamina --skill lamina-product-behaviorWhat comes with it
21 759 bytes besides the instructionThe instruction itself
4 sections, as written by the authorLamina Product Behavior
Reference-loading protocol
- Match the request's primary runtime-truth decision to one row below.
- Open that linked reference before answering. Add another only when a second
decision materially changes the answer; do not preload the directory.
- Start the response with
Using lamina-product-behavior: <topic path(s)>so
the selected behavior lens is auditable.
Topic index
| Runtime signal | Read | Adds |
|---|---|---|
| Need the represented domain model to match how actors understand the task | Product Behavior | entities, permissions, workflows, surfaces, and illegal states |
| Need to choose how much power or complexity each actor sees | Product Density | actor- and surface-specific complexity budgets |
| One mutation must update, notify, invalidate, audit, or retry elsewhere | Side Effects | primary effect, downstream effects, delivery lifecycle, and failure recovery |
| Need a rule that must hold in every valid state | Invariants | explicit predicates and violation probes |
| Views may lag or disagree after a state change | Consistency Guarantees | strong, eventual, and read-your-writes product promises |
| An operation may repeat, race, conflict, or arrive after state changed | Idempotency and Concurrency | duplicate safety, conflict policy, and fencing |
| Behavior depends on zones, dates, recurrence, duration, deadline, or correction | Time Semantics | explicit temporal meaning and boundary behavior |
| A workflow requires prior setup, ownership, state, or another workflow | Dependencies | prerequisite edges and unmet behavior |
| Need to decide which domain owns a rule or what data crosses a boundary | Modularity Boundaries | information hiding and cohesive ownership |
| Several roles or surfaces must agree on the same entity and lifecycle | Multi-View Integrity | handoffs, visibility, and cross-view truth |
Working rule
Use the smallest sufficient reference set. Common pairs are invariants +
idempotency for consequential writes, consistency + multi-view integrity for
role-based products, and side effects + time semantics for scheduled delivery.
Keep behavior in product language; do not prescribe implementation machinery
unless the user asks for it.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take aryaniyaps/lamina-product-behavior 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.