Day 10: Kiro CLI & Putting It All Together

What You'll Learn Today

Kiro CLI basics
Using Kiro from the terminal
10-day comprehensive review
Practical development workflows

What is Kiro CLI?

Kiro CLI is a command-line interface that lets you use Kiro features from the terminal. Use the AI assistant without opening the IDE.

flowchart LR
    subgraph Terminal["Terminal"]
        A["kiro-cli"]
    end

    subgraph Features["Available Features"]
        B["Interactive Chat"]
        C["Custom Agents"]
        D["MCP Integration"]
        E["Hooks"]
        F["Steering"]
    end

    A --> B
    A --> C
    A --> D
    A --> E
    A --> F

    style Terminal fill:#3b82f6,color:#fff
    style Features fill:#8b5cf6,color:#fff

Difference from IDE Version

Feature	Kiro IDE	Kiro CLI
Interface	GUI	Terminal
Chat	Panel	Interactive
File Editing	Editor	Auto/confirm
Specs	UI managed	Direct files
Hooks	GUI config	Config files

Installation and Basic Usage

Installation

curl -fsSL https://cli.kiro.dev/install | bash

Available on macOS and Linux.

Basic Usage

# Start in project directory
cd my-project
kiro-cli

Interactive Mode

$ kiro-cli

Welcome to Kiro CLI!

You: Explain the project structure

Kiro: This project is a web application using Next.js 15...

You: /exit
Goodbye!

CLI Commands

Basic Commands

Command	Description
`kiro-cli`	Start interactive mode
`kiro-cli "prompt"`	Run single prompt
`kiro-cli --help`	Show help
`kiro-cli --version`	Show version

Commands in Interactive Mode

Command	Description
`/exit`	End conversation
`/clear`	Clear conversation history
`/help`	Show command list
`/model`	Switch model

Usage Examples

# Single question
kiro-cli "Point out issues in this file" < src/api.ts

# Pipe input
cat error.log | kiro-cli "Analyze the cause of this error"

# Interactive mode
kiro-cli

CLI Workflows

Code Review

# Review git diff results
git diff | kiro-cli "Review these code changes"

Bug Fixing

# Analyze error logs
npm run build 2>&1 | kiro-cli "How do I fix this build error?"

Documentation Generation

# Generate README from files
kiro-cli "Generate README for functions in src/utils/ folder"

10-Day Comprehensive Review

Let's review all Kiro features we've learned.

flowchart TB
    subgraph Day1_3["Day 1-3: Foundation"]
        A["Installation"]
        B["Steering"]
        C["Agentic Chat"]
    end

    subgraph Day4_5["Day 4-5: Specs"]
        D["Requirements"]
        E["Design"]
        F["Tasks"]
    end

    subgraph Day6_7["Day 6-7: Hooks"]
        G["Triggers"]
        H["Actions"]
        I["Workflows"]
    end

    subgraph Day8_10["Day 8-10: Extensions"]
        J["MCP"]
        K["Powers"]
        L["CLI"]
    end

    Day1_3 --> Day4_5
    Day4_5 --> Day6_7
    Day6_7 --> Day8_10

    style Day1_3 fill:#3b82f6,color:#fff
    style Day4_5 fill:#06b6d4,color:#fff
    style Day6_7 fill:#ec4899,color:#fff
    style Day8_10 fill:#8b5cf6,color:#fff

Feature Map

Day	Feature	Purpose
1	Installation & Basics	Understand Kiro overview
2	Steering	Share project knowledge
3	Agentic Chat	Effective communication
4	Specs (Requirements)	Clarify requirements
5	Specs (Design/Tasks)	Design and task management
6	Hooks Basics	Event-driven automation
7	Hooks Practice	Advanced automation
8	MCP	External tool integration
9	Powers	One-click feature addition
10	CLI & Integration	Terminal usage, synthesis

Practical Development Workflow

Build a practical workflow combining all features.

Project Initial Setup

flowchart TB
    A["Create Project"] --> B["kiro ."]
    B --> C["Generate Steering"]
    C --> D["Configure Hooks"]
    D --> E["Add Powers"]
    E --> F["Start Development"]

    style A fill:#3b82f6,color:#fff
    style F fill:#22c55e,color:#fff

