Kiro Best Practices: A Field Guide for Development Teams

Kiro ships updates frequently; typically bi-weekly releases. For the latest features, model availability, and pricing, always check the  Kiro Changelog  and  Kiro Pricing .

Understanding How Kiro Works

CLI vs IDE: Choosing the Right Interface

When to Use the IDE

When to Use the CLI

Installation

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

Side-by-Side Comparison

The Hybrid Approach

Credit Efficiency: Making Every Request Count

For current tier pricing, credit allocations, and model multipliers, see  Kiro Pricing .

What Consumes Credits

Credit Optimization Tactics

# Triggers on every file save in the entire project
filePattern: "**/*"

# Triggers only when API route files change
filePattern: "app/api/**/*.ts"

Memory and System Performance

Where Memory Goes

Note: Recent Kiro updates introduced MCP server connection sharing across sessions, which reduces the total memory footprint when multiple sessions reference the same MCP server.

Memory Optimization for the IDE

{
  "files.watcherExclude": {
    "**/node_modules/**": true,
    "**/build/**": true,
    "**/dist/**": true,
    "**/.git/objects/**": true,
    "**/coverage/**": true
  }
}

{
  "workbench.editor.limit.enabled": true,
  "workbench.editor.limit.value": 10
}

Memory Optimization for the CLI

Machine Sizing Guidance

Context Window Management: The Quality Lever

The Four Context Approaches

Anti-Patterns

# Loads entire codebase into context; burns tokens constantly
/context add src/**/*.py

# Overly broad patterns
/context add **/*

# Everything set to "always" inclusion
inclusion: always  # for every steering file

Correct Patterns

# Semantic search; only loads what is relevant per request
/knowledge add src/ --include "**/*.py"

# Specific, targeted patterns
/context add src/components/**/*.tsx

# Conditional inclusion; loads only when working on matching files
inclusion: fileMatch
fileMatchPattern: "api/**/*"

Essential Commands

Make  /context show  a habit. If your context window is more than 60% full before you have started typing, you have a problem. Move agent resources to Knowledge Bases and steering files from  always  to  fileMatch .

MCP Servers: Extending Context Without Bloating It

Configuration

Example: AWS Documentation Server

{
  "mcpServers": {
    "awslabs.aws-documentation-mcp-server": {
      "command": "uvx",
      "args": ["awslabs.aws-documentation-mcp-server@latest"],
      "env": { "FASTMCP_LOG_LEVEL": "ERROR" }
    }
  }
}

Choosing Reputable MCP Servers

Note: I contributed the  openapi-mcp-server  to AWS Labs MCP. It dynamically generates MCP tools from any OpenAPI specification-compliant REST API, achieving 70-75% reduction in token usage through intelligent prompt generation compared to loading full API specs into context. It supports Basic Auth, Bearer Token, API Key, and Cognito authentication. If your team works with REST APIs, this server can connect the AI to your API endpoints without manually describing each one.

MCP Best Practices

For setup details, see  MCP Configuration documentation .

Steering Files: Teaching Kiro Your Standards

Inclusion Modes

Example: Conditional Steering

# .kiro/steering/api-standards.md
---
inclusion: fileMatch
fileMatchPattern: "app/api/**/*"
---

# API Standards
- Use RESTful conventions with consistent resource naming
- Return consistent error format: { error: string, code: number }
- All endpoints require authentication middleware
- Validate request bodies using schema validation

Recommended Starter Set

Global Steering: Stop Repeating Yourself

~/.kiro/steering/
├── style.md              # Formatting, language preferences
├── testing.md            # Test structure and coverage
├── security.md           # Security essentials
├── docs.md               # Documentation standards
├── git.md                # Commit message formats
└── accessibility.md      # Accessibility requirements

For the full guide, see  Kiro Steering Documentation  and  Stop repeating yourself .

Spec-Driven Development: Think Before You Code

The Three Phases

Spec Types

When to Use Specs vs. Chat

Spec Best Practices

For a deep dive, see  From chat to specs  and  New spec types .

Agent Hooks: Automate the Repetitive

Available Triggers

Practical Examples

Hook Best Practices

For the complete guide, see  Agent hooks guide .

Privacy Considerations

Team Adoption Roadmap

Week 1: Getting Started

Weeks 2-3: Optimization

Ongoing

The Optimization Checklist

Additional Resources

Conclusion