SuperClaude/docs/developer-guide/documentation-index.md
kazuki nakai d5dfd7da21
refactor(docs): normalize documentation naming to lowercase for PEP8 compliance (#434)
* refactor(docs): rename directories to lowercase for PEP8 compliance

- Developer-Guide → developer-guide
- Getting-Started → getting-started
- Reference → reference
- Templates → templates
- User-Guide → user-guide
- User-Guide-jp → user-guide-jp
- User-Guide-kr → user-guide-kr
- User-Guide-zh → user-guide-zh

This change aligns with Python PEP8 package naming conventions.
All 43 files affected.

* refactor: rename root documentation files to lowercase

- CHANGELOG.md → changelog.md
- CODE_OF_CONDUCT.md → code_of_conduct.md
- CONTRIBUTING.md → contributing.md
- SECURITY.md → security.md

Aligns with Python package naming conventions (PEP8).
README files remain uppercase as per convention.

* refactor: move documentation files to docs/ for cleaner root

Moved OSS standard files to docs/:
- CHANGELOG.md → docs/CHANGELOG.md
- CODE_OF_CONDUCT.md → docs/CODE_OF_CONDUCT.md
- CONTRIBUTING.md → docs/CONTRIBUTING.md
- SECURITY.md → docs/SECURITY.md

Root now contains only essential files:
✓ README files (表紙: en, ja, kr, zh)
✓ LICENSE (法的要件)
✓ Build configs (pyproject.toml, setup.py, MANIFEST.in)
✓ VERSION

Rationale:
Cleaner root structure following modern Python project conventions.
All detailed documentation consolidated in docs/ directory.

* refactor: update documentation links after restructure

Auto-updated internal documentation links to reflect new structure:
- docs/ subdirectories now lowercase (PEP8)
- Root files moved to docs/
- All cross-references updated

This commit includes linter-generated link updates.

* chore(docs): keep OSS-standard uppercase root files (CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY)

* chore(docs): remove duplicated PR docs from repo root (moved under docs)

* docs: rename pm-agent-implementation-status.md -> PM_AGENT.md for clarity

* docs: update links to PM_AGENT.md after rename

---------

Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
2025-10-15 21:07:39 +05:30

12 KiB

SuperClaude Framework developer-guide Index

Document Navigation Guide

This index provides comprehensive access to all SuperClaude Framework development documentation, organized by topic and skill level for efficient information discovery.

Quick Navigation

For New Contributors: Start with Contributing Guide → Setup

For System Understanding: Begin with Technical Architecture Guide → Context Architecture

For Verification: Start with Verification Guide → Installation Check


Primary Documentation

📋 Contributing Context Files Guide

Purpose: Complete context file development and contribution guidelines
Target Audience: Framework contributors and context file developers
Length: ~1,000 lines focused on context file reality

Key Sections:

🏗️ Context Architecture Guide

Purpose: Understanding how context files work and are structured
Target Audience: Anyone wanting to understand or extend SuperClaude
Length: ~800 lines focused on context file patterns and Claude Code integration

Key Sections:

🧪 Verification & Troubleshooting Guide

Purpose: Verifying installation and troubleshooting context file issues
Target Audience: Users and maintainers
Length: ~500 lines focused on file verification and Claude Code integration

Key Sections:


Topic-Based Index

🚀 Getting Started

Complete Beginners:

  1. Contributing Guide → Setup - Environment setup
  2. Architecture Guide → Overview - Understanding context files
  3. Verification Guide → Installation Check - Basic verification

Environment Setup:

🏗️ Architecture & Design

Context File Architecture:

Component Development:

🧪 Verification & Quality

File Verification:

Troubleshooting:

🔧 Development Workflows

Context File Development:

Component Development:

🛠️ MCP Integration

MCP Configuration:

🚨 Support & Troubleshooting

Common Issues:

Support Resources:


Skill Level Pathways

🟢 Beginner Path (Understanding SuperClaude)

Week 1: Foundation

  1. Architecture Overview - What SuperClaude is
  2. Installation Verification - Check your setup
  3. Context File Architecture - Directory structure

Week 2: Basic Usage

  1. How Claude Code Reads Context - Processing sequence
  2. Common Issues - Troubleshooting basics
  3. Context File Guidelines - File standards

🟡 Intermediate Path (Contributing Context Files)

Month 1: Context Development

  1. Development Setup - Environment preparation
  2. Agent Context Structure - Domain specialists
  3. Command Context Structure - Workflow patterns

Month 2: Component Creation

  1. Adding New Agents - Domain specialist development
  2. Adding New Commands - Workflow creation
  3. File Validation - Context verification

🔴 Advanced Path (Framework Extension)

Advanced Understanding

  1. The Import System - Context loading mechanics
  2. Extending the Framework - Framework expansion
  3. MCP Server Configuration - External tool integration

Reference Materials

📚 Key Concepts

Framework Fundamentals:

  • Context-Oriented Configuration Framework
  • Agent Domain Specialists
  • Command Workflow Patterns
  • Mode Behavioral Modifications
  • MCP Integration Patterns

🔗 Cross-References

Development → Architecture:

Development → Verification:

Architecture → Verification:


Quality Standards

Documentation Accuracy

  • Technical Precision: All examples reflect SuperClaude reality (context files, not software)
  • Command Accuracy: Correct Python module execution paths and Claude Code context triggers
  • No Fiction: Removed all references to non-existent testing frameworks and performance systems

Content Focus

  • Context Files: Documentation centers on .md instruction files and Claude Code behavior
  • File Verification: Practical approaches to validating context file installation and structure
  • Real Workflows: Actual development processes for context file contribution

User Experience

  • Clear Progression: Skill-based learning paths from understanding to contribution
  • Practical Examples: Working context file examples and Claude Code integration
  • Support Integration: Clear guidance to help resources for real issues

Usage Guidelines

For Contributors

  1. Start with: Development Setup
  2. Context Development: Follow Context File Guidelines
  3. Validation: Use File Validation
  4. Support: Reference Getting Help

For Architects

  1. System Understanding: Context File Architecture
  2. Component Patterns: Agent and Command Structure
  3. Extension: Extending the Framework
  4. Integration: MCP Configuration

For Verification

  1. Installation Check: Installation Verification
  2. File Validation: Context File Verification
  3. Troubleshooting: Common Issues
  4. Diagnostics: Troubleshooting Commands

This comprehensive index reflects the reality of SuperClaude as a context-oriented configuration framework, focusing on practical context file development and Claude Code integration.