kiro-steering-custom

Custom steering documents are generated by loading a domain-specific template from .kiro/settings/templates/steering-custom/ and applying project-specific steering principles to produce a tailored file. The process analyzes codebase patterns to ensure the guidance fits the target domain.

Steering documents are tailored project memory files that provide domain-specific guidance on patterns like API standards, testing strategies, and security protocols. They are needed when specialized project contexts require consistent, pattern-focused documentation over exhaustive lists.

To create a .kiro/steering/{name}.md file, provide domain details to trigger the customization flow, which analyzes your codebase patterns and applies steering principles to the chosen template, outputting a 100-200 line markdown file ready for review.

Yes, the steering customization process analyzes existing codebase patterns to tailor the generated guidance for the target domain. It focuses on identifying patterns rather than compiling exhaustive lists to produce coherent project memory.

The best way to maintain consistent project memory is using template-driven generation that enforces steering principles automatically. This approach produces 100-200 line documents that incorporate domain patterns and standardized principles, avoiding time-consuming manual creation.

The generated steering file follows a 100-200 line guideline to keep documentation concise and pattern-focused. While the output is tailored to the domain, it is designed to be reviewed and further customized manually after generation to fit specific needs.