kiro-steering

Generate and synchronize .kiro/steering/ project memory from codebase changes.

Updated Feb 25, 2024

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

Ready to run

npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-steering-ryowatanabe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper/tree/main/.claude/skills/kiro-steering
Command: npx skills add https://github.com/ryowatanabe/iidx-dp-unofficial-difficulty-scraper --skill kiro-steering-ryowatanabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains .kiro/steering/ as persistent project memory across bootstrap and synchronization, ensuring a stable, customizable memory of project decisions.

Core Features & Use Cases

Bootstrap: Generate core steering from the codebase (first-time setup)
Sync: Keep steering aligned with codebase changes (maintenance)
Preserve: User customizations are preserved and updates are additive

Quick Start

Bootstrap steering from your codebase and then periodically synchronize to keep steering in sync while preserving user modifications.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema

How do I maintain persistent project memory for a codebase?▼

Persistent project memory is maintained by generating and synchronizing steering files within a `.kiro/steering/` directory. This establishes a stable, customizable record of project decisions and patterns across codebase updates.

What is the best way to bootstrap steering documentation from an existing codebase?▼

Bootstrapping steering documentation involves analyzing the repository to generate core steering files during initial setup. This creates a foundational project memory structure based on existing code patterns.

How do I sync project steering files with code changes without losing customizations?▼

Syncing steering files aligns project memory with codebase changes through additive updates. The synchronization process detects drift and specifically preserves user customizations and sections during the update.

When do I need to synchronize steering documentation with my repository?▼

Synchronization is needed when codebase changes introduce drift in the established project patterns. Running a periodic sync aligns the steering memory with the updated code while preserving user modifications.

Does generating steering patterns overwrite my existing project documentation?▼

Generating steering patterns does not overwrite existing documentation. Updates are additive and specifically designed to preserve user sections and customizations while applying pattern-based generation.

What are the limitations of using steering files for codebase pattern detection?▼

Using steering files relies on the `.kiro/steering/` directory structure for pattern detection and drift alignment. It requires periodic synchronization to maintain accuracy and depends on the repository's existing patterns.