data-display-and-selection
SolidComplex data deserves multiple view modes — grid, list, table — chosen by the user based on their task. Row and item selection should use large hit areas (the whole row or card, not just a checkbox). Selected state is communicated through a subtle background colour shift. Mass actions appear when items are selected. Use when designing data tables, product listings, file browsers, or any multi-item collection.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- dembrandt
- Repository
- dembrandt/dembrandt-skills
- Created
- 4 months ago
- Last Updated
- yesterday
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
coordinated-data-views
When data has both a tabular/list representation and a visual representation, show both simultaneously and keep them synchronized. Clicking a row highlights the corresponding element in the visual view, and vice versa. Applies to maps, diagrams, timelines, and charts that accompany a data table. Use when designing any UI where data appears in two different representations at once.
platform-blocks-data-display
Display data with the @platform-blocks/ui React Native library. Use when rendering tabular data with DataTable (sorting, filtering, pagination, selection, bulk actions, server-side/manual pagination) or the low-level Table compound (Table.Thead/Tbody/Tr/Th/Td), building label/value detail lists with DataList, hierarchical Tree views with expansion/checkboxes/lazy loading, event feeds with Timeline, expandable sections with Accordion/Collapse/Spoiler, list rows with ListGroup, or status and identity chrome with Badge, Chip, Avatar/AvatarGroup, Indicator, Rating, Gauge, QRCode and Markdown.
show-dont-tell
Turn data-shaped answers into designed, self-contained inline UI instead of walls of text. Renders comparisons as comparison matrices, plans as timelines, numbers as stat tiles, and processes as step-flows — as theme-aware, responsive HTML/SVG that any capable chat renders. Governed by a strict anti-slop design doctrine. Triggers when the user says compare, dashboard, plan, breakdown, visualize, rank, "which should I pick", or when an answer is data-shaped enough that a visual reads better than prose.