Mastering Kiro: Spec-Driven AI Development

Learn how to autonomously build software using the Kiro Agentic IDE.

← Back to Dashboard

Prerequisites

Before diving into autonomous coding, ensure your IDE is ready:

Step 1: The Steering Directory

Kiro differs from standard coding assistants by remembering your context permanently. It does this using the steering directory.

Create a .kiro/steering/ folder in the root of your project. Inside, create a file called conventions.md:

# Coding Conventions
1. Always use TypeScript with strict mode enabled.
2. Follow the React functional component architecture.
3. Use TailwindCSS for all styling unless explicitly told otherwise.
4. Always write unit tests before implementing the core logic.

Kiro will automatically read this file before every action it takes, ensuring you never have to repeat yourself in chat prompts.

Step 2: Spec-Driven Development

Instead of chatting line-by-line, you command Kiro using specifications. Create a requirements.md file detailing what you want to build:

# Feature Requirements: Authentication
- Implement a login page with Email and Google OAuth.
- Store session tokens securely using HttpOnly cookies.
- Redirect unauthenticated users from `/dashboard` to `/login`.

Once your spec is ready, simply tag Kiro in the chat (e.g. @requirements.md Implement this feature). Kiro will analyze the entire spec, plan the architecture, and begin generating the code autonomously.

Step 3: Autonomous Task Execution

For large projects, you can break work down into a tasks.md file. Using Kiro's Agent Hooks, you can instruct Kiro to work through the list.

# tasks.md
- [ ] Initialize Next.js project with Tailwind.
- [ ] Setup Firebase Authentication.
- [ ] Build the User Profile page.

You can tell Kiro: Work on the next unchecked item in tasks.md. Kiro will write the code, verify it builds, check the box, and wait for your approval to proceed to the next item!