kiro-steering-custom

Create custom steering documents from templates and repository analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams need concise, project-specific steering documents that capture patterns, conventions, and domain knowledge without producing exhaustive specifications; this Skill streamlines creation of those focused steering files so knowledge is preserved and discoverable.

Core Features & Use Cases

  • Template-driven authoring: Load and customize templates from .kiro/settings/templates/steering-custom/ (api-standards, testing, security, etc.) to jumpstart documents.
  • Repository-aware analysis: Use glob/grep/read operations to extract domain patterns from code and tests and synthesize them into practical guidance.
  • Principles-first output: Produce concise .kiro/steering/{name}.md files that follow steering-principles.md (patterns over lists, single-domain focus, security-first).
  • Use Case: Create an API standards steering file by loading the api-standards template, analyzing src/api/, and generating a 100–200 line project memory describing endpoint naming, error formats, and auth patterns.

Quick Start

Create a custom API standards steering file named api-standards.md by loading the api-standards template and analyzing the src/api/ directory for naming, error handling, and authentication patterns.

Frequently Asked Questions about kiro-steering-custom

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

FAQPage Schema
How do I create custom steering documents for domain-specific project contexts?▼

To create custom steering documents, load templates from .kiro/settings/templates/steering-custom/, analyze repository patterns using glob and grep, and output a concise .kiro/steering/{name}.md file following steering-principles.md.

What is the best way to capture API standards and security patterns as project memory?▼

Capturing API standards and security patterns as project memory involves analyzing source code to extract conventions, then synthesizing that domain knowledge into a focused steering document to preserve and discover patterns.

Can I generate a testing steering file by analyzing existing repository patterns?▼

Yes, you can generate a testing steering file by loading the testing template, using read and grep operations to analyze existing tests, and synthesizing the extracted domain patterns into practical guidance.

Do I need templates to document database schema conventions in a steering file?▼

Templates are loaded to jumpstart authoring database schema steering files, but the core output relies on analyzing repository patterns to produce concise project memory following single-domain focus and security-first principles.

Why should I use steering documents instead of exhaustive specifications for project conventions?▼

Steering documents provide concise, project-specific guidance that captures patterns and domain knowledge without the overhead of exhaustive specifications, ensuring team knowledge remains preserved and easily discoverable.

What are the limitations of generating domain-specific steering files for project memory?▼

Generated steering files target single-domain focus and typically produce concise 100-200 line documents; they require existing repository patterns to analyze and do not replace comprehensive architectural specifications.