Skip to content

Your first /n45

Once installed, open your IDE and run /n45 in the chat. The picker will show four commands:

/n45
/n45 Resume work or show project status
/n45-feat Build a new feature
/n45-fix Investigate and fix a bug
/n45-status See the current state of N45 in this project
  1. Type /n45 in the chat input
  2. Claude Code opens its slash-command picker
  3. Select /n45 and press Enter
  1. Type /n45 in the chat panel
  2. Cursor shows the command in its picker
  3. Press Enter

What happens on the first run

N45 wakes up and inspects your project:

  • Reads your package.json, go.mod, Cargo.toml, pyproject.toml, etc.
  • Detects languages, frameworks, and tooling
  • Generates four foundational documents inside .n45/docs/:
Document What it contains
STACK Language, runtime, framework, build tooling
PATTERNS Architectural conventions found in your code
PROJECT Domain overview, modules, entry points
RUNBOOK How to start, test, and deploy

This first run takes 30–60 seconds. Subsequent runs are instant — N45 just reads the existing documents.

What to do next

After the initial analysis, N45 tells you the project is ready and shows what's possible. Three common entry points:

Command When to use
/n45-feat Build a new feature or improvement
/n45-fix Investigate a bug or unexpected behavior
/n45-status See current state — open work, pending validation, etc.

Plain /n45 later

After the initial setup, plain /n45 resumes whatever you had in progress. If there's nothing in progress, it tells you what's possible next.

Try a small feature

With your project open, type something like:

/n45-feat add a health check endpoint

N45 will ask clarifying questions, propose a plan, and then either ship the change directly (for small changes) or build a full spec and roadmap (for larger ones). You stay in control at every step.