Kiro Steering Files: 90 Ready Files for 8 Stacks + Checker

Stack facts were checked in November 2026 against each framework's official docs and release notes (for example Next.js 16 proxy.ts and async params, Django 6 Tasks and CSP, Rails 8 params.expect and Solid Queue, Supabase publishable keys and getClaims()).

python3 tools/kirokit.py detect /path/to/project          # which stacks it finds
python3 tools/kirokit.py install /path/to/project --dry-run
python3 tools/kirokit.py install /path/to/project          # writes .kiro/steering/
#   edit .kiro/steering/product.md, tech.md, structure.md (replace the TODO lines)
python3 tools/kirokit.py check /path/to/project/.kiro/steering

• --stack nextjs --stack supabase picks stacks yourself. --global installs the core files into ~/.kiro/steering/ for every workspace.
• The installer never overwrites a file you already have (it reports kept). --force overwrites and saves a .bak copy first.
• Languages are added only when the project has them (a go.mod, .tf files, a Dockerfile ...).

Finds the problems that make steering silently not load:

• front matter that is not the very first content (Kiro then ignores it), YAML errors, unknown keys
• inclusion values other than always, fileMatch, manual, auto
• fileMatch without fileMatchPattern, a comma string instead of a list, bad globs (./src/..., backslashes, src**, unbalanced braces)
• auto without name and description, duplicate names
• Cursor (globs, alwaysApply) or Cline (paths) front matter pasted into Kiro
• #[[file:...]] / #[[file:path:12-28]] / #[[folder:...]] references that don't resolve
• secrets (API keys, tokens, private keys) in a committed file
• TODO placeholders left in always-included files, and the token budget of everything that loads on every request

Exit code 1 on any error, so you can run it in CI. --json for machine output.

python3 tools/kirokit.py match --dir .kiro/steering app/blog/[slug]/page.tsx

Lists the always-included files, the fileMatch files that match, and the auto/manual files you can pull in.

python3 tools/kirokit.py convert .cursor/rules --out .kiro/steering

alwaysApply: true -> inclusion: always; globs -> inclusion: fileMatch with a fileMatchPattern list; description-only rules -> inclusion: auto with name + description; everything else -> manual. Also reads .clinerules/ (paths) and .cursorrules. AGENTS.md needs no conversion: Kiro reads it directly.

./tools/demo.sh installs the Next.js set into a copy of examples/nextjs-app, checks it, shows what loads for a page file, checks examples/broken-steering (7 typical mistakes) and converts examples/cursor-rules.

./run_tests.sh (19 tests, Python 3.9+): every shipped file passes the checker; all four inclusion modes are used; key stack facts are present; the broken example produces each expected error; install is idempotent, never overwrites, --force makes a backup, --dry-run writes nothing; match and convert results; glob matching; the demo runs.

• match uses common glob rules (a pattern without /, like *.tsx, matches the file name in any folder). Kiro's own matcher may differ on unusual patterns, so confirm in Kiro's Steering panel.
• auto inclusion depends on Kiro matching your request to the description; it is not deterministic.
• Kiro CLI V1/V2 only auto-loads always files (V3 supports all four modes).
• Written against Kiro's steering docs as of November 2026. Rules are guidance for the agent, not a guarantee of output; review what it writes.