Lustre

Skill aboio-labs/aboio-skills/skills/lustre

Gleam frontend development skill targeting JavaScript. Covers Lustre 5.x, MVU Architecture, Advanced Forms (save-lifecycle state machines/FieldState), UI Patterns, SPA Routing (modem), and HTTP requests (rsvp). Use when building UI or working in client/src/.From its SKILL.md

Install

npx -y skills add aboio-labs/aboio-skills --skill lustre

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, as published. Nobody here has run it

Lustre & Frontend Best Practices

Skill for Gleam frontend development using Lustre. Read the relevant reference before writing code.

Token Efficiency

All agents and commands using this skill MUST follow references/token-efficiency.md (from core). Use Read and Grep tools with targeted reads instead of reading entire files.

Reference routing — by task

Task	References to read
Frontend MVU Forms & UI	`advanced-mvu-forms.md` + `lustre-ui-patterns.md`
Frontend Web Components	`lustre-components.md`
Frontend HTTP / API calls	`lustre-http.md`
Frontend SPA Routing	`lustre-routing.md`

Reference routing — by topic

Topic	Reference
Lustre MVU Core Architecture	`lustre-core.md`
Lustre Effects & Paint cycle	`lustre-effects.md`
Lustre Events (debounce, throttle)	`lustre-events.md`
Lustre Testing (query, simulate)	`lustre-testing.md`
Lustre Browser APIs (plinth)	`lustre-browser-apis.md`
Lustre Advanced (Hydration, FFI)	`lustre-advanced.md`
Common Lustre gotchas	`lustre-gotchas.md`

Core Frontend Principles

Make Impossible States Impossible — Prefer sum types over Bools. Especially for async lifecycles: a form's save is SubmitIdle | SubmitSaving | SubmitSaved | SubmitFailed(err) (the model owns its data + a sibling save field); a page load is RemoteData. Never a Bool flag beside the data.
Parse, Don't Validate — Use FieldState(v, e) to wrap invalid UI state, rather than dictionaries.
Dumb Effects — Effects should be pure executors of I/O. Never pass the Model into an effect function.