Claude Code

Use this guide after Get started.

---

1. Enable Naro for Claude Code

Try for one session:

claude --plugin-dir ~/plugins/naro

Or install for ongoing use through your usual Claude Code plugin flow (local marketplace or the path your organisation provides).

Confirm:

Check	Expected
Plugin list	Naro enabled, no error tab
Agents list	Naro roles visible in context

If enable fails, stop and fix that before expecting summaries in chat.

2. Daily use

Type the request the way you always would:

add pagination to the /users list API (page + limit query params)

No special prefix. No shell wrapper.

What you should see early in the turn: a short work summary — goal, out of scope, and what must be true before send.

3. Skip Naro for a quick question

Start the message with ~:

~ what does this function do

Use this for one-line reads and “just look” questions.

4. Skills (optional)

When you want an explicit path:

Skill	When
Start	First message on a new or unwired project
Ship	You want issue → pull request language driven end to end
Design	Visual / screen work that needs design evidence

Exact slash names appear in your Claude Code / menu after the plugin loads.

5. When work is finished

Follow Prove & send. Claude Code will also refuse a push while named items are still open.

6. If nothing happens

1. Confirm the plugin is enabled.
2. Confirm you ran install in this repository.
3. See Troubleshooting.