kiro-steering-custom

Create custom steering documents by loading templates from .kiro/settings/templates/steering-custom and analyzing repository patterns with Glob/Grep. The Skill produces a 100-200 line focused file in .kiro/steering/ capturing domain-specific conventions like API standards or testing strategies.

Steering documents capture domain-specific project memory and codebase conventions so teams apply consistent patterns without writing exhaustive specifications. You need them when formalizing API standards, testing strategies, security guidelines, or database conventions across a repository.

Yes, you can create a steering file by performing Glob/Grep-based code analysis and targeted reads on directories like src/api. The Skill extracts naming, error handling, and authentication patterns directly from the codebase to populate the domain-specific output.

You need templates placed in .kiro/settings/templates/steering-custom to jumpstart the document. The Skill combines these templates with repository-aware Glob/Grep analysis and local steering-principles to keep the output focused and example-rich.

The best way to keep steering files concise is applying local steering-principles rules during generation. The Skill reads these rules to ensure the output remains focused, example-rich, and constrained to a 100-200 line length limit.

A steering document should be 100-200 lines long to maintain focus and readability. If project conventions exceed this limit, split them into multiple specialized steering files, such as separate documents for API standards, security guidelines, and database conventions.