awesome-cursorrules

repo updates their Python rules, you want to choose when and how to upgrade, just like any other dependency. Quick example: --------------------------- # Connect to a registry arm config registry add awesome-cursorrules https://github.com/PatrickJS/awesome-cursorrules --type git # Install Python rules to Cursor arm config sink add cursor --directories .cursor/rules arm install awesome-cursorrules/python # Later, update when you're ready arm update awesome-cursorrules/python ---------------------------- It creates arm.json and arm-lock.json files (like package.json/package-lock.json) so your whole team gets the same AI behavior. One-liner install: curl -fsSL https://raw.githubusercontent.com/jomadu/ai-rules-manager/ma... | bash GitHub: https://github.com/jomadu/ai-rules-manager Would love feedback from other folks dealing with AI rule management chaos!

index online documentation on architecture, build instructions, design, development of certain components, project layout. Easily 500+ lines worth of markdown. I tell Cursor where to look, i.e. online documentation of the libraries you use, reference implementations if you have any, good code examples and why they are good, and then it writes its own rule files - I don't write them manually anymore. That has been working really well for me. If you have a common technology stack you or way of working you can also try throwing in some examples from https://github.com/PatrickJS/awesome-cursorrules For a codebase containing both good and bad code; maybe you can point it to a past change where code was refactored from bad to good, so it can write out what why you prefer which style and how to manage the migration from bad to good. That said; the tools are not perfect. Even with rules the bad output still can happen but larger rule files describing what you'd like to do and what to avoid makes the chance significantly smaller and the tool more pleasant to work with. I recently switched to Claude Code because Cursor tended to get "stuck" on the same problem which I don't really experience with Claude Code but YMMV.

sts @X Launch Philosophy: - Don't beg for interaction, build something good and attract users organically. - Do not overlook the importance of launching properly. - Use all of the tools available to make launch easy and fast, but be creative. - Be humble and kind. Look at feedback as something useful and admit you make mistakes. - Do not get distracted by negativity, you are your own worst enemy and best friend. Additional Resources & Tools: Git Code Exporter (Creates a context package for code analysis or providing input to language models) - https://github.com/TechNomadCode/Git-Source-Code-Consolidator… Simple File Exporter (Simpler alternative to Git-based consolidation, useful when you only need to package files from a single, flat directory) - https://github.com/TechNomadCode/Simple-File-Consolidator… Effective Prompting Guide - https://promptquick.ai/ Cursor Rules - https://github.com/PatrickJS/awesome-cursorrules… Docs & Notes - Markdown format for LLM use and readability Markdown to PDF Converter - https://md-to-pdf.fly.dev LateX @overleaf - For PDF/Formal Documents Audio/Video Downloader - https://cobalt.tools (Re)search tool - https://perplexity.ai/ Final Notes: - Refactor your codebase when needed as you build towards an MVP if you are using AI assistance for coding. (Keep seperation of concerns intact across files for maintainability) - Success does not come overnight and expect failures along the way. - When working towards an MVP, do not be afraid to pivot. Do not spend too much time on a single product. - Build something that is 'useful', do not build something that is 'impressive'. - Stop scrolling on twitter/reddit and go build something you want to build and build it how you want to build it, that makes it original doesn't it?