Kiro Methodology

13. Appendix: Quick Reference Card

← Back to Table of Contents | Previous: Daily Rhythm


The 7 Golden Rules

# Rule
1 Module isolation — each Kiro owns one module
2 Short-lived branches — less than 24 hours
3 Frequent commits — every 10–20 minutes
4 Mandatory unit tests — every code change
5 PR + CI gate — no direct merges to main
6 Steering rules versioned in repo
7 Infrastructure as code — Terraform only

Branch Naming

kiro/<module>/<short-task-description>

Commit Format

<type>(<module>): <description>

Types: feat, fix, test, refactor, docs, chore

Kiro Steering Files

File Purpose
.kiro/steering/global-rules.md Universal rules for all agents
.kiro/steering/testing-rules.md Test generation requirements
.kiro/steering/<module>-rules.md Module-specific constraints

Kiro Hooks

Hook Trigger Action
test-on-save File saved Run tests
lint-on-save File saved Run linter
verify-tests Before write Remind: include tests
module-boundary Before write Check: correct module?
test-after-task Task completed Run full test suite

CI/CD Pipeline Stages

lint → test → build → security → deploy-dev → deploy-staging → deploy-prod

Terraform Environments

environments/dev/      → Auto-deploy on merge to main
environments/staging/  → Manual approval
environments/prod/     → Manual approval

Resource Naming

{project}-{environment}-{module}-{resource-type}
Example: myapp-prod-auth-ecs-service

Team Organization (Scrum Mode)

Dev 1 + Kiro → auth module      → kiro/auth/*
Dev 2 + Kiro → billing module   → kiro/billing/*
Dev 3 + Kiro → orders module    → kiro/orders/*
Dev 4 + Kiro → catalog module   → kiro/catalog/*
Dev 5 + Kiro → frontend         → kiro/frontend/*
Dev 6 + Kiro → infrastructure   → kiro/infra/*
Dev 7 + Kiro → gateway/shared   → kiro/gateway/*

New Product vs. Existing Code

Aspect New Product Existing Code
Start with Module boundaries + infra Assessment + test baseline
Steering rules describe Target architecture Current + target architecture
Refactoring Build it right from start Incremental improvement
Terraform Build from scratch Import existing resources
First priority CI/CD pipeline Test coverage

Anti-Patterns

Don't Do Instead
Let Kiro modify any file Enforce module boundaries
Keep branches for days Merge within hours
Skip tests Tests are mandatory, always
Commit large batches Small, frequent commits
Manually create AWS resources Terraform everything
Write verbose documentation Minimal, rule-driven docs

← Back to Table of Contents | Previous: Daily Rhythm