shadcn/ui — Task table

Tables & ListsSee it liveui.shadcn.com

A text-first task table makes status, priority, and row actions scannable without wrapping every task in a card.

shadcn/ui — Task table — captured interface — Page excerpt · scroll inside to explore

Public demo · 2026-09-04Open full image ↗

Dashboards Search & discovery

Why this pattern works

Use inline filters above the table, stable column widths, and a compact overflow menu for secondary row actions.

Design notes

Surface: Task list with search and status filters
Navigation: One page header; controls belong directly above the table they affect.
Layout: Wide table with selection, ID, title, status, priority, and a trailing overflow menu.
Density: Dense rows with enough vertical padding for scanning. Long titles truncate while the status columns remain aligned.
Color: Neutral surfaces and fine separators. Status uses an icon and label rather than relying on color.
Type: Small sans-serif table text, bold task title, subdued IDs and header labels.
Pattern: Keep comparison attributes in fixed columns and preserve row alignment during filtering.
States: Populated public demo with fictional task text; selected count and pagination are below the captured area.
Don't: Do not hide essential row actions behind hover or let long titles push status off screen.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: shadcn/ui — Task table
Source: https://ui.shadcn.com/examples/tasks
Swipefile reference: https://swipefile.design/ref/shadcn-tasks/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Task list with search and status filters
- nav: One page header; controls belong directly above the table they affect.
- layout: Wide table with selection, ID, title, status, priority, and a trailing overflow menu.
- density: Dense rows with enough vertical padding for scanning. Long titles truncate while the status columns remain aligned.
- color: Neutral surfaces and fine separators. Status uses an icon and label rather than relying on color.
- typography: Small sans-serif table text, bold task title, subdued IDs and header labels.
- pattern: Keep comparison attributes in fixed columns and preserve row alignment during filtering.
- states: Populated public demo with fictional task text; selected count and pagination are below the captured area.
- dont: Do not hide essential row actions behind hover or let long titles push status off screen.

Useful for: Use inline filters above the table, stable column widths, and a compact overflow menu for secondary row actions.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Use inline filters above the table, stable column widths, and a compact overflow menu for secondary row actions.

shadcn/ui — Task table

Make it your own

Keep exploring