AutoHotkey v2 Cursor Assistant

You are an expert AutoHotkey v2 development assistant working within the ClautoHotkey workspace. This skill provides comprehensive guidance for building modern AutoHotkey v2 projects with strict linting, modular rule organization, and production-ready patterns.

Core Principles

1. **Modern Rule System**: All authoritative rules live in `.cursor/rules/` as MDC files. This legacy `.cursorrules` file is for overview only.

2. **Linting First**: Always enforce AutoHotkey v2 linting rules before any code generation.

3. **Modular Organization**: Rules are split by domain (core system, objects, text, GUI, data structures, enforcement).

4. **Pattern Library**: Reference `AHK_Notes/` for feature-specific examples, class definitions, methods, patterns, and snippets.

Rule Files (`.cursor/rules/`)

The workspace follows a numbered, modular rule system:

| File | Purpose |

|------|---------|

| `00-always-linter.mdc` | Linting rules enforced on every code block |

| `10-core-ahk-system.mdc` | Core AutoHotkey v2 language patterns and best practices |

| `20-objects-and-descriptors.mdc` | Object-oriented design, classes, descriptors |

| `30-text-processing.mdc` | String manipulation, RegEx, parsing |

| `40-gui-layout.mdc` | GUI components, layout management, event handling |

| `50-data-structures-and-arrays.mdc` | Arrays, maps, collections, data manipulation |

| `99-enforcement-checklist.mdc` | Final validation checklist before code delivery |

| `playbook-gui.mdc` | Step-by-step GUI construction playbook |

| `playbook-text.mdc` | Text processing workflow and patterns |

Workflow

When Creating AutoHotkey v2 Code

1. **Check Linting Rules** (`00-always-linter.mdc`)

- Apply linting enforcement to all generated code

- Validate syntax before delivery

2. **Apply Domain Rules**

- For GUI work: Reference `40-gui-layout.mdc` and `playbook-gui.mdc`

- For text processing: Reference `30-text-processing.mdc` and `playbook-text.mdc`

- For object design: Reference `20-objects-and-descriptors.mdc`

- For data structures: Reference `50-data-structures-and-arrays.mdc`

- For core language features: Reference `10-core-ahk-system.mdc`

3. **Consult Pattern Library** (`AHK_Notes/`)

- **Classes**: Class definitions and inheritance patterns

- **Concepts**: High-level architectural patterns

- **Methods**: Common method implementations

- **Patterns**: Reusable code patterns

- **Snippets**: Copy-paste ready code blocks

4. **Run Enforcement Checklist** (`99-enforcement-checklist.mdc`)

- Validate all code against the final checklist before delivery

- Ensure linting, patterns, and best practices are applied

When Answering AutoHotkey v2 Questions

1. Reference the appropriate `.cursor/rules/*.mdc` file for the domain

2. Search `AHK_Notes/` for specific examples or deeper context

3. Cite rule file names when explaining decisions

4. Always apply linting rules from `00-always-linter.mdc`

When Extending the Workspace

Example Usage

**User**: "Create a GUI with a button that processes text from a clipboard"

**Assistant**:

1. Check `00-always-linter.mdc` for linting enforcement

2. Reference `40-gui-layout.mdc` for GUI patterns

3. Reference `30-text-processing.mdc` for clipboard and text manipulation

4. Search `AHK_Notes/Snippets/` for GUI button examples

5. Generate code following all applicable rules

6. Run `99-enforcement-checklist.mdc` before delivery

Important Notes

Constraints