[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FETKTXRQPNRCBFASE1FP06":3,"skill-same:01M7FETKTXRQPNRCBFASE1FP06":89},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FETKTXRQPNRCBFASE1FP06","docker-compose-patterns",null,"Use this skill when creating, modifying, or debugging Docker Compose configurations, even if the user just says they need to wire services together, add a database to their stack, or set up a local development environment with multiple containers. Covers service definitions, health checks, dependency ordering, volumes, networks, environment variables, and development overrides.","heynemann\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: docker-compose-patterns\ndescription: Use this skill when creating, modifying, or debugging Docker Compose configurations, even if the user just says they need to wire services together, add a database to their stack, or set up a local development environment with multiple containers. Covers service definitions, health checks, dependency ordering, volumes, networks, environment variables, and development overrides.\nlicense: Apache-2.0\ncompatibility: Requires Docker Compose v2 (compose.yaml format).\n---\n\n# Docker Compose Patterns\n\n## Overview\n\nThis skill provides rules for creating, reviewing, and debugging Docker Compose configurations. Use it when the main artifact is `compose.yaml` or `compose.override.yaml` and the task is about service wiring rather than image-build internals.\n\n## When to use this skill\n\nActivate this skill when:\n\n- Creating a new `compose.yaml` for a project\n- Adding or modifying services in an existing Compose file\n- Setting up development overrides with `compose.override.yaml`\n- Debugging service startup ordering or connectivity issues\n\n## Do not use this skill when\n\nDo not use this skill when:\n\n- The project has no Docker setup yet and the main need is an initial scaffold\n- The main task is writing or optimizing a `Dockerfile`\n- The main task is improving build caching, image size, or runtime user configuration\n\n## Core guidance\n\n### File naming\n\nUse `compose.yaml` as the canonical filename. Do not use `docker-compose.yml` or `docker-compose.yaml` — those are legacy names.\n\n### Service definitions\n\n- Give services clear, lowercase names that reflect their role: `web`, `db`, `cache`, `worker`.\n- Always pin image tags to a specific version. Never use `latest` or omit the tag.\n- Set `restart: unless-stopped` for long-running infrastructure services and non-development deployments.\n- Add `container_name` only when external tools need a predictable name. Otherwise, let Compose generate names.\n\n### Dependency modeling\n\n- Use `depends_on` with `condition: service_healthy` for services that must be ready before dependents start.\n- Every service listed in `depends_on` with a health condition must have a `healthcheck` defined.\n- Do not rely on `depends_on` without conditions — it only guarantees container start, not readiness.\n\n### Health checks\n\n- Always add a `healthcheck` to database services (Postgres, MySQL, Redis, MongoDB).\n- Use the service's native client tool for health checks when available (e.g., `pg_isready`, `redis-cli ping`, `mysqladmin ping`).\n- Set reasonable `interval`, `timeout`, `retries`, and `start_period` values. Start with: `interval: 5s`, `timeout: 3s`, `retries: 3`, `start_period: 10s`.\n\n#### Health checks for distroless or scratch images\n\nDistroless, scratch-based, and hardened images contain no shell, curl, or wget. Do not bake tools into these images — that defeats their purpose. Instead, use a **healthcheck sidecar** that shares the application's network namespace:\n\n```yaml\nservices:\n  api:\n    build:\n      context: .\n      target: runtime          # distroless \u002F hardened image\n    ports:\n      - \"8080:8080\"\n    # No healthcheck here — the image has no tools to run one\n\n  api-health:\n    image: curlimages\u002Fcurl:8.22.0\n    network_mode: \"service:api\"   # shares api's localhost\n    entrypoint: [\"sleep\", \"infinity\"]  # keep sidecar alive for healthcheck\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 30s\n      timeout: 5s\n      retries: 3\n      start_period: 45s\n    deploy:\n      resources:\n        limits:\n          memory: 32M\n```\n\nKey points:\n- The sidecar must stay alive with `entrypoint: [\"sleep\", \"infinity\"]` so Compose can execute the healthcheck inside it.\n- `network_mode: \"service:api\"` makes `localhost` inside the sidecar resolve to the api container's loopback — no extra networking needed.\n- Keep the sidecar lightweight with a resource limit (32MB is sufficient for curl).\n- Services that depend on `api` being ready should reference the **sidecar**, not the api directly:\n\n```yaml\n  worker:\n    depends_on:\n      api-health:\n        condition: service_healthy\n```\n\n### Volumes\n\n- Use named volumes for data that must persist across container recreations (database data, uploaded files).\n- Use bind mounts only for development-time source code syncing.\n- Define all named volumes in the top-level `volumes:` key.\n- Do not mount the Docker socket unless the service genuinely requires it.\n\n### Networks\n\n- For single-application stacks, the default network is sufficient. Do not create custom networks unless you need isolation between service groups.\n- When creating custom networks, prefer bridge driver and give networks descriptive names.\n- Use the top-level `networks:` key to define all custom networks.\n\n### Environment variables\n\n- Use `environment:` for non-sensitive values that are few in number.\n- Use `env_file:` pointing to a `.env` file for longer lists of variables.\n- Never hardcode secrets (passwords, API keys) directly in `compose.yaml`. Use `env_file:` or Docker secrets.\n- When defaults are needed in the `environment:` block for local development, use variable substitution with fallbacks: `${DB_PASSWORD:-postgres}`. Never write bare plaintext values for password fields.\n- Add `.env` to `.gitignore`.\n\n### Development overrides\n\n- Use `compose.override.yaml` for development-only settings. Compose loads it automatically alongside `compose.yaml`.\n- Put bind mounts for source code, debug ports, and development environment variables in the override file.\n- Use `develop.watch` for file-syncing and auto-rebuild in development when supported.\n- Keep production-oriented settings in the base `compose.yaml` and override only what changes for development.\n\n### Compose Watch\n\n- Prefer `develop.watch` over manual bind mounts for development workflows.\n- Use `action: sync` for files that should be copied into the container on change (source code).\n- Use `action: rebuild` for files that require a full image rebuild (dependency files like `package.json`, `requirements.txt`).\n- Use `action: sync+restart` for configuration files that need a process restart.\n\n### Destructive commands\n\nSome Compose commands delete data irreversibly. Before running any of the following, state exactly which data will be deleted and get explicit confirmation from the user — do not run them as a side effect of debugging, restarting, or \"cleaning up\" a stack:\n\n- `docker compose down -v` \u002F `docker compose down --volumes` — deletes named volumes, including database data.\n- `docker volume rm` \u002F `docker volume prune` run against a Compose project's volumes — deletes volumes directly. For the standalone case (no Compose project in play), see `docker-destructive-guardrails` instead. A volume referenced via `external: true` isn't managed by the Compose project either (`down -v` won't touch it) — treat it as the standalone case too: run `docker volume rm` without `-f` first, and get explicit confirmation before deleting it.\n- `docker compose rm -v` — deletes anonymous volumes attached to removed containers.\n\nIf the goal is only to restart services or reclaim containers\u002Fnetworks, use `docker compose down` (no `-v`) or `docker compose restart` instead — these leave named volumes intact.\n\n## Related skills\n\n- For first-time Docker project scaffolding and baseline file creation, use `docker-project-foundations`.\n- For Dockerfile internals, build caching, multi-stage builds, and `.dockerignore`, use `docker-build-strategies`.\n- For destructive Docker CLI commands outside Compose (`docker system prune`, `docker rm -f`, image\u002Fnetwork\u002Fbuilder pruning, standalone volume deletion) and a cross-product index of destructive-command guardrails, use `docker-destructive-guardrails`.\n\n## References\n\n- `references\u002Fservice-dependencies.md` — Detailed guidance on `depends_on`, health check patterns for common databases, and startup ordering strategies.\n- `references\u002Fvolumes-and-networks.md` — Patterns for volume mounts, named volumes, bind mounts, and network configuration.\n\n## Assets\n\n- `assets\u002Fcompose-web-app.yaml` — Complete multi-service web app (app + Postgres + Redis) with health checks, dependencies, and named volumes.\n- `assets\u002Fcompose-dev-override.yaml` — Development override showing bind mounts, debug ports, and Compose Watch configuration.\n- `assets\u002Fbad-vs-good.md` — Before\u002Fafter comparisons of common Compose mistakes and their fixes.\n\n## Scripts\n\n- **`scripts\u002Fverify-compose.sh`** — Validates the Compose project in the current directory with `docker compose config --quiet`, without printing resolved configuration. Run it from the project root (the directory that contains `compose.yaml`), with the script path resolved under this skill's directory:\n  ```bash\n  bash \"\u003Cskill-dir>\u002Fscripts\u002Fverify-compose.sh\" [--help]\n  ```\n  Replace `\u003Cskill-dir>` with the absolute path of the folder that contains this `SKILL.md`; the `scripts\u002F` path is relative to that folder, not to the project. Do not change into the skill directory first: the script validates whatever Compose project is in the current directory. If the skill directory cannot be resolved, run `docker compose config --quiet` directly. Exit status is `0` when the Compose configuration is valid or help is requested, the non-zero status from `docker compose config --quiet` when validation fails, and `2` for invalid arguments. Plain `docker compose config` can expose interpolated and `env_file` credentials in tool output or logs; use quiet validation by default. Compose warnings and errors are still emitted and may contain sensitive details.\n\n## Checks\n\n- `checks\u002Fverification.md` — Detailed verification runbook for manual review.\n","# Docker Compose Patterns\n\n## Overview\n\nThis skill provides rules for creating, reviewing, and debugging Docker Compose configurations. Use it when the main artifact is `compose.yaml` or `compose.override.yaml` and the task is about service wiring rather than image-build internals.\n\n## When to use this skill\n\nActivate this skill when:\n\n- Creating a new `compose.yaml` for a project\n- Adding or modifying services in an existing Compose file\n- Setting up development overrides with `compose.override.yaml`\n- Debugging service startup ordering or connectivity issues\n\n## Do not use this skill when\n\nDo not use this skill when:\n\n- The project has no Docker setup yet and the main need is an initial scaffold\n- The main task is writing or optimizing a `Dockerfile`\n- The main task is improving build caching, image size, or runtime user configuration\n\n## Core guidance\n\n### File naming\n\nUse `compose.yaml` as the canonical filename. Do not use `docker-compose.yml` or `docker-compose.yaml` — those are legacy names.\n\n### Service definitions\n\n- Give services clear, lowercase names that reflect their role: `web`, `db`, `cache`, `worker`.\n- Always pin image tags to a specific version. Never use `latest` or omit the tag.\n- Set `restart: unless-stopped` for long-running infrastructure services and non-development deployments.\n- Add `container_name` only when external tools need a predictable name. Otherwise, let Compose generate names.\n\n### Dependency modeling\n\n- Use `depends_on` with `condition: service_healthy` for services that must be ready before dependents start.\n- Every service listed in `depends_on` with a health condition must have a `healthcheck` defined.\n- Do not rely on `depends_on` without conditions — it only guarantees container start, not readiness.\n\n### Health checks\n\n- Always add a `healthcheck` to database services (Postgres, MySQL, Redis, MongoDB).\n- Use the service's native client tool for health checks when available (e.g., `pg_isready`, `redis-cli ping`, `mysqladmin ping`).\n- Set reasonable `interval`, `timeout`, `retries`, and `start_period` values. Start with: `interval: 5s`, `timeout: 3s`, `retries: 3`, `start_period: 10s`.\n\n#### Health checks for distroless or scratch images\n\nDistroless, scratch-based, and hardened images contain no shell, curl, or wget. Do not bake tools into these images — that defeats their purpose. Instead, use a **healthcheck sidecar** that shares the application's network namespace:\n\n```yaml\nservices:\n  api:\n    build:\n      context: .\n      target: runtime          # distroless \u002F hardened image\n    ports:\n      - \"8080:8080\"\n    # No healthcheck here — the image has no tools to run one\n\n  api-health:\n    image: curlimages\u002Fcurl:8.22.0\n    network_mode: \"service:api\"   # shares api's localhost\n    entrypoint: [\"sleep\", \"infinity\"]  # keep sidecar alive for healthcheck\n    healthcheck:\n      test: [\"CMD\", \"curl\", \"-f\", \"http:\u002F\u002Flocalhost:8080\u002Fhealth\"]\n      interval: 30s\n      timeout: 5s\n      retries: 3\n      start_period: 45s\n    deploy:\n      resources:\n        limits:\n          memory: 32M\n```\n\nKey points:\n- The sidecar must stay alive with `entrypoint: [\"sleep\", \"infinity\"]` so Compose can execute the healthcheck inside it.\n- `network_mode: \"service:api\"` makes `localhost` inside the sidecar resolve to the api container's loopback — no extra networking needed.\n- Keep the sidecar lightweight with a resource limit (32MB is sufficient for curl).\n- Services that depend on `api` being ready should reference the **sidecar**, not the api directly:\n\n```yaml\n  worker:\n    depends_on:\n      api-health:\n        condition: service_healthy\n```\n\n### Volumes\n\n- Use named volumes for data that must persist across container recreations (database data, uploaded files).\n- Use bind mounts only for development-time source code syncing.\n- Define all named volumes in the top-level `volumes:` key.\n- Do not mount the Docker socket unless the service genuinely requires it.\n\n### Networks\n\n- For single-application stacks, the default network is sufficient. Do not create custom networks unless you need isolation between service groups.\n- When creating custom networks, prefer bridge driver and give networks descriptive names.\n- Use the top-level `networks:` key to define all custom networks.\n\n### Environment variables\n\n- Use `environment:` for non-sensitive values that are few in number.\n- Use `env_file:` pointing to a `.env` file for longer lists of variables.\n- Never hardcode secrets (passwords, API keys) directly in `compose.yaml`. Use `env_file:` or Docker secrets.\n- When defaults are needed in the `environment:` block for local development, use variable substitution with fallbacks: `${DB_PASSWORD:-postgres}`. Never write bare plaintext values for password fields.\n- Add `.env` to `.gitignore`.\n\n### Development overrides\n\n- Use `compose.override.yaml` for development-only settings. Compose loads it automatically alongside `compose.yaml`.\n- Put bind mounts for source code, debug ports, and development environment variables in the override file.\n- Use `develop.watch` for file-syncing and auto-rebuild in development when supported.\n- Keep production-oriented settings in the base `compose.yaml` and override only what changes for development.\n\n### Compose Watch\n\n- Prefer `develop.watch` over manual bind mounts for development workflows.\n- Use `action: sync` for files that should be copied into the container on change (source code).\n- Use `action: rebuild` for files that require a full image rebuild (dependency files like `package.json`, `requirements.txt`).\n- Use `action: sync+restart` for configuration files that need a process restart.\n\n### Destructive commands\n\nSome Compose commands delete data irreversibly. Before running any of the following, state exactly which data will be deleted and get explicit confirmation from the user — do not run them as a side effect of debugging, restarting, or \"cleaning up\" a stack:\n\n- `docker compose down -v` \u002F `docker compose down --volumes` — deletes named volumes, including database data.\n- `docker volume rm` \u002F `docker volume prune` run against a Compose project's volumes — deletes volumes directly. For the standalone case (no Compose project in play), see `docker-destructive-guardrails` instead. A volume referenced via `external: true` isn't managed by the Compose project either (`down -v` won't touch it) — treat it as the standalone case too: run `docker volume rm` without `-f` first, and get explicit confirmation before deleting it.\n- `docker compose rm -v` — deletes anonymous volumes attached to removed containers.\n\nIf the goal is only to restart services or reclaim containers\u002Fnetworks, use `docker compose down` (no `-v`) or `docker compose restart` instead — these leave named volumes intact.\n\n## Related skills\n\n- For first-time Docker project scaffolding and baseline file creation, use `docker-project-foundations`.\n- For Dockerfile internals, build caching, multi-stage builds, and `.dockerignore`, use `docker-build-strategies`.\n- For destructive Docker CLI commands outside Compose (`docker system prune`, `docker rm -f`, image\u002Fnetwork\u002Fbuilder pruning, standalone volume deletion) and a cross-product index of destructive-command guardrails, use `docker-destructive-guardrails`.\n\n## References\n\n- `references\u002Fservice-dependencies.md` — Detailed guidance on `depends_on`, health check patterns for common databases, and startup ordering strategies.\n- `references\u002Fvolumes-and-networks.md` — Patterns for volume mounts, named volumes, bind mounts, and network configuration.\n\n## Assets\n\n- `assets\u002Fcompose-web-app.yaml` — Complete multi-service web app (app + Postgres + Redis) with health checks, dependencies, and named volumes.\n- `assets\u002Fcompose-dev-override.yaml` — Development override showing bind mounts, debug ports, and Compose Watch configuration.\n- `assets\u002Fbad-vs-good.md` — Before\u002Fafter comparisons of common Compose mistakes and their fixes.\n\n## Scripts\n\n- **`scripts\u002Fverify-compose.sh`** — Validates the Compose project in the current directory with `docker compose config --quiet`, without printing resolved configuration. Run it from the project root (the directory that contains `compose.yaml`), with the script path resolved under this skill's directory:\n  ```bash\n  bash \"\u003Cskill-dir>\u002Fscripts\u002Fverify-compose.sh\" [--help]\n  ```\n  Replace `\u003Cskill-dir>` with the absolute path of the folder that contains this `SKILL.md`; the `scripts\u002F` path is relative to that folder, not to the project. Do not change into the skill directory first: the script validates whatever Compose project is in the current directory. If the skill directory cannot be resolved, run `docker compose config --quiet` directly. Exit status is `0` when the Compose configuration is valid or help is requested, the non-zero status from `docker compose config --quiet` when validation fails, and `2` for invalid arguments. Plain `docker compose config` can expose interpolated and `env_file` credentials in tool output or logs; use quiet validation by default. Compose warnings and errors are still emitted and may contain sensitive details.\n\n## Checks\n\n- `checks\u002Fverification.md` — Detailed verification runbook for manual review.\n",{"name":5,"license":15,"description":7,"compatibility":24},"Requires Docker Compose v2 (compose.yaml format).","main","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill docker-compose-patterns",{"tool":39,"command":40},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill docker-compose-patterns",{"tool":42,"command":43},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill docker-compose-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002FSKILL.md",true,[47,53,59,63,67,71,75,79,85],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fbad-vs-good.md","ASSET","资产文件",2841,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fassets\u002Fbad-vs-good.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fcompose-dev-override.yaml",858,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fassets\u002Fcompose-dev-override.yaml",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Fcompose-web-app.yaml",1127,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fassets\u002Fcompose-web-app.yaml",{"path":68,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":69,"sourceHtmlUrl":70},"checks\u002Fverification.md",3830,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fchecks\u002Fverification.md",{"path":72,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fservice-dependencies.md",2829,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Freferences\u002Fservice-dependencies.md",{"path":76,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fvolumes-and-networks.md",3522,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Freferences\u002Fvolumes-and-networks.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fverify-compose.sh","SCRIPT","脚本",672,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fscripts\u002Fverify-compose.sh",{"path":86,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":87,"sourceHtmlUrl":88},"skill.yaml",848,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fdocker-compose-patterns\u002Fskill.yaml",[90,98,105,112,119,126],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]