Hardware agent tooling: how the pieces fit
Follow the tool family from runtime and review guidance to simulation, synthesis, and workflow automation.
The problem
Hardware tooling spans containers, editor environments, review rubrics, individual operations, CI, and orchestration. A collection of repository names does not explain which piece to use first.
What I built
I organized EDA MCP servers, agent instruction packs, runtime images, a starter CLI, and workflow tools. This hub explains their relationships and includes a FIFO review → simulation → synthesis walkthrough.
Usable tool
Who it is for: Engineers choosing hardware-agent tools and readers evaluating the portfolio.
First task: Follow the small FIFO walkthrough to see RTL review, simulation, and synthesis together.
What you can produce: A map of the tool family, a recorded example, and links to individual tools.
Current scope: A documentation hub with example transcripts; each tool is installed and maintained in its own repository.
Start with the example Source and documentation Step-by-step tutorials
A first useful result
Start with the scaffold for a first simulation, use one MCP server for a specific operation, or read the FIFO walkthrough. The tutorial adds smaller consecutive exercises and a real MCP SDK client that needs no LLM account.
Evidence and limits
Each tool keeps its own code, checks, and releases. The hub transcripts illustrate a workflow; fresh execution and toolchain versions establish a result for your input. The complete directory distinguishes usable tools from exercises and architecture plans.