AWS Builder Center

Builder Center

Kiro Powers: Build Smarter Workflows with On‑Demand AI Capabilities

Kiro Powers: Build Smarter Workflows with On‑Demand AI Capabilities

Kiro Powers let you give Kiro just‑in‑time expertise. Instead of loading every tool and document all the time, Kiro activates the right knowledge and integrations only when your task needs them. This tutorial is written for beginners and practitioners who want a clear, practical walkthrough — from installing your first power to creating one yourself.

Johnnie Ng

What are Kiro Powers?

A Kiro Power is a reusable capability package that can include:
  • POWER.md (required) – instructions and guardrails for the agent
  • MCP integrations (optional) – connect APIs, CLIs, or services
  • Steering files (optional) – structured guidance for workflows and style
  • Hooks (optional) – automation triggered by IDE actions or commands
Kiro automatically activates powers based on your task, keywords, and context.
Why this matters:
  • Better accuracy
  • Less prompt engineering
  • Cleaner, repeatable workflows


Installing Your First Kiro Power

Option 1: Install from the Kiro IDE

  1. Open Kiro
  1. Navigate to the Powers panel
  1. Browse or search for a power (e.g. Stripe, Terraform, Supabase)
  1. Click Install
  1. Review permissions and environment requirements
Once installed, the power is ready to use — no manual activation needed.

Option 2: Install from kiro.dev

  1. Visit the Kiro powers directory on kiro.dev
  1. Choose a power
  1. Click Install
  1. Confirm the install in the Kiro IDE


Using a Power in Practice

You don’t need special commands. Just work normally.

Example

plaintext
Add a Stripe checkout flow with best practices.
Kiro detects the intent and activates the Stripe power automatically. If multiple powers are relevant (e.g. payments + observability), Kiro can load them together.
How to tell a power is active: - Active power indicator in the IDE - More concrete, tool‑aware responses


Installing a Custom or Community Power

Install from GitHub

  1. Open the Powers panel
  1. Select Install from GitHub
  1. Paste a repository URL
  1. Click Install
✅ The repository must contain a valid POWER.md file in its root.

Install from a Local Folder

Perfect for private or internal powers.
  1. Clone or create a power folder locally
  1. In Kiro, select Install from Local Path
  1. Choose the folder containing POWER.md


Creating Your Own Kiro Power

Creating a power is easier than it sounds. Start small.

Step 1: Pick a Focused Use Case

Good first powers:
  • Company API integration
  • Deployment or CI workflows
  • Security or code review checklists

Step 2: Create the Folder Structure

plaintext
my-first-power/

  POWER.md

  mcp.json        # optional

  steering/       # optional

  hooks/          # optional



Step 3: Write POWER.md

This is the most important file. It tells Kiro how to behave.
Minimal template:
   
# Power: My First Power
## Purpose What this power helps with.
## Activation signals - Keywords: - Typical prompts:
## Agent behavior - Do: - Don’t:
## Golden path 1. 2. 3.
## Examples Prompt: Expected outcome:
   
Think of POWER.md as a playbook, not documentation.

Step 4 (Optional): Add MCP Integrations

If your power needs real tools (APIs, CLIs, services), define them in mcp.json. When users install your power, Kiro can register the MCP server automatically.

Step 5 (Optional): Add Steering Files

Steering files help enforce consistency.
Common examples:
  • overview.md – system context
  • workflows.md – step‑by‑step processes
  • style.md – naming and formatting rules


Testing and Improving Your Power

  1. Try 5–10 real prompts
  1. Note where Kiro gets confused
  1. Add clearer guardrails and examples
  1. Iterate
Pro tip: Document failure cases (what the agent should not do).

Sharing Your Power

Once stable, you can:
  • Share privately via local installs
  • Publish to GitHub for community use
  • Version it like a real project


Final Thoughts

Kiro Powers turn one‑off prompts into reusable, expert workflows. Start with documentation and guardrails, then layer in MCP tools and automation as needed.
# kiro# kiro-agent# agentic-ai# agents# ai
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article