lamina-flow-design

Solid

Design reachable actor workflows from typed product operations, dependencies, and terminal outcomes, including complete cross-actor handoffs and recovery.

Web & Frontend 65 stars 2 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 79/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
38
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Workflow design A workflow is a user-reachable sequence of `operation.<id>` references owned by one actor and ending in named terminal outcomes. For each critical workflow: 1. Name its trigger and `actor_ref`. 2. Reference ordered operations rather than restating them in prose. 3. Link dependencies that change reachability. 4. Name success, rejection, degraded, and recovery terminal outcomes that materially differ. 5. Complete cross-actor handoffs through delivery, recipient binding, accept/reject, durable authority change, both projections, expiry, replay, and recovery. 6. Add surfaces only where the workflow needs a user-visible realization. Do not create a full application flow inventory when only one product slice is being changed.

Details

Author
aryaniyaps
Repository
aryaniyaps/lamina
Created
3 weeks ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

lamina-design

Use only when explicitly invoked as lamina-design. Shape intended product behavior in Lamina's transactional graph and publish a validated graph version.

65 Updated today
aryaniyaps
AI & Automation Featured

agent-workflow-designer

Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.

23,263 Updated 1 weeks ago
alirezarezvani
Web & Frontend Listed

dev-flow

Orchestrate an end-to-end product-development workflow built on atomic skills. Reads `.workflow/meta.json` in a project directory, figures out what phase the user is in (idea → PRD → tasks → design → scaffolded → pages → modules → tests), and delegates to the right specialist skill: `prd-from-idea`, `prd-to-tasks`, `figma-to-design-md`, `image-to-design-md`, `design-md-to-app`, `screenshot-to-page`, `module-add`, `write-tests`, `forms`, `data-fetching`, `state-discipline`, `eve-agent` (the eve agent engine behind the app). Use when the user wants to "start a new project end-to-end", "advance my project to the next stage", "what should I do next on this project", or pastes a brand-new product idea / Figma URL / inspiration images with a request to "build the app". Not for: deeply-specialized work inside one stage (in that case, invoke the specialist skill directly).

4 Updated 2 days ago
lukedj78