Quality Bar (Read Before Contributing)
We maintain a high quality bar. PRs that meet any of the following criteria will be closed without review:- Generic/project-unrelated content — e.g. “code optimization guides,” “best practices checklists,” or boilerplate docs that could apply to any repo
- AI-generated filler — bulk-generated content with no project-specific substance
- No linked issue — all PRs must reference an open issue or a clear gap in the project
- Untested changes — if you can’t demonstrate it works, don’t submit it
- Drive-by contributions — contributors with no prior engagement (issues, discussions, or meaningful context) submitting unsolicited docs or refactors
Before You Open an Issue
Ask Athena first. That’s what it’s built for.Most questions, troubleshooting, and “how do I…” queries can be answered by your own Athena agent. Try asking it directly:
- “How do I get a Gemini API key?”
- “How do I write a protocol?”
- “How do I set up Supabase?”
- “I’m getting [error]. Can you help me fix it?”
How to Contribute
1. Submit a PR (Preferred)
Don’t just report it — fix it. We actively welcome pull requests:- Fork the repo
- Let your Athena agent help you implement the change
- Test your changes locally
- Submit a PR with a clear description of what and why
2. Share Your Workflows
Built a useful workflow? Submit a PR with:- Your workflow file in
examples/workflows/ - A brief description of what it does
3. Improve Documentation
Found something unclear? Help make it better:- Fix typos or clarify explanations
- Add examples where helpful
4. Add Templates
Created a useful template? Share it:- Add to
examples/templates/ - Include usage instructions
5. Agent-Assisted Contributions
Let your Athena agent help you contribute! Using Protocol 408:- Ask a question: “Does Athena support X?”
- Agent verifies: Searches codebase to confirm it’s a gap
- Agent drafts: Creates a structured RFC using templates
- You submit: One-click GitHub Issue submission
Guidelines
Modularity
Keep files modular (< 500 lines)
Naming
Use clear, descriptive names
Documentation
Include comments where helpful
Testing
Test your changes before submitting
One PR = one topic. Don’t bundle unrelated changes.