kiro-steering-custom

To create custom steering documents, load matching templates from the settings directory, analyze repository files using glob and grep, and output a concise markdown file into the project's steering folder.

Project steering documents capture implicit code patterns and team preferences as reusable project memory. You need them when core steering files are insufficient for specialized domains like API standards or security.

Yes, you can generate API standards and testing strategy documentation by scanning directories like src/api/ for naming and error-handling patterns, synthesizing the findings into a customized steering file.

Use templates by loading files from the custom steering templates directory, which provides a structured baseline. The skill customizes this baseline using your repository's specific code patterns and configurations.

A custom steering file should be a maintainable markdown document of 100 to 200 lines. This concise format ensures the synthesized guidance remains focused and actionable for the project.

To avoid sensitive data in generated project memory files, the document creation process follows established steering principles that explicitly exclude sensitive information and agent-specific tooling from the final output.