kiro-steering

To maintain project memory and prevent documentation drift, you can use steering sync to detect changes in your codebase and propose additive updates to core documentation files without overwriting your customizations.

The best way to bootstrap initial steering documentation is to analyze the codebase and generate core files like product.md, tech.md, and structure.md using predefined templates and pattern-based steering principles.

Non-destructive steering synchronization works by reading existing markdown files and templates, detecting content drift, and proposing additive updates rather than overwriting user content, preserving all customizations.

Yes, you can use custom templates by placing them in the settings directory, and the generation process will load steering principles from a dedicated rules file to drive pattern-based project memory creation.

A limitation of detecting drift across core project files is that synchronization relies on file reading and pattern matching, meaning unstructured content outside of markdown templates may not trigger accurate additive update proposals.

You need persistent steering when you want to maintain consistent architectural guidelines and project memory over time, ensuring that bootstrapped guidance stays synchronized with your evolving codebase.