kiro-steering

Generate and synchronize .kiro/steering/ markdown files as persistent project knowledge.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-steering-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-steering
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-steering-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project context scattered across codebases is hard to keep documented and aligned with actual code. This Skill bootstraps and maintains .kiro/steering/ markdown files as persistent project memory, detecting drift between documentation and code. ## Core Features & Use Cases - Bootstrap Mode: Analyzes README, package.json, configs, and directory structure to generate core steering files (product.md, tech.md, structure.md) capturing patterns rather than exhaustive lists. - Sync Mode: Compares existing steering files against the current codebase, detects drift in both directions, and proposes additive updates that preserve user customizations. - Granularity Principles: Loads shared rules from rules/steering-principles.md to document patterns and conventions instead of file catalogs, and excludes secrets and tooling directories. - Use Case: After adding a new /api directory to a React TypeScript project, run a sync to update structure.md, flag files not following import conventions, and get a recommendation for an api-standards.md file. ## Quick Start Ask the assistant to bootstrap or sync the .kiro/steering/ directory based on the current codebase.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema
How do I create steering files for a Kiro project?

Run the bootstrap flow when .kiro/steering/ is empty or missing core files. It analyzes your README, package.json, configs, and directory structure, then generates product.md, tech.md, and structure.md following templates from .kiro/settings/templates/steering/.

How do I keep steering documentation in sync with code changes?

Use the sync flow, which loads all existing steering files, analyzes the codebase for changes, and detects drift in both directions. It proposes additive updates that preserve your custom sections and reports warnings and recommendations.

What should steering files document versus avoid?

Steering files should document organizational patterns, naming conventions, import strategies, and architectural decisions. They should avoid complete file listings, every dependency, implementation details, and agent-specific tooling directories like .cursor/ or .claude/.

Does syncing steering files overwrite my custom content?

No, updates are additive by default and preserve user sections and custom examples. The sync flow adds an updated_at timestamp and notes why changes were made rather than replacing existing content.

Can steering files contain secrets or credentials?

No, steering files must never include API keys, passwords, credentials, database URLs, internal IPs, or other sensitive data. This security rule is enforced by the steering-principles.md guidelines.