跳到正文
cccskills
免费在 GitHub 公开

kiro-steering

Create and maintain project reference documents from the codebase, covering product purpose, technology choices, and organization patterns. Detect differences between documentation and code while preserving user additions during updates.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Maintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.

查看安装方法

适用场景

  • Creating initial project reference documents
  • Updating documentation after code changes
  • Checking code against documented conventions
  • Maintaining project knowledge while preserving user notes

包含的文件(1)

  • SKILL.md4.7 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

kiro-steering Skill

Role

You are a specialized skill for maintaining {{KIRO_DIR}}/steering/ as persistent project memory.

Core Mission

Role: Maintain {{KIRO_DIR}}/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_DIR}}/steering/*.md treated 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_DIR}}/settings/templates/steering/
  • For Sync mode: Read all existing {{KIRO_DIR}}/steering/*.md files
  • Read rules/steering-principles.md from this skill's directory for steering principles

Scenario Detection

Check {{KIRO_DIR}}/steering/ status:

Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md) Sync Mode: All core files exist


Bootstrap Flow

  1. Load templates from {{KIRO_DIR}}/settings/templates/steering/
  2. Analyze codebase (JIT):

Parallel Research

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

  1. Product analysis: README, package.json, documentation files for purpose, value, core capabilities
  2. Tech analysis: Config files, dependencies, frameworks for technology patterns and decisions
  3. Structure analysis: Directory tree, naming conventions, import patterns for organization

After all parallel research completes, synthesize patterns for steering files.

  1. Extract patterns (not lists):
    • Product: Purpose, value, core capabilities
    • Tech: Frameworks, decisions, conventions
    • Structure: Organization, naming, imports
  2. Generate steering files (follow templates)
  3. Load principles from rules/steering-principles.md from this skill's directory
  4. Present summary for review

Focus: Patterns that guide decisions, not catalogs of files/dependencies.


Sync Flow

  1. Load all existing steering ({{KIRO_DIR}}/steering/*.md)
  2. Analyze codebase for changes (JIT)
  3. Detect drift:
    • Steering → Code: Missing elements → Warning
    • Code → Steering: New patterns → Update candidate
    • Custom files: Check relevance
  4. Propose updates (additive, preserve user content)
  5. 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 files
  • Read: Read steering, docs, configs
  • Grep: Search patterns
  • Bash with ls: 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.md

Examples

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_DIR}}/steering/*.md loaded 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_DIR}}/settings/ content should NOT be documented in steering files (settings are metadata, not project knowledge)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Add coding-agent support to cc-sdd through a documented workflow. Research the agent’s official formats, prepare an integration plan, implement registry entries and templates, and verify generated files, including Japanese and English output.

中文简介正在准备中。当前显示英语简介。

  • Adding support for a new coding agent
  • Adding an agent variant with subagent support
  • Planning migration to SKILL.md-based templates
gotalab/cc-sdd37322026年10月22日 更新

Investigate blocked implementation work and recurring failures using error output, code changes, configuration, and dependency evidence. Get a root cause report with a focused repair plan, verification steps, and a recommendation to retry, block, or seek human input.

中文简介正在准备中。当前显示英语简介。

  • Investigating an implementation blocker
  • Finding why repeated fixes keep failing
  • Checking runtime and dependency conflicts
gotalab/cc-sdd37322026年10月22日 更新

Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.

中文简介正在准备中。当前显示英语简介。

  • Clarify a development idea before defining requirements
  • Choose between updating a specification and implementing directly
  • Split a large request into features with explicit dependencies
gotalab/cc-sdd37322026年10月22日 更新

kiro-impl

免费

Implement approved development tasks one at a time using test-driven development, which starts with a failing test. Process all pending tasks or selected ones, check changes against requirements and design, and update progress after review and completion verification.

中文简介正在准备中。当前显示英语简介。

  • Working through all approved pending tasks
  • Implementing selected task numbers
  • Developing features with tests written first
gotalab/cc-sdd37322026年10月22日 更新

kiro-impl

免费

Implement approved tasks using test-driven development, writing tests before code. Run all pending tasks one at a time or select specific tasks, with configurable review and verification before updating completion status.

中文简介正在准备中。当前显示英语简介。

  • Implement all pending tasks from an approved plan
  • Work on selected task numbers
  • Develop features by writing tests before code
gotalab/cc-sdd37322026年10月22日 更新

kiro-impl

免费

Implement approved tasks through test-driven development, writing tests before code. Run all pending tasks sequentially with subagents or select tasks for direct execution, then track completion using reviews and verification evidence.

中文简介正在准备中。当前显示英语简介。

  • Running all pending approved implementation tasks
  • Implementing selected tasks by number
  • Developing features with tests written first
gotalab/cc-sdd37322026年10月22日 更新

查看 gotalab 的全部技能

报告此技能的问题