Give local agents the Lucra build contract.
Lucra can teach local tools how to think in layers, Theme, text hierarchy, forms, chips, badges, buttons, and publishing decisions before those tools write into Studio directly.
Layer tree
Read guides
AGENTS.md, UI voice, layout, Theme, text.
Propose draft
Validation before Studio state changes.
Request publish
User control stays final.
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
Read guides
AGENTS.md, UI voice, layout, Theme, text.
Propose draft
Validation before Studio state changes.
Request publish
User control stays final.
Agent Guides
Page
Agent workflow
Model
Theme and layers
System
Local agents can read AGENTS.md, the UI voice guide, and Lucra agent guides today.
Guide-assisted code work still needs human review in the worktree or Studio.
Direct Studio write access belongs to the future Agent API, not the current guide-only setup.
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.