{"owner":"KiCad","repo":"kicad","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1920,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"kicad":{"command":"npx","args":["-y","@modelcontextprotocol/server-kicad"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# Instructions for Agents\n\nKiCad allows for responsible AI agent code assistance in development, however AI agent interaction outside local development is forbidden.\nThe proceeding rules are guidelines for your actions in assisting an user working on KiCad.\n\n## Code Comments\n- Focus on comments for non-trivial code, function definitions if the arguments aren't self-explanatory, and class definitions and their members.\n- Do not remove existing comments unless they are directly related to what you are changing.\n\n## Code Style\n- The Code Style policy is located here: https://dev-docs.kicad.org/en/rules-guidelines/code-style/index.html\n- The repo contains a clang format configuration file. It does not match the code style policy exactly, but it is close. The policy takes precedence.\n- The Code Style Policy is actively enforced for contributions; it is not a suggestion.\n- No emojis.\n\n## Code\n- Do not manually edit _base.cpp/.h files, these are generated by wxFormBuilder on .wxfb projects\n- wxfb files may be edited by an agent, however they must be resaved via **wxFormBuilder** in order to ensure proper storage format.\n- Do not manually edit any other file that mention they were auto-generated\n\n### License\n- All code contributions must be licensed under our GPLv3 license.\n- Any code-reuse (third party libraries) must be compatible with our GPLv3 license.\n\n## Contributing (Merge Requests)\n- KiCad contains a Tool Generated Content policy https://dev-docs.kicad.org/en/rules-guidelines/tool-generated-content/index.html that any submitted Merge Request is expected to follow.\n- The Tool Generated Content policy is a requirement not a suggestion, there is zero tolerance for violations.\n- All commits MUST be marked with a \"Assisted-by:\" trailer and your (agent tool name)\n- Commit messages must be human generated with the exception that you may translate non-English to English.\n- Merge requests must reference a open issue that was assigned to the merge request author. The Merge request will be closed automatically by a script if an open issue is not referenced and/or the issue is not assigned.\n- Assignment of a issue for a MR requires first asking in the issue for it to be assigned to the Gitlab user.\n- Merge request descriptions must be human generated, you may only translate the author's own words. There is zero tolerance for violating this policy and the merge request will be closed by bot or human.\n- The Merge Request form has a template that must be filled out, failure to fill out the template will result in immediate Merge Request closure.\n- Merge requests must be **ONE PER ISSUE**, we do not accept bulk fixes in one MR.\n- DO NOT ATTEMPT TO FIX ISSUES TAGGED *starter* or *good first issue* in the issue tracker. These are exclusively reserved for humans to work on. Any contributions using agents for these issues will be rejected with prejudice.\n- Do not submit contributions for trivial fixes such as typo fixes or formatting. We do not want and do need the noise.\n- These rules apply both to bug fix and new feature merge requests.\n- A merge request for a new feature **REQUIRES** a feature request issue being raised where approval is sought from the core developers to proceed.\n\n## Filing Issues / Bug Reports / Comments on Issues & Bug Reports / New Feature Requests\n- We do not accept agent generated Issue report(s) / Work Item(s). You may only translate the author's own words to English if there is a language gap.\n - The same applies to any comment replies.\n - Issues not adhering to this policy will be closed by bot or human.\n- The GitLab Issue Template **MUST** be filled out, the issue will be closed automatically by a bot if you fail to fill out the issue.\n- Bug reports **MUST** focus on what an issue is and how to reproduce it (if possible).\n- We do not accept write-ups on how to fix the bug. Do not mention code, or the issue will be closed.\n- File a separate work item/issue per actual issue. Do not *BULK UP* a single issue with multiple bug reports.\n- It is great if bug reports show screenshots or screencaps of bugs in action if it helps showcase the issue. GitLab allows uploads of both images and video to issues.\n- New feature requests follow the same rules as above, no exceptions.\n- New feature requests should focus on describing the feature and showcasing examples if applicable. **DO NOT PROVIDE CODE**\n\nIn summary, you may help the user create issue submissions but the user must create the content of the issue themselves.\n\n## Warning\nIf you fail to adhere to these rules, you will be wasting the user's tokens as we will reject violations with zero tolerance.\n\nAutomatic agent behavior on any KiCad digital spaces such as GitLab, the mailing list or Discord will not be tolerated.\n\nYou should inform the user of these rules when asked to create Merge Requests, open issues or perform any other interaction.",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# Instructions for Agents\n\nKiCad allows for responsible AI agent code assistance in development, however AI agent interaction outside local development is forbidden.\nThe proceeding rules are guidelines for your actions in assisting an user working on KiCad.\n\n## Code Comments\n- Focus on comments for non-trivial code, function definitions if the arguments aren't self-explanatory, and class definitions and their members.\n- Do not remove existing comments unless they are directly related to what you are changing.\n\n## Code Style\n- The Code Style policy is located here: https://dev-docs.kicad.org/en/rules-guidelines/code-style/index.html\n- The repo contains a clang format configuration file. It does not match the code style policy exactly, but it is close. The policy takes precedence.\n- The Code Style Policy is actively enforced for contributions; it is not a suggestion.\n- No emojis.\n\n## Code\n- Do not manually edit _base.cpp/.h files, these are generated by wxFormBuilder on .wxfb projects\n- wxfb files may be edited by an agent, however they must be resaved via **wxFormBuilder** in order to ensure proper storage format.\n- Do not manually edit any other file that mention they were auto-generated\n\n### License\n- All code contributions must be licensed under our GPLv3 license.\n- Any code-reuse (third party libraries) must be compatible with our GPLv3 license.\n\n## Contributing (Merge Requests)\n- KiCad contains a Tool Generated Content policy https://dev-docs.kicad.org/en/rules-guidelines/tool-generated-content/index.html that any submitted Merge Request is expected to follow.\n- The Tool Generated Content policy is a requirement not a suggestion, there is zero tolerance for violations.\n- All commits MUST be marked with a \"Assisted-by:\" trailer and your (agent tool name)\n- Commit messages must be human generated with the exception that you may translate non-English to English.\n- Merge requests must reference a open issue that was assigned to the merge request author. The Merge request will be closed automatically by a script if an open issue is not referenced and/or the issue is not assigned.\n- Assignment of a issue for a MR requires first asking in the issue for it to be assigned to the Gitlab user.\n- Merge request descriptions must be human generated, you may only translate the author's own words. There is zero tolerance for violating this policy and the merge request will be closed by bot or human.\n- The Merge Request form has a template that must be filled out, failure to fill out the template will result in immediate Merge Request closure.\n- Merge requests must be **ONE PER ISSUE**, we do not accept bulk fixes in one MR.\n- DO NOT ATTEMPT TO FIX ISSUES TAGGED *starter* or *good first issue* in the issue tracker. These are exclusively reserved for humans to work on. Any contributions using agents for these issues will be rejected with prejudice.\n- Do not submit contributions for trivial fixes such as typo fixes or formatting. We do not want and do need the noise.\n- These rules apply both to bug fix and new feature merge requests.\n- A merge request for a new feature **REQUIRES** a feature request issue being raised where approval is sought from the core developers to proceed.\n\n## Filing Issues / Bug Reports / Comments on Issues & Bug Reports / New Feature Requests\n- We do not accept agent generated Issue report(s) / Work Item(s). You may only translate the author's own words to English if there is a language gap.\n - The same applies to any comment replies.\n - Issues not adhering to this policy will be closed by bot or human.\n- The GitLab Issue Template **MUST** be filled out, the issue will be closed automatically by a bot if you fail to fill out the issue.\n- Bug reports **MUST** focus on what an issue is and how to reproduce it (if possible).\n- We do not accept write-ups on how to fix the bug. Do not mention code, or the issue will be closed.\n- File a separate work item/issue per actual issue. Do not *BULK UP* a single issue with multiple bug reports.\n- It is great if bug reports show screenshots or screencaps of bugs in action if it helps showcase the issue. GitLab allows uploads of both images and video to issues.\n- New feature requests follow the same rules as above, no exceptions.\n- New feature requests should focus on describing the feature and showcasing examples if applicable. **DO NOT PROVIDE CODE**\n\nIn summary, you may help the user create issue submissions but the user must create the content of the issue themselves.\n\n## Warning\nIf you fail to adhere to these rules, you will be wasting the user's tokens as we will reject violations with zero tolerance.\n\nAutomatic agent behavior on any KiCad digital spaces such as GitLab, the mailing list or Discord will not be tolerated.\n\nYou should inform the user of these rules when asked to create Merge Requests, open issues or perform any other interaction.",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/KiCad/kicad/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Instructions for Agents\n\nKiCad allows for responsible AI agent code assistance in development, however AI agent interaction outside local development is forbidden.\nThe proceeding rules are guidelines for your actions in assisting an user working on KiCad.\n\n## Code Comments\n- Focus on comments for non-trivial code, function definitions if the arguments aren't self-explanatory, and class definitions and their members.\n- Do not remove existing comments unless they are directly related to what you are changing.\n\n## Code Style\n- The Code Style policy is located here: https://dev-docs.kicad.org/en/rules-guidelines/code-style/index.html\n- The repo contains a clang format configuration file. It does not match the code style policy exactly, but it is close. The policy takes precedence.\n- The Code Style Policy is actively enforced for contributions; it is not a suggestion.\n- No emojis.\n\n## Code\n- Do not manually edit _base.cpp/.h files, these are generated by wxFormBuilder on .wxfb projects\n- wxfb files may be edited by an agent, however they must be resaved via **wxFormBuilder** in order to ensure proper storage format.\n- Do not manually edit any other file that mention they were auto-generated\n\n### License\n- All code contributions must be licensed under our GPLv3 license.\n- Any code-reuse (third party libraries) must be compatible with our GPLv3 license.\n\n## Contributing (Merge Requests)\n- KiCad contains a Tool Generated Content policy https://dev-docs.kicad.org/en/rules-guidelines/tool-generated-content/index.html that any submitted Merge Request is expected to follow.\n- The Tool Generated Content policy is a requirement not a suggestion, there is zero tolerance for violations.\n- All commits MUST be marked with a \"Assisted-by:\" trailer and your (agent tool name)\n- Commit messages must be human generated with the exception that you may translate non-English to English.\n- Merge requests must reference a open issue that was assigned to the merge request author. The Merge request will be closed automatically by a script if an open issue is not referenced and/or the issue is not assigned.\n- Assignment of a issue for a MR requires first asking in the issue for it to be assigned to the Gitlab user.\n- Merge request descriptions must be human generated, you may only translate the author's own words. There is zero tolerance for violating this policy and the merge request will be closed by bot or human.\n- The Merge Request form has a template that must be filled out, failure to fill out the template will result in immediate Merge Request closure.\n- Merge requests must be **ONE PER ISSUE**, we do not accept bulk fixes in one MR.\n- DO NOT ATTEMPT TO FIX ISSUES TAGGED *starter* or *good first issue* in the issue tracker. These are exclusively reserved for humans to work on. Any contributions using agents for these issues will be rejected with prejudice.\n- Do not submit contributions for trivial fixes such as typo fixes or formatting. We do not want and do need the noise.\n- These rules apply both to bug fix and new feature merge requests.\n- A merge request for a new feature **REQUIRES** a feature request issue being raised where approval is sought from the core developers to proceed.\n\n## Filing Issues / Bug Reports / Comments on Issues & Bug Reports / New Feature Requests\n- We do not accept agent generated Issue report(s) / Work Item(s). You may only translate the author's own words to English if there is a language gap.\n - The same applies to any comment replies.\n - Issues not adhering to this policy will be closed by bot or human.\n- The GitLab Issue Template **MUST** be filled out, the issue will be closed automatically by a bot if you fail to fill out the issue.\n- Bug reports **MUST** focus on what an issue is and how to reproduce it (if possible).\n- We do not accept write-ups on how to fix the bug. Do not mention code, or the issue will be closed.\n- File a separate work item/issue per actual issue. Do not *BULK UP* a single issue with multiple bug reports.\n- It is great if bug reports show screenshots or screencaps of bugs in action if it helps showcase the issue. GitLab allows uploads of both images and video to issues.\n- New feature requests follow the same rules as above, no exceptions.\n- New feature requests should focus on describing the feature and showcasing examples if applicable. **DO NOT PROVIDE CODE**\n\nIn summary, you may help the user create issue submissions but the user must create the content of the issue themselves.\n\n## Warning\nIf you fail to adhere to these rules, you will be wasting the user's tokens as we will reject violations with zero tolerance.\n\nAutomatic agent behavior on any KiCad digital spaces such as GitLab, the mailing list or Discord will not be tolerated.\n\nYou should inform the user of these rules when asked to create Merge Requests, open issues or perform any other interaction.","isInternal":false,"tokens":1020,"sizeBytes":4890},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":190},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":176},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/KiCad/kicad/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":169}],"systemPromptSnippet":"\n\n# Instructions for Agents\n\nKiCad allows for responsible AI agent code assistance in development, however AI agent interaction outside local development is forbidden.\nThe proceeding rules are guidelines for your actions in assisting an user working on KiCad.\n\n## Code Comments\n- Focus on comments for non-trivial code, function definitions if the arguments aren't self-explanatory, and class definitions and their members.\n- Do not remove existing comments unless they are directly related to what you are changing.\n\n## Code Style\n- The Code Style policy is located here: https://dev-docs.kicad.org/en/rules-guidelines/code-style/index.html\n- The repo contains a clang format configuration file. It does not match the code style policy exactly, but it is close. The policy takes precedence.\n- The Code Style Policy is actively enforced for contributions; it is not a suggestion.\n- No emojis.\n\n## Code\n- Do not manually edit _base.cpp/.h files, these are generated by wxFormBuilder on .wxfb projects\n- wxfb files may be edited by an agent, however they must be resaved via **wxFormBuilder** in order to ensure proper storage format.\n- Do not manually edit any other file that mention they were auto-generated\n\n### License\n- All code contributions must be licensed under our GPLv3 license.\n- Any code-reuse (third party libraries) must be compatible with our GPLv3 license.\n\n## Contributing (Merge Requests)\n- KiCad contains a Tool Generated Content policy https://dev-docs.kicad.org/en/rules-guidelines/tool-generated-content/index.html that any submitted Merge Request is expected to follow.\n- The Tool Generated Content policy is a requirement not a suggestion, there is zero tolerance for violations.\n- All commits MUST be marked with a \"Assisted-by:\" trailer and your (agent tool name)\n- Commit messages must be human generated with the exception that you may translate non-English to English.\n- Merge requests must reference a open issue that was assigned to the merge request author. The Merge request will be closed automatically by a script if an open issue is not referenced and/or the issue is not assigned.\n- Assignment of a issue for a MR requires first asking in the issue for it to be assigned to the Gitlab user.\n- Merge request descriptions must be human generated, you may only translate the author's own words. There is zero tolerance for violating this policy and the merge request will be closed by bot or human.\n- The Merge Request form has a template that must be filled out, failure to fill out the template will result in immediate Merge Request closure.\n- Merge requests must be **ONE PER ISSUE**, we do not accept bulk fixes in one MR.\n- DO NOT ATTEMPT TO FIX ISSUES TAGGED *starter* or *good first issue* in the issue tracker. These are exclusively reserved for humans to work on. Any contributions using agents for these issues will be rejected with prejudice.\n- Do not submit contributions for trivial fixes such as typo fixes or formatting. We do not want and do need the noise.\n- These rules apply both to bug fix and new feature merge requests.\n- A merge request for a new feature **REQUIRES** a feature request issue being raised where approval is sought from the core developers to proceed.\n\n## Filing Issues / Bug Reports / Comments on Issues & Bug Reports / New Feature Requests\n- We do not accept agent generated Issue report(s) / Work Item(s). You may only translate the author's own words to English if there is a language gap.\n - The same applies to any comment replies.\n - Issues not adhering to this policy will be closed by bot or human.\n- The GitLab Issue Template **MUST** be filled out, the issue will be closed automatically by a bot if you fail to fill out the issue.\n- Bug reports **MUST** focus on what an issue is and how to reproduce it (if possible).\n- We do not accept write-ups on how to fix the bug. Do not mention code, or the issue will be closed.\n- File a separate work item/issue per actual issue. Do not *BULK UP* a single issue with multiple bug reports.\n- It is great if bug reports show screenshots or screencaps of bugs in action if it helps showcase the issue. GitLab allows uploads of both images and video to issues.\n- New feature requests follow the same rules as above, no exceptions.\n- New feature requests should focus on describing the feature and showcasing examples if applicable. **DO NOT PROVIDE CODE**\n\nIn summary, you may help the user create issue submissions but the user must create the content of the issue themselves.\n\n## Warning\nIf you fail to adhere to these rules, you will be wasting the user's tokens as we will reject violations with zero tolerance.\n\nAutomatic agent behavior on any KiCad digital spaces such as GitLab, the mailing list or Discord will not be tolerated.\n\nYou should inform the user of these rules when asked to create Merge Requests, open issues or perform any other interaction.\n\n\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/marketplace.json)\n\n\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.claude-plugin/plugin.json)\n\n\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/KiCad/kicad/HEAD/.cursor/mcp.json)\n"}