First off, thank you for considering contributing to the (RTX⚡) Core Framework! ⚡
It is people like you who make RTX a robust and versatile blueprint for AI agents everywhere.
By participating in this project, you agree to maintain a professional, respectful, and collaborative environment.
- Check the existing issues and discussions before opening a new one.
- Use a clear and descriptive title.
- Describe the exact steps to reproduce the issue, the expected behavior, and what actually happened.
- Open a new discussion or issue describing your feature request.
- Explain why this enhancement would be useful to most RTX users.
- Fork the repository and create your branch from
master. - Ensure your modifications align with the core philosophy of RTX (Reasoning, Thinking, Xtreme).
- Update the documentation (including the Wiki, if applicable) if your changes introduce new protocols or behaviors.
- Maintain clean, descriptive commit messages following Conventional Commits (e.g.
feat:,fix:,docs:).
If you want to contribute a new persona example (like a specific language or role target) to the examples/ directory:
- File Naming: Format the filename as
[Language]-[Role]-[Name].md(e.g.,Spanish-Dev-Carlos.mdorPython-Dev-Ananya.md). - Follow the Compiled Format: Do NOT copy-paste Section 0 (First-boot) or the Global Omnipresence section. Your contributed file should start directly with the header tag
# ***(PersonaName (RTX⚡))*** Core Frameworkand contain Sections 1 to 6. - Format Validation: Verify that:
- The 3-Step Universal Output Protocol uses a custom addressal suitable for that persona.
- The language mix is defined precisely as 70% Romanized [Language] + 30% English tech terms.
- Emojis and Tone are tailored to the role and language context.
- No Credentials: Never commit credentials, passwords, personal paths, or API keys in your pull requests or examples.
- Strict Anti-Inline Rule: Ensure any numbered list inside the markdown file includes empty lines (
\n\n) between items to prevent rendering issues on markdown platforms. - Opt-In Rules: Do not write rules that command the agent to silently modify local file systems or run scheduled loops without user confirmation. All propagation steps must remain transparent and opt-in.
Thank you for your support in making (RTX⚡) the default framework for multilingual developers! 🚀🔥