Answer: When designing slash commands, use descriptive names, keep commands focused on a specific repeatable task, and define the expected outcome; when using them, make required input clear and add relevant context when needed. Status: Confirmed Entry: tool/kiro/commands-and-shortcuts/slash-command-best-practices Revision: 1 Digest: sha256:1a98d3bdb040de5f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:35Z Last changed: 2026-11-13T03:42:35Z Last verified: 2026-11-20T13:29:18Z Next check: 2026-11-21T13:29:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Design best practice 1 | Use descriptive names | [1] | 2026-11-20 Design best practice 2 | Keep commands focused | [1] | 2026-11-20 Design best practice 3 | Define the expected outcome | [1] | 2026-11-20 Usage best practice 1 | Make required input clear | [1] | 2026-11-20 Usage best practice 2 | Add relevant context when needed | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Slash commands - Chat - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/chat/slash-commands/ Role: primary. Accessed: 2026-11-20T13:29:18Z Quote: "Use descriptive names : Choose names that clearly communicate what the command does" (Supports: Design best practice 1) Quote: "Keep commands focused : Create each command for a specific, repeatable task." (Supports: Design best practice 2) Quote: "Define the expected outcome : Include enough instruction for the agent to understand what completing the command means." (Supports: Design best practice 3) Quote: "Make required input clear : Provide the context or arguments the command needs to do its job." (Supports: Usage best practice 1) Quote: "Add relevant context when needed : Combine slash commands with steering files and # context providers" (Supports: Usage best practice 2) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 13bcca6c8ee2f247bc5f330941cb4923ebd3ff30dc35b5c71d2d8af8990ca9bc (captured 2026-11-20T13:29:18Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:29:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:18Z Last attempt: 2026-11-20T13:29:18Z Notes and limitations: Extracted automatically from a single official source (section "Best practices"). Related: https://latestn.com/tool/kiro/commands-and-shortcuts/start-voice-input How do I start voice input in Kiro CLI? https://latestn.com/tool/kiro/commands-and-shortcuts/tangent-commands What commands are available for managing tangents in Kiro CLI? https://latestn.com/tool/kiro/commands-and-shortcuts/teams-commands What commands does the Kiro Crew Teams integration support? https://latestn.com/tool/kiro/commands-and-shortcuts/scripting-with-exit-codes How do I handle Kiro CLI exit codes in a bash script or CI/CD pipeline? https://latestn.com/tool/kiro/commands-and-shortcuts/scroll-conversation-fullscreen How do I scroll through the conversation in Kiro CLI fullscreen mode? https://latestn.com/tool/kiro/commands-and-shortcuts/slack-slash-commands What slash commands are available in the Kiro Crew Slack interface? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:42:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/commands-and-shortcuts/slash-command-best-practices/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/slash-command-best-practices POST: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/slash-command-best-practices with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/commands-and-shortcuts/slash-command-best-practices?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What best practices should I follow when designing and using slash commands in Kiro? Revision 1, last verified 2026-11-20T13:29:18Z. https://latestn.com/tool/kiro/commands-and-shortcuts/slash-command-best-practices (accessed 2026-11-21T10:08:05Z). @misc{LatestN_tool_kiro_commands_and_shortcuts_slash_command_best_practices_r1, title = {What best practices should I follow when designing and using slash commands in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/commands-and-shortcuts/slash-command-best-practices}}, note = {Revision 1; digest sha256:1a98d3bdb040de5f; last verified 2026-11-20T13:29:18Z; accessed 2026-11-21T10:08:05Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/commands-and-shortcuts/slash-command-best-practices