Build a catalog people can actually use on mobile.

The command catalog is strongest when it behaves like a runbook: fast category names, short human titles, and import/export when a team wants to share a set of known commands.

Step 1: Start with jobs, not abstractions

Good categories:

Start
Files
Docker
Production

Very broad names like Misc or Utilities force extra thinking on mobile and slow people down. A user should know where to tap before reading every command title.

Step 2: Keep titles short and obvious

Good titles:

Who Am I
Compose PS
Restart Service
Device Login

The title is the human layer. It is what you see above the keyboard before sending, so it should reduce doubt, not add it.

Catalog management, import, and export are Premium features.

Step 3: Mark long-running entries for Stream Mode

Good stream defaults:

Compose Build
Compose Pull
Codex Update

Short entries like pwd, df -h, or docker compose ps should usually stay normal. Your saved commands carry the right execution mode automatically.

Step 4: Import and export when a set is worth reusing

When to export: After you built a useful catalog for Docker, maintenance, or production checks and you want a backup or a shareable set.

When to import: When you want to seed a second device or bring in a known command set without rebuilding it manually.

The catalog should stay small enough that the quick row remains useful. Favor the commands you actually run from a phone.