kiro-steering

Bootstrap and sync persistent project steering in .kiro/steering/ to prevent drift.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-steering-shimamatz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-steering
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-steering-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap and maintain persistent project steering stored in .kiro/steering/ to prevent drift.

Core Features & Use Cases

  • Bootstrap: Generate core steering content from the codebase using templates and principles.
  • Sync: Detect drift between steering and code, apply additive updates, and preserve user customizations.
  • Principles: Load guiding principles from rules/steering-principles.md to inform updates and guardrails.

Quick Start

Run the bootstrap process to generate core steering, then run sync regularly to keep steering aligned with the codebase.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema
How do I prevent project steering drift as my codebase evolves?▼

To prevent project steering drift, you can bootstrap persistent steering content in .kiro/steering/ and run regular syncs to detect codebase changes and apply additive updates while preserving customizations.

What is project steering and how does template-driven generation work?▼

Project steering is persistent documentation stored in .kiro/steering/ that aligns with code. Template-driven generation extracts patterns from the codebase using templates and principles to bootstrap core steering files.

How do I sync steering files when the codebase changes without losing custom rules?▼

Syncing steering files detects drift between code and steering, then applies additive updates that preserve user customizations. This ensures alignment without overwriting existing rules in .kiro/steering/.

Can I load custom steering principles to guide project updates?▼

Yes, you can load custom steering principles from rules/steering-principles.md. These principles inform updates, guardrails, and template-driven steering generation to keep project memory aligned.

What's the best way to maintain project memory across ongoing development?▼

The best way to maintain project memory is to bootstrap steering content initially, then run regular syncs. This detects drift, applies additive updates, and preserves user customizations in .kiro/steering/.

When should I not use additive updates for steering sync?▼

Additive updates are designed for ongoing development to preserve user customizations. If you need a complete regeneration of steering content from templates, additive sync may not be the appropriate approach.