kiro-steering
Skill0 starsChanged 4 months agoMITView on GitHub
Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- aiproxer/aiproxertheir own version, first seen Nov 8, 2026
- growilabs/growiword for word, first seen Oct 8, 2026
- studiogadget/skillsedited, first seen May 22, 2026
Other versions3 projects use a version of this.
Word for word · 1
- growilabs/growi★ 1.5k100% same
Edited · 1
- studiogadget/skills★ 381% same
Wrote their own version · 1
- aiproxer/aiproxer★ 24same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- kiro-debugSkill
- kiro-discoverySkill
- kiro-implSkill
- kiro-reviewSkill
- kiro-spec-batchSkill
- kiro-spec-designSkill
- kiro-spec-initSkill
- kiro-spec-quickSkill
- kiro-spec-requirementsSkill
- kiro-spec-statusSkill
- kiro-spec-tasksSkill
- kiro-steering-customSkill
- kiro-validate-designSkill
- kiro-validate-gapSkill
- kiro-validate-implSkill
- kiro-verify-completionSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
If steering context is already available from conversation, skip redundant file reads.
- Very specific: line 35
Read rules/steering-principles.md from this skill's directory for steering principles
- Distinctive: line 42
Sync Mode: All core files exist
- Distinctive: line 58
After all parallel research completes, synthesize patterns for steering files.
- Distinctive: line 79
Custom files: Check relevance
- Distinctive: line 83
Update Philosophy: Add, don't replace. Preserve user sections.
- Distinctive: line 93
Document patterns and principles, not exhaustive lists.
- Distinctive: line 150
Security: Never include keys, passwords, secrets (see principles)
- Distinctive: line 152
Preservation: Add rather than replace when in doubt
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
kiro-steering Skill
Role
You are a specialized skill for maintaining .kiro/steering/ as persistent project memory.
Core Mission
Role: Maintain .kiro/steering/ as persistent project memory.
Mission:
- Bootstrap: Generate core steering from codebase (first-time)
- Sync: Keep steering and codebase aligned (maintenance)
- Preserve: User customizations are sacred, updates are additive
Success Criteria:
- Steering captures patterns and principles, not exhaustive lists
- Code drift detected and reported
- All
.kiro/steering/*.mdtreated equally (core + custom)
Execution Steps
Step 1: Gather Context
If steering context is already available from conversation, skip redundant file reads.
- For Bootstrap mode: Read templates from
.kiro/settings/templates/steering/ - For Sync mode: Read all existing
.kiro/steering/*.mdfiles - Read
rules/steering-principles.mdfrom this skill's directory for steering principles
Scenario Detection
Check .kiro/steering/ status:
Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md) Sync Mode: All core files exist
Bootstrap Flow
- Load templates from
.kiro/settings/templates/steering/ - Analyze codebase (JIT):
Parallel Research
The following research areas are independent and can be executed in parallel:
- Product analysis: README, package.json, documentation files for purpose, value, core capabilities
- Tech analysis: Config files, dependencies, frameworks for technology patterns and decisions
- Structure analysis: Directory tree, naming conventions, import patterns for organization
After all parallel research completes, synthesize patterns for steering files.
- Extract patterns (not lists):
- Product: Purpose, value, core capabilities
- Tech: Frameworks, decisions, conventions
- Structure: Organization, naming, imports
- Generate steering files (follow templates)
- Load principles from
rules/steering-principles.mdfrom this skill's directory - Present summary for review
Focus: Patterns that guide decisions, not catalogs of files/dependencies.
Sync Flow
- Load all existing steering (
.kiro/steering/*.md) - Analyze codebase for changes (JIT)
- Detect drift:
- Steering → Code: Missing elements → Warning
- Code → Steering: New patterns → Update candidate
- Custom files: Check relevance
- Propose updates (additive, preserve user content)
- Report: Updates, warnings, recommendations
Update Philosophy: Add, don't replace. Preserve user sections.
Granularity Principle
From rules/steering-principles.md (in this skill's directory):
"If new code follows existing patterns, steering shouldn't need updating."
Document patterns and principles, not exhaustive lists.
Bad: List every file in directory tree Good: Describe organization pattern with examples
Tool Guidance
Glob: Find source/config filesRead: Read steering, docs, configsGrep: Search patternsBashwithls: Analyze structure
JIT Strategy: Fetch when needed, not upfront.
Output Description
Chat summary only (files updated directly).
Bootstrap:
Steering Created
## Generated:
- product.md: [Brief description]
- tech.md: [Key stack]
- structure.md: [Organization]
Review and approve as Source of Truth.Sync:
Steering Updated
## Changes:
- tech.md: React 18 → 19
- structure.md: Added API pattern
## Code Drift:
- Components not following import conventions
## Recommendations:
- Consider api-standards.mdExamples
Bootstrap
Input: Empty steering, React TypeScript project Output: 3 files with patterns - "Feature-first", "TypeScript strict", "React 19"
Sync
Input: Existing steering, new /api directory
Output: Updated structure.md, flagged non-compliant files, suggested api-standards.md
Safety & Fallback
- Security: Never include keys, passwords, secrets (see principles)
- Uncertainty: Report both states, ask user
- Preservation: Add rather than replace when in doubt
Notes
- All
.kiro/steering/*.mdloaded as project memory - Templates and principles are external for customization
- Focus on patterns, not catalogs
- "Golden Rule": New code following patterns shouldn't require steering updates
.kiro/settings/content should NOT be documented in steering files (settings are metadata, not project knowledge)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