1. Configure Steering

# Open project in Kiro
kiro .

# Generate Steering docs
# (From Kiro panel: "Generate Steering Docs")

2. Configure Basic Hooks

# .kiro/hooks/format.yaml
name: Auto Format
trigger: onSave
pattern: "**/*.{ts,tsx}"
action: shell
command: "npx prettier --write ${file}"

# .kiro/hooks/lint.yaml
name: Auto Lint
trigger: onSave
pattern: "**/*.{ts,tsx}"
action: shell
command: "npx eslint ${file} --fix"

3. Add Powers

Install needed Powers (Supabase, Stripe, etc.)

Feature Development Flow

flowchart TB
    subgraph Planning["Planning Phase"]
        A["Describe feature requirements"]
        B["Generate Spec"]
        C["Review & adjust"]
    end

    subgraph Implementation["Implementation Phase"]
        D["Select task"]
        E["Kiro implements"]
        F["Auto test"]
    end

    subgraph Review["Review Phase"]
        G["Code review"]
        H["Corrections"]
        I["Complete"]
    end

    Planning --> Implementation
    Implementation --> Review

    style Planning fill:#3b82f6,color:#fff
    style Implementation fill:#8b5cf6,color:#fff
    style Review fill:#22c55e,color:#fff

Step 1: Define Feature Requirements

Add user notification feature.
- Email notifications
- Push notifications
- In-app notifications
- Notification preference customization

Step 2: Generate and Review Spec

Review Requirements, Design, and Tasks generated by Kiro

Step 3: Execute Tasks

Start with T1: Create notification model

Step 4: Auto Validation

Hooks automatically:

Format
Lint
Type check
Run tests

Step 5: Review and Fix

#git diff

Review these changes.
Check especially from a security perspective.

Best Practices Summary

Steering

Keep three basic files updated
Use fileMatch to load only when needed
Include concrete examples and code

Specs

Use EARS syntax to eliminate ambiguity
Keep tasks small with explicit dependencies
Sync Specs with code

Hooks

Configure auto-checks on save
Share and standardize across team
Set patterns considering performance

MCP & Powers

Enable only needed tools
Manage secrets with environment variables
Create team-specific Powers

Troubleshooting

Common Issues

Issue	Solution
Kiro responding slowly	Optimize Steering files, disable unused MCP
Hooks not working	Check patterns and triggers, check logs
Can't connect to MCP	Check environment variables and prerequisites
Specs not generating correctly	Be more specific in requirements description

Debugging Methods

# Check Kiro CLI logs
kiro-cli --verbose

# Test MCP connection
# (Kiro panel > Output > Kiro - MCP Logs)

# Check Hook execution logs
# (Kiro panel > Output > Kiro - Hooks)

Next Steps

You've completed 10 days of Kiro learning. To go deeper:

Official Resources

Community

Join Kiro forums
Share custom Powers
Submit feedback

Practice

Use Kiro on real projects
Introduce Kiro to your team
Continuously improve workflows

Summary

Day	What You Learned
1	Kiro basics, installation
2	Share project knowledge with Steering
3	Communicate effectively with Agentic Chat
4	Clarify requirements with Specs
5	Manage design and implementation with Design/Tasks
6	Event-driven automation with Hooks
7	Advanced Hooks patterns
8	External tool integration with MCP
9	One-click feature addition with Powers
10	CLI usage and integrated workflows

Keys to Mastering Kiro

Practice spec-driven development
Accumulate project knowledge in Steering
Automate repetitive tasks with Hooks
Extend capabilities with MCP and Powers
Continuously improve workflows

Final Exercise

Comprehensive Exercise

Create a mini-project with these requirements:

Configure Steering
- product.md: TODO app
- tech.md: Next.js + TypeScript
- structure.md: Appropriate structure
Create Specs
- Requirements for task addition feature
- Design (API design, component design)
- Tasks breakdown
Configure Hooks
- Auto-format on save
- Test generation on component create
Implementation
- Execute tasks based on Specs
- Utilize Kiro's suggestions
Review
- Code review with #git diff
- Apply improvements

Evaluation Points

References

Congratulations! You've completed 10 days of Kiro learning. Now use Kiro to achieve more efficient and higher quality development.