Claude Code Tool Guide
Updated July 2026
Claude Code is an AI coding CLI for repository work. PromptDC Desktop detects Claude Code and rewrites the selected prompt in the terminal before you press Enter.
Claude Code tool guide
Rewrite prompts in place inside Claude Code.
Works everywhere
PromptDC Desktop works in any app on Mac or Windows. The Chrome extension covers any website.
In-Place Rewrites
Transform rough notes into clear, structured instructions instantly.
See PromptDC in Action
This demo shows the standard PromptDC flow, and it works the same way in Claude Code.
Why Use PromptDC with Claude Code?
What changes when you rewrite prompts with PromptDC inside Claude Code.
Claude Code CLI Detection
PromptDC Desktop detects Claude Code in the terminal and tailors the selected draft before you press Enter. It does not run the CLI or send commands.
Claude Code Coding Briefs
The Code profile turns a rough terminal draft into implementation-ready instructions covering task, repository scope, constraints, sequencing, and verification.
Verified Terminal Support
Rewrite Claude Code prompts in verified macOS and Windows terminals, including supported integrated terminals.
Profile Shortcuts
Assign a shortcut to the Code profile for Claude Code, and keep separate shortcuts for Concise or Custom Action rewrites.
Reusable Repository Rules
Use Always Include to carry repository conventions, protected files, and required commands into each Claude Code rewrite.
Formats and Languages
Choose Text, JSON, XML, or YAML for the rewritten Claude Code prompt, and select its output language.
Before and after prompts for Claude Code
See how specific context, constraints, and outcomes turn a rough request into a prompt Claude Code can act on.
Refactor payments
Before PromptDC
Clean up the payment code.
After PromptDC
Refactor packages/api/src/payments without behavior changes. Map entry points, side effects, and tests first. Put provider logic behind the existing PaymentGateway interface. Preserve Stripe webhook signature verification exactly. Run targeted tests and typecheck; summarize risks and files.
Why this is better: Repository scope, invariants, sequence, and verification make the refactor safer.
Implement a prune command
Before PromptDC
Add a command that removes old caches.
After PromptDC
Add tool cache prune under packages/cli. Default to dry run; print path, age, and size. Require --confirm; accept --older-than in days. Never follow symlinks or leave the configured cache directory. Test dry run, confirmation, boundaries, and empty state.
Why this is better: Safe defaults, filesystem boundaries, flags, and tests protect a destructive command.
Investigate flaky uploads
Before PromptDC
Fix the flaky upload tests.
After PromptDC
Investigate test/upload.integration.test.ts failures. Run repeatedly and inspect timing, shared state, and cleanup. Do not solve primarily with retries or longer timeouts. Make the smallest deterministic fix and explain the race. Report reproduction rates before and after.
Why this is better: The prompt demands evidence and rules out superficial timeout workarounds.
Frequently Asked Questions
Learn shortcuts & usage?
Read the shortcuts docs
Need assistance with Claude Code?
Contact help & support
Write better with AI
Enhance any text you select on the desktop, on the web, in your editor or terminals.
Download PromptDC