Start faster without losing the layer tree.
Lucra templates are most useful when they behave like editable starting structures, not locked pages that fight the Studio model.
Layer tree
Project recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Section recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Component recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Show the feature as a working surface.
A Lucra feature page should present the product model with enough detail to feel usable: panels, states, layer choices, and the tradeoffs a builder would understand.
Layer tree
Project recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Section recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Component recipe
Clear responsibility keeps the page tree easier to inspect and edit.
Templates
Page
Reusable structures
Model
Theme and layers
System
Templates should start the page without hiding how the page is built.
Recipes and reusable structures need clear scope.
The user should be able to adjust the layers after the starting point lands.
Theme, layers, and agent guidance belong together.
Lucra's edge is strongest when the visual system, page structure, and local agent instructions all point to the same build model.
Theme
Set the system for color, type, rounding, forms, and color modes.
Layers
Keep each section readable as Wrapper, Container, Flex, Grid, Surface, and content.
Agents
Let local tools learn the public contract before API-backed Studio writes exist.
Plan a Lucra site review.
This form uses native validation for the local marketing test. It keeps the form pattern visible without pretending a backend has been wired here.