Menú
Quick reference for all nanostack commands. Shows available skills, what each one does, and how to use them. Triggers on /nano-help.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user asks about available workflow skills, wants an overview of the engineering workflow, or references "nanostack". Also triggers on /nanostack.
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
Orchestrate parallel agent sessions through a sprint. Coordinates task claiming, dependency resolution, and artifact handoff between independent agents. Triggers on /conductor, /sprint, /parallel.
Use when working near production, sensitive systems, or destructive operations. Activates on-demand safety hooks that block dangerous commands. Supports modes — careful (warn), freeze (block writes outside scope), unfreeze (remove restrictions). Triggers on /guard, /careful, /freeze, /unfreeze.
Use to list the open-source licenses of every dependency in this project, grouped by license family. Flags GPL or AGPL dependencies that may force the project itself to be open-source. Triggers on /audit-licenses.
Use to verify that code works correctly — browser-based testing with Playwright, native app testing with computer use, CLI testing, API testing, or root-cause debugging. Supports --quick, --standard, --thorough modes. Triggers on /qa.
| name | nano-help |
| description | Quick reference for all nanostack commands. Shows available skills, what each one does, and how to use them. Triggers on /nano-help. |
| concurrency | read |
| depends_on | [] |
| summary | Help and quick reference for nanostack skills. |
| estimated_tokens | 100 |
Show the user a concise overview of nanostack. No walls of text. Organized by what they want to do.
Print this directly:
nanostack
Make your AI agent think first.
What do you want to do?
Start a brand new project → /think (or /think --autopilot)
Add to a project that exists → /feature <what to add>
Already wrote code, check it → /review (then /security, /qa)
Ready to save / publish → /ship
First time using nanostack → /nano-run
Not sure where to start → /think (it helps you decide)
Reference — every command:
Getting started:
/nano-run First-time setup. Configures your project conversationally.
/nano-help You are here.
The sprint:
/think Challenge the scope before building.
/nano Plan the implementation. Files, steps, risks.
build You or the agent writes the code.
/review Two-pass code review. Scope drift detection.
/security OWASP Top 10 + STRIDE audit. Graded A-F.
/qa Test it. Browser, API, CLI, or debug.
/ship Create PR, verify CI, generate sprint journal.
Shortcuts:
/think --autopilot Full sprint. Think, plan, build, review, audit, test, ship.
/feature <description> Add a feature to an existing project with full sprint.
After shipping:
/compound Save what you learned. Future sprints find it automatically.
Safety:
/guard Block dangerous commands. /freeze locks edits to a scope.
Team:
/conductor Parallel sprints across multiple agents or terminals.
Modes (for /review, /security, /qa):
--quick Small changes. Only the obvious.
--standard Default. Normal work.
--thorough Auth, payments, infra. Flag everything.
Update:
/nano-update Pull latest version.
github.com/garagon/nanostack
If the user asks about a specific skill, invoke it: use Skill tool with the skill name. Don't explain the skill yourself — let the skill's own SKILL.md handle it.