steering

Package structure

How a steering package is discovered and laid out in a repo.

A source repo is discovered in this order:

  1. a steering.json manifest at the root
  2. .md files inside a steering/ directory
  3. .md files at the repo root

steering.json

{
  "name": "incu-standards",
  "version": "1.0.0",
  "steering": [
    {
      "name": "security",
      "description": "OWASP + banking",
      "file": "steering/security.md"
    }
  ]
}

Per-file frontmatter

Each steering file is a .md with optional frontmatter (the canonical Kiro schema):

---
inclusion: always | fileMatch | manual | auto
fileMatchPattern: "**/*.java"   # only when inclusion: fileMatch
description: "..."              # only when inclusion: auto
---

# Steering file content

Invalid frontmatter is reported as a warning — it never blocks installation. With no frontmatter, Kiro assumes inclusion: always.

Sources

Source types supported by steering add.

Scopes & lock files

Where files are installed and how the lock files work.

On this page

steering.jsonPer-file frontmatter