kiro-steering

Bootstrap or synchronize .kiro/steering/ documents from repository templates and principles.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-steering-taku-o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-steering
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-steering-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a concise, principle-driven project memory in .kiro/steering/ so teams have a single, reviewable source of patterns and decisions rather than sprawling, out-of-sync documentation. The Skill prevents documentation drift by detecting mismatches between code and steering content and ensures updates are additive and preservative of user edits.

Core Features & Use Cases

  • Bootstrap steering: Generate core steering files (product.md, tech.md, structure.md) from repository signals and templates when steering is missing.
  • Sync and detect drift: Analyze the codebase on demand, detect code→steering or steering→code mismatches, and propose additive updates while preserving custom sections.
  • Principles-driven output: Apply steering-principles.md to keep guidance at the pattern/rationale level (not exhaustive lists), and avoid documenting settings or secrets.
  • Use case: Bootstrapping steering for a new repository to produce concise guidance on purpose, tech stack, and organization, or regularly syncing steering to surface new architectural patterns and recommended next files.

Quick Start

Run a repository analysis to bootstrap or sync .kiro/steering/ using the skill's templates and steering-principles.md to generate or update product.md, tech.md, and structure.md.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema
How do I prevent documentation drift between my codebase and project steering files?▼

To prevent documentation drift, you can sync project steering files by analyzing the codebase on demand to detect code→steering mismatches and propose additive updates while preserving custom edits.

What is project steering memory and when do I need it?▼

Project steering memory is a concise, principle-driven source of patterns and decisions stored in .kiro/steering/ files, needed when you want a reviewable source of architectural guidance instead of sprawling documentation.

How do I bootstrap steering documentation for a new repository?▼

Bootstrap steering documentation by running a repository analysis to generate core files like product.md, tech.md, and structure.md from repository signals and templates when steering is missing.

Can I sync steering documents without overwriting my custom sections?▼

Yes, you can sync steering documents without losing customizations because the sync process proposes additive updates and preserves user edits while applying steering principles to maintain pattern-focused guidance.

What's the best way to maintain concise architectural patterns in project memory?▼

The best way to maintain concise architectural patterns is applying steering-principles.md to keep guidance at the pattern and rationale level, avoiding exhaustive lists or documenting settings and secrets.

Does the steering sync process document repository settings and secrets?▼

No, the steering sync process explicitly avoids documenting settings and secrets, focusing instead on producing pattern-focused steering updates that capture architectural decisions and rationale.