# RepoKey Agent Rules

When this RepoKey customer package or its generated `AI_AGENT_START_HERE.local.md`
is being used, all Vivado operations must go through the RepoKey MCP server:

```text
repokey-client.cmd vivado serve
```

For a fresh rebuild from synthesis through bitstream, prefer the packaged
one-command flow:

```cmd
repokey-client.cmd flow --project-root <Vivado project directory> --synth-run synth_1 --impl-run impl_1 --reset
```

Use the individual RepoKey MCP tools such as
`mcp__repokey_vivado__start_session`, `mcp__repokey_vivado__run_synthesis`,
`mcp__repokey_vivado__run_implementation`, and
`mcp__repokey_vivado__generate_bitstream` when the user needs step-by-step
control, live session inspection, or repair of a specific run stage.

Do not bypass RepoKey with another Vivado MCP server, SynthPilot, direct
`vivado.bat`, `launch_runs`, `runme.bat`, or generated Vivado Tcl scripts
unless the user explicitly asks to debug outside RepoKey.

If any non-RepoKey Vivado control path is visible, ignore it for this package
and choose RepoKey. If RepoKey MCP is not connected, stop and report:

```text
RepoKey MCP not connected
```

Do not modify RTL, XDC, IP configuration, block designs, Tcl project settings,
or preprocessor macros to bypass synthesis, implementation, debug-core, timing,
or bitstream failures unless the user explicitly approves that design change.
