Typer and Rich Best Practices

<user_input>$ARGUMENTS</user_input>

If <user_input/> contains a directory or file then that is what should be examined against this guide specifically. Start immediately. If it is empty, then use this as a reference for existing tasks.

Correctness patterns for building CLI applications with Typer and Rich, focused on non-TTY environments and common failure modes. For API reference, load the dedicated skills:

• Skill(skill="python-engineering:typer") — Typer CLI framework API reference
• For Rich API reference, see ../python3-cli/references/rich-console-and-markup.md and related Rich references

Non-TTY and Programmatic Usage

Consult python-engineering:standards-for-python-development for the shared rules (architecture, typing, testing, CLI rules).

See ../python3-cli/references/typer-rich-non-tty-patterns.md — Console behavior without TTY, width defaults, force_terminal vs width, Progress/Live in non-interactive contexts, environment variables.

Rich Table Width Measurement