Kiro Tool Guide
Updated July 2026
Kiro is an AI coding workspace for specifications and implementation. PromptDC for Desktop rewrites your prompt in place in Kiro and covers its integrated terminal.
Kiro tool guide
Rewrite prompts in place inside Kiro.
Works everywhere
PromptDC for 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.
Why Use PromptDC with Kiro?
What PromptDC for Desktop does inside Kiro.
Review before Replace
Select your prompt, use the desktop shortcut, and review the rewrite before Replace or Copy.
Clearer prompts
Turn a rough request into a complete prompt with the details Kiro needs before you send it.
Supported app coverage
PromptDC for Desktop works in supported coding apps and their integrated terminals.
Set coding defaults
Choose any profile that fits, or add your own profiles and Custom Actions.
Reuse saved context
On the Code profile, use Always Include for project rules. Custom Action works with any profile for one-off guidance.
Choose output formats
On the Code profile, choose Regular, JSON, XML, or YAML output. Auto keeps your prompt's original language on every profile.
Before and after prompts for Kiro
Rough request on the left, the PromptDC rewrite on the right.
Before
Create a spec for adding SAML login to this app.
After
Create a Kiro spec for organization level SAML single sign on in the open repository. Requirements: domain discovery, signed assertions, user linking, session expiry, and password fallback. Design: reuse current authentication boundaries and identify security sensitive decisions. Tasks: sequence implementation, migration, testing, documentation, and rollout work.
Why this is better: The prompt gives Kiro requirements, design concerns, and task structure for a complete SAML spec.
Before
Fix requirements staying in progress after all their tasks finish.
After
Fix requirement status so it reflects all current child task states. Inspect the existing spec aggregation, edits, deletion, undo, and session restore paths. Exclude cancelled tasks and ensure a requirement with no tasks is not marked complete. Add tests for every transition and preserve current status names and stored data format.
Why this is better: The prompt adds lifecycle and aggregation rules so Kiro can repair requirement completion reliably.
Before
How should our spec handle long audit retention and deletion requests?
After
Add a design section for seven year audit retention and customer deletion requests. Assess the repository's current storage, partitioning, tenant keys, and deletion workflow. Define what is retained, anonymized, deleted, or made inaccessible and explain each tradeoff. Identify unresolved legal or product decisions instead of silently choosing policy.
Why this is better: The prompt separates technical design from policy choices so Kiro can document retention tradeoffs.
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 in any app on desktop, in browsers, in your editor or terminals.
Download PromptDC