Contribute to CentenarianOS

Help build the personal operating system for executing multi-decade goals. All skill levels welcome.

View on GitHub

Ways to Contribute

Write Code

Implement features, fix bugs, improve performance, or refactor for better maintainability.

Frontend (Next.js, TypeScript, Tailwind)
Backend (Supabase, PostgreSQL)
Offline sync logic (IndexedDB)

Improve Documentation

Write tutorials, improve README, add code comments, or create architecture diagrams.

Setup guides for beginners
API documentation
Video tutorials or screencasts

Report Bugs

Find and report issues with detailed reproduction steps to help us fix problems faster.

Include error messages
Provide steps to reproduce
Note your browser/OS version

Suggest Features

Share ideas for new features or improvements to existing functionality.

Describe the problem it solves
Explain the user benefit
Add mockups if possible

Getting Started

1

Fork & Clone the Repository

Create your own fork and clone it to your local machine.

git clone https://github.com/YOUR_USERNAME/centenarian-os.git
2

Set Up Development Environment

Install dependencies and configure your local environment.

npm install
cp .env.example .env.local
# Add your Supabase credentials to .env.local
3

Create a Feature Branch

Never work directly on main. Create a descriptive branch name.

git checkout -b feature/add-nutrition-module
4

Make Changes & Test

Write clean, documented code. Run tests before committing.

npm run lint
npm run type-check
npm test
5

Submit a Pull Request

Push your branch and open a PR with a clear description of changes.

git push origin feature/add-nutrition-module

Contribution Guidelines

Code Standards

  • •TypeScript strict mode (no any without comment)
  • •JSDoc comments for all exported functions
  • •Test coverage for new features (80%+ for business logic)
  • •Accessible UI (keyboard navigation, ARIA labels)

Commit Messages

Use Conventional Commits format:

feat(planner): add milestone grouping
fix(auth): prevent duplicate signups
docs(readme): update installation steps

Security

  • •Never commit API keys or secrets
  • •Always validate user input
  • •Enable RLS on new database tables
  • •Report vulnerabilities to security@example.com

Full guidelines in CONTRIBUTING.md

Join Our Community

Contributors are the heart of open source. Every contribution—big or small—makes a difference.

Browse IssuesJoin Discussions