agentleFS
kyuki3rainkyuki3rain/cc-sdd-adr/.claude/skills/kiro-steering-custom/SKILL.md

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

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
  1. Distinctive:

    Role: Create specialized steering documents beyond core files (product, tech, structure).

    line 15
  2. Distinctive:

    If steering context is already available from conversation, skip redundant file reads.

    line 28
  3. Very specific:

    Check .kiro/settings/templates/steering-custom/ for available templates

    line 30
  4. Very specific:

    Read rules/steering-principles.md from this skill's directory for steering principles

    line 31
  5. Distinctive:

    Use as starting point, customize based on project

    line 41
  6. Distinctive:

    After all parallel research completes, synthesize findings for steering document.

    line 51
  7. Distinctive:

    Follow template structure if available

    line 54
  8. Distinctive:

    Keep to 100-200 lines (2-3 minute read)

    line 57
  9. Distinctive:

    testing.md: - Test organization, mocking, coverage

    line 66
  10. Distinctive:

    Patterns over lists: Document patterns, not every file/component

    line 79
  11. Distinctive:

    Security first: Never include secrets or sensitive data

    line 83
  12. Distinctive:

    Grep: Search for specific patterns

    line 89
  13. Distinctive:

    Security: Never include secrets (load principles)

    line 133
  14. Distinctive:

    Validation: Ensure doesn't duplicate core steering content

    line 134
  15. Distinctive:

    Follow same granularity principles as core steering

    line 139
  16. Distinctive:

    All steering files loaded as project memory

    line 140
  17. Very specific:

    Avoid documenting agent-specific tooling directories (e.g.

    line 142

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md from this skill's directory for steering principles

Workflow

  1. Ask user for custom steering needs:
    • Domain/topic (e.g., "API standards", "testing approach")
    • Specific requirements or patterns to document
  2. Check if template exists:
    • Load from .kiro/settings/templates/steering-custom/{name}.md if available
    • Use as starting point, customize based on project
  3. Analyze codebase (JIT) for relevant patterns:

Parallel Research

The following research areas are independent and can be executed in parallel:

  1. Template & principles: Load matching template and steering-principles.md
  2. Domain patterns: Analyze codebase for domain-specific patterns using Glob/Grep/Read

After all parallel research completes, synthesize findings for steering document.

  1. Generate custom steering:
    • Follow template structure if available
    • Apply principles from rules/steering-principles.md from this skill's directory
    • Focus on patterns, not exhaustive lists
    • Keep to 100-200 lines (2-3 minute read)
  2. Create file in .kiro/steering/{name}.md

Available Templates

Templates available in .kiro/settings/templates/steering-custom/:

  1. api-standards.md - REST/GraphQL conventions, error handling
  2. testing.md - Test organization, mocking, coverage
  3. security.md - Auth patterns, input validation, secrets
  4. database.md - Schema design, migrations, query patterns
  5. error-handling.md - Error types, logging, retry strategies
  6. authentication.md - Auth flows, permissions, session management
  7. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.