Pulumi Component

This is the guide you want when building Pulumi ComponentResources that actually work across languages. It covers the four required elements (extending ComponentResource, calling super with a type URN, setting parent: this, calling registerOutputs), shows why registerOutputs isn't optional (your component gets stuck "creating" without it), and explains how to design args interfaces that don't break Python or Go SDK generation. The examples are complete and show both TypeScript and Python. Use it when you're authoring reusable infrastructure components, making them multi-language compatible, or debugging why child resources appear at the wrong level in the console tree.

skills.sh installs: 1.5K
GitHub stars: 79
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pulumi/agent-skills --skill pulumi-component --agent claude-code

Installs into .claude/skills of the current project.

Files

Authoring Pulumi Components

A ComponentResource groups related infrastructure resources into a reusable, logical unit. Components make infrastructure easier to understand, reuse, and maintain. Components appear as a single node with children nested underneath in pulumi preview/pulumi up output and in the Pulumi Cloud console.

This skill covers the full component authoring lifecycle. For general Pulumi coding patterns (Output handling, secrets, aliases, preview workflows), use the pulumi-best-practices skill instead.

When to Use This Skill

Invoke this skill when:

Creating a new ComponentResource class
Designing the args interface for a component
Making a component consumable from multiple Pulumi languages
Publishing or distributing a component package
Refactoring inline resources into a reusable component
Debugging component behavior (missing outputs, stuck creating, children at wrong level)