Overview
Everything Claude Code is a community resource. We welcome contributions of agents, skills, hooks, commands, and improvements. Repository: github.com/affaan-m/everything-claude-codeWhat We’re Looking For
Agents
New agents that handle specific tasks:- Language-specific reviewers (Python, Go, Rust, C++)
- Framework experts (Django, Rails, Laravel, Spring, NestJS)
- DevOps specialists (Kubernetes, Terraform, CI/CD, Docker)
- Domain experts (ML pipelines, data engineering, mobile, embedded)
Skills
Workflow definitions and domain knowledge:- Language best practices
- Framework patterns
- Testing strategies
- Architecture guides
- Domain-specific knowledge
Hooks
Useful automations:- Linting/formatting hooks
- Security checks
- Validation hooks
- Notification hooks
- Custom tooling integration
Commands
Slash commands that invoke useful workflows:- Deployment commands
- Testing commands
- Code generation commands
- Analysis commands
Quick Start
Contributing Skills
Directory Structure
SKILL.md Template
Skill Checklist
- Focused on one domain/technology
- Includes practical code examples
- Under 500 lines
- Uses clear section headers
- Tested with Claude Code
- No sensitive information (API keys, paths)
Example Skills
| Skill | Purpose |
|---|---|
coding-standards/ | TypeScript/JavaScript patterns |
frontend-patterns/ | React and Next.js best practices |
backend-patterns/ | API and database patterns |
security-review/ | Security checklist |
Contributing Agents
File Location
Agent Template
Agent Fields
| Field | Description | Options | |-------|-------------|---------|| |name | Lowercase, hyphenated | code-reviewer |
| description | Used to decide when to invoke | Be specific! |
| tools | Only what’s needed | Read, Write, Edit, Bash, Grep, Glob, WebFetch, Task |
| model | Complexity level | haiku (simple), sonnet (coding), opus (complex) |
Agent Checklist
- Clear, specific description
- Minimal tool set (only what’s needed)
- Appropriate model selection
- Well-defined boundaries
- Includes examples
- Tested with Task tool
Example Agents
| Agent | Purpose | |-------|---------|| |tdd-guide.md | Test-driven development |
| code-reviewer.md | Code review |
| security-reviewer.md | Security scanning |
| build-error-resolver.md | Fix build errors |
Contributing Hooks
File Location
Hook Types
| Type | Trigger | Use Case |
|---|---|---|
PreToolUse | Before tool runs | Validate, warn, block |
PostToolUse | After tool runs | Format, check, notify |
SessionStart | Session begins | Load context |
Stop | Session ends | Cleanup, audit |
Hook Format
Matcher Syntax
Hook Checklist
- Matcher is specific (not overly broad)
- Includes clear error/info messages
- Uses correct exit codes (
exit 1blocks,exit 0allows) - Tested thoroughly
- Has description
- Cross-platform compatible (use Node.js, not bash)
Contributing Commands
File Location
Command Template
Command Checklist
- Clear description
- Usage examples
- Defined workflow
- Expected output documented
- Tested with Claude Code
Example Commands
| Command | Purpose | |---------|---------|| |tdd.md | TDD workflow |
| code-review.md | Review code changes |
| plan.md | Implementation planning |
| e2e.md | E2E testing |
Pull Request Process
1. PR Title Format
Use conventional commits:2. PR Description Template
3. Review Process
- Maintainers review within 48 hours
- Address feedback if requested
- Once approved, merged to main
- Contribution added to next release
Guidelines
Do
- Keep contributions focused and modular
- Include clear descriptions
- Test before submitting
- Follow existing patterns
- Document dependencies
- Use cross-platform code (Node.js over bash)
Don’t
- Include sensitive data (API keys, tokens, paths)
- Add overly complex or niche configs without discussion
- Submit untested contributions
- Create duplicates of existing functionality
- Use platform-specific code (bash, PowerShell)
File Naming
- Use lowercase with hyphens:
python-reviewer.md - Be descriptive:
tdd-workflow.mdnotworkflow.md - Match name to filename
Testing Your Contribution
For Skills
For Agents
For Hooks
Documentation
If your contribution requires documentation updates:- Update README.md if adding new component type
- Update relevant skill/agent/hook README if modifying existing
- Add examples to CONTRIBUTING.md if introducing new pattern
Getting Help
Questions?
- GitHub Issues: github.com/affaan-m/everything-claude-code/issues
- GitHub Discussions: github.com/affaan-m/everything-claude-code/discussions
- X/Twitter: @affaanmustafa
Ideas for Contributions
- Language-specific skills: Rust, C#, Swift, Kotlin, Ruby
- Framework-specific configs: Rails, Laravel, FastAPI, NestJS, Phoenix
- DevOps agents: Kubernetes, Terraform, AWS, Docker, CI/CD
- Testing strategies: Different frameworks, visual regression, load testing
- Domain-specific knowledge: ML, data engineering, mobile, embedded, gaming
Recognition
Contributors are recognized in:- README.md contributors section
- Release notes
- GitHub contributors page
- Special thanks in documentation
Thank you for contributing! Let’s build a great resource together.