convez.ai
MCP Server
seandkendall

kiro-config

seandkendall/kiro-config

Ver no GitHub
BomPluginScore · de 0 a 100

Multi-agent Kiro CLI config — master orchestrator, 12 specialist subagents, 16 steering docs, 24 skills, AWS Agent Toolkit MCP stack, self-evolving personal rules

Instalação

$npx convez-ai seandkendall/kiro-config

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
8
Forks
1
Acompanhando
0
Saúde
57%
Último commit
há 2 dias
Versão
v0.10.0
Issues abertas
0
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

Kiro CLI Setup

Version: 0.10

Latest release Last commit License

Multi-agent AWS development environment for the Kiro CLI — master orchestrator, 12 specialist subagents, 16 always-loaded steering docs, 24 skills, and a curated MCP server stack centered on the AWS Agent Toolkit.

💡 Tips for AI Agents working on this repo

  • NEVER push directly to main without running ./validate.sh first. It validates every agent JSON, JSON syntax, bash syntax, and the gitignore privacy guard. The script prints ✓ All checks passed. Safe to push. when green. Run after ANY change to agents/, prompts/, skills/, steering/, settings/, or import.sh.
  • Prefer the configured MCP servers over CLI commands (gh, aws, curl, etc.) for the same operation. See steering/mcp-server-preference.md for the full mapping table.
  • Don't recommend CI/CD pipelines or git hooks — both are explicitly banned in steering/post-task-recommendations.md. Validation belongs in ./validate.sh and deploy.sh, not automation hooks.
  • When generating recommendations, follow the user/AI Agent split in steering/post-task-recommendations.md.

See Releases for the latest version notes.

Prerequisites

  • Kiro CLI installed (latest tested with 2.7.0)
  • Python 3.14+ with uv and uvx
  • Node.js 20+ with npx
  • AWS CLI v2 configured with named profiles
  • Git

Local Tooling Required by MCP Servers

Several MCP servers shell out to local tools. If you're using an AI coding agent to set this config up automatically, the agent must install everything below before any MCP server will work. The included import.sh handles all of this on macOS.

ToolInstall (macOS)Install (Linux)Used by
Homebrew/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"n/a — use distro package managerMac base
uv / uvxcurl -LsSf https://astral.sh/uv/install.sh | shsameAll uvx MCP servers (AWS toolkit, DuckDuckGo, etc.)
node / npxbrew install nodeapt install nodejs npm (or nvm)Context7, GitHub, Playwright, shadcn, 21st.dev, Figma, Browser Lens, Sequential Thinking, Fetch, Chrome DevTools, Google Drive
AWS CLI v2brew install awscliAWS docsAll AWS-flavored agents (configured profiles required)
awsdacbrew install awsdacgo install github.com/awslabs/diagram-as-code/cmd/awsdac@latestaws-diagram-png skill (PNG architecture diagrams with real AWS icons)
Playwright browsersnpx playwright install --with-deps chromium firefox webkitsame@playwright/mcp server (E2E testing, browser automation) on frontend, testing, web-builder agents
graphvizbrew install graphvizapt install graphvizOptional — needed if anyone uses Python diagrams for ad-hoc PNG output
ruff, prettier, shfmt, git-deltabrew install ruff shfmt git-delta && npm i -g prettierapt/npm equivalentsPostToolUse formatter hooks (auto-format files after writes)

Rule of thumb for AI agents setting this up autonomously: if import.sh is available, run it — it installs everything above interactively. If you must script it from scratch, install Homebrew first, then uv, then node, then awscli, then awsdac, then the formatter tools — in that order.

One-shot install (macOS, AI-agent friendly)

# Homebrew
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# uv (Python package runner)
curl -LsSf https://astral.sh/uv/install.sh | sh

# Everything else via Homebrew
brew install node awscli awsdac graphviz ruff shfmt git-delta
npm install -g prettier

# Then run the importer (handles MCP keys + Google Workspace OAuth + agent installs)
./import.sh

Clone the repo into your Kiro config directory:

git clone https://github.com/seandkendall/kiro-config.git ~/.kiro
cd ~/.kiro

Start Kiro CLI:

kiro-cli chat -a -r

Then paste this prompt:

Please review my Kiro/Kiro CLI config in this directory including all agents,
subagents, configurations, steering docs, skills, prompts, and all MCP servers
we have configured in the various files.

