Separate what works now from what writes later.
Lucra Agent is the emerging path for letting external AI tools work with Studio safely. The near-term value is guidance; the future value is authenticated, validated, reviewable changes.
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.
Lucra Agent
Page
Agent workflow
Model
Theme and layers
System
Available now: local guides, prompt tests, layer vocabulary, and repo-backed instructions.
Planned: agent tokens, validation, drafts, recipe creation, data setup, and publish requests.
Restricted: secrets, direct production publishing, cross-project access, and unreviewed writes.
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.