Answer: Steering files are best for rules that should always apply, including coding standards, deployment conventions, team context, workflow rules, and boundaries. Examples include "always use TypeScript strict mode," "run tests before marking work done," and "don't modify files in the /vendor directory." Status: Confirmed Entry: tool/kiro/memory-and-context/steering-file-content Revision: 2 Digest: sha256:f0046ceef5116cfa (changes whenever the content changes) Timeline: Created: 2026-11-13T03:38:12Z Last changed: 2026-11-20T13:22:39Z (boundaries: — → don't modify files in the /vendor directory) Last verified: 2026-11-20T13:22:39Z Next check: 2026-11-21T13:22:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of coding standards | always use TypeScript strict mode | [1] | 2026-11-20 deployment conventions | run tests before marking work done | [1] | 2026-11-20 team context | we use Jira for tickets | [1] | 2026-11-20 workflow rules | always create a branch before making changes | [1] | 2026-11-20 boundaries | don't modify files in the /vendor directory | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Steering - Agent Capabilities - Crew - Docs - Kiro". https://kiro.dev/docs/crew/capabilities/steering/ Role: primary. Accessed: 2026-11-20T13:22:39Z Quote: "Coding standards — "always use TypeScript strict mode," "prefer named exports"" (Supports: coding standards) Quote: "Deployment conventions — "run tests before marking work done," "never push to main directly"" (Supports: deployment conventions) Quote: "Team context — "we use Jira for tickets," "the staging URL is staging.example.com"" (Supports: team context) Quote: "Workflow rules — "always create a branch before making changes," "commit messages follow conventional commits"" (Supports: workflow rules) Quote: "Boundaries — "don't modify files in the /vendor directory," "ask before deleting anything"" (Supports: boundaries) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 3944386dd456ec7e065d68a5ee284e0a1fa8eef4cfa5eace05911b6bacfd2718 (captured 2026-11-20T13:22:36Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:22:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:22:39Z Last attempt: 2026-11-20T13:22:39Z Notes and limitations: Extracted automatically from a single official source (section "What to put in steering files"). Related: https://latestn.com/tool/kiro/memory-and-context/steering-file-references How do I reference files inside a Kiro steering file? https://latestn.com/tool/kiro/memory-and-context/steering-file-scope What is the difference between workspace, global, and team steering in Kiro? https://latestn.com/tool/kiro/memory-and-context/steering-files-multi-root How do steering files behave in Kiro multi-root workspaces? https://latestn.com/tool/kiro/memory-and-context/review-memory How can I review what Kiro remembers about my project? https://latestn.com/tool/kiro/memory-and-context/set-up-steering-files How do I set up steering files in Kiro? https://latestn.com/tool/kiro/memory-and-context/setup-steering-files How do I set up Kiro steering files to guide the agent? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:22:39Z | changed | boundaries: — → don't modify files in the /vendor directory | [1] 2026-11-20T13:22:39Z | changed | workflow rules: — → always create a branch before making changes | [1] 2026-11-20T13:22:39Z | changed | team context: — → we use Jira for tickets | [1] 2026-11-20T13:22:39Z | changed | deployment conventions: — → run tests before marking work done | [1] 2026-11-20T13:22:39Z | changed | coding standards: — → always use TypeScript strict mode | [1] 2026-11-20T13:22:39Z | changed | Boundaries: don't modify files in the /vendor directory → — | [1] 2026-11-20T13:22:39Z | changed | Workflow rules: always create a branch before making changes → — | [1] 2026-11-20T13:22:39Z | changed | Team context: we use Jira for tickets → — | [1] 2026-11-20T13:22:39Z | changed | Deployment conventions: run tests before marking work done → — | [1] 2026-11-20T13:22:39Z | changed | Coding standards: always use TypeScript strict mode → — | [1] 2026-11-13T03:38:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/memory-and-context/steering-file-content/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/memory-and-context/steering-file-content POST: https://latestn.com/dispute/tool/kiro/memory-and-context/steering-file-content with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/memory-and-context/steering-file-content?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What should I put in Kiro Crew steering files? Revision 2, last verified 2026-11-20T13:22:39Z. https://latestn.com/tool/kiro/memory-and-context/steering-file-content (accessed 2026-11-21T09:58:51Z). @misc{LatestN_tool_kiro_memory_and_context_steering_file_content_r2, title = {What should I put in Kiro Crew steering files?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/memory-and-context/steering-file-content}}, note = {Revision 2; digest sha256:f0046ceef5116cfa; last verified 2026-11-20T13:22:39Z; accessed 2026-11-21T09:58:51Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/memory-and-context/steering-file-content