kiro-steering

Bootstrap and sync .kiro/steering markdown files while preserving user content.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/manatago/gion --skill kiro-steering-manatago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/manatago/gion/tree/main/.claude/skills/kiro-steering
Command: npx skills add https://github.com/manatago/gion --skill kiro-steering-manatago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a concise, living project memory in the repository so that product and technical guidance (steering) stays aligned with the codebase and user customizations are preserved.

Core Features & Use Cases

  • Bootstrap steering: Generate core steering documents (product.md, tech.md, structure.md) from repository patterns when steering is missing.
  • Sync and detect drift: Analyze the codebase to detect divergences between steering guidance and code, then propose additive updates while preserving user sections.
  • Preservation-first updates: Always avoid overwriting custom content and add timestamps and rationales when changes are suggested.
  • Use case: Initialize steering for a new repo to create project memory, or run periodic syncs to surface architecture or convention changes and recommended steering edits.

Quick Start

Bootstrap or sync the .kiro/steering folder by generating or updating product.md, tech.md, and structure.md from the codebase while preserving any user customizations.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema
How do I bootstrap steering documents for a new repository?

To bootstrap steering documents, the skill generates core markdown files like product.md, tech.md, and structure.md by analyzing existing code patterns to create persistent project memory.

What is the best way to detect code drift in project documentation?

Detect code drift by running a sync that analyzes the codebase against existing steering guidance, proposes additive updates, and reports divergences while preserving user customizations.

Does updating project steering files overwrite my custom sections?

Updating steering files uses a preservation-first approach, ensuring custom content is never overwritten; suggested changes are additive and include timestamps and rationales.

Can I use this skill on a repository without a .kiro/steering folder?

You can use this skill on repositories without a .kiro/steering folder to bootstrap core steering documents, generating essential project memory from the existing codebase.

When should I run a steering sync on my codebase?

Run a steering sync periodically during maintenance to surface architecture or convention changes, detect code-to-steering drift, and receive recommended markdown edits.

What is the difference between bootstrapping and syncing steering markdown files?

Bootstrapping creates initial steering markdown files from repository patterns when missing, while syncing detects divergences between code and existing guidance to propose additive updates.