Hey all! I'm new in cursor and using it less than 1 month. The problem which I've got right now is how to set up proper cursor rules for my project? I'm trying to use ChatGPT to generate me this rules but it's not working very well, the structure is mess and rules sometimes too complecated. Anybody know the way how to do it well? My project has external backend, I'm developing frontend in one folder and backend in another and would like to seperate rools for backend and frontend.

Lee Robinson from Cursor published a six-part video course on AI foundations. It's designed for beginners to learn concepts like tokens, context, and agents. The course covers AI development fundamental topics: 1. How AI models work 2. Hallucination & limitations 3. Tokens & pricing 4. Context 5. Tool calling 6. Agents And more to come The course takes roughly 1 hours to complete Check it out here!

I am excited to be here! And ready to learn more about cursor so that i can build awesome application that are gonna make life much easier for my clients💪💪

Thank you for having me join you. I hope I can learn a lot from this group. Name: John Location: Belgium Cursor usage: 6 months Current construction: Testing, no projects

"Just ask grok-code-fast-1" Quick thought that came to mind: I'm setting up deployment for an application and needed to define environment variables for it. I had no idea what environment variables the project had or what I should set. It's a new project so I couldn't even look it up from the documentation. So I just asked grok-code-fast-1 to go through the code and list all the environment variables that are used in the codebase. Couple seconds later I had a list of the environment variables. My first instinct was "I should document these somewhere" But that got me thinking: why? Why can't I just do the same thing next time I need to know the environment variables? Documentation gets out of date while the code is always correct. So if possible, I feel like I should prefer just asking the documentation-related questions directly from AI, especially now that we have a blazing-fast, ridiculously cheap model to comb through the code. Which means that in the future, documentation should focus way more on the things that can't be figured out just by looking at the code. Design decisions, tradeoffs, reasonings, specifications, and so on. This kind of documentation also helps the model when developing software. Side question that I have here: is there a way for Cursor to do the same without context pollution? Could Cursor Agent somehow ask Grok to go through the code, look for the environment variables, and just return a summary so that the main Agent doesn't have to read all the code? What do you think? Give me your thoughts in the comments