reactive-form-inputlisted
Install: claude install-skill tdw8147-crypto/skill-delivery-kit
# Reactive Form Input
Stop reporting “the field is filled” as success when the application has not accepted the value.
## When to use
- A controlled field shows the expected text while its dependent state remains unchanged.
- A page has a visible contact field, a hidden duplicate, and a similarly named search box.
- A valid-looking value leaves a spinner, validation error, or disabled control.
- A client-side navigation replaced the field while a test was in progress.
- The user wants an evidence record from page notes even though no browser is available.
## When NOT to use
- The user wants to send a finished application or complete a payment.
- A submission already timed out and the question is whether it reached the destination.
- The input is in a local text editor, not a form with app-level state.
- The task is to implement validation logic rather than observe a field.
- The user only needs to know what format to type, not whether the application accepted it.
## Core rules
1. **Identify the visible, editable control within its own form.** Hidden duplicates and same-named search fields can produce convincing but irrelevant observations.
2. **Prefer normal fill or keyboard input; say how replacement clears the old value.** Ordinary interaction exercises the app's expected path while preserving the requested format and units.
3. **Do not claim success from DOM property changes.** A rendered string is not proof that the application accepted it; honor control limits and