What problem does it solve? Designing tables and data grids for complex enterprise applications involves dozens of decisions — column selection, widths, alignment, sorting, pagination, null handling, bulk actions — and inconsistent choices across screens produce confusing, unpredictable interfaces. This Skill encodes a complete set of opinionated house rules so every table follows the same constraints. ## Core Features & Use Cases - Column and layout rules: Enforces one table per object type with status as a column, populated-column requirements, no exception columns, no horizontal scrolling, and widths set by data type. - Interaction rules: Governs clickable rows, record entry points, add affordances at the table header, bulk action regions, inline editing consistency, and multi-sort behind long-press. - Data presentation rules: Specifies alignment by content type, truncate-vs-wrap logic, italic neutral-500 NA for null cells, default sort indication, fixed headers and footers, and totals placement. - Use Case: When building a list view of customer records, apply this Skill to decide which columns exist, how currency aligns, where the add button sits, and how pending-approval rows display — then verify against the included pre-flight checklist. ## Quick Start Review this table design against the house rules and flag any violations before I ship it.
