jterrazz-studio

The exact tool roster provisioned on a jterrazz machine — modern CLI replacements (fd, ripgrep, eza, bat, sd, dust, zoxide, difftastic), AI tooling (rtk, qmd, ollama, skills), dev apps and services (gh, lazygit, docker/orbstack, linear, notion). Activates at the start of shell work, when searching or listing files, processing text, diffing, or checking whether a tool or capability is available on this machine.

Use when organizing or restructuring a repository's documentation, skills, AGENTS.md/CLAUDE.md, README, or generated docs — where knowledge lives, what gets committed, corpus vs injection layers vs compiler, projections vs presentations.

Overview of the @jterrazz ecosystem — shared npm packages, project naming ({product}-{role}, package-*), required files, CI/CD workflows, testing and architecture conventions. Use when working on any jterrazz project, choosing a package, scaffolding decisions, or understanding how the stack composes.

Scaffolds a new @jterrazz project with all conventions — package.json, tsconfig, Makefile, CI workflows, linting. Use when creating a new app or library from scratch.