From 28ce7325dd80487b0ba7f86200d98304cac74e40 Mon Sep 17 00:00:00 2001 From: Bastien Chanot Date: Mon, 6 Jul 2026 16:54:08 +0200 Subject: [PATCH] =?UTF-8?q?job3:=20B2=20profile=20=E2=80=94=20document=20a?= =?UTF-8?q?ctual=20plugin/MCP=20toggling=20(BDR-008)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- skills/profile/SKILL.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/skills/profile/SKILL.md b/skills/profile/SKILL.md index 9bba572..e986809 100644 --- a/skills/profile/SKILL.md +++ b/skills/profile/SKILL.md @@ -116,8 +116,9 @@ bash "$HOME/.claude/lib/profile.sh" $ARGUMENTS - gstack skills still depend on `~/.claude/skills/gstack/bin/` for telemetry, update-check, learnings — script doesn't touch that infra. Disabled skills are just hidden from Claude Code's scanner; the gstack repo stays installed. -- Profile changes do NOT toggle Claude Code plugins (ui-ux-pro-max, etc.) or - MCP servers — those are advisory only. The user runs `claude plugin - enable|disable` and `claude mcp add|remove` manually. +- Profile changes DO toggle the managed Claude Code plugins (ui-ux-pro-max, + plugin-dev, pr-review-toolkit) and the `magic` MCP — see the Mechanism table + above (BDR-008). Anything outside that managed set stays manual: + `claude plugin enable|disable`, `claude mcp add|remove`. - `set` is destructive in the sense that it disables non-listed gstack skills. Use `apply` if the user wants additive behavior.