tjforge
A skill for Claude Code · MIT

Decide once. Build the same way.

tjforge writes your project's engineering contract on day one, then every Claude Code session follows it: same stack rules, same design brief, the right model for each job.

Sonnet 5.5 leadsOpus 5.5 builds the risky partsFable 5.2 on callno Co-Authored-By
01 / How it works

One command. Then it just holds.

Run /tjforge in any repository. It asks almost nothing in an existing codebase, because detection already answered it.

i.

Detect

Reads the manifest, lint and type config, tests, UI signals and git history. Your existing conventions win over any default.

ii.

Write the contract

docs/PROJECT-PROFILE.md: system design, coding standards, the exact verify commands, git rules. Every line is tagged detected, user or default.

iii.

Pick a design direction

UI projects get three genuinely different directions: palette, type, layout and a motion signature. You choose; it lands in DESIGN.md. No centered-hero-plus-three-cards.

iv.

Install the enforcement

Model-pinned subagents, attribution off, a commit hook, and a short block in CLAUDE.md, so plain sessions follow the contract too. Re-running syncs; your edits are never overwritten.

your-project/ ├── CLAUDE.md # tjforge block ├── DESIGN.md # design brief ├── docs/ │ ├── PROJECT-PROFILE.md # the contract │ └── worker-brief.md # what workers read ├── .claude/ │ ├── settings.json # attribution off │ ├── tjforge.lock.json # protects your edits │ ├── tjforge/quiet-test.sh # quiet test output │ └── agents/ │ ├── tj-builder.md # Sonnet · low │ ├── tj-implementer.md# Opus · medium │ ├── tj-reviewer.md # Opus · high │ ├── tj-architect.md # Fable · on call │ └── tj-scout.md # Haiku · trial └── .githooks/ └── commit-msg # strips trailers

Plain files you can read, edit and commit.

Nothing hidden, no service to sign up for. The contract is Markdown, the agents are Markdown, the installer is one Python script with a --check mode.

Commit them and the rules travel with the repository. Change tjforge once and every project picks up the update the next time you call /tjforge there.

02 / Model routing

The cheapest model that gets it right the first time.

Pick a request and watch where it goes. Sonnet does most of the work, Opus takes only the risky part, and Fable is an advisor you call, not the lead. A wrong cheap attempt costs more than one correct expensive one; an expensive model on mechanical work is waste.

Main session
Inline
no agent
Sonnet 5.5
Fill
tj-builder · low
Opus 5.5
Build
tj-implementer · medium
Fable 5.2
Advise
tj-architect · on call
Haiku 5.5
Scout
tj-scout · runs tests
Lead
Check
risky diff, cheapest check
Opus 5.5
Review
tj-reviewer · high
You
Report
what ran, what didn't
TierModel · effortTakes
FillSonnet 5.5 · lowThe default worker, and the lead of long builds. Anything that copies a named pattern: routes, screens, tests, e2e specs, docs, config
BuildOpus 5.5 · mediumOnly the risky part: schema, access rules, money, concurrency, a new provider interface, an unknown-cause bug, expressive UI
ReviewOpus 5.5 · highIndependent pass on risky diffs, given the diff, not the conclusion. Ranks findings, skips style
AdviseFable 5.2 · highOn call: a ruling when a worker is blocked, a root cause Opus missed, a trade-off you ask about. 300 words, then back
ScoutHaiku 5.5 · lowTrial tier. Read-only lookups and test runs through the quiet wrapper
Inlinecurrent sessionOne file, about 20 lines, obvious. Delegating would cost more than doing it
03 / Long builds

Many tasks. Short sessions.

A build of more than five tasks keeps its plan and progress in files, not in one long chat. Tasks run in groups of two to four, each group with a fresh Sonnet lead. In the Claude desktop app, every group is its own chat in the sidebar. Inside it, each task goes to one cheap worker.

Sonnet leads. one group, one fresh chatstate in resume.md, not the chat tj-implementerOpus 5.5 · medium · backend task tj-builderSonnet 5.5 · low · screen task tj-scoutHaiku 5.5 · low · test run resume.mdthen a fresh chat
One task per worker

Each worker reads a 60-line brief and its own task, has a hard budget, and stops at a clean state instead of asking.

Features split in two

The backend task goes to Opus, the screen that calls it to Sonnet. Two workers never edit the same file.

