Connect inputs and runtime content with guardrails.
Lucra form and data work should be planned as part of the page. The user needs readable fields, tested calls, clear bindings, and guarded runtime behavior.
Layer tree
Form Section
Data call
Source, test response, binding, fallback, and secret boundary.
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
Form Section
Data call
Source, test response, binding, fallback, and secret boundary.
Forms And Data
Page
Forms and data
Model
Theme and layers
System
Use Form, Form Section, Form Grid, fields, choices, and Form Message for real submissions.
Plan source shape, data calls, bindings, empty states, and failure states before wiring live content.
Do not expose secret values to pages or agent tools.
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.