render-blueprints

Authors and validates render.yaml Blueprints for Render infrastructure as code.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-blueprints-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-blueprints
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-blueprints
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-blueprints-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing render.yaml Blueprints by hand is error-prone: miswired service references, deprecated field names, immutable field edits, and preview misconfigurations cause failed deploys or destructive changes like wiped read replicas. This Skill provides the schema knowledge, wiring patterns, and validation workflow to author correct Blueprints the first time. ## Core Features & Use Cases - Blueprint Authoring: Defines services (web, pserv, worker, cron, keyvalue), databases, env var groups, projects, and environments with correct field usage and runtime selection. - Cross-Service Wiring: Connects resources with fromDatabase, fromService, fromGroup, generateValue, and sync:false patterns instead of hardcoding connection strings. - Validation & Safety: Validates against the official JSON Schema and Render CLI, and flags immutable fields (type, runtime, database name/region/version) and destructive patterns like empty readReplicas lists. - Use Case: You are splitting a monolith into a web API, a background worker, Postgres, and Key Value with staging and production environments. Use this Skill to generate a projects/environments Blueprint with correct wiring, then validate it with render blueprints validate before merging. ## Quick Start Ask the AI to write a render.yaml Blueprint for a Node web service connected to a managed Postgres database and validate it against the Render schema.

Frequently Asked Questions about render-blueprints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a render.yaml Blueprint for Render?▼

Define services and databases as top-level lists, or group them under projects and environments for multi-service apps. Each service needs a type, runtime, plan, and build/start commands; wire dependencies with fromDatabase or fromService env vars instead of hardcoded strings.

How do I connect a Render service to a Postgres database in a Blueprint?▼

Add an envVars entry using fromDatabase with the database name and a property such as connectionString, host, port, user, password, or database. The referenced database must be defined in the same Blueprint scope or already exist in the workspace.

How do I validate a render.yaml file before deploying?▼

Run render blueprints validate with Render CLI v2.7.0 or later from the repo root. You can also configure your IDE to validate against the public JSON Schema at https://render.com/schema/render.yaml.json for completions and diagnostics.

Which render.yaml fields cannot be changed after creation?▼

Service type and runtime are immutable after creation. For databases, name, databaseName, user, region, and postgresMajorVersion cannot change; editing them requires creating replacement resources.

Why did my Render Blueprint delete my read replicas?▼

Setting readReplicas to an empty list is treated as authoritative and destroys all read replicas. Only include replica entries you want to exist, and validate changes in a non-production environment first.

How do preview environments work in Render Blueprints?▼

Set previews.generation to off, manual, or automatic, and optionally expireAfterDays for automatic cleanup. Note that sync:false env vars are excluded from previews, autoscaling is disabled, and previewPlan must be compatible with the primary plan family.