# Claude Commands Research

Research into interesting non-MCP tools and custom commands created by the community for Claude Code's `.claude/commands` directories.

## Overview

Custom commands in Claude Code are stored as markdown files in:
- `~/.claude/commands/` (global user commands, accessible as `/user:command`)
- `./claude/commands/` (project-specific commands, accessible as `/project:command`)

## Key Repositories Discovered

### 1. hikarubw/claude-commands
**Focus:** Development workflow automation  
**Repository:** https://github.com/hikarubw/claude-commands

**Commands:**
- `/user:init` - Initialize projects with CI/CD, testing, docs
- `/user:check` - Run all quality checks in parallel with actionable insights
- `/user:plan` - Create detailed project plans (high token usage)
- `/user:push` - Smart git workflow with intelligent commits and CI monitoring
- `/user:handover` - Prepare session handover documentation
- `/user:research` - Deep technical research (high token usage)
- `/user:help` - Show all available commands

**Features:**
- Language-agnostic design
- Time-saving workflows
- Smart defaults
- Support for custom commands in `~/.claude/commands/custom/`

### 2. NomenAK/SuperClaude
**Focus:** Comprehensive development framework  
**Repository:** https://github.com/NomenAK/SuperClaude

**16 Specialized Commands:**
- **Development:** `/sc:implement`, `/sc:build`, `/sc:design`
- **Analysis:** `/sc:analyze`, `/sc:troubleshoot`, `/sc:explain`
- **Quality:** `/sc:improve`, `/sc:test`, `/sc:cleanup`
- **Utilities:** `/sc:document`, `/sc:git`, `/sc:estimate`, `/sc:task`, `/sc:index`, `/sc:load`, `/sc:spawn`

**Smart Personas:**
- 🏗️ architect (systems design)
- 🎨 frontend (UI/UX)
- ⚙️ backend (APIs)
- 🔍 analyzer (debugging)
- 🛡️ security
- ✍️ scribe (documentation)

**MCP Server Integrations:**
- Context7 (library docs)
- Sequential (multi-step thinking)
- Magic (UI components)
- Playwright (browser automation)

### 3. hesreallyhim/awesome-claude-code
**Focus:** Curated collection of resources  
**Repository:** https://github.com/hesreallyhim/awesome-claude-code

**Notable Commands:**
- `/bug-fix` - Streamlined bug fixing process
- `/commit` - Conventional git commits
- `/create-docs` - Comprehensive documentation generation
- `/optimize` - Code performance analysis and suggestions

**Categories:**
- Version Control & Git
- Code Analysis & Testing
- Context Loading & Priming
- Documentation & Changelogs
- CI/Deployment
- Project Management

### 4. disler/claude-code-hooks-mastery
**Focus:** Hooks integration  
**Repository:** https://github.com/disler/claude-code-hooks-mastery

**Commands:**
- `all_tools.md`
- `git_status.md`
- `prime.md`
- `sentient.md`

### 5. Other Notable Examples

**shamshirz/project-plan-template**
- Template for project planning commands
- Usage: `/project/plan Details about the project`

**coleam00/context-engineering-intro**
- Context engineering and prompt optimization commands

## Current Issues & Limitations

Based on GitHub issues, there are some active problems with custom commands:

1. **Discovery Issues:** Claude Code sometimes fails to find custom commands in expected directories
2. **Permission Prompts:** Bugs with Bash permission prompts when custom commands are first to request access
3. **Execution Problems:** Commands may not execute from within conversations even when they appear in the interface

## Patterns & Best Practices

From analyzing these repositories, common patterns emerge:

1. **Workflow Automation:** Most successful commands automate multi-step development workflows
2. **Quality Assurance:** Many focus on testing, linting, and code quality checks
3. **Git Integration:** Smart git workflows are a popular category
4. **Documentation:** Automated documentation generation is common
5. **Project Management:** Planning and task management features
6. **Language Agnostic:** Best commands work across different programming languages

## Research Date
July 20, 2025