What problem does it solve? Tables are often designed as just rows and columns with borders, leading to poor readability, broken responsive behavior, and misuse of component-library grids. This Skill guides the design, implementation, and review of tabular interfaces so users can accurately find, compare, and act on values. ## Core Features & Use Cases - Task-driven structure: Decides whether a surface should be a native HTML table or an interactive data grid based on lookup, comparison, scanning, or row-action needs. - Density, alignment, and formatting rules: Covers row identity, column semantics, units, numeric alignment, missing values, and consistent formatting. - Responsive strategy: Chooses between preserving table geometry with horizontal scroll or recomposing into stacked layouts without losing column-label relationships. - Use Case: When building an admin dashboard listing hundreds of resources with sortable columns and batch actions, use this Skill to decide between a native table and a managed-focus grid, then verify dense, narrow, keyboard, and zoom states with realistic data. ## Quick Start Review this table component using the table-design skill and tell me whether it should stay a native table or become an interactive grid, and how it should behave on narrow screens.
