# Form depth

Forms should disclose complexity gradually. Start with clear field labels and
helper text, group fields by task, and reserve advanced settings for users who
need direct control.

## Schema-driven configuration

Configuration-heavy tools can use a shared schema to drive their form controls,
validation, and serialized output. This keeps a CLI, a web UI, and a CI job on
the same configuration contract without forcing every page to hand-author its
own field layout. The same schema can serialize to JSON or YAML; the example below
uses JSON here so the generated payload stays easy to inspect.

## Depth principles

- Keep labels persistent; use placeholders only as examples.
- Place validation beside the field that needs attention.
- Separate task sections with spacing or quiet rules instead of nested cards.
- Reveal advanced settings without clearing existing form state.