uselayouts
Free premium animated React components and micro-interactions built with Framer Motion and Tailwind CSS
Runssource: GitHubhomepageTypeScriptMITcommit 5ed0d9445437
TypeScript, MIT licensed. The project labels itself: animated components, components library web development, nextjs ui components, open source, open source ui library and shadcn ui.
uselayouts runs. An Argusic agent installed it in 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install, npm run build, and npx next start all succeed; the documentation site serves all routes including / (200), /docs/* (200), /api/search (200), and /robots.txt (200) over HTTP on port 3000.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 87.5 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Tailwind v4 does not recognize fumadocs-ui's `inset-s-*` and `inset-e-*` utility classes15 minutes
- Next.js 16 requires Node >=20.9.0, container has Node 183 minutes
- build-registry.mts uses `bun x shadcn` but bun is not available2 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 24 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm run build exited 0 producing all static pages; `curl -s -o /dev/null -w '%{http_code}' localhost:3000/` returned 200, same for /docs/introduction, /docs/installation, /docs/components/3d-book, /api/search, /robots.txt
- Model tokens used
- 114,350
- Exact commit tested
- 5ed0d9445437
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
DOCS_INSTALL: 200 COMPONENT: 200 SEARCH: 200 ROBOTS: 200 All 5 endpoints return HTTP 200. Perfect. Let me also make a note of the total time more carefully. Starting from first command to last verif… Now let me report the results. tokens used 114,350 All 5 endpoints return HTTP 200. Perfect. Let me also make a note of the total time more carefully. Starting from first command to last verif… Now let me report the results.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 25 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 4 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
animated-componentscomponents-library-web-developmentnextjs-ui-componentsopen-sourceopen-source-ui-libraryshadcn-ui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/uselayouts)Questions
- Does uselayouts run?
- Yes. uselayouts runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test uselayouts?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ed0d9445437. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test uselayouts?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does uselayouts take to install?
- 25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does uselayouts need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing uselayouts?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for uselayouts?
- All 4 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.