Tests that stay quiet

Workers run only their own tests, through a wrapper that prints one line on a pass. Full suites run once per group.

04 / Git history

Your name on your commits. Only yours.

Two layers, so it holds whichever tool writes the commit.

1
Off at the source

.claude/settings.json sets attribution to empty, so Claude Code never adds the trailer or the pull-request footer.

2
Stripped by a hook

.githooks/commit-msg removes Co-authored-by, "Generated with Claude Code / Cursor" and Made-with: Cursor before the commit is written. Chains into husky or lefthook instead of replacing them.

Local commits only. Commits made in the cloud, in GitHub's web editor or with --no-verify skip local hooks.

05 / Fit

Where it earns its keep.

Good fit

  • New projects with Claude. Stack, architecture and design decided before the first file.
  • Inherited codebases. Conventions written down, so Claude stops "improving" them.
  • Landing pages and brand sites. A specific design direction instead of a template.
  • Product apps and dashboards. Tokens, consistent states, motion only as feedback.
  • Long or multi-session work. Decisions persist; you stop re-explaining.
  • Large features. Planned, built in parallel, risky parts reviewed.

Not worth it

  • One-off scripts. Just ask Claude.
  • Throwaway prototypes. Plain Claude Code is faster.
  • Repos where you can't commit .claude/. Keep rules in your personal CLAUDE.md.
  • Pairing with human co-authors. Edit the hook first; it strips every Co-authored-by line.
06 / Install

Thirty seconds, then every project.

Needs Claude Code, git, bash and python3. macOS and Linux ship the last three.

git clone https://github.com/tjthouhid/tjforge.git ~/.claude/skills/tjforge

Start a new Claude Code session. /tjforge is now available in every project.

Then, in a project
  1. Open it in Claude Code and pick Sonnet 5.5 (Opus 5.5 for a build that is mostly schema, money or access rules). Medium effort.
  2. Run /tjforge init. Accept the summary, pick a design direction if it has a UI.
  3. If the project had no .claude/agents folder, start a new session so the agents load.
  4. Work normally. "Add a booking page." The session hands each task to the cheapest agent that can do it, and asks Fable only for rulings.

Every command

Type these in Claude Code. Every run except check first syncs the project with the latest skill, and prints nothing when it was already current.

CommandWhat it doesWhen
In Claude Code
/tjforge initDetects the stack, drafts the contract, asks you to confirm once, proposes design directions for UI projects, installs agents, settings, hook and the CLAUDE.md block. Plain /tjforge does this in a project that has no profile yet.Once per project
/tjforge <task>Does a task under the contract with model routing, e.g. /tjforge add a booking page. Plain requests follow the contract too, but don't sync first.Everyday work
/tjforge designRedoes only the design brief: three new directions, then rewrites DESIGN.md.Changing the look
/tjforge syncBrings agents, hook, settings and the CLAUDE.md block up to date. Never touches your profile or DESIGN.md, and skips files you edited.After updating tjforge, or in a fresh clone
/tjforge resume <dir>Picks up a multi-task build from its resume.md in a fresh session.Next group of a long build
/tjforge checkReports what is installed, missing, outdated or edited. Changes nothing.Anytime
In a terminal
git -C ~/.claude/skills/tjforge pullUpdates the skill itself.When a new version ships
python3 ~/.claude/skills/tjforge/scripts/install.pySame as /tjforge sync, without opening Claude Code. Run it from the project folder.Scripts, CI, new clones
… install.py --checkReport only. Exits 1 if anything is missing, outdated or edited.CI checks
… install.py --quietPrints nothing when everything is already in sync.Loops over many projects
… install.py --forceReplaces managed files even if you edited them in the project.Only when you want the template back
git config core.hooksPath .githooksTurns on the commit hook in a fresh clone (the installer also does this).Once per clone

If it saves you
an afternoon, star it.

Stars help other people find it. Issues and pull requests are welcome too: a better rule, a detector for your stack, a sharper agent brief.

07 / Who made it

Made by

Senior software engineer and founder · London, UK

Tj builds secure, scalable web platforms end to end in Laravel, Next.js and NestJS, and has shipped for the web since 2013. Tj also founded TheCreativex, the studio behind Lokstack. More work, writing and contact details are on tjthouhid.me.