Everything Kiro

Best practices, agents, and automation for Kiro — like Everything Claude Code but for Kiro.

What You Get

Global Steering Rules (apply to ALL projects)

File	What It Does
coding-style.md	Immutability, error handling, file size limits, code quality checklist
security.md	OWASP checks, secret management, critical patterns table
testing.md	TDD workflow, 80% coverage, edge case requirements
git-workflow.md	Conventional commits, PR workflow, branch strategy
patterns.md	Repository pattern, API response format, architecture principles
performance.md	Keep-it-simple rules, efficiency guidelines

Language-Specific Rules (auto-activate per file type)

File	Activates For	Covers
python.md	*.py, *.pyi	PEP 8, type hints, ruff, pytest, common mistakes
typescript.md	*.ts, *.tsx	Strict mode, immutability, React/Next.js patterns
go.md	*.go	Error handling, table-driven tests, goroutine safety
java.md	*.java	Records, Optional, Spring Boot, JUnit 5

Custom Agents (invoke by name in chat)

Agent	Purpose	Invoke With
code-reviewer	Quality + security review	"Use the code-reviewer"
security-reviewer	OWASP Top 10 vulnerability scan	"Ask the security-reviewer"
architect	System design and trade-off analysis	"Use the architect"
planner	Break features into phased implementation plans	"Use the planner"
tdd-guide	Enforce test-first development	"Use the tdd-guide"
python-reviewer	Python-specific review (PEP 8, type hints)	"Use the python-reviewer"

Project Template (per-project config)

Pre-configured .kiro/ directory with:

• product.md template (fill in your project details)
• Auto-review hook (reviews code when agent stops)
• Secret-blocking hook (prevents hardcoded credentials)

---

Quick Start

1. Clone this repo

git clone <this-repo-url> ~/everything-kiro

2. Install globally

~/everything-kiro/scripts/install.sh

This copies steering rules and agents to ~/.kiro/. They apply to every project you open in Kiro.

3. (Optional) Initialize a project

cd /path/to/your/project
~/everything-kiro/scripts/init-project.sh

This creates a .kiro/ directory in your project with hooks and a product.md template. Edit .kiro/steering/product.md with your project details.

---

What Each Team Member Does

1. Clone this repo
2. Run ./scripts/install.sh
3. Open any project in Kiro
4. Done — rules, agents, and language support are active

That's it. No other setup required.

---

Directory Structure

everything-kiro/
├── README.md                          ← You are here
├── global/                            ← Installed to ~/.kiro/
│   ├── steering/                      ← AI behavior rules
│   │   ├── coding-style.md            ← Always loaded
│   │   ├── security.md                ← Always loaded
│   │   ├── testing.md                 ← Always loaded
│   │   ├── git-workflow.md            ← Always loaded
│   │   ├── patterns.md               ← Always loaded
│   │   ├── performance.md            ← Always loaded
│   │   ├── python.md                  ← Loaded for *.py files
│   │   ├── typescript.md              ← Loaded for *.ts files
│   │   ├── go.md                      ← Loaded for *.go files
│   │   └── java.md                    ← Loaded for *.java files
│   └── agents/                        ← Custom sub-agents
│       ├── code-reviewer.md
│       ├── security-reviewer.md
│       ├── architect.md
│       ├── planner.md
│       ├── tdd-guide.md
│       └── python-reviewer.md
├── project-template/                  ← Copy into any project
│   └── .kiro/
│       ├── steering/product.md        ← Fill in project details
│       ├── hooks/                     ← Auto-review + secret blocking
│       ├── agents/                    ← Add project-specific agents
│       ├── specs/                     ← Kiro creates specs here
│       └── settings/                  ← MCP server config
└── scripts/
    ├── install.sh                     ← Install global config
    └── init-project.sh                ← Initialize project .kiro/

---

Customizing

Add a steering rule

Create ~/.kiro/steering/<name>.md (global) or .kiro/steering/<name>.md (project):

---
inclusion: always
---
# My Custom Rule

Your instructions here...

Add a language rule

Use fileMatch inclusion:

---
inclusion: fileMatch
fileMatchPattern: ["**/*.rs"]
---
# Rust Standards

Your Rust-specific rules...

Add an agent

Create ~/.kiro/agents/<name>.md or .kiro/agents/<name>.md:

---
name: my-agent
description: What this agent does. Kiro uses this to route requests.
tools: ["read", "shell"]
model: claude-sonnet-4
---

Your agent prompt here...

Add a hook

Create .kiro/hooks/<name>.kiro.hook:

{
  "title": "Hook Name",
  "description": "What it does",
  "event": "onFileSave",
  "filePattern": "**/*.py",
  "actionType": "command",
  "command": "ruff check --fix ${filePath}"
}

Available events: onFileSave, onFileCreate, onFileDelete, onAgentStop, preToolUse, postToolUse, promptSubmit, manualTrigger

Add MCP servers

Edit .kiro/settings/mcp.json:

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-server-fetch"]
    }
  }
}

---

ECC vs Everything Kiro

ECC Feature	Everything Kiro Equivalent	Status
CLAUDE.md	steering/product.md	✅
rules/common/*.md	steering/*.md (always)	✅
rules/python/*.md	steering/python.md (fileMatch)	✅
Agents (16)	Agents (6 — most useful ones)	✅
PreToolUse/PostToolUse hooks	.kiro.hook files	✅
Slash commands (40)	Specs + agent invocation	⚡ Partial
Skills (68)	Steering rules (key patterns inlined)	⚡ Partial
Instincts / learning	Not available in Kiro	❌
Model routing	Not available in Kiro	❌
Eval harness	Not available in Kiro	❌
Multi-model orchestration	Not available in Kiro	❌

---

Using Kiro Specs (replaces ECC's /plan command)

For complex features, use Kiro's built-in spec workflow instead of slash commands:

1. Open the Specs panel in Kiro
2. Choose Feature Spec or Bugfix Spec
3. Describe what you want to build
4. Kiro generates: requirements.md → design.md → tasks.md
5. Execute tasks individually or batch

This replaces ECC's /plan, /orchestrate, and /multi-workflow commands.

---

License

MIT