[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EDEDXAFWHYCGT0RDBCFBHF":3,"skill-same:01M7EDEDXAFWHYCGT0RDBCFBHF":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7EDEDXAFWHYCGT0RDBCFBHF","render-blueprints",null,"为 Render 基础设施编写并校验 render.yaml Blueprint。当用户需要编写或编辑 render.yaml、用 fromDatabase\u002FfromService\u002FfromGroup 串联服务、为多服务应用设置 project 与 environment、配置预览环境、对照 schema 校验，或修复不可变字段报错时使用。触发词:render.yaml、Blueprint、IaC、fromDatabase、fromService、envVarGroups、previews、projects、environments。","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: render-blueprints\ndescription: \"为 Render 基础设施编写并校验 render.yaml Blueprint。当用户需要编写或编辑 render.yaml、用 fromDatabase\u002FfromService\u002FfromGroup 串联服务、为多服务应用设置 project 与 environment、配置预览环境、对照 schema 校验，或修复不可变字段报错时使用。触发词:render.yaml、Blueprint、IaC、fromDatabase、fromService、envVarGroups、previews、projects、environments。\"\nlicense: MIT\ncompatibility: >-\n  Git repository on GitHub, GitLab, or Bitbucket for Blueprint sync. Render CLI\n  v2.7.0+ recommended for `render blueprints validate`. IDEs can validate\n  against the public JSON Schema URL below.\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: configuration\r\n---\r\n\r\n# Render Blueprints (render.yaml)\r\n\r\nBlueprints define Render infrastructure as YAML (commonly `render.yaml` at the repo root). This skill focuses on **authoring**, **wiring**, **projects\u002Fenvironments**, **previews**, **validation**, and **immutable fields**. Heavy detail lives under `references\u002F`.\r\n\r\n## When to Use\r\n\r\nApply this skill when the user:\r\n\r\n- Creates or edits a `render.yaml` \u002F Blueprint\r\n- Wires databases, private services, or Key Value into app env vars\r\n- Groups services with **projects** and **environments**\r\n- Configures **preview environments** for pull requests\r\n- Validates YAML against Render’s schema or CLI\r\n- Asks what can or cannot change after a resource is created\r\n\r\nFor end-to-end deploy flows and MCP\u002FCLI operations, see **render-deploy**. For env var strategy outside Blueprint syntax, see **render-env-vars**. For Docker-specific Blueprint fields, see **render-docker**.\r\n\r\n## Blueprint Structure\r\n\r\n### Top-level keys\r\n\r\n| Key | Purpose |\r\n|-----|---------|\r\n| `services` | Web, worker, cron, private service, Key Value, static (via `web` + `runtime: static`) |\r\n| `databases` | Managed PostgreSQL instances |\r\n| `envVarGroups` | Reusable env var sets attached to services |\r\n| `projects` | Optional grouping; contains `environments` and service lists |\r\n| `previews` | Defaults for PR preview environments |\r\n\r\nA Blueprint may also use patterns like **ungrouped** resources vs **environment-scoped** lists, depending on whether you adopt the projects model. Avoid duplicating the same logical resource in multiple places (see `references\u002Fcommon-mistakes.md`).\r\n\r\n### Schema and IDE validation\r\n\r\n- **JSON Schema URL:** `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\r\n- Configure your editor to associate `render.yaml` with that schema for completions and diagnostics.\r\n\r\n### Minimal example: web + PostgreSQL\r\n\r\n```yaml\r\ndatabases:\r\n  - name: mydb\r\n    plan: basic-256mb\r\n    region: oregon\r\n\r\nservices:\r\n  - type: web\r\n    name: api\r\n    runtime: node\r\n    region: oregon\r\n    plan: starter\r\n    buildCommand: npm ci && npm run build\r\n    startCommand: npm start\r\n    envVars:\r\n      - key: DATABASE_URL\r\n        fromDatabase:\r\n          name: mydb\r\n          property: connectionString\r\n```\r\n\r\n## Service Types\r\n\r\n| `type` | Role |\r\n|--------|------|\r\n| `web` | Public HTTP service (use `runtime: static` for static sites) |\r\n| `pserv` | Private service (internal HTTP\u002FTCP; not public) |\r\n| `worker` | Long-running background process |\r\n| `cron` | Scheduled job (`schedule` required) |\r\n| `keyvalue` | Managed Key Value (Redis-compatible); alias **`redis`** accepted in Blueprints |\r\n\r\n## Runtimes\r\n\r\nCommon `runtime` values: **`node`**, **`python`**, **`go`**, **`ruby`**, **`rust`**, **`elixir`**, **`docker`**, **`image`**, **`static`**.\r\n\r\n- **`docker`**: Build from `Dockerfile` (see `dockerfilePath`, `dockerContext`, `dockerCommand`).\r\n- **`image`**: Run a prebuilt container image (registry + optional `registryCredential`).\r\n- **`static`**: Static site; requires `staticPublishPath` and build output paths (see references).\r\n\r\n## Cross-Service Wiring\r\n\r\nEnv vars under `envVars` (and analogous patterns in groups) can pull values from other resources instead of hardcoding secrets.\r\n\r\n### `fromDatabase`\r\n\r\nReference a database in `databases:` by `name`. Properties include:\r\n\r\n- `connectionString`, `host`, `port`, `user`, `password`, `database`\r\n\r\n### `fromService`\r\n\r\nReference a service by `name`. Typical properties:\r\n\r\n- `host`, `port`, `hostport`, `connectionString`, `envVarKey`\r\n\r\nWhich properties are valid depends on target service type (e.g. Key Value vs `pserv`). See `references\u002Fwiring-patterns.md`.\r\n\r\n### `fromGroup`\r\n\r\nAttach shared vars from `envVarGroups` (by group `name`).\r\n\r\n### Other env var keys\r\n\r\n- **`value`**: Literal string.\r\n- **`generateValue`**: Let Render generate a random secret (password\u002FAPI key).\r\n- **`sync`**: Set `sync: false` for secrets that should not sync from repo on every update (see edge cases in wiring reference).\r\n\r\nFull patterns and combinations: `references\u002Fwiring-patterns.md`.\r\n\r\n## Projects and Environments\r\n\r\nFor multi-service apps, use the **`projects`\u002F`environments`** pattern instead of flat top-level `services`\u002F`databases`. This groups all related resources into a single Render project, supports multiple environments (production, staging), and enables environment-scoped configuration.\r\n\r\n```yaml\r\nprojects:\r\n  - name: my-app\r\n    environments:\r\n      - name: production\r\n        services:\r\n          - type: web\r\n            name: api\r\n            runtime: node\r\n            plan: standard\r\n            buildCommand: npm ci && npm run build\r\n            startCommand: npm start\r\n            envVars:\r\n              - key: DATABASE_URL\r\n                fromDatabase:\r\n                  name: db\r\n                  property: connectionString\r\n              - key: REDIS_URL\r\n                fromService:\r\n                  type: keyvalue\r\n                  name: cache\r\n                  property: connectionString\r\n              - key: API_SECRET\r\n                sync: false\r\n\r\n          - type: worker\r\n            name: jobs\r\n            runtime: node\r\n            plan: starter\r\n            buildCommand: npm ci\r\n            startCommand: node worker.js\r\n            envVars:\r\n              - key: DATABASE_URL\r\n                fromDatabase:\r\n                  name: db\r\n                  property: connectionString\r\n              - key: REDIS_URL\r\n                fromService:\r\n                  type: keyvalue\r\n                  name: cache\r\n                  property: connectionString\r\n\r\n          - type: keyvalue\r\n            name: cache\r\n            plan: starter\r\n            maxmemoryPolicy: noeviction\r\n            ipAllowList:\r\n              - source: 0.0.0.0\u002F0\r\n                description: everywhere\r\n\r\n        databases:\r\n          - name: db\r\n            plan: starter\r\n```\r\n\r\nKey rules:\r\n\r\n- Each environment owns its `services` and `databases` lists.\r\n- Do not define the same resource at both the root level and inside an environment.\r\n- `envVarGroups` can be scoped to a project environment or shared across the workspace.\r\n- Environment isolation (Professional+) can block cross-environment private network traffic.\r\n\r\nFor single-service apps, flat top-level `services`\u002F`databases` is fine. Reach for the projects pattern when you have multiple services, need staging\u002Fproduction separation, or want environment-scoped env groups.\r\n\r\n## Preview Environments\r\n\r\nTop-level `previews` controls PR previews:\r\n\r\n- **`previews.generation`**: `off` (default), `manual`, or `automatic`\r\n- **`previews.expireAfterDays`**: Auto-delete preview stacks after N days\r\n\r\nServices can override preview behavior (e.g. service-level `previews.generation`). Limitations: autoscaling behavior, `sync: false` vars, `previewPlan` \u002F flexible instance constraints—see `references\u002Fpreview-environments.md`.\r\n\r\n## Validation\r\n\r\n```bash\r\nrender blueprints validate\r\n```\r\n\r\nRequires **Render CLI v2.7.0+**. Run from the repo root (or pass the appropriate path options your CLI version supports). Fix schema and semantic errors before merging Blueprint changes.\r\n\r\nOfficial schema: `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\r\n\r\n## Immutable Fields\r\n\r\n**CRITICAL:** Some fields cannot change after the resource is created. Edits may be rejected or require replacement resources.\r\n\r\n### Services\r\n\r\n- **`type`**: Cannot change (e.g. web → worker).\r\n- **`runtime`**: Cannot change (e.g. node → docker).\r\n\r\n### Databases\r\n\r\nCannot change after creation:\r\n\r\n- `name` (logical Blueprint\u002Fdatabase identifier in this context)\r\n- `databaseName`\r\n- `user`\r\n- `region`\r\n- `postgresMajorVersion`\r\n\r\nPlan other fields (disk, HA, replicas) carefully up front; consult Render docs for fields that can scale vs require recreation.\r\n\r\n## Key Fields (Quick Map)\r\n\r\n| Area | Fields |\r\n|------|--------|\r\n| Plans | `plan`, `previewPlan` (previews), database `plan` |\r\n| Build\u002Frun | `buildCommand`, `startCommand`, `preDeployCommand`, `rootDir` |\r\n| Deploy | `autoDeployTrigger`: `commit`, `checksPass`, or `off` |\r\n| Lifecycle | `maxShutdownDelaySeconds`: 1–300, default **30** |\r\n| HTTP | `healthCheckPath`, `domains` |\r\n| Storage | `disk` (`name`, `mountPath`, `sizeGB`) |\r\n| Scale | `scaling` \u002F `numInstances` (see references) |\r\n| Monorepo | `buildFilter` (`paths`, `ignoredPaths`) |\r\n| Docker | `dockerfilePath`, `dockerContext`, `dockerCommand`, `registryCredential` |\r\n\r\nDeprecated names to avoid: `env` (use `runtime`), `redis` (use `keyvalue`), `autoDeploy` (use `autoDeployTrigger`), `pullRequestPreviewsEnabled` (use `previews.generation`). Details: `references\u002Fcommon-mistakes.md`.\r\n\r\n## References\r\n\r\n| Document | Contents |\r\n|----------|----------|\r\n| `references\u002Ffield-reference.md` | YAML fields by service type, database, groups, projects, previews, scaling, disk, static, Key Value |\r\n| `references\u002Fwiring-patterns.md` | `fromDatabase` \u002F `fromService` \u002F `fromGroup` examples, `sync: false`, `generateValue`, combinations |\r\n| `references\u002Fcommon-mistakes.md` | Branch + previews, `buildFilter`, replicas, duplicates, preview plans, wiring mistakes |\r\n| `references\u002Fpreview-environments.md` | `previews.generation`, expiry, overrides, `previewPlan`, disks, PR workflow |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — Deploy flows, Blueprint vs direct create, MCP\u002Fdeeplinks\r\n- **render-env-vars** — Env var strategy, secrets, Dashboard vs Blueprint\r\n- **render-docker** — Dockerfile-backed services and image runtime nuances\r\n","# Render Blueprints (render.yaml)\r\n\r\nBlueprints define Render infrastructure as YAML (commonly `render.yaml` at the repo root). This skill focuses on **authoring**, **wiring**, **projects\u002Fenvironments**, **previews**, **validation**, and **immutable fields**. Heavy detail lives under `references\u002F`.\r\n\r\n## When to Use\r\n\r\nApply this skill when the user:\r\n\r\n- Creates or edits a `render.yaml` \u002F Blueprint\r\n- Wires databases, private services, or Key Value into app env vars\r\n- Groups services with **projects** and **environments**\r\n- Configures **preview environments** for pull requests\r\n- Validates YAML against Render’s schema or CLI\r\n- Asks what can or cannot change after a resource is created\r\n\r\nFor end-to-end deploy flows and MCP\u002FCLI operations, see **render-deploy**. For env var strategy outside Blueprint syntax, see **render-env-vars**. For Docker-specific Blueprint fields, see **render-docker**.\r\n\r\n## Blueprint Structure\r\n\r\n### Top-level keys\r\n\r\n| Key | Purpose |\r\n|-----|---------|\r\n| `services` | Web, worker, cron, private service, Key Value, static (via `web` + `runtime: static`) |\r\n| `databases` | Managed PostgreSQL instances |\r\n| `envVarGroups` | Reusable env var sets attached to services |\r\n| `projects` | Optional grouping; contains `environments` and service lists |\r\n| `previews` | Defaults for PR preview environments |\r\n\r\nA Blueprint may also use patterns like **ungrouped** resources vs **environment-scoped** lists, depending on whether you adopt the projects model. Avoid duplicating the same logical resource in multiple places (see `references\u002Fcommon-mistakes.md`).\r\n\r\n### Schema and IDE validation\r\n\r\n- **JSON Schema URL:** `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\r\n- Configure your editor to associate `render.yaml` with that schema for completions and diagnostics.\r\n\r\n### Minimal example: web + PostgreSQL\r\n\r\n```yaml\r\ndatabases:\r\n  - name: mydb\r\n    plan: basic-256mb\r\n    region: oregon\r\n\r\nservices:\r\n  - type: web\r\n    name: api\r\n    runtime: node\r\n    region: oregon\r\n    plan: starter\r\n    buildCommand: npm ci && npm run build\r\n    startCommand: npm start\r\n    envVars:\r\n      - key: DATABASE_URL\r\n        fromDatabase:\r\n          name: mydb\r\n          property: connectionString\r\n```\r\n\r\n## Service Types\r\n\r\n| `type` | Role |\r\n|--------|------|\r\n| `web` | Public HTTP service (use `runtime: static` for static sites) |\r\n| `pserv` | Private service (internal HTTP\u002FTCP; not public) |\r\n| `worker` | Long-running background process |\r\n| `cron` | Scheduled job (`schedule` required) |\r\n| `keyvalue` | Managed Key Value (Redis-compatible); alias **`redis`** accepted in Blueprints |\r\n\r\n## Runtimes\r\n\r\nCommon `runtime` values: **`node`**, **`python`**, **`go`**, **`ruby`**, **`rust`**, **`elixir`**, **`docker`**, **`image`**, **`static`**.\r\n\r\n- **`docker`**: Build from `Dockerfile` (see `dockerfilePath`, `dockerContext`, `dockerCommand`).\r\n- **`image`**: Run a prebuilt container image (registry + optional `registryCredential`).\r\n- **`static`**: Static site; requires `staticPublishPath` and build output paths (see references).\r\n\r\n## Cross-Service Wiring\r\n\r\nEnv vars under `envVars` (and analogous patterns in groups) can pull values from other resources instead of hardcoding secrets.\r\n\r\n### `fromDatabase`\r\n\r\nReference a database in `databases:` by `name`. Properties include:\r\n\r\n- `connectionString`, `host`, `port`, `user`, `password`, `database`\r\n\r\n### `fromService`\r\n\r\nReference a service by `name`. Typical properties:\r\n\r\n- `host`, `port`, `hostport`, `connectionString`, `envVarKey`\r\n\r\nWhich properties are valid depends on target service type (e.g. Key Value vs `pserv`). See `references\u002Fwiring-patterns.md`.\r\n\r\n### `fromGroup`\r\n\r\nAttach shared vars from `envVarGroups` (by group `name`).\r\n\r\n### Other env var keys\r\n\r\n- **`value`**: Literal string.\r\n- **`generateValue`**: Let Render generate a random secret (password\u002FAPI key).\r\n- **`sync`**: Set `sync: false` for secrets that should not sync from repo on every update (see edge cases in wiring reference).\r\n\r\nFull patterns and combinations: `references\u002Fwiring-patterns.md`.\r\n\r\n## Projects and Environments\r\n\r\nFor multi-service apps, use the **`projects`\u002F`environments`** pattern instead of flat top-level `services`\u002F`databases`. This groups all related resources into a single Render project, supports multiple environments (production, staging), and enables environment-scoped configuration.\r\n\r\n```yaml\r\nprojects:\r\n  - name: my-app\r\n    environments:\r\n      - name: production\r\n        services:\r\n          - type: web\r\n            name: api\r\n            runtime: node\r\n            plan: standard\r\n            buildCommand: npm ci && npm run build\r\n            startCommand: npm start\r\n            envVars:\r\n              - key: DATABASE_URL\r\n                fromDatabase:\r\n                  name: db\r\n                  property: connectionString\r\n              - key: REDIS_URL\r\n                fromService:\r\n                  type: keyvalue\r\n                  name: cache\r\n                  property: connectionString\r\n              - key: API_SECRET\r\n                sync: false\r\n\r\n          - type: worker\r\n            name: jobs\r\n            runtime: node\r\n            plan: starter\r\n            buildCommand: npm ci\r\n            startCommand: node worker.js\r\n            envVars:\r\n              - key: DATABASE_URL\r\n                fromDatabase:\r\n                  name: db\r\n                  property: connectionString\r\n              - key: REDIS_URL\r\n                fromService:\r\n                  type: keyvalue\r\n                  name: cache\r\n                  property: connectionString\r\n\r\n          - type: keyvalue\r\n            name: cache\r\n            plan: starter\r\n            maxmemoryPolicy: noeviction\r\n            ipAllowList:\r\n              - source: 0.0.0.0\u002F0\r\n                description: everywhere\r\n\r\n        databases:\r\n          - name: db\r\n            plan: starter\r\n```\r\n\r\nKey rules:\r\n\r\n- Each environment owns its `services` and `databases` lists.\r\n- Do not define the same resource at both the root level and inside an environment.\r\n- `envVarGroups` can be scoped to a project environment or shared across the workspace.\r\n- Environment isolation (Professional+) can block cross-environment private network traffic.\r\n\r\nFor single-service apps, flat top-level `services`\u002F`databases` is fine. Reach for the projects pattern when you have multiple services, need staging\u002Fproduction separation, or want environment-scoped env groups.\r\n\r\n## Preview Environments\r\n\r\nTop-level `previews` controls PR previews:\r\n\r\n- **`previews.generation`**: `off` (default), `manual`, or `automatic`\r\n- **`previews.expireAfterDays`**: Auto-delete preview stacks after N days\r\n\r\nServices can override preview behavior (e.g. service-level `previews.generation`). Limitations: autoscaling behavior, `sync: false` vars, `previewPlan` \u002F flexible instance constraints—see `references\u002Fpreview-environments.md`.\r\n\r\n## Validation\r\n\r\n```bash\r\nrender blueprints validate\r\n```\r\n\r\nRequires **Render CLI v2.7.0+**. Run from the repo root (or pass the appropriate path options your CLI version supports). Fix schema and semantic errors before merging Blueprint changes.\r\n\r\nOfficial schema: `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\r\n\r\n## Immutable Fields\r\n\r\n**CRITICAL:** Some fields cannot change after the resource is created. Edits may be rejected or require replacement resources.\r\n\r\n### Services\r\n\r\n- **`type`**: Cannot change (e.g. web → worker).\r\n- **`runtime`**: Cannot change (e.g. node → docker).\r\n\r\n### Databases\r\n\r\nCannot change after creation:\r\n\r\n- `name` (logical Blueprint\u002Fdatabase identifier in this context)\r\n- `databaseName`\r\n- `user`\r\n- `region`\r\n- `postgresMajorVersion`\r\n\r\nPlan other fields (disk, HA, replicas) carefully up front; consult Render docs for fields that can scale vs require recreation.\r\n\r\n## Key Fields (Quick Map)\r\n\r\n| Area | Fields |\r\n|------|--------|\r\n| Plans | `plan`, `previewPlan` (previews), database `plan` |\r\n| Build\u002Frun | `buildCommand`, `startCommand`, `preDeployCommand`, `rootDir` |\r\n| Deploy | `autoDeployTrigger`: `commit`, `checksPass`, or `off` |\r\n| Lifecycle | `maxShutdownDelaySeconds`: 1–300, default **30** |\r\n| HTTP | `healthCheckPath`, `domains` |\r\n| Storage | `disk` (`name`, `mountPath`, `sizeGB`) |\r\n| Scale | `scaling` \u002F `numInstances` (see references) |\r\n| Monorepo | `buildFilter` (`paths`, `ignoredPaths`) |\r\n| Docker | `dockerfilePath`, `dockerContext`, `dockerCommand`, `registryCredential` |\r\n\r\nDeprecated names to avoid: `env` (use `runtime`), `redis` (use `keyvalue`), `autoDeploy` (use `autoDeployTrigger`), `pullRequestPreviewsEnabled` (use `previews.generation`). Details: `references\u002Fcommon-mistakes.md`.\r\n\r\n## References\r\n\r\n| Document | Contents |\r\n|----------|----------|\r\n| `references\u002Ffield-reference.md` | YAML fields by service type, database, groups, projects, previews, scaling, disk, static, Key Value |\r\n| `references\u002Fwiring-patterns.md` | `fromDatabase` \u002F `fromService` \u002F `fromGroup` examples, `sync: false`, `generateValue`, combinations |\r\n| `references\u002Fcommon-mistakes.md` | Branch + previews, `buildFilter`, replicas, duplicates, preview plans, wiring mistakes |\r\n| `references\u002Fpreview-environments.md` | `previews.generation`, expiry, overrides, `previewPlan`, disks, PR workflow |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — Deploy flows, Blueprint vs direct create, MCP\u002Fdeeplinks\r\n- **render-env-vars** — Env var strategy, secrets, Dashboard vs Blueprint\r\n- **render-docker** — Dockerfile-backed services and image runtime nuances\r\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","configuration","Git repository on GitHub, GitLab, or Bitbucket for Blueprint sync. Render CLI v2.7.0+ recommended for `render blueprints validate`. IDEs can validate against the public JSON Schema URL below.","main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Frender\u002Fskills\u002Frender-blueprints",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill render-blueprints",{"tool":45,"command":46},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill render-blueprints",{"tool":48,"command":49},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill render-blueprints","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"agents\u002Fopenai.yaml","REFERENCE","参考文档",220,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002Fagents\u002Fopenai.yaml",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcommon-mistakes.md",4502,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fcommon-mistakes.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Ffield-reference.md",8696,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002Freferences\u002Ffield-reference.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fpreview-environments.md",3933,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fpreview-environments.md",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fwiring-patterns.md",4641,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fwiring-patterns.md",[76,85,92,100,107,114],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EDVCKB89EF755PQMKV1BZA","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EDHHD98T8ZH09F40Q973G3","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]