Keyboard Maestro Macro Planner: Law Office Matter Intake with Typed String Triggers, Prompt for User Input, and Pause Until Conditions
Ppromptstudio·Oct 5, 2026
No rating
Plan Keyboard Maestro macros for a legal assistant's repetitive matter intake: a macro group scoped to the right apps, hot key and typed string triggers, Prompt for User Input and Local variables, folder creation with date tokens, regex capture from a pasted intake email, and form filling that waits on Pause Until conditions instead of fixed delays.
Act as a Keyboard Maestro consultant who builds macros for small law offices on macOS and documents them so the next assistant can maintain them. You design macros action by action using real Keyboard Maestro action names and tokens, and you prefer conditions over guessed pauses.
Inputs:
- The repetitive task, step by step as it is done today: [ManualSteps]
- Apps and browsers involved, and which web form or window titles appear: [AppsAndWindows]
- Folder naming convention and root path: [FolderConvention]
- Sample intake email or form text the macro will read: [IntakeSample]
- Hot keys or typed strings the office already uses: [ExistingTriggers]
- Sensitive fields that must not persist after the macro ends: [SensitiveFields]
- Keyboard Maestro version: [KmVersion]
- Output format: [Format]
Generate:
1. Macro group plan: group name, available in which applications, and one line per macro with its trigger (Hot Key, Typed String, or Application trigger) chosen to avoid ExistingTriggers.
2. For each macro, an ordered action list using Keyboard Maestro names: Prompt for User Input, Set Variable to Text, Search using Regular Expression, New Folder, Insert Text by Pasting, Insert Text by Typing, Type a Keystroke, Activate a Specific Application, Pause Until, If Then Else, Display Text, and Cancel This Macro.
3. Variables: names with the Local prefix for anything in SensitiveFields so they are not saved to disk, token syntax such as %Variable%Local_Client% and %ICUDateTime%yyyy-MM-dd%, and default values.
4. The regular expressions that capture each field from IntakeSample, with capture groups mapped to variables, and what happens when a match fails.
5. Reliability: Pause Until conditions for window titles or found images in place of fixed Pause actions, a guard that stops if the wrong window is front, and a test plan on a dummy matter.
6. Maintenance note for the office: what each macro does, how to disable the group, and what to check after a browser or form update.
Constraints:
- Only use actions that exist in KmVersion; mark anything uncertain VERIFY.
- Never store client identifiers in global variables or clipboard history longer than needed.
- No em dashes.