Kiro: `.kiro/steering/*.md` location, format and template

Where Kiro reads project instructions, whether it reads AGENTS.md, and what the format allows. From the official documentation, checked Oct 7, 2026. See also Kiro: pricing, popularity and alternatives.

Project files

.kiro/steering/*.md, including the generated product.md, tech.md and structure.md
AGENTS.md at the root and in subfolders

Global (all projects)

~/.kiro/steering/

AGENTS.md

✓ Yes, always included.

Format and limits

Front matter inclusion: always (default), fileMatch (with fileMatchPattern), manual or auto (needs name and description).
Reference files with #[[file:path]].

Sources: kiro.dev/docs/steering/

Templates

Kiro steering file for the API.kiro/steering/api-standards.md

---
inclusion: fileMatch
fileMatchPattern: "src/api/**/*.ts"
---

# API standards
- REST resources are plural nouns; errors use the shared error type.
- Every endpoint has an integration test.

AGENTS.md for a TypeScript projectAGENTS.md

# AGENTS.md

## Project
One paragraph: what this repository does and who uses it.

## Commands
- Install: `pnpm install`
- Dev server: `pnpm dev`
- Tests: `pnpm test` (run before you finish)
- Lint and types: `pnpm lint && pnpm typecheck`

## Layout
- `src/app/`: routes and pages
- `src/lib/`: shared logic, no UI code
- `tests/`: mirrors `src/`

## Conventions
- TypeScript strict mode; avoid `any`.
- Follow the patterns already in `src/` before adding new ones.
- Small, focused functions; name things for what they do.

## Boundaries
- Never read or edit `.env*` files or commit secrets.
- Ask before adding a dependency or changing a public API.

## Done means
Tests pass, lint is clean, and the change is explained in the PR description.

Written by AgentGid as a starting point; swap in your own commands and folders.

Kiro: .kiro/steering/*.md location, format and template