GuidesLumos 0.0.4New
What changed in v0.0.4
New paths, tooling and CSS behavior in the Lumos v0.0.4 release.
Lumos v0.0.4 was released September 23, 2026. It keeps the component API documented here while making paths consistent, strengthening browser resets and shipping the workflows used to build and upgrade a Lumos site.
Update import paths
Every component group directory is now lowercase. For example, @/components/Typography/Heading.astro becomes @/components/typography/Heading.astro, and @/components/Wrapper/Section.astro becomes @/components/wrapper/Section.astro. The component names and props stay the same.
The utility files were renamed too: src/utils/text.ts is now src/utils/slug.ts, and src/utils/uid.ts is now src/utils/unique-id.ts. Their exported functions are still named slug() and uid().
Safer global defaults
- Buttons now clear the browser's native border as part of the reset.
- Unordered and ordered lists reset their padding and marker once in
base.css, so navs and controls no longer repeat the same reset. - Nested lists inside
RichTextuse circle markers at the second level and square markers at the third. - Field padding variables are now private component variables:
--_field-pad-blockand--_field-pad-inline.
Agent workflows ship with the project
The framework now includes agent skills for importing Figma designs and Webflow sites, auditing component props, building editable scaling graphics and upgrading a customized site. They live in .agents/skills, with Claude Code aliases in .claude/skills.
New projects record the Lumos version and exact source commit in package.json. The upgrade workflow uses that stamp for a three-way merge and compares screenshots before and after, so framework updates can be separated from project customizations.
Runtime versions
| Dependency | v0.0.4 |
|---|---|
| Node | 22.12.0 or newer |
| Astro | 7.2.9 |
| create-lumos | 0.3.5 |