NIMOS / ENGINES / LocalDev
← THE BUILD SYSTEMLocalDev
THE WORKSHOP
Local Development, WSL & OpenCode TUI Tools
The workshop floor: terminal, git, browsers, containers and the local server that every build runs on before a domain sees it.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
20
TOOLS
GLOBAL
WIRE
USED
THIS BUILD
The package lockfile and the local toolchain; the workshop floor.
THE PROOF LEDGER →WHAT
What it is
Twenty entries across binaries, shell and npm: tmux, lazygit, fzf, gh, ripgrep, nvm, Wrangler, Docker Compose, the v0 SDK, dotenv, tsx, husky and the rest of the workspace set.
WHY
Why it exists
A slow terminal is a slow business. Parallel builds, clean git history and a reproducible local environment are throughput, not developer comfort.
HOW
How it runs
Global bins and PATH wiring, all checked by `engctl doctor`. The engine also owns the local server, browser and screenshot lanes used by the QA corridor.
WHEN
When it runs
Every session; new-computer bring-up; long-running builds; repo hygiene before a push; local reproduction of a production issue.
WHO
Who owns it
CEO owns the floor; Research watches the toolchain; Build maintains rc files and shims; Data keeps doctor snapshots; Ops runs the computer queue.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
tmux
binTerminal multiplexer orchestrating parallel long-running build workflows.
lazygit
binVisual keyboard-driven TUI separating style edits from logic before push.
fzf
binBlazing-fast interactive filtering — swap between template sub-directories.
gh
binGitHub CLI — repos, staging issues, cloud env vars from the TUI.
ripgrep
binInstantly locate nested CSS utility definitions across massive monorepos.
zsh-autosuggestions
shellAdaptive history expansion to accelerate repetitive terminal commands.
v0
npmVercel's generative component engine — ready-to-use layouts straight into the workspace.
docker-compose
binCoordinate isolated local staging components (databases, vector memory) side-by-side.
nvm
binInstant runtime switching between Node versions per ecosystem requirement.
wrangler
binCloudflare edge worker orchestration for sub-millisecond route modifications.
next-mdx-remote
npmDynamic document delivery in Next.js apps.
@next/bundle-analyzer
npmVisual inspection of production bundle size footprints.
dotenv
npmEnvironment variable handling for isolated environments.
cross-env
npmOS-uniform environment for npm scripts.
chokidar
npmFile-system watching that triggers generation jobs.
ts-node
npmDirect TypeScript execution for backend structures.
tsx
npmUltra-fast script execution powered by esbuild.
rimraf
npmPortable recursive cleaning of build folders.
npm-run-all
npmSequential and parallel script loops across frameworks.
husky
npmValidation hooks guarding repository updates before commits.
20 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show localdev$ engctl awaken localdev$ engctl install localdev --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
The package lockfile and the local toolchain; the workshop floor.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
The proof is a lockfile, not a claim that every local tool is installed on every computer.
The engine is the how. The brief is the start.