Tutorial

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 of 4Waiting for confirmation

Step 1: Start with jobs, not abstractions

sshChat App
Good categories
Start
Files
Docker
Production
Bad categories

Very broad names like Misc or Utilities force extra thinking on mobile and slow people down.

Goal

A user should know where to tap before reading every command title.

Step 2: Keep titles short and obvious

sshChat AppRemote Server
Good titles
Who Am I
Compose PS
Restart Service
Device Login
Why

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

Premium note

Catalog management, import, and export are Premium features.

Step 3: Mark long-running entries for Stream Mode

sshChat App
Good stream defaults
Compose Build
Compose Pull
Codex Update
Leave normal

Short entries like pwd, df -h, or docker compose ps should usually stay normal.

Result

Your saved commands carry the right execution mode automatically.

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

sshChat App
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.

Do not overcomplicate it

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