Kiro — Rules
- File format
- Markdown
- Discovery path
-
.kiro/steering - Syllago install method
- Project scope, Direct copy
- Symlink support
- Yes
- Native frontmatter fields
-
inclusion,fileMatchPattern,name,description
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Fields
Native frontmatter or config fields this provider exposes. The first column is the provider's own field name; the canonical key column links to syllago's cross-provider equivalent.
| Provider field | Conversion | Canonical key | Summary |
|---|---|---|---|
inclusion | Conversion type: No canonical equivalent — appended as prose in a conversion notes block so nothing is silently lost. Learn more → | — | Frontmatter field controlling when a steering file loads (always, conditional via globs, manual, or auto). |
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|---|---|
activation_mode | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | kiro_steering_inclusion_mode: Kiro steering files support always, conditional, and manual inclusion modes |
cross_provider_recognition | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | kiro_agents_md_recognition: Kiro reads AGENTS.md files from other providers in addition to its own steering files |
file_imports | Translated Conversion type: Translated Actively mapped to the target provider’s equivalent field during conversion. Learn more → | kiro_steering_file_references: Kiro steering files can reference other files using @file syntax |
| File references (@path/to/file) in steering files | Preserved Conversion type: Preserved Syntax survives conversion but the target provider may not interpret it. Learn more → | Body syntax '@path/to/file' that Kiro inlines into the steering context, enabling modular composition. |
| AGENTS.md root file recognition | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Kiro reads repo-root AGENTS.md as a steering source, matching the cross-provider AGENTS.md convention. |
| Foundational steering files (auto-created) | Not portable Conversion type: Not portable Unique to this provider — can’t be carried across providers. Learn more → | Kiro auto-creates product_requirements.md, tech_stack.md, and architecture.md on workspace init. |
Sources
| Source |
|---|
| https://kiro.dev/docs/steering/ |