EXAMPLE / UI
Capture now, complete when ready
Use form contracts to accept a minimal intake while keeping missing readiness fields visible.
Follow the pattern. Inspect its limits.
Explore the source walkthrough, its evidence and the choices you would make in your own application.
Choose the form contract
Inspect all-fields, progressive-steps, and customer-projection forms. The package includes field kinds, conditional rules, sections, and step layouts.
An exploration of the inspected source; no example is executed here.
The situation.
A customer intake can begin with a name. In the fixture, a quick capture is accepted while email, phone, and consent remain completion debt. A richer profile can then determine whether the record is ready for the next workflow.
What you will learn
- Describe form controls and layout with FormSpec metadata.
- Separate accepted intake from a complete business record.
- Expose public form and proof entrypoints without depending on private preview helpers.
Follow the operation.
- 01
Choose the form contract
Inspect all-fields, progressive-steps, and customer-projection forms. The package includes field kinds, conditional rules, sections, and step layouts.
- 02
Inspect minimal intake
The quick-capture fixture contains a customer ID and display name. The smoke test expects capture to succeed and completion to remain incomplete with email, phone, and consent debt.
- 03
Inspect conditional validation
Another test builds Zod validation with relations and expects a missing repeated contact value to be reported at contacts[0].value.
- 04
Use the public proof map
The proof-config export lists docs, sandbox, forms, and UI entrypoints. Adapt through the supported exports, then supply your own persistence and submission behavior.
What the source demonstrates.
- The inspected fixture separates acceptance from completion status.
- The source tests inspect field coverage, step layout, conditional validation, and public exports.
- The public preview is deterministic fixture state with no required backend or credentials.
What it does not establish.
- Production form storage, submission delivery, or authentication.
- A production renderer for every host application.
- A PII hint automatically implementing a privacy control.
Bring it into your environment.
Use the exact source context and prerequisites below. A source walkthrough is not a verified public-package installation recipe.
- Access to the inspected source repository and a checkout at the cited revision.
- The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.
Working directory: examples/form-showcase
bun run smokeThe source assertions cover quick-capture acceptance, incomplete readiness, conditional validation, and supported public entrypoints.
Commands and tests inspected; not executed here.
Read the related guide →Make the pattern your own.
- Decide which fields block intake and which block later readiness.
- Map the FormSpec fields to your host design system.
- Add storage, submission, and authorization tests when connecting the form to real actions.
Inspect the evidence.
Reviewed 2026-10-27 · b67c376f
Pinned source links require repository access; publication and anonymous package availability were not checked for this example.
- Declared maturity
- stable
- Catalogue registration
- Registered
- Inline preview
- Registered
- Execution in this review
- Not rerun
- Production qualification
- Not assessed