kiro-steering

Maintain .kiro/steering as persistent project memory with additive updates.

2|Updated Apr 8, 2026

Search Tags:#documentation #patterns #sync #drift-detection #bootstrap #steering #project-memory

Ready to run

npx skills add https://github.com/snicmakino/kolt --skill kiro-steering-snicmakino

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/snicmakino/kolt/tree/main/.claude/skills/kiro-steering
Command: npx skills add https://github.com/snicmakino/kolt --skill kiro-steering-snicmakino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains .kiro/steering/ as persistent project memory, ensuring bootstrapped guidance and ongoing synchronization as the codebase evolves, while preserving user customizations.

Core Features & Use Cases

Bootstrap: generate core steering from codebase using templates and project analysis.
Sync: detect drift and propose additive updates to core steering without overwriting user content.
Principles: reference rules in rules/steering-principles.md to drive pattern-based steering.

Quick Start

Bootstrap the steering for a new project, then keep it synchronized as the codebase evolves.

Frequently Asked Questions about kiro-steering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain project memory and prevent documentation drift as my codebase evolves?▼

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.

What is the best way to bootstrap initial steering documentation for a new project?▼

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.

How does non-destructive steering synchronization work with existing markdown files?▼

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.

Can I use custom templates and principles to drive project memory generation?▼

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.

What limitations exist when detecting drift across core project files?▼

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.

When do I need persistent steering for my software engineering workflow?▼

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.