Everything Claude Code for Kiro

Bring Everything Claude Code (ECC) workflows to Kiro. This repository provides custom agents, skills, hooks, steering files, and scripts that can be installed into any Kiro project with a single command.

Quick Start

# Go to .kiro folder
cd .kiro

# Install to your project
./install.sh /path/to/your/project

# Or install to the current directory
./install.sh

# Or install globally (applies to all Kiro projects)
./install.sh ~

The installer uses non-destructive copy — it will not overwrite your existing files.

Component Inventory

What's Included

Agents

Agents are specialized AI assistants with specific tool configurations.

Format:

• IDE: Markdown files (.md) - Access via automatic selection or explicit invocation
• CLI: JSON files (.json) - Access via /agent swap command

Both formats are included for maximum compatibility.

Note: Agent models are determined by your current model selection in Kiro, not by the agent configuration.

Usage in IDE:

• You can run an agent in / in a Kiro session, e.g., /code-reviewer.
• Kiro's Spec session has native planner, designer, and architects that can be used instead of planner and architect agents.

Usage in CLI:

1. Start a chat session
2. Type /agent swap to see available agents
3. Select an agent to switch (e.g., code-reviewer after writing code)
4. Or start with a specific agent: kiro-cli --agent planner

Skills

Skills are on-demand workflows invocable via the / menu in chat.

Usage:

1. Type / in chat to open the skills menu
2. Select a skill (e.g., tdd-workflow when starting a new feature, security-review when adding auth)
3. The agent will guide you through the workflow with specific instructions and checklists

Note: For planning complex features, use the planner agent instead (see Agents section above).

Steering Files

Steering files provide always-on rules and context that shape how the agent works with your code.

Steering files with auto inclusion are loaded automatically. No action needed — they apply as soon as you install them.

To create your own, add a markdown file to .kiro/steering/ with YAML frontmatter:

---
inclusion: auto        # auto | fileMatch | manual
description: Brief explanation of what this steering file contains
fileMatchPattern: "*.ts"  # required if inclusion is fileMatch
---

Your rules here...

Hooks

Kiro supports two types of hooks:

1. IDE Hooks - Standalone JSON files in .kiro/hooks/ (for Kiro IDE)
2. CLI Hooks - Embedded in agent configurations (for kiro-cli)

IDE Hooks (Standalone Files)

These hooks appear in the Agent Hooks panel in the Kiro IDE and can be toggled on/off. Hook files use the .kiro.hook extension.

IDE Hook Format:

{
  "version": "1.0.0",
  "enabled": true,
  "name": "hook-name",
  "description": "What this hook does",
  "when": {
    "type": "fileEdited",
    "patterns": ["*.ts"]
  },
  "then": {
    "type": "runCommand",
    "command": "npx tsc --noEmit"
  }
}

Required fields: version, enabled, name, description, when, then

Available trigger types: fileEdited, fileCreated, fileDeleted, userTriggered, promptSubmit, agentStop, preToolUse, postToolUse

CLI Hooks (Embedded in Agents)

CLI hooks are embedded within agent configuration files for use with kiro-cli.

Example: See .kiro/agents/tdd-guide-with-hooks.json for an agent with embedded hooks.

CLI Hook Format:

{
  "name": "my-agent",
  "hooks": {
    "postToolUse": [
      {
        "matcher": "fs_write",
        "command": "npx tsc --noEmit"
      }
    ]
  }
}

Available triggers: agentSpawn, userPromptSubmit, preToolUse, postToolUse, stop

See .kiro/hooks/README.md for complete documentation on both hook types.

Scripts

Shell scripts used by hooks to perform quality checks and formatting.

Project Structure

.kiro/
├── agents/                       # 16 agents (JSON + MD formats)
│   ├── planner.json              # Planning specialist (CLI)
│   ├── planner.md                # Planning specialist (IDE)
│   ├── code-reviewer.json        # Code review specialist (CLI)
│   ├── code-reviewer.md          # Code review specialist (IDE)
│   ├── tdd-guide.json            # TDD specialist (CLI)
│   ├── tdd-guide.md              # TDD specialist (IDE)
│   ├── security-reviewer.json    # Security specialist (CLI)
│   ├── security-reviewer.md      # Security specialist (IDE)
│   ├── architect.json            # Architecture specialist (CLI)
│   ├── architect.md              # Architecture specialist (IDE)
│   ├── build-error-resolver.json # Build error specialist (CLI)
│   ├── build-error-resolver.md   # Build error specialist (IDE)
│   ├── doc-updater.json          # Documentation specialist (CLI)
│   ├── doc-updater.md            # Documentation specialist (IDE)
│   ├── refactor-cleaner.json     # Refactoring specialist (CLI)
│   ├── refactor-cleaner.md       # Refactoring specialist (IDE)
│   ├── go-reviewer.json          # Go review specialist (CLI)
│   ├── go-reviewer.md            # Go review specialist (IDE)
│   ├── python-reviewer.json      # Python review specialist (CLI)
│   ├── python-reviewer.md        # Python review specialist (IDE)
│   ├── database-reviewer.json    # Database specialist (CLI)
│   ├── database-reviewer.md      # Database specialist (IDE)
│   ├── e2e-runner.json           # E2E testing specialist (CLI)
│   ├── e2e-runner.md             # E2E testing specialist (IDE)
│   ├── harness-optimizer.json    # Test harness specialist (CLI)
│   ├── harness-optimizer.md      # Test harness specialist (IDE)
│   ├── loop-operator.json        # Verification lo