lattice
Install engineering discipline into any AI coding assistant. Composable skills for design, implementation, review, and team standards. Better process, not just better prompts.
Runssource: GitHubhomepageJavaScriptMITcommit 4b0bc6e625b9
JavaScript, MIT licensed. The project labels itself: agent, agent framework, agent skills, agentic, agentic ai, claude code plugin, claude skills and clean architecture.
lattice runs. An Argusic agent installed it in 45 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
The Lattice skils install, distribution rebuild, and the portable verification runner all run correctly (27 skills installed, runner passes and fails as specified), while the website build remains blocked on the container's Node 18 versus the repo's pinned Node >=20 requirement.
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 80 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.
- npm run build fails: Minimum Node.js version not met (Node v18.19.1 vs engines.node >=20.0 pinned by repo and CI)30 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- tools/install.sh printed 'Installed 27 skills' exit 0; build-skills.sh exit 0 with clean git status; scripts/run-verification.sh exit 0 with summary.json overallStatus passed in 25/25 concurrent runs and failure-path exits 1/2 as designed; npm ci exit 0 (1321 packages); npm run build exits 2 with only the Node version error.
- Model tokens used
- 1,169,732
- Exact commit tested
- 4b0bc6e625b9
- 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.
- `tools/install.sh` and `tools/build-skills.sh` both printed `Installed 27 skills` and exited 0; i… - `scripts/run-verification.sh` is the repo's executable core and works: real pass stage (exit 0, `… - The only hard error is the website build: `npm run build` fails with `[ERROR] Minimum Node.js ver… - The repo contains no test suite (0 test/spec files) and no test CI job, so `launch_succeeded` ref… tokens used 1,169,732 Final state verified. Summary of the run and the result line: **Findings** - `tools/install.sh` and `tools/build-skills.sh` both printed `Installed 27 skills` and exited 0; i… - `scripts/run-verification.sh` is the repo's executable core and works: real pass stage (exit 0, `… - The only hard error is the website build: `npm run build` fails with `[ERROR] Minimum Node.js ver… - The repo contains no test suite (0 test/spec files) and no test CI job, so `launch_succeeded` ref…
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.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 45 minutes to install, slower than the median of the 130 comparable projects Argusic has measured.
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 131 agent projects Argusic has installed and timed, lattice was the 126th fastest to reach a running state, and 85 of 131 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.
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)
agentagent-frameworkagent-skillsagenticagentic-aiclaude-code-pluginclaude-skillsclean-architecturecodexcodex-plugincodex-skillscontext-engineeringcursor-plugindddengineering-enablementgorkkimikimi-codelatticesdlc-workflow
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lattice)Questions
- Does lattice run?
- Yes. lattice runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test lattice?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4b0bc6e625b9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lattice?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lattice take to install?
- 45 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 lattice need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lattice?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does lattice compare with the alternatives?
- Of the 131 agent projects Argusic has installed and timed, lattice was the 126th fastest to reach a running state, and 85 of 131 reached one at all.
- Where is the evidence for lattice?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.