[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71S8JDZV6TH4B7CX4VGV3SB":3,"skill-same:01M71S8JDZV6TH4B7CX4VGV3SB":105},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M71S8JDZV6TH4B7CX4VGV3SB","docker-best-practices",null,"Docker expert — image optimization, security hardening, multi-stage builds, orchestration, production deployment","HigorAlves\u002Forc","HigorAlves","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11262976?v=4","01M71S79EZEMHZ8PQSV0XQJHYY","Higor Alves","01M71S79FKKTCHCN1EDR8DSTWQ",7,"MIT","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"best practices","docker best practices","docker","multi","stage","use","container","deployment","Optimization","compose","security","2026","unknown","image","when","orchestration","writing","docker expert","expert","community","2026-11-10 13:02:02",false,"---\nname: docker-best-practices\ndescription: Docker expert — image optimization, security hardening, multi-stage builds, orchestration, production deployment\nwhen_to_use: Use when writing or reviewing Dockerfiles, Compose, or container deploys.\ncategory: devops\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Docker Expert\n\nAdvanced Docker containerization expertise: container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment based on current industry best practices.\n\n## When to use\n\nUse this skill when writing, optimizing, or reviewing Docker setups — Dockerfiles, `.dockerignore`, Docker Compose, multi-stage builds, image-size reduction, container security, resource limits, health checks, or production container deployment.\n\n## When NOT to use (recommend switching and stop)\n\nIf the issue requires ultra-specific expertise outside Docker, recommend switching and stop:\n\n- Kubernetes orchestration, pods, services, ingress → kubernetes-expert (future)\n- GitHub Actions CI\u002FCD with containers → github-actions-expert\n- AWS ECS\u002FFargate or cloud-specific container services → devops-expert\n- Database containerization with complex persistence → database-expert\n\nExample to output:\n\"This requires Kubernetes orchestration expertise. Please invoke: 'Use the kubernetes-expert subagent.' Stopping here.\"\n\n## Workflow\n\n1. **Analyze** the container setup comprehensively (environment detection, project structure, running containers). See `references\u002Fproduction-deploy.md`. Prefer internal tools (Read, Grep, Glob) over shell; shell is a fallback.\n2. **Identify** the specific problem category and complexity level (see the index below).\n3. **Apply** the appropriate solution strategy from the relevant reference file.\n4. **Validate** thoroughly (build, security scan, runtime, Compose config). See `references\u002Fproduction-deploy.md`.\n\nRead the relevant `references\u002F\u003Ctopic>.md` file when you need that detail — each file holds the patterns, code review checklist items, and diagnostics for that topic. For a partial task, load only the references you need.\n\n## Topic index\n\n| Topic | When you need it | Reference |\n|-------|------------------|-----------|\n| Multi-stage builds & layer caching | Optimizing Dockerfiles, dependency caching, cross-platform\u002Fbuildx, base image selection | `references\u002Fmultistage-builds.md` |\n| Image size optimization | Distroless, artifact selection, layer consolidation, shrinking large images | `references\u002Fimage-optimization.md` |\n| Security hardening | Non-root users, secrets management, build-time secrets, health checks, attack surface | `references\u002Fsecurity-hardening.md` |\n| Compose & dev workflow | Docker Compose orchestration, service deps, networks, volumes, hot-reload dev overrides | `references\u002Fcompose.md` |\n| Performance, resources & networking | Resource limits, restart policies, service discovery, networking issues, expert handoff | `references\u002Forchestration.md` |\n| Production deploy, validation & diagnostics | Environment detection, build\u002Fruntime\u002FCompose validation, full diagnostics catalog | `references\u002Fproduction-deploy.md` |\n\n## Core philosophy\n\nComprehensive Docker containerization with focus on practical optimization, security hardening, and production-ready patterns. Solutions emphasize performance, maintainability, and security best practices for modern container workflows.\n\n## Limitations\n\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Docker Expert\n\nAdvanced Docker containerization expertise: container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment based on current industry best practices.\n\n## When to use\n\nUse this skill when writing, optimizing, or reviewing Docker setups — Dockerfiles, `.dockerignore`, Docker Compose, multi-stage builds, image-size reduction, container security, resource limits, health checks, or production container deployment.\n\n## When NOT to use (recommend switching and stop)\n\nIf the issue requires ultra-specific expertise outside Docker, recommend switching and stop:\n\n- Kubernetes orchestration, pods, services, ingress → kubernetes-expert (future)\n- GitHub Actions CI\u002FCD with containers → github-actions-expert\n- AWS ECS\u002FFargate or cloud-specific container services → devops-expert\n- Database containerization with complex persistence → database-expert\n\nExample to output:\n\"This requires Kubernetes orchestration expertise. Please invoke: 'Use the kubernetes-expert subagent.' Stopping here.\"\n\n## Workflow\n\n1. **Analyze** the container setup comprehensively (environment detection, project structure, running containers). See `references\u002Fproduction-deploy.md`. Prefer internal tools (Read, Grep, Glob) over shell; shell is a fallback.\n2. **Identify** the specific problem category and complexity level (see the index below).\n3. **Apply** the appropriate solution strategy from the relevant reference file.\n4. **Validate** thoroughly (build, security scan, runtime, Compose config). See `references\u002Fproduction-deploy.md`.\n\nRead the relevant `references\u002F\u003Ctopic>.md` file when you need that detail — each file holds the patterns, code review checklist items, and diagnostics for that topic. For a partial task, load only the references you need.\n\n## Topic index\n\n| Topic | When you need it | Reference |\n|-------|------------------|-----------|\n| Multi-stage builds & layer caching | Optimizing Dockerfiles, dependency caching, cross-platform\u002Fbuildx, base image selection | `references\u002Fmultistage-builds.md` |\n| Image size optimization | Distroless, artifact selection, layer consolidation, shrinking large images | `references\u002Fimage-optimization.md` |\n| Security hardening | Non-root users, secrets management, build-time secrets, health checks, attack surface | `references\u002Fsecurity-hardening.md` |\n| Compose & dev workflow | Docker Compose orchestration, service deps, networks, volumes, hot-reload dev overrides | `references\u002Fcompose.md` |\n| Performance, resources & networking | Resource limits, restart policies, service discovery, networking issues, expert handoff | `references\u002Forchestration.md` |\n| Production deploy, validation & diagnostics | Environment detection, build\u002Fruntime\u002FCompose validation, full diagnostics catalog | `references\u002Fproduction-deploy.md` |\n\n## Core philosophy\n\nComprehensive Docker containerization with focus on practical optimization, security hardening, and production-ready patterns. Solutions emphasize performance, maintainability, and security best practices for modern container workflows.\n\n## Limitations\n\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":39,"source":46,"category":52,"date_added":53,"description":7,"when_to_use":54},"devops","2026-02-27","Use when writing or reviewing Dockerfiles, Compose, or container deploys.","main","7522fd7266944e30052204c2f6df287d8b5516be","codex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices",0,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc","https:\u002F\u002Forc.novacstack.com\u002F","https:\u002F\u002Fgithub.com\u002FHigorAlves","higoralves.dev","Software Engineering","2026-11-07 07:26:38",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add HigorAlves\u002Forc --skill docker-best-practices",{"tool":71,"command":72},"bunx","bunx skills add HigorAlves\u002Forc --skill docker-best-practices",{"tool":74,"command":75},"pnpm","pnpm dlx skills add HigorAlves\u002Forc --skill docker-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002FSKILL.md",true,[79,85,89,93,97,101],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fcompose.md","REFERENCE","参考文档",3392,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Fcompose.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fimage-optimization.md",1123,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Fimage-optimization.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fmultistage-builds.md",2430,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Fmultistage-builds.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Forchestration.md",2055,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Forchestration.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fproduction-deploy.md",2881,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Fproduction-deploy.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fsecurity-hardening.md",1874,"https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Fcodex\u002Forc\u002Fcontent\u002Fskills\u002Fdocker-best-practices\u002Freferences\u002Fsecurity-hardening.md",[106,141,165,186,208,228],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":123,"publishedAt":47},"01M71SW40F9TAAEDKBYYBCM814","writing-plans","Write a comprehensive implementation plan of bite-sized TDD tasks that an engineer with zero codebase context could execute — exact files, code, tests, and verification steps","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[112,115,120],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000036","内容创作者",[43,124,125,126,127,128,129,41,130,131,132,133,134,135,136,137,138,139,140,32],"writing plans","plans","engineer","superpowers","implementation plan","files","you","code","tasks","verification","plan","write","steps","context","ZeRO","for","tests",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":47},"01M71SW15KHE4MHJW9NEXV65X2","writing-for-agents","orc's doctrine layer for writing any document an agent consumes — skills, AGENTS.md\u002FCLAUDE.md, reference docs","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[147,148,149],{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":121,"categoryName":122,"taxonomyType":118,"taxonomyTypeDesc":119},[151,43,139,152,41,153,154,155,156,157,158,159,32,160,161,162,163,164],"writing for agents","matt pocock","inline","tuning","a skill","layer","doctrine","push","editing","document","github","https","reference","docs",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":47},"01M71SVYQKXT743HHHWGHT3G13","workspace-mode","Use when cwd is a parent dir holding multiple sibling git repos — defines repo auto-detection, --repos\u002F--repo\u002F--all-repos\u002F--this-repo precedence, per-repo dispatch, and linked-PR mechanics.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fworkspace-mode\u002FSKILL.md",[171],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,175,176,177,41,178,179,180,181,32,182,183,184,185],"workspace mode","mode","workspace","mechanics","auto","repos","git","pr","repo","dispatch","auto-detection","detection","parent",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":47},"01M71SVVP3BXS06G9395P2K0RH","wizard","Generate an interactive bash wizard walking a human through work only they can perform — credentials, secrets, one-off migrations","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwizard\u002FSKILL.md",[192],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[188,194,195,196,197,152,41,198,199,200,201,202,203,136,204,205,139,32,206,207],"condition","never","provisioning infrastructure","only","Bash","work","credentials","generate","human","secrets","infrastructure","do","one","interactive",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":47},"01M71SVT4AR6NKAM5B077E7QSJ","wait-what","Stop and re-pitch — the last message did not land; say it again simply, in the project's own vocabulary.","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[215,216,217,218,219,152,220,221,222,223,161,162,224,225,226,227],"wait what","wait","project","re","true","pitch","last","say","message","land","it","stop","vocabulary",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":238,"publishedAt":47},"01M71SVQVYRA9QBQ6G8MWR8G6F","vitest","Vitest fast unit testing framework powered by Vite with Jest-compatible API","https:\u002F\u002Fgithub.com\u002FHigorAlves\u002Forc\u002Fblob\u002Fmain\u002Forc\u002Fskills\u002Fvitest\u002FSKILL.md",[234,237],{"categoryNo":235,"categoryName":236,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[230,239,240,241,242,243,43,41,244,245,38,246,247,248,249,250,251,252,140,253],"coverage","unit","testing","testing framework","generated","api","jest","at","scripts","unit testing","antfu","framework","vite","mocking","dev"]