Pulumi Powers for Kiro

A collection of Kiro Powers for Pulumi Infrastructure as Code development.

Available Powers

Power	Description
pulumi-typescript	TypeScript IaC with Pulumi Cloud, ESC, and Registry
pulumi-go	Go IaC with Pulumi Cloud, ESC, and Registry
pulumi-python	Python IaC with Pulumi Cloud, ESC, and Registry
pulumi-neo	AI-powered infrastructure automation with Pulumi Neo

Features

All powers include:

• Pulumi Cloud Integration - Manage stacks, deployments, and resources
• ESC (Environments, Secrets, Configuration) - Centralized secrets and config management
• Registry Access - Search providers, resources, and functions via MCP
• OIDC Authentication - Dynamic credentials for AWS, Azure, and GCP
• IDP Best Practices - Templates, Components, Environments, and Policies patterns
• Neo AI Agent - Conversational infrastructure management

Installation

Note: Kiro Powers are currently only available via IDE installation. Cloud installation is not yet supported.

Install from Local Path

1. Clone this repository:

   git clone https://github.com/dirien/pulumi-powers.git

2. Open Kiro IDE

3. Open the Powers panel (click the Powers icon in the sidebar)

4. Click "Add power from Local Path"

5. Navigate to and select the power directory you want to install:

   • pulumi-powers/pulumi-typescript/
   • pulumi-powers/pulumi-go/
   • pulumi-powers/pulumi-python/
   • pulumi-powers/pulumi-neo/

6. Click "Install"

Install from GitHub

1. Open Kiro IDE

2. Open the Powers panel

3. Click "Add power from GitHub"

4. Enter the repository URL with the specific power path:

   https://github.com/dirien/pulumi-powers/tree/main/pulumi-typescript
   

   Or for other powers:

   https://github.com/dirien/pulumi-powers/tree/main/pulumi-go
   https://github.com/dirien/pulumi-powers/tree/main/pulumi-python
   https://github.com/dirien/pulumi-powers/tree/main/pulumi-neo
   

5. Click "Install"

Prerequisites

For All Powers

• Pulumi CLI installed
• Pulumi Cloud account
• Logged in via pulumi login

Language-Specific

Power	Requirements
pulumi-typescript	Node.js 18+, npm/pnpm/yarn
pulumi-go	Go 1.21+
pulumi-python	Python 3.8+
pulumi-neo	Pulumi Cloud with Neo access

MCP Server Authentication

The powers use the Pulumi MCP server at https://mcp.ai.pulumi.com/mcp. On first use:

1. Kiro will prompt for authentication
2. A browser window will open for OAuth
3. Log in with your Pulumi Cloud credentials
4. Authorization is cached for future sessions

Power Structure

Each power follows the Kiro Powers standard structure:

pulumi-<language>/
├── POWER.md              # Metadata, keywords, and onboarding
├── mcp.json              # Pulumi MCP server configuration
└── steering/             # Workflow-specific guidance
    ├── getting-started.md
    ├── code-style.md
    ├── esc-integration.md
    ├── best-practices.md
    ├── idp-patterns.md
    └── mcp-usage.md

Usage

Once installed, powers activate automatically based on keywords. Examples:

TypeScript Power

"Create a new Pulumi TypeScript project for AWS"
"Help me set up ESC for my TypeScript stack"

Go Power

"Initialize a Pulumi Go project for Kubernetes"
"Create a component resource in Go"

Python Power

"Start a new Pulumi Python project for Azure"
"Show me Python best practices for Pulumi"

Neo Power

"Use Neo to analyze my production stack security"
"Create a Neo task to upgrade my EKS cluster"

Steering Files

Each power includes specialized guidance:

File	Description
getting-started.md	Interactive project setup
code-style.md	Language-specific conventions
esc-integration.md	ESC environment and secrets
best-practices.md	Security and deployment patterns
idp-patterns.md	Internal Developer Platform best practices
mcp-usage.md	MCP tools and registry access

IDP Best Practices

The powers incorporate Pulumi's IDP best practices based on the Four Factors:

1. Templates - Standardized project starting points
2. Components - Reusable, composable infrastructure
3. Environments - ESC-based configuration management
4. Policies - CrossGuard compliance and governance

See steering/idp-patterns.md in each power for detailed guidance.

MCP Tools Available

The Pulumi MCP server provides:

Pulumi Cloud

• get-stacks - List organization stacks
• resource-search - Query resources with Lucene syntax
• get-policy-violations - Retrieve compliance violations

Registry

• get-resource - Get resource documentation
• list-resources - Browse provider catalogs
• get-function - Get function documentation

Neo (AI Agent)

• neo-bridge - Create automation tasks
• neo-get-tasks - List task status
• neo-continue-task - Monitor task progress

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Disclaimer

These are third-party Kiro Powers. Please review the documentation and only install from trusted sources. Pulumi and Kiro are trademarks of their respective owners.