pulumi

Pulumi infrastructure as code performance and reliability guidelines. This skill should be used when writing, reviewing, or refactoring Pulumi code to ensure optimal deployment performance and infrastructure reliability. Triggers on tasks involving Pulumi stacks, components, state management, secrets configuration, resource lifecycle options, or CI/CD automation.

Jump to install

Repository: pproenca/dot-skills
Last source activity: May 27, 2026 at 09:50
Detected SKILL.md language: English
Stars: 194
Forks: 17

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

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

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

52 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

View all from this repository

name	pulumi
description	Pulumi infrastructure as code performance and reliability guidelines. This skill should be used when writing, reviewing, or refactoring Pulumi code to ensure optimal deployment performance and infrastructure reliability. Triggers on tasks involving Pulumi stacks, components, state management, secrets configuration, resource lifecycle options, or CI/CD automation.

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

pulumi

Install options

Review the source files

Pulumi Best Practices

When to Apply

Rule Categories by Priority

Pulumi Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. State Management and Backend (CRITICAL)

2. Resource Graph Optimization (CRITICAL)

3. Component Design (HIGH)

4. Secrets and Configuration (HIGH)

5. Stack Organization (MEDIUM-HIGH)

6. Resource Options and Lifecycle (MEDIUM)

7. Testing and Validation (MEDIUM)

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

How to Use

Full Compiled Document

pulumi

Source facts

Install options

Review the source files

More from this repository

Pulumi Best Practices

When to Apply

Rule Categories by Priority

Pulumi Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. State Management and Backend (CRITICAL)

2. Resource Graph Optimization (CRITICAL)

3. Component Design (HIGH)

4. Secrets and Configuration (HIGH)

5. Stack Organization (MEDIUM-HIGH)

6. Resource Options and Lifecycle (MEDIUM)

7. Testing and Validation (MEDIUM)

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

How to Use

Full Compiled Document

More from this repository