Kiro Tool Guide
Updated July 2026
Kiro is an AI coding workspace for specifications and implementation. PromptDC Desktop rewrites selected requests in place in Kiro and also works in the integrated terminal.
Kiro tool guide
Rewrite prompts in place inside Kiro.
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 Kiro.
Why Use PromptDC with Kiro?
What changes when you rewrite prompts with PromptDC inside Kiro.
Rewrite in Kiro
Select a draft in Kiro, press Command+Shift+E on Mac or Ctrl+Shift+E on Windows, review the rewrite, and choose Replace.
Structured Kiro Requests
The Code profile turns a rough Kiro request into implementation-ready instructions covering requirements, design boundaries, implementation tasks, and acceptance criteria.
Integrated Terminal
PromptDC Desktop also rewrites selected text in the integrated terminal, so you can refine shell or coding instructions without leaving Kiro.
Default Profile for Kiro
Set Code as the default profile for Kiro, and assign per-profile shortcuts for other rewrite tasks.
Reusable Project Rules
Use Always Include to carry repository conventions, product rules, and required commands into each Kiro rewrite.
Formats and Languages
Choose Text, JSON, XML, or YAML for the rewritten Kiro request, and select its output language.
Before and after prompts for Kiro
See how specific context, constraints, and outcomes turn a rough request into a prompt Kiro can act on.
Specify report notifications
Before PromptDC
Add notifications when reports finish.
After PromptDC
Create a feature spec for report-completion notifications. Users choose email, in-app, both, or neither by report type. Cover failures, duplicates, timezones, and preference changes. Write EARS-style acceptance criteria. Produce design and tasks, without implementing.
Why this is better: The request uses Kiro's spec workflow to make behavior testable before code.
Define repository steering
Before PromptDC
Make the agent follow our coding style.
After PromptDC
Derive steering guidance from this repository. Inspect scripts, TypeScript, tests, APIs, and components. Document only patterns supported by two examples. Include lint, typecheck, test, and build commands. Separate product context from engineering conventions.
Why this is better: Persistent guidance is based on evidence instead of generic preferences.
Design audit retention
Before PromptDC
Delete old audit logs.
After PromptDC
Specify enterprise audit-log retention. Default 365 days; admins choose 90 to 2555. Never delete legal-hold records; batch resumably. Cover authorization, auditability, recovery, and visible status. Produce requirements, architecture, and ordered tasks.
Why this is better: Deletion becomes a safe policy feature with permissions and recovery.
Frequently Asked Questions
Learn shortcuts & usage?
Read the shortcuts docs
Need assistance with Kiro?
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