dotnet-init

Wiring dotnet-toolkit into a project

Installing this plugin (/plugin install, or --plugin-dir) makes its MCP tools available. It does not make Claude prefer them — nothing tells a fresh session in a consuming repo that Grep and Read give wrong answers on C#, or that validate_patch is the write path, or that the plugin ships coding standards at all. A plugin cannot ship a .claude/rules/ file the harness auto-loads; only a repo's own .claude/rules/ gets scanned, and a plugin has no manifest field to register one. This skill writes that guidance into a target repo, additively, and only with explicit approval.

This skill does not touch the repo's CLAUDE.md. Per Claude Code's documentation (code.claude.com/docs/en/memory), .claude/rules/ is discovered and loaded independently of CLAUDE.md — rules are not appended into that file at runtime, they are a separate context injection. The project's own CLAUDE.md — its architecture, commands, and conventions, written and owned by the project — is left alone entirely.

Be honest with the user about the loading mechanics. A paths:-scoped rule fires only when the built-in Read touches a matching file — and here .cs contact goes through the MCP tools or is blocked by the guards, so paths: ["**/*.cs"] would almost never load. Worse, it does not reliably suppress either: the read guard deliberately allows Read on .cs files no project compiles, so such a rule fires unpredictably rather than on demand. (Earlier versions of this skill shipped standards as path-scoped rules for exactly this reason, and it was wrong both ways.)

So: one file is copied, dotnet-index.md, carrying no paths: and therefore always-loaded — which is why it is kept short. It costs tokens in every session, and is inherited by every subagent with no opt-out, so a parallel review pays it once per instance. The coding standards are not copied at all: they live at ${CLAUDE_PLUGIN_ROOT}/standards/ and are read by explicit path, so a consuming repo is always on the current versions and has nothing to refresh. Rules load alongside CLAUDE.md at the same priority — never tell the user they "override" anything. Actual enforcement is the plugin's PreToolUse hooks, which travel with the plugin and need no per-repo setup.

Do not skip the approval step under any circumstances, even if the user's request sounded like a green light to "just do it." These files change how every future session in that repo behaves; show the exact content and wait for a yes.