pulumi

Name: pulumi
Author: pproenca

github.com/pproencaCloud & DevOps218307 installsUpdated 11w ago

About pulumi

A Pulumi best-practices skill for AI agents and LLMs, organized as 46 rules across eight categories. It guides infrastructure code writing and refactoring, from state management and component design to testing and CI/CD.

Key features

0146 rules across eight categories
02Priority-ranked guidance
03State and resource graph practices
04Component, secrets, and stack guidance
05Testing and CI/CD recommendations

Use cases

01Writing new Pulumi infrastructure code
02Reviewing stack and state organization
03Designing reusable components
04Preparing infrastructure tests and CI/CD

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pproenca/dot-skills --skill pulumi

After installing, type/pulumiin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

AGENTS.md

metadata.json

README.md

assets/templates/

_template.md

references/

_sections.md

auto-automation-api-workflows.md

auto-ci-cd-preview.md

auto-deployments-api.md

auto-drift-detection.md

auto-inline-programs.md

auto-review-stacks.md

graph-avoid-apply-side-effects.md

graph-conditional-resources.md

graph-explicit-depends.md

graph-output-dependencies.md

graph-parallel-resources.md

graph-stack-references-minimal.md

lifecycle-aliases.md

lifecycle-custom-timeouts.md

lifecycle-delete-before-replace.md

lifecycle-ignore-changes.md

lifecycle-protect-stateful.md

lifecycle-replace-on-changes.md

lifecycle-retain-on-delete.md

pcomp-component-resources.md

pcomp-multi-language.md

pcomp-parent-child.md

pcomp-register-outputs.md

pcomp-transformations.md

pcomp-unique-naming.md

Details

From the project README

Pulumi Best Practices

Comprehensive performance and reliability guide for Pulumi infrastructure as code, designed for AI agents and LLMs. Contains 46 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

Writing new Pulumi infrastructure code
Designing component abstractions for reuse
Configuring secrets and sensitive values
Organizing stacks and cross-stack references
Setting up CI/CD pipelines for infrastructure

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	State Management and Backend	CRITICAL	`pstate-`
2	Resource Graph Optimization	CRITICAL	`graph-`
3	Component Design	HIGH	`pcomp-`
4	Secrets and Configuration	HIGH	`secrets-`
5	Stack Organization	MEDIUM-HIGH	`stack-`
6	Resource Options and Lifecycle	MEDIUM	`lifecycle-`
7	Testing and Validation	MEDIUM	`test-`
8	Automation and CI/CD	LOW-MEDIUM	`auto-`

Quick Reference

1. State Management and Backend (CRITICAL)

pstate-backend-selection - Use managed backend for production stacks
pstate-checkpoint-skipping - Enable checkpoint skipping for large stacks
pstate-stack-size - Keep stacks under 500 resources
pstate-refresh-targeting - Use targeted refresh instead of full stack
pstate-export-import - Use state export/import for migrations
pstate-import-existing - Import existing resources before managing

2. Resource Graph Optimization (CRITICAL)

graph-parallel-resources - Structure resources for maximum parallelism
graph-output-dependencies - Use outputs to express true dependencies
graph-explicit-depends - Use dependsOn only for external dependencies
graph-avoid-apply-side-effects - Avoid side effects in apply functions
graph-conditional-resources - Use conditional logic at resource level
graph-stack-references-minimal - Minimize stack reference depth

3. Component Design (HIGH)

pcomp-component-resources - Use ComponentResource for reusable abstractions
pcomp-parent-child - Pass parent option to child resources
pcomp-unique-naming - Use name prefix pattern for unique resource names
pcomp-register-outputs - Register component outputs explicitly
pcomp-multi-language - Design components for multi-language consumption
pcomp-transformations - Use transformations for cross-cutting concerns

4. Secrets and Configuration (HIGH)

secrets-use-secret-config - Use secret config for sensitive values
secrets-avoid-state-exposure - Prevent secret leakage in state
secrets-external-providers - Use external secret managers for production
secrets-generate-random - Generate secrets with random provider
secrets-provider-rotation - Rotate secrets provider when team members leave
secrets-environment-isolation - Isolate secrets by environment

5. Stack Organization (MEDIUM-HIGH)

stack-separation-by-lifecycle - Separate stacks by deployment lifecycle
stack-references-parameterized - Parameterize stack references
stack-output-minimal - Export only required outputs
stack-naming-conventions - Use consistent stack naming convention

6. Resource Options and Lifecycle (MEDIUM)

lifecycle-protect-stateful - Protect stateful resources
lifecycle-delete-before-replace - Use deleteBeforeReplace for unique constraints
lifecycle-retain-on-delete - Use retainOnDelete for shared resources
lifecycle-ignore-changes - Use ignoreChanges for externally managed properties
lifecycle-replace-on-changes - Use replaceOnChanges for immutable dependencies
lifecycle-aliases - Use aliases for safe resource renaming
lifecycle-custom-timeouts - Set custom timeouts for long-running resources

7. Testing and Validation (MEDIUM)

test-unit-mocking - Use mocks for fast unit tests
test-property-policies - Use policy as code for property testing
test-integration-ephemeral - Use ephemeral stacks for integration tests
test-preview-assertions - Assert on preview results before deployment
test-stack-reference-mocking - Mock stack references in unit tests

8. Automation and CI/CD (LOW-MEDIUM)

auto-automation-api-workflows - Use Automation API for complex workflows
auto-inline-programs - Use inline programs for dynamic infrastructure
auto-ci-cd-preview - Run preview in PR checks
auto-deployments-api - Use Pulumi Deployments for GitOps
auto-review-stacks - Use review stacks for PR environments
auto-drift-detection - Enable drift detection for production

How to Use

Read individual reference files for detailed explanations and code examples:

Section definitions - Category structure and impact levels
Rule template - Template for adding new rules

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Comments

Markdown supported

Details

Author: pproenca
Repository: pproenca/dot-skills
Category: Cloud & DevOps
Installs: 307
GitHub stars: 218

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.