multi-surface-single-engine

To share operation logic without duplicating code, centralize your engine within a single shell script, AppleScript, API, or binary, then wrap it with various user interfaces to maintain a single source of truth.

A single-source-of-truth architecture for multi-surface applications centralizes core operation logic in one engine, ensuring consistent operations while allowing independent UX adaptation across CLI, web, and GUI access points.

To maintain consistent engine logic when adding a GUI, wrap the existing centralized shell script or binary with the new interface, ensuring the underlying logic remains untouched and coordinates without duplication.

Yes, you can use a single shell script as the core engine for both web and CLI interfaces, centralizing the operation logic so that multiple user access points interact with the exact same binary or API.

You should avoid wrapping multiple user interfaces around a single binary if your surfaces require fundamentally different processing logic, as this approach specifically enforces consistent operations across all coordinated access points.

No specific dependencies are required to coordinate interfaces, as the skill relies on centralizing your existing shell scripts, AppleScripts, APIs, or binaries to serve as the unified engine for all surfaces.