Tooling Operations

Use the project tools that already exist instead of recreating their workflows manually.

Workflow

Identify whether the task is PDF work or a helper-command workflow.
Use the matching tool directly.
Stop and ask only when the required tool is missing or the task needs a capability the tool does not provide.

Use Poppler for any PDF processing.
If Poppler is not installed, stop and ask the user.
Prefer Poppler tools such as pdfinfo, pdftotext, and pdftoppm over ad hoc alternatives.

Use gbr when the user wants to create a branch, commit, push, and open an MR or PR.
Use remote to open a pod shell or run a command in *-dev, *-stg, *-uat, or *-prod namespaces.
Use remote-tinker for php artisan tinker code in remote pods, especially when the snippet contains $, ->, quotes, closures, or spans multiple lines.
Use remote-info for concise namespace diagnostics and resource usage. Use --full only when the expanded snapshot is needed.
Use hosts to list, add, or delete hosts entries. Let the command handle backups and cleanup.

Prefer the purpose-built helper command over rebuilding the same behavior with lower-level commands.
Keep command usage aligned with the tool's supported workflow instead of layering custom wrappers on top.
When relevant, suggest tool choices or workflow improvements that would make the task faster, safer, or more repeatable.