Aryan Iyappan

Route 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.

Frontend · aryaniyaps/lamina

Design 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.

Content & Marketing · aryaniyaps/lamina

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.

Other · aryaniyaps/lamina

Plan 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.

Data & Analytics · aryaniyaps/lamina

Frame 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 & Presentation · aryaniyaps/lamina

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.

Workflow & Productivity · aryaniyaps/lamina

Judge 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.

Code Review & Quality · aryaniyaps/lamina

Product design skill for developers who build with AI coding agents. Use when you need to know what to build before prompting your agent — domain model, workflows, edge cases, product states, and UX gaps handled upfront. Works alongside Cursor, Claude Code, Codex, Gemini, Pi. Any stack, any UI library. Do NOT use for visual styling, pixel layouts, or writing app source.

Frontend · aryaniyaps/lamina

Use only when explicitly invoked as lamina-init. Establish business evidence and canonical Product, Actor, and Persona resources in Lamina's transactional graph.

Other · aryaniyaps/lamina

Verify graph-backed product Missions after ordinary implementation work or when explicitly invoked as lamina-verify. Run isolated Persona and live UI audits; explicit verification is source-read-only.

Frontend · aryaniyaps/lamina

Shape intended product behavior in Lamina's transactional graph when explicitly invoked as lamina-design or when passive implementation preparation reports design gaps. Publish an implementation-ready graph version without editing application source.

Design & Presentation · aryaniyaps/lamina