---
name: mcp-data-table-designer
description: >
  Design, implement, review, optimize, and migrate semantic tables and interactive data grids. Use for column and row modeling, sorting, filtering, pagination, selection, bulk actions, editing, server contracts, virtualization, responsive behavior, accessibility, security, and enterprise datasets. Use mcp-grid-ui-debugger for recurring rendering, scroll, flicker, drag, or first-load geometry bugs, and mcp-frontend-performance-debugger for systemic runtime performance profiling.
---

# MCP Data Table Designer

Definire tabelle e grid comprensibili, accessibili e coerenti con contratti dati e operazioni reali.

## Ambito

Usare per:

- semantic table
- sorting/filtering/pagination
- selection e bulk action
- inline editing
- large dataset e virtualization

Non usare per:

- trasformare ogni elenco in una grid complessa
- client-side processing di dataset non adatti
- azioni ambigue senza contesto riga
- virtualizzazione senza test keyboard/screen reader

## Workflow operativo

1. Definire utenti, task, dataset, dimensione, frequenza aggiornamento e operazioni consentite.
2. Eseguire `scripts/mcp-data-table-designer/inspect_data_tables.py <project>` come inventory statico.
3. Scegliere tabella semantica o grid interattiva in base al modello di interazione reale.
4. Definire colonne, priorita, query state, sorting, filtering, pagination e URL persistence.
5. Specificare selection, editing, transazioni, concorrenza, errori e rollback.
6. Verificare responsive, accessibility, security, export e dataset realistici.
7. Separare design/contract da debugging runtime specialistico.

## 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. interaction model
2. column/query contract
3. state matrix
4. responsive strategy
5. accessibility behavior
6. server contract
7. test e regression plan

## References

Caricare solo le reference necessarie al task:

- [editing-and-transactions](references/editing-and-transactions.md)
- [foundations-and-selection](references/foundations-and-selection.md)
- [libraries-and-legacy-migration](references/libraries-and-legacy-migration.md)
- [official-sources](references/official-sources.md)
- [query-state-and-interactions](references/query-state-and-interactions.md)
- [responsive-and-small-screens](references/responsive-and-small-screens.md)
- [semantic-tables-and-accessibility](references/semantic-tables-and-accessibility.md)
- [server-contracts-and-security](references/server-contracts-and-security.md)
- [testing-and-regression](references/testing-and-regression.md)
- [virtualization-and-large-datasets](references/virtualization-and-large-datasets.md)