Skip to content

Getting started

factory-kit is a library of Claude Code skills, specialist subagents, and slash commands. It installs once into ~/.claude/ and auto-loads in every project — no per-repo setup. This page takes you from nothing to your first command.

One command. No config, no API key.

Terminal window
npx @nonlinear-labs/factory-kit

This symlinks the skills, subagents, and commands into ~/.claude/. It’s additive — it doesn’t overwrite your existing Claude Code settings.

Skills load at startup, so restart once after installing. That’s the whole setup.

Three surfaces, three ways to reach them:

  • Skills (14) auto-load on the factory-* namespace. You don’t invoke them by hand — they activate when the work matches (writing a form pulls in factory-forms, touching the schema pulls in factory-data-layer). Browse the skills →
  • Subagents (10) are callable through the Agent tool. Ask for one by role — “use the security-engineer to review this” — and Claude routes to it. Browse the subagents →
  • Slash commands (6) run from any project by typing / followed by the name. Browse the commands →

The fastest way to feel it working — get a standup view of your open work:

> /standup

You’ll get a tight, grouped read of what’s in flight, what’s in review, and the single best thing to pick up next. (Linear-backed commands like /standup, /entry, and /submit need a one-time /setup-linear to point at your team — run that first if prompted.)

Prefer to start from the build itself? Drop a vague ask and let the architect scope it:

Use the feature-architect to scope: "add an invite-by-email flow to the org settings page."

It returns a buildable spec and routes the work to the right specialist subagents — the intended entry point for any non-trivial feature.