First, research all changes AWS has made to Kiro CLI in this changelog:
https://kiro.dev/changelog/cli/
and the IDE in this changelog:
https://kiro.dev/changelog/ide/
available models in this changelog:
https://kiro.dev/changelog/models/
and other general changes in this changelog:
https://kiro.dev/changelog/general/

Next, research the AWS AIDLC GitHub page to see if there is anything valuable
from this project to port into our Kiro configuration:
https://github.com/awslabs/aidlc-workflows/tree/main

Next, AWS has released the Agent Toolkit for AWS which you can find here:
https://aws.amazon.com/products/developer-tools/agent-toolkit-for-aws/
and the GitHub for this here:
https://github.com/aws/agent-toolkit-for-aws

Deep research these projects to see what we should be pulling into our Kiro
configuration. Also make sure you are looking at the changelogs to see what
is new and how that can make our Kiro environment better.

For any MCP server that requires an API key, check to see if I have a key.
If I do not have a key on my machine, then ask me for it, and if I decline,
then simply remove that MCP server from the configuration.
# Clone directly into your Kiro config directory
git clone https://github.com/seandkendall/kiro-config.git ~/.kiro

# Or clone elsewhere and copy over
git clone https://github.com/seandkendall/kiro-config.git
cp -r kiro-config/{agents,steering,skills,prompts,settings} ~/.kiro/

What's Included

Agents (15)

AgentDescription
masterOrchestrator — routes to the right specialist subagent
master-demoSingle-agent demo for serverless backend builds — only aws-mcp-server, no subagents, CORS-aware, no UI/WAF/Route53
serverlessAWS Lambda, API Gateway, DynamoDB, Step Functions, Powertools
frontendReact, TypeScript, Tailwind CSS, shadcn/ui, Playwright, Figma
testingpytest, Jest/Vitest, Playwright E2E via subagent
architectArchitecture diagrams, cost estimation, Well-Architected reviews
ai-builderAmazon Bedrock, Strands Agents, prompt engineering, RAG, AgentCore (full agentic apps)
devopsCloudWatch monitoring, alerting, cost optimization
dataDynamoDB single-table design, data modeling
securityIAM, encryption, cdk-nag, CloudTrail
docsREADMEs, API docs, ADRs, runbooks
image-genImage generation via Bedrock (Nova Canvas + SD 3.5)
researchDeep research with web search, AWS docs, GitHub
web-builderReact + AWS full-stack web apps; delegates AI features to ai-builder
google-workspaceGoogle Docs, Sheets, Drive (read-only)

Steering Docs (16)

Rules and standards automatically loaded into every session: accessibility, API design, AWS/CDK patterns, AWS Agent Toolkit usage, development workflow, error handling, performance, Python standards, security policies, and more.

Personal steering — say "always …" / "from now on …" / "I prefer …" or repeat a preference 2+ times in a session, and the agent will offer to save it as a personal-<topic>.md steering doc on your machine. These files are gitignored and ALWAYS win over base rules. No extra tooling required — they just work via Kiro's existing steering loader. See steering/personal-rules-protocol.md and skills/personal-rules-management.md.

Skills (27)

SourceSkills
Custom (11)AWS serverless patterns, CDK infrastructure, React frontend, testing patterns, deploy-on-aws, AWS architecture diagrams (draw.io XML), AWS diagram PNG (awsdac), personal rules management, email template rendering, Cognito email migration, Cypress-to-Playwright migration
AWS Agent Toolkit (16)Lambda+API GW, Lambda+DynamoDB, debugging timeouts, CloudFront routing, serverless decision guide, S3 security, IAM, Secrets Manager, observability, CloudWatch alarms, app failure troubleshooting, Bedrock, billing/cost, CloudFormation, messaging/streaming, MCP tool discovery

MCP Servers

Agents configure their own MCP servers. Key servers used across agents:

ServerAgentsPurpose
AWS MCP ServerAll 15 agentsFull AWS API, docs, skills, scripts
Context7frontend, serverless, architect, data, web-builder, masterLive library docs (React, AWS, etc.)
PlaywrightfrontendBrowser automation and E2E testing
shadcnfrontend, web-builderComponent registry browsing/install
21st.dev Magicfrontend, web-builderAI UI generation from descriptions
Figma FramelinkfrontendDesign-to-code from Figma URLs
Browser Lensfrontend, web-builderLive CSS/layout debugging
Sequential Thinkingmaster, frontendStructured reasoning chains
DuckDuckGomaster, research + 3Privacy-first web search
GitHubmaster, research, devops + 1GitHub API (repos, PRs, issues)
Chrome DevToolsfrontend, web-builder, testingChrome debugging
Bedrock Imagefrontend, web-builder, image-gen + 3Image generation
Google Drivegoogle-workspaceGoogle Docs/Sheets/Drive (read-only)

