What problem does it solve?
Teams need concise, project-specific steering documents that capture patterns, conventions, and domain knowledge without producing exhaustive specifications; this Skill streamlines creation of those focused steering files so knowledge is preserved and discoverable.
Core Features & Use Cases
- Template-driven authoring: Load and customize templates from .kiro/settings/templates/steering-custom/ (api-standards, testing, security, etc.) to jumpstart documents.
- Repository-aware analysis: Use glob/grep/read operations to extract domain patterns from code and tests and synthesize them into practical guidance.
- Principles-first output: Produce concise .kiro/steering/{name}.md files that follow steering-principles.md (patterns over lists, single-domain focus, security-first).
- Use Case: Create an API standards steering file by loading the api-standards template, analyzing src/api/, and generating a 100–200 line project memory describing endpoint naming, error formats, and auth patterns.
Quick Start
Create a custom API standards steering file named api-standards.md by loading the api-standards template and analyzing the src/api/ directory for naming, error handling, and authentication patterns.