kiro-agent-team 1.0.0

package/.kiro/documentation/docs_cli_chat_context.md

@@ -0,0 +1,258 @@
+# Context management
+## Choosing the right context approach[](https://kiro.dev/docs/cli/chat/context/#choosing-the-right-context-approach)
+Kiro offers three ways to provide context, each optimized for different use cases:
+Approach | Context Window Impact | Persistence | Best For  
+---|---|---|---  
+Agent Resources | Always active (consumes tokens) | Persistent across sessions | Essential project files, standards, configs  
+Session Context | Always active (consumes tokens) | Current session only | Temporary files, quick experiments  
+Knowledge Bases | Only when searched | Persistent across sessions | Large codebases, extensive documentation  
+## Decision flowchart[](https://kiro.dev/docs/cli/chat/context/#decision-flowchart)
+  1. Use this decision tree to choose the appropriate context approach:
+     * Is your content larger than 10MB or contains thousands of files? 
+       * Yes → Use Knowledge Bases
+       * No → Continue to step 2
+  2. Do you need this context in every conversation?
+     * Yes → Use Agent Resources
+     * No → Use Session Context
+
+
+### Quick reference[](https://kiro.dev/docs/cli/chat/context/#quick-reference)
+  * Essential project files (README, configs, standards) → Agent Resources
+  * Large codebases or documentation sets → Knowledge Bases
+  * Temporary files for current task → Session Context
+
+
+## Understanding context window impact[](https://kiro.dev/docs/cli/chat/context/#understanding-context-window-impact)
+  * Context files and agent resources consume tokens from your context window on every request, whether referenced or not.
+
+
+bash
+```
+
+> /context show
+
+Agent 
+  - .kiro/steering/**/*.md  <project-root>/.kiro/steering/product.md
+<project-root>/.kiro/steering/structure.md
+<project-root>/.kiro/steering/tech.md
+<project-root>/.kiro/steering/testing.md
+  - README.md <project-root>/snake/README.md
+  - ~/.kiro/steering/**/*.md (no matches)
+
+Session (temporary)
+  <none>
+
+5 matched files in use
+- <project-root>/.kiro/steering/testing.md (0.1% of context window)
+- <project-root>/snake/.kiro/steering/tech.md (0.1% of context window)
+- <project-root>/snake/README.md (0.1% of context window)
+- <project-root>/snake/.kiro/steering/structure.md (0.2% of context window)
+- <project-root>/snake/.kiro/steering/product.md (0.1% of context window)
+
+Context files total: 0.5% of context window
+
+
+```
+
+  * The output shows:
+    * **Agent** : Persistent context from your agent's resources field
+    * **Session** : Temporary context added during the current session
+  * Context files are limited to 75% of your model's context window. Files exceeding this limit are automatically dropped.
+  * Knowledge bases don't consume context window space until searched, making them ideal for large reference materials. For more information, see Knowledge base context (for large datasets).
+
+
+## Managing context[](https://kiro.dev/docs/cli/chat/context/#managing-context)
+Context files contain information you want Kiro to consider during your conversations. These can include project requirements, coding standards, development rules, or any other information that helps Kiro provide more relevant responses.
+### Configuring persistent context with agent resources[](https://kiro.dev/docs/cli/chat/context/#configuring-persistent-context-with-agent-resources)
+The recommended way to configure context is through the resources field in your agent configuration file. This creates persistent context that is available every time you use the agent.
+Add file paths or glob patterns to the resources array in your agent config:
+json
+```
+
+{
+  "name": "my-agent",
+  "description": "My development agent",
+  "resources": [
+    "file://README.md",
+    "file://docs/**/*.md",
+    "file://src/config.py"
+  ]
+}
+
+
+```
+
+Resources must be prefixed with file:// to be included as context files. These files will be automatically available in all chat sessions using this agent.
+### Adding temporary session context[](https://kiro.dev/docs/cli/chat/context/#adding-temporary-session-context)
+You can temporarily add files to your current chat session using the /context add command. These additions are only available for the current session and will not persist when you start a new chat session.
+bash
+```
+
+> /context add README.md
+Added 1 path(s) to context.
+
+
+```
+
+**Note** : Context modifications via slash command is temporary.
+You can also add multiple files at once using glob patterns:
+bash
+```
+
+> /context add docs/*.md
+Added 3 path(s) to context.
+
+
+
+```
+
+To make context changes permanent, add the files to your agent's resources field instead. For more information, see Configuring persistent context with agent resources.
+### Knowledge base context (for large datasets)[](https://kiro.dev/docs/cli/chat/context/#knowledge-base-context-for-large-datasets)
+For large codebases, documentation sets, or reference materials that would exceed context window limits, use knowledge bases. Knowledge bases provide semantic search capabilities without consuming context window space until searched.
+Enable knowledge bases:
+kiro-cli settings chat.enableKnowledge true
+Add content to a knowledge base:
+kiro-cli chat
+> /knowledge add /path/to/large-codebase --include "**/*.py" --exclude "node_modules/** "
+Knowledge bases are searched on-demand by Kiro when relevant information is needed, making them ideal for large reference materials.
+### Viewing context usage[](https://kiro.dev/docs/cli/chat/context/#viewing-context-usage)
+To view your current context, use the /context show command:
+bash
+```
+
+> /context show
+
+Current context window (5.9% used)
+|||████████████████████████████████████████████████████████████████ 5.9%
+
+█ Context files 0.9%
+█ Tools 0.5%
+█ Kiro responses 0.7%
+█ Your prompts 3.8%
+
+
+```
+
+### Removing context[](https://kiro.dev/docs/cli/chat/context/#removing-context)
+To remove files from your current session context:
+bash
+```
+
+> /context remove src/temp-file.py
+Removed 1 path(s) from context.
+
+
+```
+
+To clear all session context, use the /context clear command:
+bash
+```
+
+> /context clear
+Cleared context
+Note: Context modifications via slash command is temporary.
+
+
+```
+
+Note: You cannot remove agent-defined context using /context commands. To permanently remove context, edit your agent's resources field.
+## Context management actions[](https://kiro.dev/docs/cli/chat/context/#context-management-actions)
+Here are some common reasons for actively managing your context window:
+  1. If you find yourself repeatedly adding the same context files using `/context add` commands, consider moving them to your agent's resources field for persistence:
+
+
+bash
+```
+
+# Instead of running these commands every session:
+> /context add README.md
+> /context add docs/*.md
+
+# Add them to your agent config once:
+{
+  "resources": [
+    "file://README.md",
+    "file://docs/**/*.md"
+  ]
+}
+
+
+```
+
+You can configure a default agent that includes your preferred context files. This ensures your context is automatically available in new chat sessions without needing to specify the agent each time.
+bash
+```
+
+   >kiro-cli settings chat.defaultAgent my-project-agent
+
+
+```
+
+  1. If you have large context files (consume significant part of context window) consider using knowledge base instead of including those files as is. Use cases to consider knowledge: 
+     * You have large codebases or documentation sets
+     * You need semantic search across extensive materials
+     * You want to avoid constant context window consumption
+     * Example: Instead of adding a large codebase as context files:
+
+
+bash
+```
+
+# This would consume too many tokens:
+> /context add src/**/*.py
+
+# Use knowledge base instead:
+> /knowledge add src/ --include "**/*.py" --exclude "__pycache__/**"
+
+
+```
+
+## Best practices[](https://kiro.dev/docs/cli/chat/context/#best-practices)
+### Context file organization[](https://kiro.dev/docs/cli/chat/context/#context-file-organization)
+  1. Keep context files focused and relevant to avoid token limits
+  2. Use descriptive filenames that indicate their purpose
+  3. Organize rules and documentation in logical directory structures
+  4. Consider file size - very large files may consume significant tokens
+
+
+### Performance considerations[](https://kiro.dev/docs/cli/chat/context/#performance-considerations)
+  1. Monitor token usage with /context show to stay within limits
+  2. Use specific glob patterns rather than overly broad ones
+  3. Remove unused context files from agent configurations
+  4. Consider splitting large context files into smaller, focused files
+  5. Use knowledge bases for large datasets to avoid context window consumption
+
+
+### Security considerations[](https://kiro.dev/docs/cli/chat/context/#security-considerations)
+  1. Avoid including sensitive information in context files
+  2. Use `.gitignore` to prevent accidental commits of sensitive context
+  3. Review context files regularly to ensure they don't contain outdated information
+  4. Be mindful of what information is shared when using context in conversations
+
+
+## Related documentation[](https://kiro.dev/docs/cli/chat/context/#related-documentation)
+  * [Slash Commands](https://kiro.dev/docs/cli/reference/slash-commands) - In-chat context commands
+  * [CLI Commands](https://kiro.dev/docs/cli/reference/cli-commands) - Terminal context commands
+  * [Interactive Chat Mode](https://kiro.dev/docs/cli/chat/interactive-mode) - Using context in chat
+
+
+Page updated: November 21, 2025
+[Prompts](https://kiro.dev/docs/cli/chat/manage-prompts/)
+[Responding to messages](https://kiro.dev/docs/cli/chat/responding/)
+On this page
+  * [Choosing the right context approach](https://kiro.dev/docs/cli/chat/context/#choosing-the-right-context-approach)
+  * [Decision flowchart](https://kiro.dev/docs/cli/chat/context/#decision-flowchart)
+  * [Quick reference](https://kiro.dev/docs/cli/chat/context/#quick-reference)
+  * [Understanding context window impact](https://kiro.dev/docs/cli/chat/context/#understanding-context-window-impact)
+  * [Managing context](https://kiro.dev/docs/cli/chat/context/#managing-context)
+  * [Configuring persistent context with agent resources](https://kiro.dev/docs/cli/chat/context/#configuring-persistent-context-with-agent-resources)
+  * [Adding temporary session context](https://kiro.dev/docs/cli/chat/context/#adding-temporary-session-context)
+  * [Knowledge base context (for large datasets)](https://kiro.dev/docs/cli/chat/context/#knowledge-base-context-for-large-datasets)
+  * [Viewing context usage](https://kiro.dev/docs/cli/chat/context/#viewing-context-usage)
+  * [Removing context](https://kiro.dev/docs/cli/chat/context/#removing-context)
+  * [Context management actions](https://kiro.dev/docs/cli/chat/context/#context-management-actions)
+  * [Best practices](https://kiro.dev/docs/cli/chat/context/#best-practices)
+  * [Context file organization](https://kiro.dev/docs/cli/chat/context/#context-file-organization)
+  * [Performance considerations](https://kiro.dev/docs/cli/chat/context/#performance-considerations)
+  * [Security considerations](https://kiro.dev/docs/cli/chat/context/#security-considerations)
+  * [Related documentation](https://kiro.dev/docs/cli/chat/context/#related-documentation)

package/.kiro/documentation/docs_cli_chat_git-aware-selection.md

@@ -0,0 +1,41 @@
+# Working with Git
+When working with Git repositories, Kiro CLI's fuzzy finder is Git-aware, making it easier to select and add relevant files to your context. This feature helps you quickly identify and include files that are part of your Git repository.
+## How Git-aware selection works[](https://kiro.dev/docs/cli/chat/git-aware-selection/#how-git-aware-selection-works)
+The Git-aware fuzzy finder automatically integrates with your repository's Git information to provide enhanced file selection capabilities:
+  * Recognizes Git-tracked files in your repository
+  * Shows Git status indicators alongside files
+  * Prioritizes relevant files based on Git history
+
+
+## Using Git-aware file selection[](https://kiro.dev/docs/cli/chat/git-aware-selection/#using-git-aware-file-selection)
+###### To use git-aware file selection[](https://kiro.dev/docs/cli/chat/git-aware-selection/#to-use-git-aware-file-selection)
+  1. Navigate to your Git repository in the terminal.
+  2. Run the context add command:
+```
+
+/context add
+
+
+```
+
+  3. In the fuzzy finder interface, you'll see files from your repository with Git status indicators:
+     * `M` – Modified files
+     * `A` – Added files
+     * `?` – Untracked files
+  4. Type to filter files, using Git status as part of your search criteria.
+  5. Use the arrow keys to navigate and press Enter to select files to add to your context.
+
+
+## Tips for Git-aware selection[](https://kiro.dev/docs/cli/chat/git-aware-selection/#tips-for-git-aware-selection)
+  * Use Git status indicators in your search to quickly find modified or untracked files
+  * The fuzzy finder prioritizes recently modified files in Git history
+  * Files ignored by Git (via .gitignore) are still available but deprioritized in the results
+
+
+Page updated: November 17, 2025
+[Permissions](https://kiro.dev/docs/cli/chat/permissions/)
+[Images](https://kiro.dev/docs/cli/chat/images/)
+On this page
+  * [How Git-aware selection works](https://kiro.dev/docs/cli/chat/git-aware-selection/#how-git-aware-selection-works)
+  * [Using Git-aware file selection](https://kiro.dev/docs/cli/chat/git-aware-selection/#using-git-aware-file-selection)
+  * [Tips for Git-aware selection](https://kiro.dev/docs/cli/chat/git-aware-selection/#tips-for-git-aware-selection)

package/.kiro/documentation/docs_cli_chat_images.md

@@ -0,0 +1,53 @@
+# Working with images
+Kiro can analyze and discuss images directly in your chat session. You can share images with Kiro by dragging and dropping them into your terminal window or by using the `read` tool with the Image mode.
+## Drag and drop images[](https://kiro.dev/docs/cli/chat/images/#drag-and-drop-images)
+The simplest way to share images with Kiro is to drag and drop them directly into your terminal window. When you drag an image into the terminal:
+  1. The image path is automatically inserted into your prompt
+  2. You can then add text to provide context about what you want Kiro to do with the image
+  3. Kiro will process the image and respond based on its content
+
+
+Example:
+```
+
+Kiro> /path/to/architecture-diagram.png Can you explain this architecture and generate sample code for implementing it?
+
+
+```
+
+## Using fs_read with images[](https://kiro.dev/docs/cli/chat/images/#using-fs_read-with-images)
+You can also explicitly use the `read` tool to share images:
+```
+
+Kiro> Can you analyze this screenshot at /path/to/screenshot.png?
+
+
+```
+
+Kiro will automatically suggest using fs_read with Image mode when you mention image files.
+## Image use cases[](https://kiro.dev/docs/cli/chat/images/#image-use-cases)
+Common use cases for sharing images with Kiro include:
+  * Analyzing screenshots of error messages for troubleshooting
+  * Converting architecture diagrams into code implementations
+  * Discussing UI/UX designs and generating corresponding HTML/CSS
+  * Understanding flowcharts and translating them into algorithms
+  * Reviewing code snippets shared as images
+  * Interpreting technical diagrams for documentation
+
+
+## Supported formats and limitations[](https://kiro.dev/docs/cli/chat/images/#supported-formats-and-limitations)
+Supported image formats include JPEG/JPG, PNG, GIF, and WebP. Images must be under 10MB in size, and you can share up to 10 images in a single request.
+For best results:
+  * Use high-resolution images with clear text
+  * Provide specific instructions about what you want Kiro to do with the image
+  * For complex diagrams, consider providing additional context
+
+
+Page updated: November 25, 2025
+[Working with Git](https://kiro.dev/docs/cli/chat/git-aware-selection/)
+[Security considerations](https://kiro.dev/docs/cli/chat/security/)
+On this page
+  * [Drag and drop images](https://kiro.dev/docs/cli/chat/images/#drag-and-drop-images)
+  * [Using fs_read with images](https://kiro.dev/docs/cli/chat/images/#using-fs_read-with-images)
+  * [Image use cases](https://kiro.dev/docs/cli/chat/images/#image-use-cases)
+  * [Supported formats and limitations](https://kiro.dev/docs/cli/chat/images/#supported-formats-and-limitations)

package/.kiro/documentation/docs_cli_chat_manage-prompts.md

@@ -0,0 +1,216 @@
+# Manage prompts
+The Kiro CLI provides comprehensive prompt management capabilities for both local prompts and Model Context Protocol (MCP) prompts. This system allows you to create, edit, organize, and use reusable prompts across your development workflow.
+## About prompt types[](https://kiro.dev/docs/cli/chat/manage-prompts/#about-prompt-types)
+The prompt system supports three types of prompts:
+  * **Local prompts** : Project-specific prompts stored in your workspace
+  * **Global prompts** : User-wide prompts available across all projects
+  * **MCP prompts** : Prompts provided by MCP servers with enhanced functionality
+
+
+## Commands[](https://kiro.dev/docs/cli/chat/manage-prompts/#commands)
+All prompt management is accessed through the `/prompts` command with various subcommands.
+### List prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#list-prompts)
+```
+
+/prompts list
+
+
+```
+
+Displays all available prompts in a three-column layout showing names, descriptions, and sources. Shows prompt counts and indicates which prompts come from local storage, global storage, or MCP servers.
+### Create prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#create-prompts)
+```
+
+/prompts create --name name [--content content]
+
+
+```
+
+Creates a new local prompt in the current workspace.
+###### Parameters[](https://kiro.dev/docs/cli/chat/manage-prompts/#parameters)
+`name` (required) : Prompt name (maximum 50 characters)
+`--content content` (optional) : Direct content specification
+**Behavior:**
+  * If `--content` is provided, creates prompt with specified content
+  * If no content provided, opens your default editor for content creation
+  * Prompts are saved to `.kiro/prompts/` in the current workspace
+
+
+### Edit prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#edit-prompts)
+```
+
+/prompts edit name
+
+
+```
+
+Opens an existing prompt in your default editor for modification.
+**Supported prompts:**
+  * Local workspace prompts
+  * Global user prompts
+  * MCP prompts (where supported by the server)
+
+
+### View prompt details[](https://kiro.dev/docs/cli/chat/manage-prompts/#view-prompt-details)
+```
+
+/prompts details name
+
+
+```
+
+Shows comprehensive information about a prompt including:
+  * Metadata and argument details
+  * Complete prompt content before AI processing
+  * Parameter requirements and examples
+  * Source information (local, global, or MCP server)
+
+
+## Using prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#using-prompts)
+Once you've created prompts, invoke them in chat using the @ prefix:
+```
+
+@prompt-name
+
+
+```
+
+### Examples[](https://kiro.dev/docs/cli/chat/manage-prompts/#examples)
+```
+
+@code-review
+# Uses your local code-review prompt
+
+
+```
+
+```
+
+@team-standup
+# Uses your team-standup prompt
+
+
+```
+
+## Passing arguments to MCP prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#passing-arguments-to-mcp-prompts)
+MCP server prompts can accept arguments to customize their behavior. File-based prompts (local and global) do not support arguments.
+### MCP prompt argument syntax[](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompt-argument-syntax)
+```
+
+@server-name/prompt-name <required-arg> [optional-arg]
+
+
+```
+
+Use `/prompts details prompt-name` to discover what arguments an MCP prompt accepts.
+```
+
+# Example: Using MCP prompt with arguments
+@dev-tools/analyze "performance issue" "detailed"
+@security-tools/scan "web-app" "high-severity"
+
+
+```
+
+## Storage locations[](https://kiro.dev/docs/cli/chat/manage-prompts/#storage-locations)
+### Local prompts (workspace-specific)[](https://kiro.dev/docs/cli/chat/manage-prompts/#local-prompts-workspace-specific)
+  * **Location** : `project/.kiro/prompts/`
+  * **Scope** : Available only within the current project
+  * **Priority** : Highest (overrides global and MCP prompts with same name)
+
+
+### Global prompts (user-wide)[](https://kiro.dev/docs/cli/chat/manage-prompts/#global-prompts-user-wide)
+  * **Location** : `~/.kiro/prompts/`
+  * **Scope** : Available across all projects
+  * **Priority** : Medium (overrides MCP prompts with same name)
+
+
+### MCP prompts[](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompts)
+  * **Source** : Provided by configured MCP servers
+  * **Scope** : Depends on server configuration
+  * **Priority** : Lowest (overridden by local and global prompts)
+
+
+## Priority system[](https://kiro.dev/docs/cli/chat/manage-prompts/#priority-system)
+When multiple prompts have the same name, the system uses this priority order:
+  1. **Local prompts** (highest priority)
+  2. **Global prompts**
+  3. **MCP prompts** (lowest priority)
+
+
+This allows you to override MCP or global prompts with project-specific versions when needed.
+## Enhanced features[](https://kiro.dev/docs/cli/chat/manage-prompts/#enhanced-features)
+### Content preview[](https://kiro.dev/docs/cli/chat/manage-prompts/#content-preview)
+The system displays the complete prompt content before sending it to the AI model, eliminating confusion about what information was actually processed.
+### Improved error handling[](https://kiro.dev/docs/cli/chat/manage-prompts/#improved-error-handling)
+  * MCP server errors are converted to user-friendly messages
+  * Helpful usage examples are generated from prompt metadata
+  * Clear guidance for invalid parameters or missing requirements
+
+
+### Visual formatting[](https://kiro.dev/docs/cli/chat/manage-prompts/#visual-formatting)
+  * Consistent terminal styling across all prompt operations
+  * Proper content display for all prompt message types
+  * Three-column layout for improved readability in listings
+
+
+## MCP integration[](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-integration)
+The prompt system seamlessly integrates with MCP servers:
+  * **Automatic discovery** : MCP prompts are automatically discovered from configured servers
+  * **Enhanced UX** : Improved user experience for MCP prompt management
+  * **Error translation** : Raw JSON errors are converted to actionable messages
+  * **Content preview** : Full content preview for MCP prompts before execution
+
+
+## Examples[](https://kiro.dev/docs/cli/chat/manage-prompts/#examples-1)
+These examples demonstrate file-based prompt creation and MCP prompt usage.
+### Basic file-based prompt creation and usage[](https://kiro.dev/docs/cli/chat/manage-prompts/#basic-file-based-prompt-creation-and-usage)
+```
+
+# Create a simple prompt without arguments
+/prompts create --name code-review --content "Please review this code for best practices, security issues, and potential improvements:"
+
+# Use the prompt (no arguments supported for file-based prompts)
+@code-review
+
+
+```
+
+### MCP prompt usage with arguments[](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompt-usage-with-arguments)
+```
+
+# Using MCP prompts with arguments
+@dev-tools/analyze "performance bottleneck" "cpu usage"
+@security-tools/scan "web-app" "high-severity"
+@aws-tools/deploy "my-service" "production" "us-west-2"
+
+
+```
+
+Page updated: November 16, 2025
+[Planning Agent](https://kiro.dev/docs/cli/chat/planning-agent/)
+[Context management](https://kiro.dev/docs/cli/chat/context/)
+On this page
+  * [About prompt types](https://kiro.dev/docs/cli/chat/manage-prompts/#about-prompt-types)
+  * [Commands](https://kiro.dev/docs/cli/chat/manage-prompts/#commands)
+  * [List prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#list-prompts)
+  * [Create prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#create-prompts)
+  * [Edit prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#edit-prompts)
+  * [View prompt details](https://kiro.dev/docs/cli/chat/manage-prompts/#view-prompt-details)
+  * [Using prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#using-prompts)
+  * [Examples](https://kiro.dev/docs/cli/chat/manage-prompts/#examples)
+  * [Passing arguments to MCP prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#passing-arguments-to-mcp-prompts)
+  * [MCP prompt argument syntax](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompt-argument-syntax)
+  * [Storage locations](https://kiro.dev/docs/cli/chat/manage-prompts/#storage-locations)
+  * [Local prompts (workspace-specific)](https://kiro.dev/docs/cli/chat/manage-prompts/#local-prompts-workspace-specific)
+  * [Global prompts (user-wide)](https://kiro.dev/docs/cli/chat/manage-prompts/#global-prompts-user-wide)
+  * [MCP prompts](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompts)
+  * [Priority system](https://kiro.dev/docs/cli/chat/manage-prompts/#priority-system)
+  * [Enhanced features](https://kiro.dev/docs/cli/chat/manage-prompts/#enhanced-features)
+  * [Content preview](https://kiro.dev/docs/cli/chat/manage-prompts/#content-preview)
+  * [Improved error handling](https://kiro.dev/docs/cli/chat/manage-prompts/#improved-error-handling)
+  * [Visual formatting](https://kiro.dev/docs/cli/chat/manage-prompts/#visual-formatting)
+  * [MCP integration](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-integration)
+  * [Examples](https://kiro.dev/docs/cli/chat/manage-prompts/#examples-1)
+  * [Basic file-based prompt creation and usage](https://kiro.dev/docs/cli/chat/manage-prompts/#basic-file-based-prompt-creation-and-usage)
+  * [MCP prompt usage with arguments](https://kiro.dev/docs/cli/chat/manage-prompts/#mcp-prompt-usage-with-arguments)