/nano-run — Start with a conversation

Configures your stack, permissions, and preferences. Run once per project.

What it does

/nano-run is a guided setup that asks you a few questions and writes the answers into your project config. After it runs, every other skill knows your stack, your testing preferences, and how much autonomy you want the agent to have.

Specifically, it:

  • Detects your project type from the repo (package.json, Cargo.toml, go.mod, etc.)
  • Asks about your preferred stack when there is ambiguity (e.g., Vitest vs. Jest)
  • Sets permission levels: can the agent auto-fix review issues, or should it always ask?
  • Runs any init scripts your project needs (dependency install, env setup)
  • Writes a .nanostack/config.json at the project root

What the conversation looks like

> /nano-run

Detected: Node.js project (package.json found)
  Framework: Next.js 14
  Package manager: pnpm
  Test runner: not configured

? What test runner do you want to use?
  1. Vitest (recommended for Vite/Next)
  2. Jest
  3. None for now
> 1

? How should I handle review issues?
  1. Auto-fix when confident, ask otherwise
  2. Always ask before changing code
  3. Fix everything silently
> 1

? Preferred intensity for /review and /security?
  1. Quick (fast, catches obvious issues)
  2. Standard (default, good balance)
  3. Thorough (slow, catches edge cases)
> 2

✓ Config written to .nanostack/config.json
✓ Dependencies installed (pnpm install)
✓ Ready. Try /think or /feature to start building.

When to run it again

You generally run /nano-run once and forget about it. But there are a few cases where running it again makes sense:

  • You switched frameworks (e.g., migrated from Create React App to Next.js)
  • You want to change your permission or intensity defaults
  • You cloned the project on a new machine and need to re-run init scripts
  • You added a new agent and want to verify it picks up the config

Running it again is safe. It detects the existing config and asks whether you want to update it or start fresh.

Adding features to an existing project

If your project is already set up and you want to add a feature, skip /nano-run and use /feature instead. It reads the existing config and jumps straight into planning without re-asking setup questions.

/feature Add a dark mode toggle to the settings page

/feature is covered in detail on the Workflows page.

Previous← First sprintNextWorkflows →