What problem does it solve? Adding a new field type to a JSON Forms-driven intake stepper requires creating a control renderer, choosing a correct ranked tester, registering it in the renderer registry, and optionally wiring up a debug screen — a multi-step process that is easy to get wrong. ## Core Features & Use Cases - Control Renderer Creation: Generates a control renderer file with a ranked tester (formatIs, optionIs, scopeEndsWith, isEnumControl, etc.) following the project's rank conventions. - Input Component Scaffolding: Creates specialized input components wrapping shared UI primitives like MutedInput with correct keyboard and autocomplete settings. - Registry Integration: Adds exports to the controls barrel and entries to the intakeRenderers array before the text fallback tester. - Use Case: Ask to "add a phone control" and get a fully registered renderer with a proper tester, plus a debug form screen entry to verify it renders in the stepper. ## Quick Start Ask the assistant to create a new JSON Forms control for a field such as "email" or "weight-ruler" in the intake stepper.