Kilo Code Tool Guide
Updated July 2026
Kilo Code is an AI coding agent used in a coding workspace. PromptDC Desktop rewrites selected requests in place in Kilo Code and also works in the integrated terminal.
Kilo Code tool guide
Rewrite prompts in place inside Kilo 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 Kilo Code.
Why Use PromptDC with Kilo Code?
What changes when you rewrite prompts with PromptDC inside Kilo Code.
Rewrite in Kilo Code
Select a draft in Kilo Code, press Command+Shift+E on Mac or Ctrl+Shift+E on Windows, review the rewrite, and choose Replace.
Structured Kilo Code Requests
The Code profile turns a rough Kilo Code request into implementation-ready instructions covering task, repository scope, plan, constraints, and verification.
Integrated Terminal
PromptDC Desktop also rewrites selected text in the integrated terminal, so you can refine shell or coding instructions without leaving Kilo Code.
Default Profile for Kilo Code
Set Code as the default profile for Kilo Code, 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 Kilo Code rewrite.
Formats and Languages
Choose Text, JSON, XML, or YAML for the rewritten Kilo Code request, and select its output language.
Before and after prompts for Kilo Code
See how specific context, constraints, and outcomes turn a rough request into a prompt Kilo Code can act on.
Plan product search
Before PromptDC
Add search to the products page.
After PromptDC
Add server-backed product search. Inspect routes, database access, and URL-filter patterns first. Propose a short plan before editing. Search name and SKU with debounce and shareable query state. Verify loading, error, no-result, and keyboard-clear states.
Why this is better: The plan phase, repository discovery, semantics, and UI states fit Kilo Code's modes.
Debug empty exports
Before PromptDC
Fix why exports are empty.
After PromptDC
In analysis mode, trace UI filters through API to export query. State the root cause before implementation. Then make the smallest correction. Preserve column order, timezone formatting, and permissions. Test with a non-default date filter.
Why this is better: Separating analysis from implementation protects important export invariants.
Modernize a controller
Before PromptDC
Rewrite this old controller.
After PromptDC
Modernize src/controllers/invoices.js incrementally. Keep routes, bodies, and status codes compatible. Extract validation, then data access, testing each step. Do not change the ORM or unrelated CommonJS files. List remaining debt and follow-up boundaries.
Why this is better: Incremental steps and compatibility rules make a risky rewrite controlled.
Frequently Asked Questions
Learn shortcuts & usage?
Read the shortcuts docs
Need assistance with Kilo 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