--- description: Display information about this Claude Code setup - agents, commands, configuration, and capabilities allowed-tools: Read(*), Glob(*), Bash(ls:*) disable-model-invocation: false --- # Setup Info Command Display comprehensive information about your Claude Code configuration. ## Instructions Provide a detailed overview of the Claude Code setup for this project. 1. **Scan Configuration** - List all available agents in `.claude/agents/` - List all available commands in `.claude/commands/` - List all output styles in `.claude/output-styles/` - Check for CLAUDE.md project configuration - Identify configured MCP servers 2. **Read Project Configuration** - Read CLAUDE.md to show technology stack - Check `.claude/settings.json` for configuration - Identify project structure from CLAUDE.md 3. **Generate Report** ## Output Format ```markdown # Claude Code Setup Information ## Project Configuration ### Technology Stack [Read from CLAUDE.md - show languages, frameworks, testing tools] ### Project Structure [From CLAUDE.md - show directory organization] --- ## Available Agents 🤖 Specialized AI assistants for different tasks: ### [Agent Name] - [Description] **Use when**: [Trigger scenarios] **Capabilities**: [What it can do] **Tools**: [Available tools] [List all agents found in .claude/agents/] --- ## Available Commands ⚡ Slash commands for quick actions: ### /[command-name] - [Description] **Usage**: `/command-name [arguments]` **Purpose**: [What it does] [List all commands found in .claude/commands/] --- ## Output Styles 🎨 Communication style options: ### [Style Name] - [Description] **Best for**: [When to use] **Activate**: [How to enable] [List all output styles found in .claude/output-styles/] --- ## MCP Servers 🔌 Enhanced capabilities through Model Context Protocol: ### Configured MCP Servers - **serena**: Semantic code navigation and refactoring - **context7**: Up-to-date library documentation - **memory**: Project knowledge graph - **fetch**: Web content retrieval - **playwright**: Browser automation - **windows-mcp**: Windows desktop automation - **sequential-thinking**: Complex reasoning [Show which are actually configured based on settings.json or environment] --- ## Quick Start Guide ### For New Features 1. Use `/implement [description]` to create features 2. Use `/test [file]` to generate tests 3. Use `/review [file]` for code quality check ### For Understanding Code 1. Use `/explain [file]` for detailed explanations 2. Use `/analyze [path]` for metrics and analysis ### For Improvements 1. Use `/optimize [function]` for performance 2. Use `/scaffold [type] [name]` for boilerplate 3. Invoke agents: "Use the architect agent to design..." ### For Code Quality 1. Use `/review` before committing 2. Invoke security-analyst for security reviews 3. Use code-reviewer agent for thorough analysis --- ## Customization ### Adding New Commands 1. Create file in `.claude/commands/[name].md` 2. Use [`.COMMANDS_TEMPLATE.md`](.claude/commands/.COMMANDS_TEMPLATE.md) as guide 3. Add frontmatter with description and tools 4. Command becomes available as `/[name]` ### Adding New Agents 1. Create file in `.claude/agents/[name].md` 2. Use [`.AGENT_TEMPLATE.md`](.claude/agents/.AGENT_TEMPLATE.md) as guide 3. Define tools, model, and instructions 4. Invoke with: "Use the [name] agent to..." ### Configuring Technology Stack Edit [CLAUDE.md](../CLAUDE.md) Technology Stack section: - Update languages and frameworks - Define testing tools - Specify build commands - All agents/commands adapt automatically --- ## Directory Structure ``` .claude/ ├── agents/ # Specialized AI agents ├── commands/ # Slash commands ├── output-styles/ # Response formatting ├── settings.json # Configuration └── [other files] CLAUDE.md # Project tech stack config ``` --- ## Helpful Resources - **Templates**: Check `.AGENT_TEMPLATE.md` and `.COMMANDS_TEMPLATE.md` - **Documentation**: See `.claude/IMPLEMENTATION_COMPLETE.md` - **Analysis**: See `.claude/TEMPLATE_REVIEW_ANALYSIS.md` - **Official Docs**: https://docs.claude.com/en/docs/claude-code/ --- ## Support ### Getting Help 1. Ask Claude directly: "How do I...?" 2. Read template files for examples 3. Check CLAUDE.md for project conventions 4. Review agent/command markdown files ### Common Tasks - **Create tests**: `/test [file]` or use test-engineer agent - **Review code**: `/review [file]` or use code-reviewer agent - **Add feature**: `/implement [description]` - **Generate boilerplate**: `/scaffold [type] [name]` - **Explain code**: `/explain [file]` - **Analyze codebase**: `/analyze [path]` - **Optimize performance**: `/optimize [function]` --- **Setup Version**: 2.0.0 (Technology-Agnostic with MCP Integration) **Last Updated**: [Current date] ``` ## MCP Server Usage ### Serena MCP **Code Navigation**: - `list_dir` - Scan .claude directory for agents/commands - `find_file` - Locate configuration files - `get_symbols_overview` - Analyze configuration structure **Persistent Memory** (stored in `.serena/memories/`): - Use `read_memory` to include custom setup notes if stored - Use `list_memories` to show available project memories ### Memory MCP (Knowledge Graph) **Temporary Context**: Not needed for this informational command. ### Context7 MCP - Not needed for this informational command ## Notes This command provides a comprehensive overview of: - What capabilities are available - How to use them effectively - How to customize and extend - Where to find more information The information is dynamically generated based on actual files in the `.claude/` directory and CLAUDE.md configuration.