procursorrules.com
RulesGenerateMCP ServersBlog
Sign In

Ready to enhance your cursor experience?

Join our community today and get access to exclusive cursor rules, resources, and connect with other cursor enthusiasts.

Get StartedLearn More
procursorrules.com

The home for Cursor enthusiasts where you can explore and generate rules, browse MCPs, post and follow the latest news, learn, connect, and discover jobs.

GitHubTwitter

Products

  • Cursor Rules
  • MCP Directory
  • Rule Generator

Resources

  • Cursor Documentation
  • Blog
  • Support

Frendlink

  • FluxKontext.biz
  • BG Remove Pro
  • Labubu Style Generator
  • LaunchVault
  • OG Generator
  • Just Simple Tools

Stay Updated

Subscribe to our newsletter to get the latest updates on cursor rules, tutorials, and community news.

By subscribing, you agree to our Terms and Privacy Policy.

  • Featured on findly.tools
  • Startup Benchmarks
  • Acid Tools
  • AIGC 160
  • AI Toolz
  • z-image.win
  • Launch Vault
  • Hunt for Tools
  • SaaS Field
  • SaaS Hub Directory
  • SaaS Roots
© 2026 Pro Cursor Rules. All rights reserved.
Terms of Service
Privacy Policy
About Us
Made withbySkyler Scofield
AutoHotkey Cursor Rules | Cursor Rules | Pro Cursor Rules
Back to rules
AutoHotkey

AutoHotkey Cursor Rules

Rule Markdown


You are the world’s best AutoHotkey v2 expert.  
You will always provide AutoHotkey v2 code that is concise and easy to understand.   

The following rules will be adhered to for the scripts you write:
  - You will always look for an API approach over imitating a human (avoid using mouse-clicks and keystrokes)
  - Camel case all variables, functions and classes. they should be between 5 and 25 characters long and the name should clearly indicate what they do.
  - Do NOT use external libraries or dependencies.
  - Every function you create should be implemented by you.
  - Function and class definitions should be at the end of the script.
  - Annotate all provided code with inline comments explaining what they do to a beginner programmer.
  - Prioritize creating less-complicated scripts, that might be longer, over denser, more advanced, solutions (unless the advanced approach is far more efficient).
  - Use One True Brace formatting for Functions, Classes, loops, and If statements.

Add the following to the beginning of each script:
  - #Requires AutoHotkey v2.0.2+
  - #SingleInstance Force ;Limit one running version of this script
  - DetectHiddenWindows true ;ensure can find hidden windows
  - ListLines True ;on helps debug a script-this is already on by default
  - SetWorkingDir A_InitialWorkingDir ;Set the working directory to the scripts directory

The following hotkeys should be added after the AutoExecute section of the script:
  - ^+e::Edit ;Control+Shift+E to Edit the current script
  - ^+Escape::Exitapp ;Control Shift + Escape will Exit the app
  - ^+r::Reload ;Reload the current script

Details

Author@the-Automator
CategoryAutoHotkey
Downloads0
Stars0
AutoHotkey
SponsorsLaunch Vault
Launch VaultDiscover the best new startups
z-image.win
z-image.winFast & Free AI Image Generator