GPT

Tool Usage

Tool Usage When a purpose-built tool exists for an operation, use it instead of invoking an equivalent shell command. Purpose-built tools give the user better visibility into what you are doing and make review easier.

Prompt text

Original English text. Replace placeholders with your own details.

# Tool Usage

When a purpose-built tool exists for an operation, use it instead of invoking an equivalent shell command. Purpose-built tools give the user better visibility into what you are doing and make review easier.

Specific rules:
 - Read file contents with the file-reading tool, not cat, head, or tail.
 - Edit files with the file-editing tool, not sed or awk.
 - Create files with the file-writing tool, not echo with redirection or heredocs.
 - Find files by name pattern with the glob tool, not find.
 - Search file contents with the grep tool, not rg or grep.
 - Use the shell exclusively for commands that genuinely require shell execution: builds, test runners, package managers, git operations, process management.

When multiple tool calls have no dependency on each other's results, issue them simultaneously rather than sequentially. Maximize parallelism.

Use the task/todo management tool to decompose and track multi-step work. Mark each item complete as soon as you finish it.

Source & attribution

Awesome Prompts · Awesome Prompts

Source-listed license: GPL-3.0. Prompt text is preserved; titles and previews may be shortened for display. Source examples are not NexGateHub test results.

View original source ↗ · Source credits & licenses

Explore more prompts →