A comprehensive boilerplate repository establishing best practices and conventions for team development with Claude AI assistance.
This repository serves as a foundation for projects that leverage Claude AI for development assistance while maintaining consistent code quality and team collaboration standards.
- Structured AI Context: Pre-configured
CLAUDE.mdfor optimal AI assistance - Development Guidelines: Clear conventions for code quality and architecture
- Team Workflows: Standardized processes for collaboration
- Testing Standards: Comprehensive testing requirements and patterns
- Git Conventions: Consistent commit messages and branching strategies
- Git
- Your preferred code editor
- Project-specific runtime (Node.js, Ruby, Python, etc.)
-
Clone the repository
git clone https://github.com/your-org/claude-boilerplate.git cd claude-boilerplate -
Copy to your project
cp -r claude-boilerplate/* your-project/ cd your-project
-
Customize for your project
- Update
CLAUDE.mdwith project-specific instructions - Modify
.github/templates for your workflow - Adjust
CONTRIBUTING.mdfor your team's processes
- Update
claude-boilerplate/
├── .claude/ # Claude AI configuration (local)
├── .github/ # GitHub templates and workflows
│ ├── ISSUE_TEMPLATE/
│ └── pull_request_template.md
├── docs/ # Documentation
│ ├── architecture/ # Architecture decisions
│ ├── workflows/ # Development workflows
│ └── guidelines/ # Coding guidelines
├── scripts/ # Utility scripts
│ ├── setup.sh # Initial setup script
│ └── validate.sh # Validation script
├── CLAUDE.md # AI assistant instructions
├── CONTRIBUTING.md # Contribution guidelines
├── CODE_OF_CONDUCT.md # Code of conduct
└── README.md # This file
- Clear Instructions: Always provide context in
CLAUDE.md - Incremental Development: Break work into small, testable chunks
- Test-First Approach: Write tests before implementation
- Code Review: Review AI-generated code before committing
The CLAUDE.md file contains:
- Project-specific conventions
- Technology stack details
- Testing requirements
- Architecture patterns
- Common commands
- Simplicity First: Choose boring, obvious solutions
- Incremental Progress: Small, working commits
- Test Coverage: All new code must have tests
- Clear Communication: Descriptive commits and documentation
- Create feature branch from
main - Implement with tests
- Ensure all checks pass
- Create pull request
- Code review and merge
- All new features must have tests
- Tests must pass before merging
- Coverage should not decrease
- Tests should be deterministic
# Project-specific test command
# Examples:
npm test # JavaScript/TypeScript
bundle exec rspec # Ruby
pytest # Python
go test ./... # GoFormat: type(scope): description
Types:
feat: New featurefix: Bug fixdocs: Documentationstyle: Formattingrefactor: Code restructuringtest: Testingchore: Maintenance
- Feature:
feature/description - Bugfix:
fix/description - Hotfix:
hotfix/description
- Architecture decisions in
docs/architecture/ - API documentation
- Setup instructions
- Deployment guides
- Never commit secrets or credentials
- Use environment variables for configuration
- Follow OWASP guidelines
- Regular dependency updates
Before merging:
- All tests passing
- Code review approved
- No linting errors
- Documentation updated
- Commit messages follow convention
Please see CONTRIBUTING.md for detailed contribution guidelines.
[Your License Here]
- Create an issue for bugs
- Use discussions for questions
- Check documentation first
This boilerplate is actively maintained by [Your Team Name]