Creating custom packs

Pack Editor (Pro)

The visual Pack Editor is the fastest way to build or tweak a pack without touching JSON:

1. Create a pack with a human-readable app name and one or more processNames (e.g. myapp.exe).
2. Add categories to mirror how shortcuts should appear in the overlay.
3. Add shortcuts with display name, key chord, optional menu path, and notes.
4. Export JSON for backup or sharing, or import packs others created.

JSON pack format

Every pack must include appName, processNames, and a non-empty shortcuts array. Optional metadata (id, version, category, author, …) helps you organise larger libraries.

Minimal example:

{
  "appName": "Contoso Writer",
  "processNames": ["contoso.exe"],
  "shortcuts": [
    { "command": "Save", "keys": "Ctrl+S" },
    { "command": "Export PDF", "keys": "Ctrl+Shift+E", "menuPath": "File > Export" }
  ]
}

Schema reference

The canonical JSON Schema lives in the FluentOverlay repository and is mirrored here for convenience:

/schemas/pack.schema.json

Validate locally with tooling such as check-jsonschema against that file in CI or before you share a pack.

Localization

Bundled packs store translations under Packs/i18n/{locale}/.... For custom packs, follow the same folder pattern so WinUI can resolve strings per user locale.

Testing

1. Place or import your pack where FluentOverlay expects user packs (see in-app help / settings).
2. Focus the target app and open the overlay — confirm the process match and categories.
3. Run check-jsonschema (or equivalent) against /schemas/pack.schema.json to catch structural errors early.