lamina-controls-and-menus
SolidActions and reversibility in contracts — primary/destructive actions, undo policy, confirmations. Use when destructive ops lack scenarios.
AI & Automation 65 stars
2 forks Updated today Apache-2.0
Install
Quality Score: 82/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Controls and Actions (agent-native)
Specify **action semantics** in screen and workflow contracts — destructive, reversible, confirmation policy — not menu widget styling.
## Contract encoding
Per action on `surfaces[]`:
- `id`, `label`, `destructive: true|false`
- `reversible: true|false` → if true, confirmation usually unnecessary
- `confirmation_required` only when undo impossible + scenario documents
- `undo_scope`: step | session | none
Working-set actions on primary toolbar area in screen spec; full catalog in nav/menus.
## Frameworks
- **Ask forgiveness, not permission**: undo replaces confirm dialogs for recoverable ops.
- **Rich modeless feedback**: status in view, not modal for normalcy.
- **Preview/compare**: before irreversible-feeling changes — note in workflow step.
## Design checklists
1. Destructive ops have `scenarios[]` + recovery or undo policy.
2. Daily working-set actions ≤1-2 clicks from working screen.
3. Confirm only when invariant violation risk and undo absent.
4. Selection + manipulation pattern documented for sovereign apps.
5. Platform conventions noted in `implement.md` (web vs desktop) — Lamina stays unopinionated on library.
## Verify checks
- Actor walk: destructive op matches contract confirmation/undo behavior.
- Accidental click recovery — undo or cancel path exists per contract.
## Anti-patterns
- Confirm dialog for undoable delete.
- Modal error for recoverable validation.
- All actions equal weight on crowded screen spec.
-...
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
AI & Automation Solid
lamina-discoverability
Signifiers and affordances in screen contracts — actors must see what they can do. Use when actor walks report execution/evaluation gulfs.
65 Updated today
aryaniyaps AI & Automation Solid
lamina-forms
Form behavior in contracts — validation timing, field semantics, and recovery UX. Use when data entry blocks workflows or causes scenario gaps.
65 Updated today
aryaniyaps Web & Frontend Solid
lamina-product-behavior
Represented model matches domain — UI must not imply illegal states or permissions. Use when the active GraphVersion domain and screens diverge from implementation shape.
65 Updated today
aryaniyaps