Put project rules in steering files
Kiro steering files use markdown to give Kiro persistent project knowledge, including established patterns, libraries, and standards. Workspace steering files live in .kiro/steering/ and apply to that workspace. Kiro steering documentation
Global steering files live in ~/.kiro/steering/ and apply across workspaces. If global and workspace instructions conflict, Kiro prioritizes the workspace instructions. Kiro steering documentation
Choose when each instruction applies
Write custom steering in standard markdown and describe requirements in natural language. Kiro makes created steering files available across interactions. Kiro steering documentation
Steering files can use inclusion modes. always applies every interaction, fileMatch applies when working with matching files, manual makes a file available through a #steering-file-name reference, and auto uses its name and description to decide relevance. Kiro steering documentation
Use Kiro's foundation files and AGENTS.md
Kiro can generate product.md, tech.md, and structure.md in .kiro/steering/; these foundation files are included in every interaction by default. Kiro steering documentation
Kiro also supports AGENTS.md. It can discover these files in the global steering location, workspace root, and subdirectories. Unlike steering files with inclusion modes, AGENTS.md files are always included. Kiro steering documentation
Add steering to custom agents
Custom agents do not include steering files automatically. Add steering resources to the agent configuration; the file://.kiro/steering/**/*.md pattern loads markdown files from that steering directory. Kiro steering documentation
Give Kiro directions as you work
You can also guide Kiro during a session by giving directions in chat. For Kiro Web, feedback on pull requests can teach the agent patterns for future work across repositories, and only feedback from the task's creator affects what it learns. Kiro steering documentation
Where KnowMan fits
Steering files hold instructions about how Kiro should work. KnowMan is a separate personal knowledge base for articles and links you save. Its MCP tools include kb_search for finding saved items, kb_get_item for reading one item, kb_ask for questions with citations, and kb_save for saving a URL with an optional note. Kiro steering documentation KnowMan MCP guide
KnowMan's MCP server is a local stdio server. KnowMan MCP guide
Questions people ask
Where should I put Kiro project instructions?
Put workspace steering files in .kiro/steering/ at the project root. They apply only to that workspace. Kiro steering documentation
Can Kiro use instructions across all workspaces?
Global steering files go in ~/.kiro/steering/ and apply to all workspaces. Workspace steering takes priority when instructions conflict. Kiro steering documentation
How can Kiro find my saved articles?
KnowMan provides kb_search to search saved items and kb_get_item to read an item. KnowMan's MCP server is a local stdio server. KnowMan MCP guide
Can I connect KnowMan to Kiro now?
KnowMan's MCP server is local and uses stdio. KnowMan MCP guide