Proposal: Rename repository from SuperClaude_Framework to superclaude

[kazukinakai]

Proposal: Rename repository from SuperClaude_Framework to superclaude

Summary
I’d like to propose renaming the repository from SuperClaude_Framework to superclaude. This isn’t just a cosmetic change — it aligns the project with Python’s PEP 8 and PEP 503 naming conventions, strengthens its brand consistency, and avoids potential CI or packaging inconsistencies across tools like PyPI and GitHub Actions.

Background
I completely understand and respect the pride in the SuperClaude name and its current Kebab/Pascal style. It reflects the project’s identity and its roots. However, after reviewing the CI behavior earlier, it became clear that mixed-case naming introduces subtle inconsistencies across build tools, import paths, and distribution systems. Following PEP conventions isn’t about losing identity — it’s about making the brand technically unbreakable.

Why “superclaude” works better

1. Technical Consistency

   • PEP 8 and PEP 503 both recommend all-lowercase, normalized names for Python packages and modules.
   • PyPI automatically normalizes names to lowercase, so SuperClaude_Framework would still appear as superclaude-framework.
   • Unifying the GitHub repo name, PyPI package, and CLI entry point avoids confusion and broken imports.

2. Brand Simplicity & Strength

   • A single, clean identifier (superclaude) across CLI, docs, and PyPI feels modern and cohesive.
   • The word “Framework” can remain in the README tagline: “SuperClaude is an orchestration framework for Claude Code.”
   • Simplicity amplifies identity — not reduces it.

3. Practical Benefits

   • Works seamlessly for install commands and imports:
     pip install superclaude
     from superclaude import Agent
     superclaude --help
     gh repo clone SuperClaude-Org/superclaude
   • Improves discoverability on PyPI and GitHub search.
   • Keeps CI/CD scripts, badges, and documentation paths consistent.

Suggested Migration Plan

1. Rename the repository in GitHub Settings: SuperClaude_Framework → superclaude (GitHub will automatically redirect old URLs.)
2. I can prepare a follow-up PR to update README, badges, docs, and internal links. No code or logic changes — purely naming updates.
3. Optionally note the rename in the changelog or release notes.

Impact & Risks

• Minimal breaking risk — GitHub handles redirection automatically.
• External references (e.g., clone URLs) will remain functional.
• Improves consistency for future PyPI packaging and CLI tools.

Alternative Considerations

• Keeping SuperClaude_Framework: preserves heritage but risks long-term naming friction.
• Using superclaude-framework: still redundant and less elegant for PyPI/CLI.
• The shortest, cleanest, most scalable option remains: superclaude.

Request for Maintainers
If this makes sense, I’m happy to handle the follow-up PR to update all references after the rename. Open to feedback — especially if there are legacy reasons for the current naming convention.

[kazukinakai]

@mithun50 @NomenAK

[Kepners]

I like it.