forge-profiles

Switch active Claude Code plugin profiles and preview install/remove diffs.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/dmedina-dev/dev-forge --skill forge-profiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-profiles
Source: https://github.com/dmedina-dev/dev-forge/tree/main/plugins/forge-profiles/skills/forge-profiles
Command: npx skills add https://github.com/dmedina-dev/dev-forge --skill forge-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code loads every installed plugin into the assistant context, which increases token use and noise before you start working. forge-profiles solves this by letting you define and switch between named plugin sets so only relevant plugins and MCP servers are active for the task at hand.

Core Features & Use Cases

  • Profile storage: Profiles are stored in .claude/settings.local.json under pluginConfigs["forge-profiles@dev-forge"].options.profiles so they remain personal and project-local.
  • Create, list, switch: Create profiles from the current configuration, list available profiles with descriptions, and switch profiles while previewing the diff of installs/removals.
  • Preserve runtime config: Switching computes diffs for plugins and mcpServers while preserving permissions, environment variables, and server definitions.
  • Use cases: Keep a lean "daily" set for everyday coding, a "plugin-dev" set for extension development, or a "review" set with only analysis tools.

Quick Start

Switch my active plugins to the "daily" profile and show the install/remove diff before I run /reload-plugins.

Frequently Asked Questions about forge-profiles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch active plugins in Claude Code to reduce unnecessary loaded context?

You can switch active plugins in Claude Code by defining named plugin profiles and toggling between them. This switches your work-mode context by computing plugin and mcpServer diffs, outputting an install/remove plan to apply with /reload-plugins.

How does plugin profile management work for Claude Code workflows?

Plugin profile management reads and updates .claude/settings.local.json under pluginConfigs to store named sets of active plugins. Switching profiles computes diffs of plugins and mcpServers while preserving permissions, environment variables, and server configurations.

Can I use Claude Code settings to keep a lean daily setup and a separate plugin development toolset?

Yes, you can create distinct profiles like a lean daily setup for everyday coding and a plugin-dev set for extension development. Profiles are stored locally in .claude/settings.local.json and can be switched to preview the exact install/remove diff before reloading.

What is the best way to manage per-project MCP servers and plugins without losing permissions?

The best way to manage per-project plugins is using profile switching that computes diffs for plugins and mcpServers. This preserves your permissions, environment variables, and server definitions while only loading relevant tools for your current context.

Why does Claude Code load every installed plugin into the assistant context by default?

Claude Code loads every installed plugin into the assistant context to ensure all tools are available, which increases token use and noise. Switching to named plugin profiles solves this by ensuring only relevant plugins and MCP servers are active for the task at hand.

Does switching plugin profiles affect my existing MCP server configurations?

Switching plugin profiles does not affect existing MCP server configurations. The profile switch computes the diff of plugins and mcpServers to install or remove while preserving your permissions, environment variables, and server definitions.