agentleFS
oaslanankaoaslananka/kicad-mcp-pro/.github/copilot-instructions.md

kicad-mcp-pro

Copilot instructions169 starsChanged 18 days agoMITView on GitHub

Follow the repository AGENTS.md router and the nearest scoped AGENTS.md for every change. Do not replace them with duplicated policy text. - Start in read-only mode; use KiCad MCP tools before local file transformations. - Never rewrite .kicadpcb or .kicadsch by shell/regex when a safe MCP mutation tool is unavailable. Ask for the required profile/tool instead. - Do not bypass branch protection, workflow gates, path checks, release guards, or manufacturing approvals. ERC/DRC is evidence, not human engineering signoff. - Load…

We split this copilot-instructions.md into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the repository AGENTS.md router and the nearest scoped AGENTS.md for every change.

    line 3
  2. Distinctive:

    Start in read-only mode; use KiCad MCP tools before local file transformations.

    line 6
  3. Very specific:

    Never rewrite .kicad_pcb or .kicad_sch by shell/regex when a safe MCP mutation tool is unavailable.

    line 7
  4. Distinctive:

    Do not bypass branch protection, workflow gates, path checks, release guards, or manufacturing approvals.

    line 9
  5. Distinctive:

    Verify scope and security with repository-native tests and policies.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

KiCad MCP Pro — GitHub Copilot entry point

Follow the repository AGENTS.md router and the nearest scoped AGENTS.md for every change. Do not replace them with duplicated policy text.

  • Start in read-only mode; use KiCad MCP tools before local file transformations.
  • Never rewrite .kicad_pcb or .kicad_sch by shell/regex when a safe MCP mutation tool is unavailable. Ask for the required profile/tool instead.
  • Do not bypass branch protection, workflow gates, path checks, release guards, or manufacturing approvals. ERC/DRC is evidence, not human engineering signoff.
  • Load only relevant skills from .agents/skills/; canonical source: skills/. Change canonical skills then run python scripts/sync_agent_skills.py --write.
  • Verify scope and security with repository-native tests and policies.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.