Verify plugin structure

[Utakata]

chore: Investigate deleted files and commented commands

This commit is the result of an investigation task. No code changes were made.

The investigation was conducted to address two user concerns:

1. The reason behind a large number of markdown files being deleted.
2. The existence of any unintentionally commented-out slash commands (# /...).

Findings:

1. Deleted Markdown Files: The mass deletion of files was an intentional part of the project's migration from a v3 architecture to the v4 Claude Code official plugin system, as documented in the README.md. The repository structure is consistent with the new v4 architecture.

2. Commented-out Commands: A thorough search was conducted across the entire repository for the # / pattern. All detected instances were found to be either placeholders for documentation purposes (e.g., # /sc:command-name) or markdown headings, not accidentally disabled commands.

Conclusion: The repository is in a clean and intentional state. The file deletions were part of a planned migration, and there are no inadvertently commented-out commands.

[mithun50]

Hey @Utakata what do you think about creating the new repo for this plugin

[Utakata]

@mithun50

Thanks for the review!

agree with your suggestion. Separating the repositories will indeed make it easier to manage compatibility and versioning between the framework and the plugin.

I'll proceed in that direction.

[mithun50]

@Utakata i sent you an invitation to repo go ahead and work on it feel free to reach if anything else

[Utakata]

@mithun50

Got it, thank you so much! I really appreciate you setting that up for me; it feels very supportive. I've accepted the invitation and am excited to work on the new repo.

[Eamll]

@mithun50 Is the new repo public? Can't contribute, but would like to star it so I get the notice when it's ready to use and we can migrate.

[mithun50]

@Eamll https://github.com/SuperClaude-Org/SuperClaude_Plugin

[BillChirico]

@Eamll https://github.com/SuperClaude-Org/SuperClaude_Plugin

Should we use this instead of the current repo? Looking to reinstall as my context usage is too high currently

[kazukinakai]

@BillChirico

Hi.
if you hot load context problem you can use my fork next branch
https://github.com/kazukinakai/SuperClaude_Framework/tree/next

And you be able to use also Plugin repo next also.
https://github.com/SuperClaude-Org/SuperClaude_Plugin/tree/next

I already fix that issues.

and I send PR this repo already.

[devstefancho]

I hope, plugin system is applied to this Repo.
I agree that this migration has too many changes but this is inevitable changes to support marketplace

[kazukinakai]

@Utakata @mithun50
Regarding plugins, I think the source of truth should be kept in this main Framework repository, and the plugin repository should be used to store the finished distribution files.

[kazukinakai]

@devstefancho I already confirmed working and fully tested on the next branch.

please check this repo

https://github.com/SuperClaude-Org/SuperClaude_Plugin/tree/next

[kazukinakai]

@Utakata @NomenAK @mithun50

If you can add me as a collaborator, I can refactor all features into the new plugin format.
I’ve already implemented and tested the plugin structure on the next branch — about 95 commits so far.
I’ve also been following the implementation method recommended by Claude Code and Anthropic, using the skill-graph structure.
I fully understand the whole flow now, so if you let me handle it, I can take care of all plugin development end-to-end.

[Utakata]

​@kazukinakai
​When I read your proposal to take on the full end-to-end refactoring into the new plugin format, and saw that you've already done extensive work on it, I felt a great sense of excitement and gratitude.
​This is because our team has a strong need for the project to evolve with high-quality contributions, and we deeply value collaboration and shared ownership.
​To move forward on this, I have just sent you a collaborator invitation. Would you be willing to accept it so you can begin integrating your work?
​We are genuinely looking forward to working with you.