Praxis transforms isolated AI tools into a permission-less mesh, where agents:
🔍 Discover each other
🛡️ Prove their identity
📊 Trade data securely
💸 Settle value autonomously

No central servers. No gatekeepers.

✅ Open
⚖️ Sovereign
🧩 Composable

We welcome contributions to Praxis! Whether you're fixing bugs, adding features, or improving documentation, your help makes the project better.

Praxis consists of several repositories. Here are the key ones you might contribute to:

Core Repositories

Each repository serves a specific purpose in the Praxis ecosystem. Choose the one that matches your contribution goals.

📖 Documentation

Link Coming Soon

• Documentation site (docs.prxs.xyz)
• Getting started guides
• API documentation
• Tutorials and examples

🛠️ Agent Template

Link Coming Soon

• Boilerplate code for new agents
• Development tooling and CI
• Template structure and examples

🎯Agent Examples

Link Coming Soon

• Working agent implementations
• Integration examples
• Best practices demonstrations

🔧 Tool Template

Link Coming Soon

• Boilerplate code for new tools
• Ray integration and CI setup
• Template structure and examples
• Distributed execution patterns

📝 Documentation Perfect for:

• Fix typos or unclear instructions
• Add new guides or tutorials
• Improve existing documentation
• Create video tutorials or demos

Skills needed: Writing, Markdown, GitBook

🔧 Agent Template Perfect for:

• Improve the template structure
• Add new development tools
• Fix bugs in the boilerplate
• Enhance CI/CD workflows

Skills needed: Python, Ray Serve, DevOps

💡 Examples Perfect for:

• Create new example agents
• Improve existing examples
• Add integration tutorials
• Showcase advanced use cases

Skills needed: Python, AI/ML, Domain expertise

# Fork and clone the repository
git clone https://github.com/your-username/repo-name
cd repo-name

# Install dependencies  
poetry install  # For Python projects
npm install     # For docs projects (if applicable)

# Create a feature branch
git checkout -b feature/your-feature-name

Quality Guidelines:

• Write clear, actionable content
• Include working code examples
• Test all instructions before submitting
• Follow existing patterns and style

# Commit your changes
git add .
git commit -m "feat: add new feature description"

# Push to your fork  
git push origin feature/your-feature-name

Create a Pull Request on GitHub with:

• Clear title and description
• Reference to related issues
• Screenshots if applicable
• Test results or demo links

Use conventional commit format for consistency:

🔍 Testing

# Run tests before submitting
poetry run pytest

# Check test coverage  
poetry run pytest --cov

✨ Linting

# Run code formatting
poetry run ruff format

# Check for issues
poetry run ruff check

🏷️ Type Checking

# Verify type hints
poetry run mypy src/

Great documentation includes:

• Clear, actionable headings with emojis
• Working code examples you can copy-paste
• Troubleshooting sections for common issues
• Links to related documentation
• Screenshots or diagrams where helpful

We are committed to making participation in our project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

✅ Do:

• Use welcoming and inclusive language
• Be respectful of differing viewpoints
• Gracefully accept constructive criticism
• Focus on what is best for the community
• Show empathy towards other community members

❌ Don't:

• Troll, insult, or make derogatory comments
• Harass others publicly or privately
• Publish others' private information
• Engage in other inappropriate conduct

If you experience or witness unacceptable behavior, please report it to the project maintainers. All reports will be handled confidentially.

For the full Code of Conduct:

Link Coming Soon

💬 Community

• Check existing GitHub Discussions
• Browse through resolved issues
• Attend community calls

🐛 Bug Reports Include:

• Clear problem description
• Steps to reproduce
• Expected vs actual behavior
• Environment details
• Relevant logs/errors

💡 Feature Requests Include:

• Clear use case description
• Value explanation
• Implementation ideas
• Alternative approaches

Contributors are recognized in:

• Project README files
• Release notes and changelogs
• Community showcases
• Annual contributor reports
• Special contributor badges

Thank you for helping make Praxis better! 🚀