Contributing Guidelines

**Repository:** System Prompts & Agent Prompts Collection **Maintainer:** Sayed Allam **Last Updated:** June 20, 2025 Thank you for your interest in contributing to this collection! This document outlines how you can help improve and expand this valuable resource for the AI community. --- ## 🎯 How You Can Contribute ### 🔍 Types of Contributions Welcome 1. **New System Prompts** - Recently discovered or leaked prompts - Official releases from AI companies - High-quality open source prompts - Academic research prompts 2. **Prompt Analysis & Documentation** - Detailed analysis of existing prompts - Usage examples and case studies - Performance comparisons - Best practice documentation 3. **Quality Improvements** - Error corrections and fact-checking - Better categorization and organization - Improved formatting and readability - Enhanced search capabilities 4. **Educational Content** - Implementation guides and tutorials - Customization examples - Testing frameworks - Use case documentation 5. **Tool and Utility Development** - Prompt analysis tools - Conversion utilities - Quality assessment scripts - Integration examples --- ## 📝 Contribution Process ### Step 1: Before You Start 1. **Check Existing Issues**: Review open issues to avoid duplication 2. **Search the Collection**: Ensure your contribution isn't already included 3. **Review Guidelines**: Read these guidelines thoroughly 4. **Understand Quality Standards**: Familiarize yourself with our quality criteria ### Step 2: Prepare Your Contribution #### For New Prompts ```markdown Required Information: □ Complete prompt text (properly formatted) □ Source attribution (URL, document, or reference) □ Model/tool information (name, version, date) □ Verification status (verified, likely authentic, community reported) □ Category classification □ Brief description of purpose/use case ``` #### For Documentation ```markdown Required Elements: □ Clear, actionable content □ Proper markdown formatting □ References and citations where applicable □ Examples and code snippets (if relevant) □ Consistency with existing documentation style ``` ### Step 3: Submit Your Contribution #### Option A: GitHub Pull Request (Preferred) 1. **Fork the Repository** ```bash git clone https://github.com/sayedallam/system-prompts-collection.git cd system-prompts-collection git checkout -b feature/your-contribution-name ``` 2. **Make Your Changes** - Add your content following the established format - Update relevant documentation - Test any code or examples 3. **Commit and Push** ```bash git add . git commit -m "Add: Brief description of your contribution" git push origin feature/your-contribution-name ``` 4. **Create Pull Request** - Provide clear description of changes - Include testing steps if applicable - Reference any related issues #### Option B: GitHub Issue If you're not comfortable with pull requests: 1. Create a new issue with the "contribution" label 2. Provide all required information in the issue description 3. Attach files or provide detailed content in the issue #### Option C: Email Submission For sensitive or complex contributions: - Email: [Your contact email] - Subject: "System Prompts Collection Contribution" - Include all required information and attachments --- ## 🎨 Content Standards ### Quality Criteria #### For System Prompts ✅ **High Quality Prompts Should:** - Be complete and functional (not partial snippets) - Include proper source attribution - Have clear verification status - Be properly formatted and readable - Serve educational or research purposes - Follow ethical guidelines ❌ **We Don't Accept:** - Partial or incomplete prompts - Prompts without proper attribution - Malicious or harmful prompts - Copyrighted content used inappropriately - Prompts that violate privacy or security - Low-quality or spam content #### For Documentation ✅ **Good Documentation Should:** - Be clear, accurate, and helpful - Follow our formatting standards - Include practical examples - Be well-researched and factual - Add genuine value to users ❌ **Avoid:** - Outdated or incorrect information - Poor formatting or unclear writing - Duplicate content without improvement - Promotional or commercial content - Content without proper citations ### Formatting Standards #### Prompt Format ```markdown #### [Model/Tool Name] System Prompt **Source:** `[Original source URL or reference]` **Model:** [Model name and version] **Date:** [Date if available] **Verification:** [Verified/Likely Authentic/Community Reported] ``` [Your actual prompt content here] ``` **Usage Notes:** [Any relevant usage information] **Analysis:** [Optional analysis or insights] ``` #### Documentation Format - Use clear, descriptive headers (H1-H4) - Include table of contents for longer documents - Use code blocks for code examples - Include relevant links and references - Follow consistent markdown formatting --- ## 🔒 Ethical Guidelines ### Responsible Sharing 1. **Respect Intellectual Property** - Always provide proper attribution - Respect copyright and licensing terms - Don't share proprietary information inappropriately - Follow fair use principles 2. **Privacy Protection** - Never include personal information - Redact sensitive data before sharing - Respect confidentiality agreements - Protect user privacy in examples 3. **Safety Considerations** - Don't share prompts designed for harmful purposes - Include appropriate safety warnings - Respect content policies of platforms - Consider potential misuse of shared content 4. **Community Standards** - Be respectful and professional - Follow community norms and expectations - Help maintain a positive environment - Support educational and research goals ### Legal Compliance - Ensure contributions comply with applicable laws - Respect terms of service of source platforms - Follow international copyright and IP laws - Consider jurisdictional differences in legal standards --- ## 🧪 Testing and Validation ### Before Submitting 1. **Prompt Testing** - Test prompts work as described - Verify formatting is correct - Check for completeness - Validate source information 2. **Documentation Review** - Proofread for errors and clarity - Test any code examples - Verify all links work - Check formatting renders correctly 3. **Quality Assurance** - Compare against our quality standards - Ensure uniqueness and value - Verify ethical compliance - Confirm proper attribution ### Testing Checklist ```markdown □ Content is complete and accurate □ Formatting follows our standards □ All links and references work □ Source attribution is proper and complete □ Content adds value to the collection □ Ethical guidelines are followed □ No personal or sensitive information included □ Testing (if applicable) has been performed ``` --- ## 📊 Review Process ### What Happens After Submission 1. **Initial Review** (1-3 days) - Check for completeness and format compliance - Verify ethical guidelines are followed - Ensure no duplicate content 2. **Quality Assessment** (2-5 days) - Evaluate content quality and value - Verify sources and attribution - Test prompts or examples if applicable - Check for accuracy and correctness 3. **Community Feedback** (3-7 days) - Allow time for community input - Address any concerns or suggestions - Make necessary revisions 4. **Final Decision** - Approve and merge high-quality contributions - Provide feedback for rejected submissions - Suggest improvements for resubmission ### Review Criteria - **Accuracy**: Information is correct and verifiable - **Quality**: Content meets our high standards - **Value**: Adds genuine value to the collection - **Originality**: Not duplicate of existing content - **Ethics**: Follows our ethical guidelines - **Format**: Properly formatted and organized --- ## 🤝 Community Guidelines ### Communication Standards - **Be Respectful**: Treat all contributors with respect and courtesy - **Be Constructive**: Provide helpful, actionable feedback - **Be Patient**: Allow time for review and response - **Be Professional**: Maintain professional standards in all interactions ### Collaboration Principles - **Openness**: Embrace diverse perspectives and approaches - **Transparency**: Be open about sources and methodologies - **Quality Focus**: Prioritize quality over quantity - **Learning**: Support learning and knowledge sharing - **Improvement**: Continuously work to improve the collection ### Conflict Resolution If you disagree with a decision or have concerns: 1. Start with respectful direct communication 2. Escalate to maintainer if needed 3. Provide clear reasoning and evidence 4. Accept final decisions gracefully 5. Focus on the common goal of improving the collection --- ## 🏆 Recognition ### Contributor Recognition We recognize valuable contributions through: - **Contributors File**: Listed in CONTRIBUTORS.md - **Release Notes**: Mentioned in version release notes - **README Acknowledgments**: Featured in main README - **Special Recognition**: Outstanding contributions highlighted ### Types of Recognition - **Regular Contributors**: Multiple accepted contributions - **Quality Contributors**: Exceptional quality submissions - **Community Leaders**: Active in discussions and reviews - **Subject Matter Experts**: Deep expertise in specific areas --- ## 📚 Resources for Contributors ### Getting Started - [Markdown Guide](https://www.markdownguide.org/) - [Git Basics](https://git-scm.com/doc) - [GitHub Flow](https://guides.github.com/introduction/flow/) - [Pull Request Best Practices](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests) ### Prompt Engineering Resources - [OpenAI Prompt Engineering Guide](https://platform.openai.com/docs/guides/prompt-engineering) - [Anthropic Prompt Library](https://docs.anthropic.com/claude/prompt-library) - [Prompt Engineering Research Papers](https://arxiv.org/search/?query=prompt+engineering) ### Community - **GitHub Discussions**: Ask questions and share ideas - **Issue Tracker**: Report bugs and request features - **Pull Requests**: Submit contributions and improvements --- ## 📞 Contact and Support ### Getting Help - **Documentation Questions**: Check our docs/ folder first - **Technical Issues**: Create a GitHub issue - **General Questions**: Use GitHub Discussions - **Private Concerns**: Email the maintainer --- ## 📝 Updates to Guidelines These guidelines may be updated periodically to improve the contribution process. Major changes will be: - Announced in GitHub Discussions - Documented in release notes - Communicated to active contributors - Effective after reasonable notice period --- Thank you for contributing to making AI knowledge more accessible to everyone! Your contributions help researchers, developers, and AI enthusiasts learn from the best examples in the field. **Happy Contributing! 🚀** --- **Contributing guidelines by Sayed Allam - June 2025** *Building the future of AI knowledge sharing together*