Environment Variables

The setup uses 3 optional API keys. If a key is missing when you run ./import.sh, the installer will prompt you for it and disable the related MCP server if you skip.

VariablePurposeGet one at
GITHUB_PERSONAL_ACCESS_TOKENGitHub MCP server — repo, PR, issue access (5 agents)github.com/settings/tokens — create a classic or fine-grained token with repo and read:org scopes
TWENTY_FIRST_API_KEY21st.dev Magic — AI UI component generation (frontend, web-builder)21st.dev/magic/console — sign in with GitHub, generate a key
FIGMA_API_KEYFigma Framelink — design-to-code from Figma URLs (frontend)figma.com/settings → Security → Personal access tokens

Add them to ~/.zshrc:

export GITHUB_PERSONAL_ACCESS_TOKEN="ghp_your_token_here"
export TWENTY_FIRST_API_KEY="your_key_here"
export FIGMA_API_KEY="your_key_here"

Then source ~/.zshrc (or open a new terminal) before starting Kiro CLI.

Configuration

The default model and settings are in settings/cli.json. Key settings:

  • chat.defaultAgent: master (the orchestrator)
  • chat.defaultModel: claude-opus-4.8
  • chat.enableSubagent: true
  • chat.enableThinking: true
  • chat.enableTodoList: true
  • chat.greeting.enabled: true
  • toolSearch.enabled: true

First-time setup tip — Kiro CLI silently mutates settings/cli.json between sessions (e.g., it can flip chat.greeting.enabled). When validate.sh runs before a push, Step 5 surfaces any uncommitted settings drift so you can confirm or revert before it sneaks into a commit. Prefer git add <specific-file> over git add -A for narrow changes — see steering/development-workflow.md ("Settings Change Confirmation" rule).

Key Conventions

  • CDK in Python only — never TypeScript for infrastructure
  • TypeScript for React frontends only
  • deploy.sh is the only deployment method — no CI/CD pipelines, no git hooks
  • Kiro Specs before code — requirements.md → design.md → tasks.md
  • 10+ recommendations after every completed task
  • cdk-nag for security validation on all stacks
  • Lambda Powertools (Logger, Tracer, Metrics) on all Lambda functions
  • MCP-over-CLI — github MCP for github.com operations (never gh); aws-mcp-server for AWS (never bare aws CLI)

Troubleshooting

Common install issues:

SymptomLikely causeFix
Agent fails to call AWS APIs ("could not load credentials")No AWS profile configuredRun aws configure --profile <name>. Most AWS-flavored agents look up credentials from a named profile, not env vars.
MCP server fails at startup with "API key not set"Missing env var in ~/.zshrcRe-run ./import.sh — it prompts for each missing key. Or set the variable manually and source ~/.zshrc.
First run of a uvx/npx MCP server times outPackage is downloading on first invocationThe config sets mcp.noInteractiveTimeout to 180s. If it still times out, run uvx <pkg> once manually to warm the cache.
import.sh fails on LinuxSome install lines use brew (macOS-specific)Adapt the Linux equivalents from the Local Tooling table above (apt install ... instead of brew install ...).
Agent silently fails to delegateCustom orchestrator agent doesn't have subagent in its tools arrayAdd "subagent" to the agent's tools array, or use "tools": ["*"] / "@builtin". See steering/AGENTS.md.
kiro-cli mcp list shows no serversTool name collision with Kiro CLI's deferred toolsRename the colliding MCP server key (e.g., sequential-thinking → sequentialthinking). See steering/troubleshooting.md.

For deeper Kiro CLI issues (settings not loading, side channels in deploy.sh, agent validation errors), see steering/kiro-cli-troubleshooting.md.

License

Apache License 2.0 — see LICENSE. Shared publicly for reference and reuse. See CONTRIBUTING.md for the pre-push validation flow and contribution guidelines.

Ver o original no GitHub

Bom para

Relacionados