Thank you for considering contributing to Layered Shade! 🎉
# Fork the project on GitHub, then:
git clone https://github.com/YOUR-USERNAME/Layered-Shade.git
cd Layered-Shadenpm installgit checkout -b feature/my-new-feature- Follow the existing code style
- Add tests for new features
- Ensure all tests pass:
npm test
git add .
git commit -m "feat: add new feature X"
git push origin feature/my-new-featureGo to the original repository and open a PR describing your changes.
- ES6+ (modules, arrow functions, destructuring)
- Variable names in
camelCase - Classes in
PascalCase - JSDoc comments for public functions
- CSS Variables for colors and spacing
- BEM-like naming (when applicable)
- Mobile-first approach
We follow Conventional Commits:
| Type | Description |
|---|---|
feat: |
New feature |
fix: |
Bug fix |
docs: |
Documentation |
style: |
Formatting (no logic change) |
refactor: |
Code refactoring |
test: |
Adding/fixing tests |
chore: |
Maintenance tasks |
# Run tests
npm test
# Run in watch mode
npm run test:watch
# Run with coverage
npm run test:coverage- Check if the bug has already been reported in Issues
- If not, open a new issue with:
- Clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Screenshots (if applicable)
Open an Issue with the enhancement label describing:
- The problem the feature solves
- How you imagine it would work
- Alternatives considered
By contributing, you agree that your contributions will be licensed under the MIT License.