Create Recurse ML rules

[ab-10]

Description

This PR adds custom Recurse ML rules to enforce best practices. Most of them (outside of effective_comments.mdc) are rust-specific.

Summary

effective_comments.mdc

Scope: all code
Purpose: Ensures comments add value by explaining why rather than what

Key principles:

• Avoid redundant comments that restate obvious code
• Use comments to clarify intent behind complex logic
• Keep TODO comments specific with assignees
• Always update comments when code changes

exhaustive_pattern_matching.mdc

Scope: Rust code
Purpose: Promotes safe enum handling through exhaustive pattern matching

Key principles:

• Use match instead of nested if-else chains for enums
• Handle all variants explicitly to prevent runtime panics
• Use match guards for conditional patterns
• Essential for Robyn's HTTP methods, response types, and middleware handling

proper_error_handling.mdc

Scope: Rust code
Purpose: Ensures robust error handling in the Python-Rust bridge

Key principles:

• Never use unwrap() in production without justification
• Use ? operator for error propagation
• Handle PyO3 integration errors gracefully
• Critical for preventing web server crashes and maintaining stability

PR Checklist

Please ensure that:

• The PR contains a descriptive title
• The PR contains a descriptive summary of the changes
• N/A: You build and test your changes before submitting a PR.
• You have added relevant documentation
• N/A: You have added relevant tests. We prefer integration tests wherever possible

Pre-Commit Instructions:

• N/A: Ensure that you have run the pre-commit hooks on your PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
robyn	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 20, 2025 2:02pm

[recurseml]

✨ No files to analyze in this PR.

^{Need help? Join our Discord for support!
https://discord.gg/qEjHQk64Z9}

[sansyrox]

Hey @ab-10 ,

Thanks for the PR. Could you please fetch the latest changes? The PR is failing for some reason.

[codspeed-hq]

CodSpeed Performance Report

Merging #1214 will not alter performance

_{Comparing Recurse-ML:main (9bcc98c) with main (40afefe)¹}

Summary

✅ 150 untouched benchmarks

Footnotes

1. No successful run was found on main (fff99fe) during the generation of this report, so 40afefe was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[sansyrox]

LGTM!