render
Expert guidance for Render, the modern cloud platform for deploying web applications, APIs, databases, and background workers. Helps developers configure Render services using `render.yaml` Infrastructure as Code, set up auto-deploy from Git, manage environment variables, and optimize for production workloads.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o render.zip https://jpskill.com/download/15337.zip && unzip -o render.zip && rm render.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/15337.zip -OutFile "$d\render.zip"; Expand-Archive "$d\render.zip" -DestinationPath $d -Force; ri "$d\render.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
render.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
renderフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
Render — Cloud Application Platform
Overview
Render, the modern cloud platform for deploying web applications, APIs, databases, and background workers. Helps developers configure Render services using render.yaml Infrastructure as Code, set up auto-deploy from Git, manage environment variables, and optimize for production workloads.
Instructions
Infrastructure as Code
Define all services in a single render.yaml:
# render.yaml — Complete application infrastructure
services:
# Web service — auto-deployed from Git
- type: web
name: api-server
runtime: node
region: oregon
plan: standard # free | starter | standard | pro
buildCommand: npm ci && npm run build
startCommand: npm start
envVars:
- key: NODE_ENV
value: production
- key: DATABASE_URL
fromDatabase:
name: main-db
property: connectionString
- key: REDIS_URL
fromService:
name: redis-cache
type: redis
property: connectionString
- key: JWT_SECRET
generateValue: true # Auto-generate a random secret
- key: SENTRY_DSN
sync: false # Must be set manually in dashboard
autoDeploy: true # Deploy on every push to branch
healthCheckPath: /health
numInstances: 2 # Horizontal scaling
scaling:
minInstances: 1
maxInstances: 5
targetMemoryPercent: 70
targetCPUPercent: 60
# Background worker — same repo, different entry point
- type: worker
name: job-processor
runtime: node
buildCommand: npm ci && npm run build
startCommand: npm run worker
envVars:
- key: DATABASE_URL
fromDatabase:
name: main-db
property: connectionString
- key: REDIS_URL
fromService:
name: redis-cache
type: redis
property: connectionString
# Static site — frontend SPA
- type: web
name: frontend
runtime: static
buildCommand: cd frontend && npm ci && npm run build
staticPublishPath: frontend/dist
headers:
- path: /*
name: Cache-Control
value: public, max-age=31536000, immutable
- path: /index.html
name: Cache-Control
value: no-cache
routes:
- type: rewrite
source: /*
destination: /index.html # SPA routing fallback
# Cron job — scheduled tasks
- type: cron
name: daily-cleanup
runtime: node
buildCommand: npm ci
startCommand: npm run cleanup
schedule: "0 3 * * *" # 3 AM daily
envVars:
- key: DATABASE_URL
fromDatabase:
name: main-db
property: connectionString
# Private service (internal only, no public URL)
- type: pserv
name: internal-api
runtime: docker
dockerfilePath: ./Dockerfile
envVars:
- key: PORT
value: "3001"
databases:
- name: main-db
plan: standard # free | starter | standard | pro
databaseName: myapp
postgresMajorVersion: 16
ipAllowList: [] # Empty = allow all Render services
- name: redis-cache
plan: starter
Dockerfile Deployment
Deploy any application with Docker:
# Dockerfile — Multi-stage build for a Node.js API
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build
FROM node:20-alpine AS runner
WORKDIR /app
RUN addgroup -g 1001 -S nodejs && adduser -S nodejs -u 1001
COPY --from=builder --chown=nodejs:nodejs /app/dist ./dist
COPY --from=builder --chown=nodejs:nodejs /app/node_modules ./node_modules
COPY --from=builder --chown=nodejs:nodejs /app/package.json ./
USER nodejs
EXPOSE 3000
ENV NODE_ENV=production
CMD ["node", "dist/index.js"]
Blueprint Sync API
Programmatically manage services:
// scripts/deploy.ts — Trigger manual deploy via Render API
const RENDER_API_KEY = process.env.RENDER_API_KEY!;
const SERVICE_ID = process.env.RENDER_SERVICE_ID!;
async function triggerDeploy(commitId?: string) {
const response = await fetch(
`https://api.render.com/v1/services/${SERVICE_ID}/deploys`,
{
method: "POST",
headers: {
Authorization: `Bearer ${RENDER_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
clearCache: "do_not_clear",
}),
}
);
const deploy = await response.json();
console.log(`Deploy triggered: ${deploy.id} (status: ${deploy.status})`);
return deploy;
}
// List recent deploys
async function getDeployHistory() {
const response = await fetch(
`https://api.render.com/v1/services/${SERVICE_ID}/deploys?limit=10`,
{
headers: { Authorization: `Bearer ${RENDER_API_KEY}` },
}
);
return response.json();
}
// Scale service
async function scaleService(numInstances: number) {
const response = await fetch(
`https://api.render.com/v1/services/${SERVICE_ID}/scale`,
{
method: "POST",
headers: {
Authorization: `Bearer ${RENDER_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ numInstances }),
}
);
return response.json();
}
Custom Domains and SSL
# render.yaml — Custom domain configuration
services:
- type: web
name: api-server
customDomains:
- domain: api.myapp.com # SSL auto-provisioned via Let's Encrypt
- domain: api.myapp.io
Environment Groups
Share environment variables across services:
# render.yaml — Using environment groups
envVarGroups:
- name: shared-config
envVars:
- key: LOG_LEVEL
value: info
- key: CORS_ORIGIN
value: https://myapp.com
- key: AWS_REGION
value: us-east-1
services:
- type: web
name: api-server
envVars:
- fromGroup: shared-config
- key: PORT
value: "3000"
- type: worker
name: job-processor
envVars:
- fromGroup: shared-config
Examples
Example 1: Setting up Render for a microservices project
User request:
I have a Node.js API and a React frontend running in Docker. Set up Render for monitoring/deployment.
The agent creates the necessary configuration files based on patterns like # render.yaml — Complete application infrastructure, sets up the integration with the existing Docker setup, configures appropriate defaults for a Node.js + React stack, and provides verification commands to confirm everything is working.
Example 2: Troubleshooting dockerfile deployment issues
User request:
Render is showing errors in our dockerfile deployment. Here are the logs: [error output]
The agent analyzes the error output, identifies the root cause by cross-referencing with common Render issues, applies the fix (updating configuration, adjusting resource limits, or correcting syntax), and verifies the resolution with appropriate health checks.
Guidelines
- Use render.yaml — Infrastructure as Code is versioned with your app; no manual dashboard config to reproduce
- Health checks are mandatory — Set
healthCheckPathso Render knows when your service is ready and can route traffic - Auto-scaling for production — Configure min/max instances with CPU/memory targets instead of fixed instance counts
- Environment groups for shared config — Don't duplicate environment variables across services; use
fromGroup - Use
generateValue: truefor secrets — Let Render generate random values for JWT secrets, API keys, etc. - Preview environments — Enable pull request previews for staging; each PR gets its own URL
- Multi-stage Docker builds — Keep production images small; separate build and runtime stages
- Database connection pooling — Use PgBouncer or connection pooling in your ORM; Render databases have connection limits