Shadcnblocks
Shadcnblocks AdminNextjs + shadcn/ui
Ecommerce
Project Management
Payment Processor
AI Chat App
    • Conversation 1
    • Conversation 2
    • Conversation 3
    • Conversation 4
    • Conversation 5
    • Conversation 6
    • Conversation 7
    • Conversation 8
    • Conversation 9
    • Conversation 10
    • Conversation 11
    • Conversation 12
    • Conversation 13
    • Conversation 14
    • Conversation 15
    • Conversation 16
    • Conversation 17
    • Conversation 18
    • Conversation 19
    • Conversation 20
    • Conversation 21
    • Conversation 22
    • Conversation 23
Todo
Original
  • Users
  • Tasks
Developers
Pages
Skip to main content
Actions
  • New chat
  • Skill library
  • Agent workspace
Workspaces
  • AI admin screens
  • Commerce workspace
Chats
  • Map agent approval states
  • Review product table density
  • Choose campaign direction
  • Summarize weekly kickoff
  • Build revenue overview
  • Preview marketing page
  • Synthesize recording
  • Plan billing webhook migration
  • Research bulk action feedback
  • Generate admin bulk actions
  • Verify generated bulk actions
  • Queue product review follow-ups
  • Review and commit verified changes
  • Triage support backlog
  • Compare response versions
  • Review release blockers
  • Review component ownership
  • Recover billing retry session
  • Compact checkout migration context
Workflows
  • Design release workflow
  • Observe live agent run
  • Review multi-agent handoff
  • Workspace settings
Tool activity and results

Tool activity and results

Review the density across our product tables. I want them to feel efficient without making row actions or status details difficult to scan.
Shadcnblocks AIUI agent

I audited the highest-traffic table patterns first, then compared how each density behaves when filters, selection, and row actions are present.

Worked for 3m 38s

Searched

Product catalogOrdersInventoryCustomers
Compared catalog, orders, inventory, and customer tables
Measured row heights, column count, and action density
Checked scan paths at desktop and tablet widths
Reviewed keyboard focus and selection behavior
Finished density audit

The best default is a balanced 44 px row. It keeps eight to eleven records visible in the common viewport while leaving enough room for a two-line product identity, status, price, and one primary action.

Recommended density system

  • Use 44 px as the shared default and 36 px only for high-volume operational tables.
  • Keep density user-selectable, but preserve column widths and row-action placement between modes.
  • Move secondary metadata into a detail panel instead of compressing it into additional columns.
Commerce workspaceProduct tables