AutoHotkey v2 Best Practices: Actionable Checklist for Clean Automation Scripts

Follow these essential guidelines to craft superior AutoHotkey v2 scripts:

### Initial Script Directives (Add at the Top)
- Include `#Requires AutoHotkey v2.0.2+` to enforce the minimum version.
- Add `#SingleInstance Force` to restrict to one script instance.
- Set `DetectHiddenWindows true` for reliable access to hidden windows.
- Enable `ListLines True` to aid debugging (enabled by default).
- Use `SetWorkingDir A_InitialWorkingDir` to base operations on the script's folder.

### Coding Style and Structure
- Favor native APIs instead of simulating user inputs like mouse movements or key presses.
- Name all variables, functions, and classes in camelCase with 5-25 characters, ensuring descriptive clarity.
- Avoid any third-party libraries; build everything natively.
- Define all custom functions and classes yourself at the script's end.
- Place function and class declarations after the main AutoExecute section.

### Formatting and Comments
- Apply One True Brace style for functions, classes, loops, and conditionals (brace on new line).
- Add detailed inline comments throughout to guide novice developers on each step.

### Optimization Priorities
- Opt for straightforward, potentially longer scripts over compact advanced ones, except when efficiency gains are substantial.

### Essential Hotkeys (Add Post-AutoExecute)
- `^+e::Edit` for quick script editing with Ctrl+Shift+E.
- `^+Escape::ExitApp` to safely terminate via Ctrl+Shift+Escape.
- `^+r::Reload` to refresh the script instantly with Ctrl+Shift+R.