typescript-style-guide
⚙️ TypeScript Style Guide and Agent Skill. A concise set of conventions and best practices for consistent, maintainable code.
Runssource: GitHubhomepageTypeScriptMITcommit 170074a0df9b
TypeScript, MIT licensed. The project labels itself: ai, ai agent, ai skill, ai tools, coding conventions, coding guidelines, nodejs and reactjs.
typescript-style-guide runs. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The website builds and serves via Docusaurus on port 3000; the skills project compiles with TypeScript 6.0.3 and has zero vulnerabilities.
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 100 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.
- Node.js v18.19.1 too old; project requires >=26.8.12 minutes
- Optional native binary @tailwindcss/oxide-linux-x64-gnu missing after npm install0.1 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm run build on website exited 0 and produced build/ dir; dev server started on port 3000 and returned HTTP 200 on /typescript-style-guide/; npm run tsc on skills passed
- Model tokens used
- 59,566
- Exact commit tested
- 170074a0df9b
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- The built `build/index.html` is present (455 KB). tokens used 59,566 Here's the complete summary of what happened and the final result: **Errors encountered:** 1. **Node.js version too old** — v18.19.1 was installed, but Docusaurus requires >=20 and package.j… 2. **Missing tailwindcss native binary** — `@tailwindcss/oxide-linux-x64-gnu` was in the lockfile b… **What was verified:** - `npm run build` on the website succeeded — generated static files in `build/` (~7s build time). - `npm start` launched a dev server on port 3000; `curl` returned HTTP 200 on `/typescript-style-gu… - `npm install` on the skills project succeeded with 0 vulnerabilities; `npm run tsc` passed (no er… - The built `build/index.html` is present (455 KB).
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 3 minutes, faster than the median of the 236 comparable projects Argusic has measured.
- Recovered from all 2 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 2 times, so the result is not a one-off.
Of the 237 ai projects Argusic has installed and timed, typescript-style-guide was the 84th fastest to reach a running state, and 168 of 237 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 3 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
aiai-agentai-skillai-toolscoding-conventionscoding-guidelinesnodejsreactjsskillstyle-guidetypescipt
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/typescript-style-guide)Questions
- Does typescript-style-guide run?
- Yes. typescript-style-guide runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test typescript-style-guide?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 170074a0df9b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test typescript-style-guide?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does typescript-style-guide take to install?
- 3 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 typescript-style-guide need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing typescript-style-guide?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does typescript-style-guide compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, typescript-style-guide was the 84th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for typescript-style-guide?
- All 2 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.