Skip to main content

Lamina vs product-design skill

mblode product-design is an agent skill for interaction judgment: reachable UI states, action scope, resilience. Lamina produces run.yaml contracts and /lamina-verify on the live build.

Curated by Aryan Iyappan · Updated 2026-07-13

Both say product design. mblode teaches judgment during build. Lamina writes contracts and verifies after.

Who this comparison is for

You are in the right place if

  • You installed product-design skill expecting the same output as Lamina.
  • You need permission matrices across guest vs partner actors.
  • mblode review mode caught UI issues but domain gates still fail in QA.
  • You read the pillar comparison row and want the full nuance.

Context

mblode product-design is the closest named behavioral skill to Lamina in the ecosystem. Fair comparison requires precision: mblode optimizes interaction decisions and lintable UI patterns; Lamina optimizes committed contracts and live verification across roles. Many teams could use both with clear boundaries.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where a behavior contract helps.

mblode shape mode on checkout actions

Situation
product-design skill recommended confirm vs pay labeling and loading button scope. Pay still enabled when hold expired.
What product-design (mblode) does
Interaction judgment: right control, reachable UI states, resilience patterns.
What Lamina adds
Domain rule: pay illegal when hold status is expired. verify walks guest persona.
Takeaway
UI state reachability is not hold lifecycle enforcement.

Single dialog interaction choice

Situation
Pick between modal vs inline confirm for delete. No multi-actor flow.
What product-design (mblode) does
mblode shape/spec modes for interaction choice.
What Lamina adds
Skip unless delete triggers domain side effects with gates.
Takeaway
Pure interaction choice: mblode may be enough.

Guest vs partner on same property model

Situation
Both roles see property UI. Partner may edit; guest may only book. mblode hardened components; role matrix missing.
What product-design (mblode) does
Component-level resilience and action scope.
What Lamina adds
Actor permissions in run.yaml and implement.md server checks.
Takeaway
Multi-actor domain rules are Lamina-shaped work.

Comparison

Lamina vs mblode product-design skill
Dimensionproduct-design (mblode)Lamina
Primary jobInteraction judgment before/during UI buildBehavior contracts + verify loop
Layer in stackProduct judgment skill in agent-skills bundleHeadless product design skill
Primary outputJudgment docs, ESLint rules, mode-based guidancerun.yaml + implement.md
Writes app source?Routes to ui-design for visual buildNo
Behavior spec (states, flows, permissions)Reachable UI states, action naming, interaction patternsDomain state machines, permissions
Durable in-repo artifactSkill references and lint config.lamina/ per feature run
Post-build verificationReview and harden modes, ESLint/lamina-verify persona walks
Repo and stack fitmblode agent-skills bundleStandalone Apache-2.0 skill at lamina.dev
Best whenChoosing right control for an interactionMulti-actor flows with gates
When you don't need LaminaSingle-surface interaction tweakmblode judgment covers scope
Compose with Lamina?Shape interaction during UI implementationContract first; mblode during UI polish

Workflow

Lamina vs product-design skill: recommended workflow
Stepproduct-design (mblode)Lamina
1Optional: mblode shape on interaction/lamina-design for behavior scope
2mblode spec/review during UI buildimplement.md for domain rules
3ESLint harden pass/lamina-verify on staging

Worked example

Better domain modelling. mblode can push richer UI states. Lamina pushed CancellationTemplate, HoldStatus, and booking enums in HavenStay when domain modelling was contracted. verify confirmed illegal transitions were blocked in the live app.

HavenStay demo walkthrough

Frequently asked questions

Both mention states. What's different?

mblode covers reachable UI states (empty, error, loading). Lamina covers domain rules (hold expiry, submit gates, refund statuses).

mblode has ESLint rules. Does Lamina?

Lamina focuses on contracts and verify, not lint plugins. Different enforcement point.

Which should I install?

mblode for interaction judgment during build. Lamina when you need committed contracts and persona verification across roles.

Comparisons map stack layers, repo artifacts, and HavenStay demo examples. Updated when major tools change positioning.

Install in one command.

A headless product-design skill for your AI coding agent. Then run the design → implement → verify loop on your next feature.

Apache-2.0 · open source. Star on GitHub if Lamina saves you a loop.

npx skills install aryaniyaps/lamina

Works with your coding agent

  • Cursor
  • Claude Code
  • Codex
  • Gemini
  • Pi
  • and more