Contribution Guidelines

We welcome all contributions — from bug fixes to new features. Please follow these guidelines to keep the codebase clean and consistent.

Code Style

• Use TypeScript for all new files
• Follow the existing Tailwind CSS patterns
• Use Server Components by default, only add "use client" when necessary
• Keep components small and focused

Commit Messages

We follow the Conventional Commits standard:

feat: add leaderboard page
fix: resolve dark mode flicker on load
chore: update dependencies
docs: add contributing guidelines
refactor: simplify project card component

Pull Request Process

1. Fork the repository
2. Create a feature branch from main
3. Make your changes and test locally
4. Open a Pull Request with a clear title and description
5. Link any related issues
6. Wait for review — we try to respond within 48 hours

What We Accept

• ✅ Bug fixes
• ✅ Performance improvements
• ✅ New features discussed in issues first
• ✅ Documentation improvements
• ✅ Accessibility improvements

What We Don't Accept

• ❌ Breaking changes without prior discussion
• ❌ PRs without a clear description
• ❌ Unrelated changes bundled together

First time contributing? Look for issues labeled good first issue on our GitHub repository — they're perfect for getting started!