kiro-steering-custom
Skill0 starsChanged 4 months agoMITView on GitHub
Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- aiproxer/aiproxeredited, 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 · 2
- aiproxer/aiproxer★ 2493% same
- studiogadget/skills★ 387% same
Wrote their own version · 0
None found.
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-steeringSkill
- kiro-validate-designSkill
- kiro-validate-gapSkill
- kiro-validate-implSkill
- kiro-verify-completionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 14 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Role: Create specialized steering documents beyond core files (product, tech, structure).
- Distinctive: line 28
If steering context is already available from conversation, skip redundant file reads.
- Very specific: line 30
Check .kiro/settings/templates/steering-custom/ for available templates
- Very specific: line 31
Read rules/steering-principles.md from this skill's directory for steering principles
- Distinctive: line 41
Use as starting point, customize based on project
- Distinctive: line 51
After all parallel research completes, synthesize findings for steering document.
- Distinctive: line 54
Follow template structure if available
- Distinctive: line 57
Keep to 100-200 lines (2-3 minute read)
- Distinctive: line 66
testing.md: - Test organization, mocking, coverage
- Distinctive: line 79
Patterns over lists: Document patterns, not every file/component
- Distinctive: line 83
Security first: Never include secrets or sensitive data
- Distinctive: line 89
Grep: Search for specific patterns
- Distinctive: line 133
Security: Never include secrets (load principles)
- Distinctive: line 134
Validation: Ensure doesn't duplicate core steering content
- Distinctive: line 139
Follow same granularity principles as core steering
- Distinctive: line 140
All steering files loaded as project memory
- Very specific: line 142
Avoid documenting agent-specific tooling directories (e.g.
≈ “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-custom Skill
Role
You are a specialized skill for creating custom steering documents beyond core files (product, tech, structure).
Core Mission
Role: Create specialized steering documents beyond core files (product, tech, structure).
Mission: Help users create domain-specific project memory for specialized areas.
Success Criteria:
- Custom steering captures specialized patterns
- Follows same granularity principles as core steering
- Provides clear value for specific domain
Execution Steps
Step 1: Gather Context
If steering context is already available from conversation, skip redundant file reads. Otherwise:
- Check
.kiro/settings/templates/steering-custom/for available templates - Read
rules/steering-principles.mdfrom this skill's directory for steering principles
Workflow
- Ask user for custom steering needs:
- Domain/topic (e.g., "API standards", "testing approach")
- Specific requirements or patterns to document
- Check if template exists:
- Load from
.kiro/settings/templates/steering-custom/{name}.mdif available - Use as starting point, customize based on project
- Load from
- Analyze codebase (JIT) for relevant patterns:
Parallel Research
The following research areas are independent and can be executed in parallel:
- Template & principles: Load matching template and steering-principles.md
- Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read
After all parallel research completes, synthesize findings for steering document.
- Generate custom steering:
- Follow template structure if available
- Apply principles from
rules/steering-principles.mdfrom this skill's directory - Focus on patterns, not exhaustive lists
- Keep to 100-200 lines (2-3 minute read)
- Create file in
.kiro/steering/{name}.md
Available Templates
Templates available in .kiro/settings/templates/steering-custom/:
- api-standards.md - REST/GraphQL conventions, error handling
- testing.md - Test organization, mocking, coverage
- security.md - Auth patterns, input validation, secrets
- database.md - Schema design, migrations, query patterns
- error-handling.md - Error types, logging, retry strategies
- authentication.md - Auth flows, permissions, session management
- deployment.md - CI/CD, environments, rollback procedures
Load template when needed, customize for project.
Steering Principles
From rules/steering-principles.md (in this skill's directory):
- Patterns over lists: Document patterns, not every file/component
- Single domain: One topic per file
- Concrete examples: Show patterns with code
- Maintainable size: 100-200 lines typical
- Security first: Never include secrets or sensitive data
Tool Guidance
- Read: Load template, analyze existing code
- Glob: Find related files for pattern analysis
- Grep: Search for specific patterns
- Bash with
ls: Understand relevant structure
JIT Strategy: Load template only when creating that type of steering.
Output Description
Chat summary with file location (file created directly).
Custom Steering Created
## Created:
- .kiro/steering/api-standards.md
## Based On:
- Template: api-standards.md
- Analyzed: src/api/ directory patterns
- Extracted: REST conventions, error format
## Content:
- Endpoint naming patterns
- Request/response format
- Error handling conventions
- Authentication approach
Review and customize as needed.Examples
Success: API Standards
Input: "Create API standards steering" Action: Load template, analyze src/api/, extract patterns Output: api-standards.md with project-specific REST conventions
Success: Testing Strategy
Input: "Document our testing approach" Action: Load template, analyze test files, extract patterns Output: testing.md with test organization and mocking strategies
Safety & Fallback
- No template: Generate from scratch based on domain knowledge
- Security: Never include secrets (load principles)
- Validation: Ensure doesn't duplicate core steering content
Notes
- Templates are starting points, customize for project
- Follow same granularity principles as core steering
- All steering files loaded as project memory
- Custom files equally important as core files
- Avoid documenting agent-specific tooling directories (e.g.
.cursor/,.gemini/,.claude/) - Light references to
.kiro/specs/and.kiro/steering/are acceptable; avoid other.kiro/directories
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.

