Use it

These guides are for people who use Agni on a design. You do not need to read any Go.

Each page here documents one feature on its own, so reach for them when you already know the name of the thing you need. If you are starting from nothing, the tutorials take one board from first read through to a house checklist gating CI, adding one capability at a time.

• Getting started takes you from install to your first check and its report.
• Concepts maps the ideas behind the tool back to bench intuition.
• Projects and designs lays out the two files that let every command find your config.
• Trying agni on your own boards runs a release from one compose file, walks the guided trial, and sends back a report that holds nothing from your design.
• Checks and reports runs the rule catalog and explains its findings.
• Comparing revisions diffs two revisions as a schematic redline.
• Beside an older comparison tool explains the rows where a semantic diff and a netlist-export spreadsheet disagree.
• Querying searches a design as data, with every answer cited.
• Asking through an LLM points Claude Code or any MCP client at agni, so a model asks the questions and every answer comes back as cited rows.
• Naming conventions encodes house style and checks it on every export.
• Interface profiles declares a bus’s signals and checks every design against it.
• Design intent declares what a board is supposed to contain, and catches it drifting.
• Datasheets compares a design against a part’s real limits.
• Running the server brings the viewer up with Docker over your mounted designs.
• CLI reference lists every command and flag.