claude-code - 💡(How to fix) Fix [FEATURE] Allow granular skill enable/disable within plugins to reduce startup overhead [1 participants]

TL;DR

Implement a granular skill enable/disable settings option to allow selective skill loading, reducing startup overhead by loading only required skills.

Guidance

• Review the proposed JSON configuration format for enabling/disabling skills within plugins, ensuring it aligns with the existing plugin architecture.
• Consider implementing a default setting that loads all skills, with an option for users to override this setting based on their usage patterns.
• Analyze the impact of selective skill loading on plugin functionality and user experience to identify potential edge cases or compatibility issues.
• Evaluate the feasibility of automatically generating the skill enable/disable settings based on user behavior and usage patterns.

Example

{
  "plugins": {
    "superpowers": {
      "skills": {
        "executing-plans": true,
        "brainstorming": true,
        "writing-plans": true,
        "using-git-worktrees": false,
        "test-driven-development": false
      }
    }
  }
}

This example demonstrates the proposed JSON configuration format for enabling/disabling skills within the "superpowers" plugin.

Notes

The implementation of selective skill loading may require significant changes to the plugin architecture and loading mechanism. It is essential to carefully evaluate the potential impact on performance, functionality, and user experience.

Recommendation

Apply the proposed workaround by implementing a granular skill enable/disable settings option, as it has the potential to significantly reduce startup overhead and improve user productivity.