Copilot Tool Guide
Updated July 2026
VS Code with GitHub Copilot is a coding workspace for editing, chat, and terminal work. PromptDC Desktop rewrites selected requests in place in Copilot and also works in the integrated terminal.
Copilot tool guide
Rewrite prompts in place inside Copilot.
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 Copilot.
Why Use PromptDC with Copilot?
What changes when you rewrite prompts with PromptDC inside Copilot.
Rewrite in Copilot
Select a draft in Copilot, press Command+Shift+E on Mac or Ctrl+Shift+E on Windows, review the rewrite, and choose Replace.
Structured Copilot Requests
The Code profile turns a rough Copilot request into implementation-ready instructions covering task, file scope, local patterns, constraints, and tests.
Integrated Terminal
PromptDC Desktop also rewrites selected text in the integrated terminal, so you can refine shell or coding instructions without leaving Copilot.
Default Profile for Copilot
Set Code as the default profile for Copilot, and assign per-profile shortcuts for other rewrite tasks.
Reusable Project Rules
Use Always Include to carry repository conventions, protected files, and required commands into each Copilot rewrite.
Formats and Languages
Choose Text, JSON, XML, or YAML for the rewritten Copilot request, and select its output language.
Before and after prompts for Copilot
See how specific context, constraints, and outcomes turn a rough request into a prompt Copilot can act on.
Generate a unit test
Before PromptDC
Write tests for this function.
After PromptDC
In src/discounts/calculateDiscount.test.ts, use Vitest. Match the table-driven style in adjacent pricing tests. Cover zero, tier boundaries, cap, and unknown customer type. Use exact currency values and do not mock pure helpers. Do not edit production code without a confirmed defect.
Why this is better: File context, local conventions, edge cases, and scope make Copilot's completion useful.
Complete a React hook
Before PromptDC
Make this hook fetch user data.
After PromptDC
Implement src/hooks/useUserProfile.ts. Use apiClient and TanStack Query v5 patterns nearby. Key by userId and disable when userId is absent. Preserve typed ApiError and five-minute stale time. Match the return shape of useAccount.
Why this is better: Repository patterns, library version, caching, and return contract remove guesswork.
Document a public function
Before PromptDC
Add docs to this code.
After PromptDC
Add TSDoc for exported parseSchedule. Explain cron subset, timezone behavior, and thrown errors. Include one weekly and one invalid example. Do not restate the signature or document private helpers. Match terminology in docs/scheduling.md.
Why this is better: It focuses documentation on useful behavior and established repository language.
Frequently Asked Questions
Learn shortcuts & usage?
Read the shortcuts docs
Need assistance with Copilot?
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