The standard library
Hundreds of behaviors, from lists and forms to games and learning instruments, ready to import and bind.
@almadar/std is the public standard library: behaviors you import with uses Alias from "std/behaviors/<name>". Each one is an orbital with its own state machines, already validated and verified. You bind it to your data and set its knobs.
Two tiers
- Atoms represent one orbital and own their state machine outright: a list, a modal form, a wizard, a calendar, a book reader.
- Organisms collect several orbitals into a larger flow by importing atoms.
There is also one ui-* behavior per UI pattern, generated directly from the pattern registry: their config knobs are the pattern's props.
Topics
| Topic | What is in it |
|---|---|
| UI core | Lists, forms, modals, wizards, detail pages, dashboards, readers, the page frame |
| Games | Game shells, boards, physics and tick-driven engines |
| Learning | Instruments for teaching: simulations, graders, drills, labs |
| AVL | Behaviors that draw programs: state machines, module cards |
| Agents | Assistant threads, tool calls, memory |
| Infrastructure | Sessions, files, integrations, the page and browser substrate |
| Machine learning | Datasets, training and inference |
The behavior reference lists every behavior with its traits, events and knobs.
Using one
1uses Wizard from "std/behaviors/std-wizard"
2
3trait Onboarding = Wizard.traits.WizardForm -> Applicant {
4 config {
5 title: "Join the team"
6 }
7}Read a behavior's entry in the reference to see what it emits; to react, add a sibling trait that listens for those events.
Your own behaviors
The same rules apply to blocks you write. A block in blocks/Invoices.lolo is imported as uses Invoices from "@app/blocks/Invoices", and behavior packages (any npm package whose package.json declares an orb block) install with orb add <package>.
Next
Localization shows how one program ships in several languages.
Orb
The language where the rule is the program.