100x-dev

---

Install

npm (any platform — macOS, Linux, Windows):

npm install -g 100x-dev && 100x-dev install

curl (macOS / Linux):

curl -fsSL https://raw.githubusercontent.com/rajitsaha/100x-dev/main/get.sh | bash
source ~/.zshrc   # or ~/.bashrc — activates the 100x-dev command

Either way, 100x-dev install clones the toolkit to ~/100x-dev and provisions your AI tools. The npm package is a thin launcher — the modules, hooks, and plugins live in that clone, which 100x-dev update keeps current.

Windows: plugin sync works, but native Windows module emit is being reworked (#54). For full module support today, install under WSL with either method above.

Set up a project:

cd your-project && 100x-dev init

Keep up to date:

100x-dev update                    # pull latest, then add/update/remove skills + plugins
100x-dev update --plugins-only     # refresh plugins only (repo already current)
npm install -g 100x-dev@latest     # (optional) upgrade the launcher itself

install and update are fully reconciling, not append-only — every run:

• adds newly shipped skills, slash commands, and curated plugins,
• updates changed ones in place, and
• removes skills, slash-command aliases, and 100x-dev-managed plugins that were deleted or merged upstream.

Your own hand-authored skills/commands and any plugins you enabled yourself are never touched. See docs/USAGE.md for details.

Cloned to a custom path? The default install lives at ~/100x-dev. If you cloned elsewhere, update your shell + Claude Code config — see Custom install location.

---

The pipeline

/understand → /context → /issue → /spec → /fix → /commit
                                                    ↓
              /techdebt ← /gate → /grill → /pr → /push → /release

Every /commit and /push runs a 5-point gate — tests, security, build, Docker, cloud. Nothing ships without passing.

---

What you get

---

Slash commands

The following 26 slash commands are available. Run them inside Claude Code. In Codex, use the generated repo skill by name instead, for example $gate, $commit, or /skills.

Lifecycle

Quality

Engineering

Data & Infrastructure

Documentation & Architecture

Auto-trigger skills (39)

These modules activate automatically when you describe a relevant task — no slash command needed.

---

How it works in your tool

Modules with tier: core (26) inline into single-file tools; tier: on-demand (39) appear as a compact index. In Claude Code, Cursor, and Codex, modules are also available as native skills/rules so full bodies load on demand. Claude Code plugins remain Claude-specific; use Codex /plugins for Codex-native plugins.

---

Common CI traps it fixes

npm install 404 inside Docker · useState(false) opacity-0 breaking Playwright · integration tests silently excluded from the gate. Full breakdown →

---

More

• Full usage guide — daily patterns, multi-project setup, CI templates, project config, troubleshooting
• Architecture — why modules replaced workflows + skills
• Token usage & optimization — audit your plugin/skill footprint and monitor token spend with the local dashboard
• Changelog · Roadmap · Issues

---