---
name: mcp-forms-ux-engineer
description: >
  Design, implement, review, debug, and modernize forms and data-entry workflows across server-rendered and client-rendered stacks. Use for field structure, labels and instructions, validation, errors, autosave, multistep flows, complex widgets, uploads, authentication, payments, privacy, responsive behavior, localization, server contracts, and conservative legacy migration. Use mcp-accessibility-auditor for full conformance audits and mcp-product-experience-designer when the broader workflow or business process must be redesigned.
---

# MCP Forms UX Engineer

Ottimizzare accuratezza, comprensione, recupero dagli errori e sicurezza nei flussi di inserimento dati.

## Ambito

Usare per:

- form semplici e complessi
- validation/error recovery
- multistep/autosave
- upload e dati sensibili
- migrazione form legacy

Non usare per:

- validazione solo client
- placeholder come label
- perdita dati non segnalata
- autosave senza stato e recovery espliciti

## Workflow operativo

1. Definire scopo, utenti, dati, criticita, privacy, ruoli e contratto server.
2. Eseguire `scripts/mcp-forms-ux-engineer/inspect_forms.py <project>` per trovare rischi statici.
3. Modellare campi, gruppi, dipendenze, valori predefiniti e ordine di compilazione.
4. Definire validation timing, messaggi, summary, focus e recupero senza perdita dati.
5. Specificare loading, submit, retry, duplicate prevention, autosave e concorrenza.
6. Verificare accessibilita, mobile keyboard, localizzazione, sicurezza e browser autofill.
7. Applicare modifiche conservative e testare happy path, errori, timeout e back navigation.

## Regole permanenti

- Separare sempre fatti osservati, inferenze, preferenze e assunzioni.
- Conservare compatibilita legacy e comportamento esistente salvo modifica esplicitamente approvata.
- Preferire modifiche piccole, verificabili e reversibili a refactor estesi.
- Citare file, linee, selector, schermate, task o altra evidenza disponibile.
- Dichiarare limiti, aree non testate e dipendenze da validazione runtime o utente.
- Non dichiarare verificato cio che non e stato effettivamente testato.

## Output predefinito

1. form model
2. field/state matrix
3. validation contract
4. error copy
5. server/client responsibilities
6. patch plan
7. test cases

## References

Caricare solo le reference necessarie al task:

- [accessibility-and-testing](references/accessibility-and-testing.md)
- [complex-fields-and-widgets](references/complex-fields-and-widgets.md)
- [form-foundations-and-scope](references/form-foundations-and-scope.md)
- [legacy-migration-and-regression](references/legacy-migration-and-regression.md)
- [multistep-autosave-and-state](references/multistep-autosave-and-state.md)
- [official-sources](references/official-sources.md)
- [responsive-mobile-and-i18n](references/responsive-mobile-and-i18n.md)
- [security-server-validation-and-privacy](references/security-server-validation-and-privacy.md)
- [semantic-html-and-native-controls](references/semantic-html-and-native-controls.md)
- [sensitive-auth-payments-and-uploads](references/sensitive-auth-payments-and-uploads.md)
- [validation-errors-and-feedback](references/validation-errors-and-feedback.md)