forked from bchanot/claude
job3: B2 profile — document actual plugin/MCP toggling (BDR-008)
This commit is contained in:
@@ -116,8 +116,9 @@ bash "$HOME/.claude/lib/profile.sh" $ARGUMENTS
|
|||||||
- gstack skills still depend on `~/.claude/skills/gstack/bin/` for telemetry,
|
- gstack skills still depend on `~/.claude/skills/gstack/bin/` for telemetry,
|
||||||
update-check, learnings — script doesn't touch that infra. Disabled skills
|
update-check, learnings — script doesn't touch that infra. Disabled skills
|
||||||
are just hidden from Claude Code's scanner; the gstack repo stays installed.
|
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
|
- Profile changes DO toggle the managed Claude Code plugins (ui-ux-pro-max,
|
||||||
MCP servers — those are advisory only. The user runs `claude plugin
|
plugin-dev, pr-review-toolkit) and the `magic` MCP — see the Mechanism table
|
||||||
enable|disable` and `claude mcp add|remove` manually.
|
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.
|
- `set` is destructive in the sense that it disables non-listed gstack skills.
|
||||||
Use `apply` if the user wants additive behavior.
|
Use `apply` if the user wants additive behavior.
|
||||||
|
|||||||
Reference in New Issue
Block a user