Getting Started with AWS Kiro

What is AWS Kiro?

AWS Kiro is an agentic IDE that helps you go from prototype to production with spec-driven development. Unlike traditional AI coding assistants that only provide code completion, Kiro takes a structured approach:

• Specs - Plan features using requirements, design, and tasks
• Hooks - Automate testing, documentation, and quality checks
• Agents - AI assistants that execute tasks autonomously

Installation & Setup

Your First Project

The best way to learn Kiro is through the built-in tutorial. However, here's what you'll experience:

Example prompt: "Add a review system for products"

# requirements.md

## User Stories

### View Reviews
WHEN a user visits a product page
THE SYSTEM SHALL display all reviews for that product

### Submit Review  
WHEN a user submits a review with valid data
THE SYSTEM SHALL save the review and display confirmation

### Rate Products
WHEN a user selects a star rating (1-5)
THE SYSTEM SHALL record the rating with the review

# design.md

## Architecture

### Database Schema
```sql
CREATE TABLE reviews (
  id SERIAL PRIMARY KEY,
  product_id INTEGER NOT NULL,
  user_id INTEGER NOT NULL,
  rating INTEGER CHECK (rating >= 1 AND rating <= 5),
  content TEXT,
  created_at TIMESTAMP DEFAULT NOW()
);
```

### API Endpoints
- GET /api/products/:id/reviews
- POST /api/products/:id/reviews
- PUT /api/reviews/:id
- DELETE /api/reviews/:id

# tasks.md

## Implementation Tasks

- [ ] Create Review model and database migration
- [ ] Implement GET /api/products/:id/reviews endpoint  
- [ ] Implement POST /api/products/:id/reviews endpoint
- [ ] Create ReviewForm React component
- [ ] Create ReviewList React component
- [ ] Add form validation for reviews
- [ ] Write unit tests for Review model
- [ ] Write integration tests for API endpoints
- [ ] Update product page to display reviews
- [ ] Add loading states and error handling

Understanding the Spec-Driven Workflow

Kiro's three-phase workflow ensures quality from requirements to code:

1. Requirements Phase

Define WHAT you're building using EARS format:

• WHEN [condition] THE SYSTEM SHALL [behavior]
• Forces clarity and testability
• Covers edge cases automatically

2. Design Phase

Define HOW you'll build it:

• Architecture diagrams and data flows
• Database schemas and API contracts
• Component hierarchies and interfaces

3. Implementation Phase

Execute the plan step by step:

• Tasks ordered by dependencies
• Built-in quality checks (tests, docs, security)
• Incremental delivery and verification

Setting up Your First Hook

Hooks automate repetitive tasks. Here's how to create a hook that runs tests when you save files:

# .kiro/hooks/test-on-save.yml
name: "Run Tests on Save"
trigger: onSave
pattern: "**/*.{js,ts,jsx,tsx}"
action: |
  Review the saved file and related test files.
  If tests exist, run them and report results.
  If no tests exist, suggest creating them.

Next Steps

Now that you have Kiro running, explore these advanced features:

• Master Spec Writing - Learn advanced EARS syntax and design patterns
• Hook Automation - Set up CI/CD, security scans, and documentation
• EARS Format Deep Dive - Write better requirements
• Kiro vs Copilot - Understand when to use each tool