[Submission] AI IDE Editors Rules for Temporal Application Development

[MasonEgger]

Project link

https://github.com/temporal-community/ai-ide-rules

Language

Other / Unofficial SDK

Short description (max 256 chars)

Repository of "rules" for various AI IDEs to aid in AI generated Temporal Application Development

Long Description

AI powered IDEs are used by developers daily to build applications. These IDEs can take in custom rule sets for building and maintaining applications, and this repository provides curated rules from both internal and external contributors for making the developers "Vibe Coding" experience better.

Author(s)

Mason Egger / Temporal / https://github.com/masonegger.png
Drew Gorton / Temporal / https://github.com/dgorton.png

[webchick]

Awesome! 🤩 Super happy to see some tooling that enables Temporal to be better utilized in agentic code editors!

Couple of (hopefully) quick adjustments:

• Requirement: Could the README for the Cursor rules please be expanded to explain how to install/use these rules in Cursor and/or link to documentation that does? (This is part of the Code Exchange acceptance criteria, but also seems important to handle upfront, given a goal of this project is to get other people to fill in similar rules for other IDEs such as Windsurf and Copilot.) — extra bonus points for the main project README being further expanded as well.
• Recommendation: If any of these rules were started by others, it would be great to add a "Credits" section to the main README to call that out explicitly.
• Recommendation: Is there any guidance you can give to contributors about best practices around writing these rules, based on what you've learned? And/or any acceptance criteria of your own? (I don't think we need a full-blown CONTRIBUTING.md necessarily, but something that helps nudge people in the direction you're envisioning would be great.)
• Recommendation: The long description of the project is also a bit barebones compared to the other Code Exchange projects (example). We don't really want filler for filler's sake, but if possible, maybe you could add a bit more detail around the "origin" story of this project, and/or your goals for its future, and/or what type of contributions you're looking for, etc. (If the project's README were to be expanded to include this info, this then becomes a copy/paste job for the description, which is generally how these go).