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.
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.
Lamina vs product-design skill: recommended workflow
Step
product-design (mblode)
Lamina
1
Optional: mblode shape on interaction
/lamina-design for behavior scope
2
mblode spec/review during UI build
implement.md for domain rules
3
ESLint 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.