Building a Kiro Power for AWS Amplify Gen 2
Source: Dev.to
TL;DR
After AWS re:Invent announced Kiro Powers, I explored building a Kiro Power that guides AWS Amplify Gen 2 usage dynamically, without loading MCP SOPs up‑front for every request.
Introduction
The new “Build with AI assistants” page in the Amplify Gen 2 docs sparked a simple question:
What if working with Amplify Gen 2 could feel more guided, intentional, and less repetitive?
That idea evolved into the AWS Amplify Gen 2 Kiro Power.
Experiments
I tried the power in several real‑world scenarios:
- Building a full application from scratch
- Adding a new backend to an existing frontend
- Creating a frontend for a project that only had a backend
- Being guided step‑by‑step through deployment and configuration
The agent didn’t just execute commands; it followed patterns, respected best practices, and reduced the mental overhead of remembering Amplify Gen 2 conventions.
Why Dynamic Loading?
Initially I loaded MCP SOPs upfront for every request. That felt wasteful because the agent could know when to activate the rules.
Traditional MCP servers are static; a Power enables dynamic MCP tool loading, saving context (and thus tokens).
Core Idea
- Encode Amplify Gen 2 best practices, workflows, and conventions.
- Make those rules automatically available whenever Amplify appears in the conversation.
The agent can then:
- Design a backend with Amplify
- Modify an existing Amplify project
- Generate frontend code for an Amplify app
- Handle environment setup or deployment
All without pre‑loading the MCP server each time.
Building the Power
I followed the official instructions for creating a Kiro Power (see the link below). Interestingly, there is a power to create powers, so I used it to scaffold my own, personal Amplify Gen 2 Power.
The process was iterative:
- Generate an initial definition.
- Review the output and tighten the rules.
- Explicitly block any Amplify Gen 1 commands.
- Add behaviors derived from hands‑on experience.
Repository Contents
- A Kiro Power definition focused on Amplify Gen 2
- Embedded AWS MCP SOPs that guide architecture, setup, and evolution
- A reusable, extensible structure
The power is not a replacement for documentation; it operationalizes it.
Implementation Details
- Link to full implementation: 👉 AWS Amplify Gen 2 Kiro Power
- A PR has been submitted to the official
kirodotdev/powersrepository, aiming to make the Power available to the broader community. - Once installed, Kiro shows a confirmation and overview of the Power’s capabilities.
- When you ask Kiro for help with Amplify Gen 2, it proposes the available workflows and guides you through the selected process.
Benefits
| Benefit | Description |
|---|---|
| Reduced cognitive load | No need to remember every Amplify Gen 2 nuance. |
| Fewer mistakes | Prevents accidental mixing of Gen 1 and Gen 2 commands. |
| Consistent architecture | Enforces best‑practice patterns across the project lifecycle. |
| Security‑first approach | Embeds security recommendations directly in the Power. |
| Token & cost savings | The MCP SOPs load only when needed, avoiding unnecessary token usage. |
In short, the Kiro agent handles Amplify Gen 2 documentation and best practices, letting you focus on building your app.
How to Use
- Install the Power via the Kiro CLI.
- Ask Kiro for assistance with any Amplify Gen 2 task (e.g.,
initialize project,add backend,deploy). - Kiro will automatically apply the embedded SOPs, guiding you step‑by‑step.
Acknowledgements
A big shout‑out to Catalin Borsan and Francesco Bertani for their feedback and reviews, which helped turn this experiment into a useful tool.