🚀 Excited to Contribute! Seeking Guidance on Code Contributions

[Zuofan-Wu]

Here's a friendly and professional GitHub issue template that requests code contributions while showing appreciation:

---

Title: 🚀 Excited to Contribute! Seeking Guidance on Code Contributions

Hi PyroSys Team! 👋

First, I wanted to express my enthusiasm for this project! 🔥 The vision of creating accessible tools for computational structural biology while bridging DL domains is incredibly inspiring. Specifically, I appreciate how you're:

• Making SOTA models accessible with permissive licensing (💖 for researchers!)
• Lowering barriers for CV/NLP developers to enter bioinformatics
• Creating educational opportunities for students

I'd love to contribute code to help accelerate PyroSys' development! Could you please clarify:

1. Contribution Priorities:

   • Are there specific model implementations/features urgently needed?
   • Is there a public roadmap for future development?

2. Implementation Guidance:

   • Preferred coding standards/conventions for the project?
   • Testing requirements (unit tests, coverage thresholds)?
   • Documentation practices (docstrings, mkdocs)?

3. Architecture Alignment:

   • How can new components best integrate with existing systems?
   • Any particular design patterns to follow?

I'm particularly interested in [your area of interest - e.g., model architectures, data pipelines, API design], but happy to help wherever most needed. The architecture guide was helpful, but would you recommend any specific starting points for first-time contributors?

Keep up the amazing work! This could truly revolutionize computational biology. 🧬💻

---

Key Features:

• Maintains enthusiastic tone while seeking actionable details
• Shows genuine engagement with project goals
• Asks specific technical questions that help contributors add value
• Aligns with their stated vision for different user types
• References existing documentation while seeking clarifications

This format encourages maintainers to respond by:

1. Feeling appreciated for their work
2. Recognizing your serious intent to contribute
3. Providing structured guidance to streamline contributions