Measured entry
ruixen-automated-tasks-panel
feature-gridunclassifiedmotion on file
A client-side feature section pairing an endlessly scrolling task card with workflow copy and badges. It ships as a shadcn registry component and expects Tailwind theme classes, local Card and Badge primitives, Motion for the loop, and Lucide icons.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 71.3 KB (136.7 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 38.62s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/badge.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A credible, responsive marketing block with a restrained task-loop animation and clean mounting once its expected scaffold exists. It needs a shadcn-style setup, and the generic automation copy and continuous motion will need product-specific editing before launch.
Use it if
- You need a compact automation or operations feature block with visible motion.
- Your app already uses shadcn conventions and can reuse its Card and Badge primitives.
- You want a responsive split layout that collapses cleanly for narrow screens.
Skip it if
- You need live task data or controls rather than a decorative marketing section.
- Your design system does not use Tailwind or shadcn-style aliases and primitives.
- You want to avoid a continuous animation or the added Motion dependency.
- Your page cannot justify the component's relatively costly dependency footprint.
Install
| Declared dependencies | motion, lucide-react, radix-ui |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add compatible Card and Badge components, configure the at-sign source alias, provide the shared class-name utility under the expected library path, map the background and foreground theme tokens, and install Motion and Lucide React. Also preserve the client-component boundary.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/ruixenui/ruixen.comAlternatives
Other published entries for the feature-grid pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-feature-grids-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-4editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- hyperui-feature-grids-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 18.3KB
- Bare
- pass
- Prov
- NO
- meraki-feature-grid-list-with-imageminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.5KB
- Bare
- pass
- Prov
- NO
- meraki-feature-simpleminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 20.2KB
- Bare
- pass
- Prov
- NO