Keyboard shortcut conflict detector for photo editors

A distinct but related frustration runs through these complaints: users accidentally trigger an unknown keyboard shortcut — a trackpad gesture rotates the canvas, a stray keypress fires a filter — and then discover that Ctrl+Z doesn't undo it. One user described it exactly: 'I accidentally click a command from my keyboard and can't undo it if I didn't know what command I accidentally hit.' Another: 'Some keyboard shortcuts you stumble upon by accident are just bonkers, and sometimes you can't Ctrl-Z to just undo them.' The undo failure is the symptom, but the root cause is that these editors have hundreds of active shortcuts with no visibility into what fired or why.

This gap persists because keyboard shortcut management inside Photoshop is a settings panel, not a live diagnostic tool. Adobe surfaces what shortcuts exist, but not what just happened, what it changed, or whether it's reversible. When a user accidentally hits a shortcut that modifies canvas orientation or resets a panel, the editor often treats it as a UI state change rather than an edit — and those changes fall outside the history stack entirely, which is why Ctrl+Z can't catch them.

What doesn't exist is a live shortcut audit layer: something that intercepts every keystroke while the editor is in focus, logs what command it triggered, flags whether that command is undo-safe, and surfaces a persistent 'last action' indicator so the user always knows what just happened and whether they can reverse it. This is narrower than a full history tool — it's specifically about the class of irreversible or hard-to-reverse actions that bypass the undo stack.

This is a business because the problem recurs every session for anyone using a complex editor, the risk compounds as files get larger and more worked-on, and the incumbent has no incentive to build a self-diagnostic layer that exposes the limitations of its own undo system. Studios training junior retouchers would pay specifically to reduce the 'accidentally nuked a file' incident rate.

What to build

Build a macOS and Windows system tray agent that hooks into Photoshop's keyboard input while the app is in focus, logs every triggered shortcut with its command name and undo-safety status, and displays a persistent floating HUD showing the last five triggered commands with a visual indicator for which ones are outside the history stack and therefore irreversible.

Where to start

Target photography training schools and bootcamps first — instructors already spend time explaining the shortcut/undo inconsistency to every new cohort, the tool directly reduces their support burden, and an institutional license means one sale covers 20-30 seats without needing individual retoucher buy-in.

The hard part

Reliably intercepting and mapping keystrokes to Photoshop's internal command names without an official API requires either Photoshop scripting hooks (limited and version-specific) or OS-level input monitoring, which triggers security warnings on macOS — getting past that friction point with first users will be the make-or-break early hurdle.

How it makes money

Per-seat annual license for individual users at $60-80/year; institutional pricing for training programs at a flat cohort rate negotiated per school.