render-blueprints

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

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/greenmartialarts/EventCore --skill render-blueprints-greenmartialarts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-blueprints
Source: https://github.com/greenmartialarts/EventCore/tree/main/.junie/skills/render-blueprints
Command: npx skills add https://github.com/greenmartialarts/EventCore --skill render-blueprints-greenmartialarts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing Render Blueprints by hand is error-prone: miswired service references, deprecated field names, immutable fields changed after creation, and misconfigured preview environments all cause failed deploys or destroyed resources. This Skill provides the schema knowledge, wiring patterns, and validation workflow needed to author correct render.yaml files the first time. ## Core Features & Use Cases - Blueprint Authoring: Defines services (web, worker, cron, pserv, keyvalue, static), databases, env var groups, and projects/environments with correct field names and structure. - 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 mistakes like empty readReplicas lists. - Use Case: You need to deploy a multi-service app with a web API, background worker, Postgres, and Key Value across production and staging environments. Use this Skill to generate a projects/environments Blueprint with proper wiring, then validate it with render blueprints validate before merging. ## Quick Start Ask the assistant to write a render.yaml Blueprint for your app with a web service, worker, Postgres database, and Key Value instance wired together, then validate it.

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 var references.

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, or password. This injects the live connection value at deploy time instead of hardcoding credentials in the repo.

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 inline diagnostics.

Which render.yaml fields cannot be changed after creation?

Service type and runtime are immutable, as are database name, databaseName, user, region, and postgresMajorVersion. Changing these requires creating replacement resources, so plan them carefully up front.

Why do Render preview environments miss my secret env vars?

Variables marked sync:false are excluded from automatic preview configuration and must be set manually on each preview service. Prefer generateValue secrets or CI-injected values for previews.

When should I use projects and environments instead of flat services in render.yaml?

Use the projects/environments pattern for multi-service apps needing staging and production separation or environment-scoped env var groups. Single-service apps can use flat top-level services and databases lists.