.kiro/steering/kiro-aws-parameter-store.md. Downloaded files need to be placed in that repository path.--- inclusion: fileMatch fileMatchPattern: "**/*" --- Parameter Store: 1. Parameters 2. Hierarchies 3. SecureString 4. Access patterns 5. Lambda access
Kiro
cloud
Kiro, built and operated by AWS, uses steering files: Markdown documents in .kiro/steering/ that give the agent persistent project knowledge. Front matter controls when each file is included: always, when matching files are in context, manually by #name, or automatically by description. Kiro also includes AGENTS.md files.
.kiro/steering/kiro-aws-parameter-store.mdStarting point, not a tested configuration for your repository. Included when files matching fileMatchPattern are in context. Review the instructions, adapt the file paths and run your project's existing checks.
--- inclusion: fileMatch fileMatchPattern: "**/*" --- Parameter Store: 1. Parameters 2. Hierarchies 3. SecureString 4. Access patterns 5. Lambda access
Ask for a small change to one matching file. Check the tool's loaded context or instruction view, inspect the diff for the requested convention, and run the relevant build or test. A well-formatted file does not guarantee the model follows every instruction.
Front matter must be at the very beginning of a steering file to be recognized. Kiro supports AGENTS.md. According to the steering docs, AGENTS.md files do not support inclusion modes and are always included, so keep scoped guidance in .kiro/steering/ files instead.
Documentation checked 2026-11-05: Kiro docs: SteeringKiro home page