Skip to main content
Start with the project you already have. The agent learns how it works, records the important rules, and uses those notes when making changes.

1. Connect Jig to the project

Follow installation and setup, using your existing project folder. Review and save what setup adds before starting a task.
Existing AGENTS.md and CLAUDE.md files are preserved. If the agent does not recognize Jig, ask it to “connect Jig to my AGENTS.md” and review the section it proposes to add. Keep the <!-- jig:begin --> and <!-- jig:end --> lines it puts around that section: with them, jig upgrade keeps the section current; without them, it stays at today’s version forever.

2. Check the agent’s understanding

Send to your agent
The agent writes project notes and shows them to you. Correct anything it misunderstood before asking it to build on that understanding. You should have: an agreed description of the project, the terms it uses, and its rules. If you already completed this during installation, continue to the next step.
jig-init reads manifests, entry points, the directory layout, and existing documents. It writes GLOSSARY.md, ARCHITECTURE.md, and RULES.md under .ai/knowledge/, and validates them with jig knowledge check. It asks about ambiguous boundaries and terms rather than inventing them.Setup detects verification profiles from the project’s manifests. Those profiles run your own tools; install the project’s dependencies before expecting the checks to run.

3. Bring in your existing rules

If your team already keeps architecture notes, coding conventions, or instructions for other AI tools, ask the agent to use them:
Send to your agent
Then say “Review the proposals.” The agent shows what it wants future sessions to follow. Accept what is right, ask for corrections, or reject it. Ordinary user guides do not need to become rules for the agent.
Proposed rules wait for your decision. They do not become instructions for future tasks just because the agent wrote them down. You can skip this step if you have no additional rules to adopt.

4. Start with a change you can check

Send to your agent
The agent chooses the steps the work needs, makes the change, and runs the available checks. For larger work it may first show a plan or ask you to approve a design. Before finishing: try the changed behaviour and ask what was tested, what was skipped, and whether anything still needs your attention.
A small first task helps you see how Jig fits your project before handing over a large feature.

Work with tasks

Continue work, give feedback, and see what is waiting for you.

Inspect or manage it yourself

Commands for task state, context, checks, and personal settings.