[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76X5MWV7ZVKBZNVCEC6Z2KH":3,"skill-same:01M76X5MWV7ZVKBZNVCEC6Z2KH":69},{"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":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M76X5MWV7ZVKBZNVCEC6Z2KH","render-docker",null,"Builds and deploys Docker containers on Render—Dockerfiles, multi-stage builds, Blueprint Docker fields, private registries, layer caching, and platform constraints. Use when the user mentions Docker, Dockerfile, container images, multi-stage builds, container registry, GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or optimizing Docker builds on Render.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: render-docker\ndescription: >-\n  Builds and deploys Docker containers on Render—Dockerfiles, multi-stage\n  builds, Blueprint Docker fields, private registries, layer caching, and\n  platform constraints. Use when the user mentions Docker,\n  Dockerfile, container images, multi-stage builds, container registry,\n  GHCR, ECR, BuildKit, dockerContext, runtime docker or image, or\n  optimizing Docker builds on Render.\nlicense: MIT\ncompatibility: >-\n  Any Render compute service (web, private, worker, cron) with runtime: docker\n  or runtime: image.\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: deployment\n---\n\n# Render Docker Deployments\n\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\n\n## When to Use\n\n- Authoring or debugging a **Dockerfile** for a Render service\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\n- Wiring **private base images** or **prebuilt images** with registry credentials\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\n- **Performance** and **security** hardening of container images on Render\n\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\n\n## Render Docker Builds\n\n- **BuildKit** is used for Docker builds on Render.\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\n\n## Blueprint Configuration\n\n| Field | Role |\n|-------|------|\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\n| `dockerContext` | Build context directory (what is sent to the daemon) |\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\n\nExample sketch (values illustrative):\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: docker\n    region: oregon\n    plan: starter\n    dockerfilePath: .\u002FDockerfile\n    dockerContext: .\n    dockerCommand: node server.js\n    envVars:\n      - key: PORT\n        value: 10000\n```\n\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\n\n## Multi-Stage Builds\n\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\n\n- Smaller images and faster pulls\n- Fewer tools and secrets in the final image (smaller attack surface)\n- Clear separation between build-time and run-time dependencies\n\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\n\n## Build Args vs Secrets\n\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\n\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\n\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\n\n## Registry Configuration\n\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\n\n- Store credentials in the Render Dashboard under **Registry Credentials**.\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\n\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\n\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\n\n## Layer Caching\n\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\n\n## Platform Specifics\n\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\n\n## `.dockerignore` and Start Commands\n\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\n","# Render Docker Deployments\n\nRender uses **BuildKit** for Docker builds. All compute service types that support custom runtimes can use **`runtime: docker`** (build from a Dockerfile in the repo) or **`runtime: image`** (pull a prebuilt image; no Dockerfile build on Render). Deeper patterns and copy-paste templates live under `references\u002F`.\n\n## When to Use\n\n- Authoring or debugging a **Dockerfile** for a Render service\n- Choosing **`runtime: docker`** vs **`runtime: image`** in a Blueprint\n- Wiring **private base images** or **prebuilt images** with registry credentials\n- **Multi-stage builds**, **build args**, **secrets**, and **layer caching**\n- **Performance** and **security** hardening of container images on Render\n\nFor full Blueprint authoring, see **render-blueprints**. For end-to-end deploy flows, see **render-deploy**.\n\n## Render Docker Builds\n\n- **BuildKit** is used for Docker builds on Render.\n- **`runtime: docker`**: Render builds an image from your repo using `dockerfilePath`, `dockerContext`, and optional `dockerCommand` (overrides image `CMD`).\n- **`runtime: image`**: Render pulls **`image.url`**; no repo-based image build. Pair with **`registryCredential`** when the registry is private.\n\n## Blueprint Configuration\n\n| Field | Role |\n|-------|------|\n| `dockerfilePath` | Path to the Dockerfile (default `.\u002FDockerfile`) |\n| `dockerContext` | Build context directory (what is sent to the daemon) |\n| `dockerCommand` | Overrides the container `CMD` after the image is built |\n| `image.url` | Image reference for `runtime: image` (registry\u002Frepo:tag or digest) |\n| `registryCredential` | Auth for private pulls; often `fromRegistryCreds` → Dashboard-stored credential |\n\nExample sketch (values illustrative):\n\n```yaml\nservices:\n  - type: web\n    name: api\n    runtime: docker\n    region: oregon\n    plan: starter\n    dockerfilePath: .\u002FDockerfile\n    dockerContext: .\n    dockerCommand: node server.js\n    envVars:\n      - key: PORT\n        value: 10000\n```\n\nFor `runtime: image`, set `image.url` and, if needed, `registryCredential` per **Registry Configuration** below.\n\n## Multi-Stage Builds\n\n**Recommended for production.** Use a **builder** stage for compilation and dependency installation, and a minimal **runner** stage that only copies artifacts and runtime files. Benefits:\n\n- Smaller images and faster pulls\n- Fewer tools and secrets in the final image (smaller attack surface)\n- Clear separation between build-time and run-time dependencies\n\nSee `references\u002Fdockerfile-patterns.md` for language-specific templates.\n\n## Build Args vs Secrets\n\n**Critical:** **Never pass secrets via `ARG`.** Build arguments are stored in image **layers** and can be recovered from the image history or intermediate layers.\n\n- Prefer **runtime environment variables** (Render **env vars** \u002F secret files) for application secrets.\n- For **build-time** secrets (e.g. private package feeds), use **Docker BuildKit secret mounts** (`RUN --mount=type=secret,...`) rather than `ARG`.\n\nTreat anything sensitive as **runtime** or **BuildKit secret mount**, not as a build arg.\n\n## Registry Configuration\n\nPrivate **base images** (for `runtime: docker`) or **prebuilt images** (`runtime: image`) need authentication:\n\n- Store credentials in the Render Dashboard under **Registry Credentials**.\n- In Blueprint, reference them with **`registryCredential.fromRegistryCreds.name`** (match the Dashboard name).\n\nSupports common registries (Docker Hub, GHCR, ECR, Google Artifact Registry, and others). Step-by-step per provider: `references\u002Fregistry-setup.md`.\n\n**Prebuilt image services** do **not** auto-deploy when the tag moves in the registry; trigger a **manual redeploy** or use a **deploy hook** when you publish a new image.\n\n## Layer Caching\n\n- Render **caches Docker layers** between builds; **order Dockerfile instructions** so that frequently unchanged layers stay early (see `references\u002Foptimization-guide.md`).\n- **Tags and caching:** mutable tags like **`latest`** can resolve to **stale cached** images. Prefer **immutable** references: **digest** (`repo\u002Fimage@sha256:...`) or **version pins** (`v1.2.3`).\n\n## Platform Specifics\n\n- Render builds **linux\u002Famd64**. Avoid assumptions about other architectures in production images.\n- **Port binding** matches native services: bind HTTP to **`0.0.0.0:$PORT`** (Render sets `PORT`).\n- **Health checks** behave like non-Docker web services (`healthCheckPath`, etc.).\n- **Secret files** from Render appear under **`\u002Fetc\u002Fsecrets\u002F`** — do not rely on repo-root secret paths inside the container unless you copy or mount them explicitly in the image.\n\n## `.dockerignore` and Start Commands\n\n- Always maintain a **`.dockerignore`** that excludes **`node_modules`**, **`.git`**, **`.env`**, build artifacts, logs, and OS junk. This shrinks context upload time and avoids leaking local files into layers. Lists and rationale: `references\u002Foptimization-guide.md`.\n- **Custom start command:** if you need multiple shell steps, use a single shell form, e.g. **`\u002Fbin\u002Fsh -c 'set -e; .\u002Fmigrate && exec node server.js'`** (prefer **`exec`** so your app receives signals for graceful shutdown).\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fdockerfile-patterns.md` | Multi-stage templates (Node, Python, Go, Ruby, Rust, static sites) |\n| `references\u002Fregistry-setup.md` | Docker Hub, GHCR, ECR, Artifact Registry + Blueprint wiring |\n| `references\u002Foptimization-guide.md` | Layer order, `.dockerignore`, BuildKit cache mounts, debugging |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs Dashboard, operational steps\n- **render-blueprints** — Full `render.yaml` schema, wiring, and validation\n- **render-web-services** — Web service behavior, health checks, and HTTP edge cases\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","deployment","Any Render compute service (web, private, worker, cron) with runtime: docker or runtime: image.","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Frender-docker",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill render-docker",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill render-docker",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill render-docker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002FSKILL.md",true,[51,57,61,65],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",204,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdockerfile-patterns.md",5495,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002Freferences\u002Fdockerfile-patterns.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Foptimization-guide.md",3297,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002Freferences\u002Foptimization-guide.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fregistry-setup.md",3118,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-docker\u002Freferences\u002Fregistry-setup.md",[70,77,86,93,100,107],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\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},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\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":81,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]