Get started

Do this once per application repository. Afterward you work inside your coding agent as usual.

Time: about ten minutes.
You need: Python 3.9+, git 2.30+, and the agent you already use (Claude Code, Codex, or Cursor).

---

Step 1 — Place the Naro package

Unpack or clone Naro to a stable path on your machine (for example ~/plugins/naro).
If you received a commercial archive from the portal, use that unpack path.

Keep that path handy — the next step points at it.

Step 2 — Open the project you will change

cd ~/projects/my-app

Use the real application repo, not the Naro package itself.

Step 3 — Wire the project

bash ~/plugins/naro/scripts/install.sh

Replace ~/plugins/naro with your actual package path.

What this does: adds shared project rules and the pieces your agent needs, without overwriting files you already have. If something already exists, install skips it and tells you.

Step 4 — Trim the rules file

Open AGENTS.md in the project root.
Delete stack sections that do not apply to this repository (for example remove Flutter guidance on a pure Node app).

Leaving the wrong stacks in place confuses the agent about which commands to run.

Step 5 — Run the first project check

bash scripts/dod_mark.sh

What you should see: either a clean result, or a clear list of what is still red. Fix or note those before you treat the project as ready.

Step 6 — Trust your agent surface

Pick one guide and complete its trust step — without trust, Naro will not participate in the chat:

You use	Next
Claude Code	Claude Code guide
Codex	Codex guide
Cursor	Cursor guide

Step 7 — Prove it with one sentence

In that agent, type a real request, for example:

add a coupon field to the cart

Pass signal: you see a short work summary (goal / what must be true) before deep coding starts — not a silent dive into random files.

If that never appears, open Troubleshooting. Do not keep working as if Naro were active.

---

What you do every day after this

1. Type the request in your agent (no special wrapper required).
2. Read the work summary and checklist.
3. Implement inside that scope.
4. Prove each open item, then send.

Commercial downloads: unpack once, run install.sh inside each consumer repository, keep license files as shipped. Account and downloads live in the Portal.