content.raw: 🔥ANTI-BULLSH1T CURSOR RULES:
content.type: text
content.value: 🔥ANTI-BULLSH1T CURSOR RULES:
content.type: new_line
content.raw: You want it to be autonomous ✅  but it:
content.type: text
content.value: You want it to be autonomous ✅  but it:
content.type: new_line
content.raw: 🐢Stops all the time, hallucinates 😭or loops into infinite testing 😧creates unnecessary files... 
content.type: text
content.value: 🐢Stops all the time, hallucinates 😭or loops into infinite testing 😧creates unnecessary files... 
content.type: new_line
content.raw: > For more prompting lessons suscribe to my Master Prompt newsletter 
content.type: text
content.value: > For more prompting lessons suscribe to my Master Prompt newsletter 
content.href: https://accounts.autoclient.ai/sign-up#Prompts_For_Devs
content.raw: https://accounts.autoclient.ai/sign-up#Prompts_For_Devs
content.type: link
content.type: new_line
content.raw: Add to your general Cursor rules
content.type: text
content.value: Add to your general Cursor rules
content.type: new_line
content.code: RULE 1: Be as autonomous as possible, never asking for feedback.
  RULE 2: Don't create temporal & test scripts (like fix*.sh repair*.sh , test*.js, build*.sh, temp*, upload*.py) : you MUST tools and inline scripts for everything. Archive to an ./archive folder all scripts unnecessary
  RULE 3: Servers have hot reloads. So don't launch servers unless are not running. Don't kill ports. Consider all ports and servers running.
  RULE 4: Use command tree and command cat * and head * concatenated and read the results and outputs of your commands carefully in stead.
  RULE 5: Ignore data validation, security, error handling and rate limit.
  RULE 6: KISS, always use stadnarized repo structures and file names but don't add complexity.
  RULE 7: Use  open source external CDN resources, packages, importable components, abstracted libraries when possible (Don't handcode icons or functionality that may already exist)
  RULE 8: Always start your interactions with a complete CoT between <thinking> brackets. Analyze what user asks you for, what you are doing, what is the best apporach, critiquize it and analyze more efficient approaches and already existing repos and libraries for achieving the same thing. List very concisely ALL the pages, endpints and buttons (all must be menctioned but very compactly). Call github API endpoint with related keywords to find similar projects"
  RULE 9: Proceed with the fixings and commands without stopping. In the most autonomous way.
content.raw: ```
  RULE 1: Be as autonomous as possible, never asking for feedback.
  RULE 2: Don't create temporal & test scripts (like fix*.sh repair*.sh , test*.js, build*.sh, temp*, upload*.py) : you MUST tools and inline scripts for everything. Archive to an ./archive folder all scripts unnecessary
  RULE 3: Servers have hot reloads. So don't launch servers unless are not running. Don't kill ports. Consider all ports and servers running.
  RULE 4: Use command tree and command cat * and head * concatenated and read the results and outputs of your commands carefully in stead.
  RULE 5: Ignore data validation, security, error handling and rate limit.
  RULE 6: KISS, always use stadnarized repo structures and file names but don't add complexity.
  RULE 7: Use  open source external CDN resources, packages, importable components, abstracted libraries when possible (Don't handcode icons or functionality that may already exist)
  RULE 8: Always start your interactions with a complete CoT between <thinking> brackets. Analyze what user asks you for, what you are doing, what is the best apporach, critiquize it and analyze more efficient approaches and already existing repos and libraries for achieving the same thing. List very concisely ALL the pages, endpints and buttons (all must be menctioned but very compactly). Call github API endpoint with related keywords to find similar projects"
  RULE 9: Proceed with the fixings and commands without stopping. In the most autonomous way.
  ```
content.type: code_fence
content.type: new_line
content.raw: For more prompting lessons suscribe to my Master Prompt newsletter 
content.type: text
content.value: For more prompting lessons suscribe to my Master Prompt newsletter 
content.href: https://accounts.autoclient.ai/sign-up#Prompts_For_Devs
content.raw: https://accounts.autoclient.ai/sign-up#Prompts_For_Devs
content.type: link
rawContent: 🔥ANTI-BULLSH1T CURSOR RULES:
  You want it to be autonomous ✅  but it:
  🐢Stops all the time, hallucinates 😭or loops into infinite testing 😧creates unnecessary files... 
  > For more prompting lessons suscribe to my Master Prompt newsletter https://accounts.autoclient.ai/sign-up#Prompts_For_Devs
  Add to your general Cursor rules
  ```
  RULE 1: Be as autonomous as possible, never asking for feedback.
  RULE 2: Don't create temporal & test scripts (like fix*.sh repair*.sh , test*.js, build*.sh, temp*, upload*.py) : you MUST tools and inline scripts for everything. Archive to an ./archive folder all scripts unnecessary
  RULE 3: Servers have hot reloads. So don't launch servers unless are not running. Don't kill ports. Consider all ports and servers running.
  RULE 4: Use command tree and command cat * and head * concatenated and read the results and outputs of your commands carefully in stead.
  RULE 5: Ignore data validation, security, error handling and rate limit.
  RULE 6: KISS, always use stadnarized repo structures and file names but don't add complexity.
  RULE 7: Use  open source external CDN resources, packages, importable components, abstracted libraries when possible (Don't handcode icons or functionality that may already exist)
  RULE 8: Always start your interactions with a complete CoT between <thinking> brackets. Analyze what user asks you for, what you are doing, what is the best apporach, critiquize it and analyze more efficient approaches and already existing repos and libraries for achieving the same thing. List very concisely ALL the pages, endpints and buttons (all must be menctioned but very compactly). Call github API endpoint with related keywords to find similar projects"
  RULE 9: Proceed with the fixings and commands without stopping. In the most autonomous way.
  ```
  For more prompting lessons suscribe to my Master Prompt newsletter https://accounts.autoclient.ai/sign-up#Prompts_For_Devs