[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADWA3BJYWGJAM9VP6E64JH":3,"skill-same:01M6ADWA3BJYWGJAM9VP6E64JH":57},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6ADWA3BJYWGJAM9VP6E64JH","multi-stage-dockerfile",null,"Create optimized multi-stage Dockerfiles for any language or framework","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmulti-stage-dockerfile\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"dockerfile","multi stage dockerfile","stage","multi","create","framework","dockerfiles","language","for","2026-11-10 10:12:30",false,"---\nname: multi-stage-dockerfile\ndescription: 'Create optimized multi-stage Dockerfiles for any language or framework'\n---\n\nYour goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.\n\n## Multi-Stage Structure\n\n- Use a builder stage for compilation, dependency installation, and other build-time operations\n- Use a separate runtime stage that only includes what's needed to run the application\n- Copy only the necessary artifacts from the builder stage to the runtime stage\n- Use meaningful stage names with the `AS` keyword (e.g., `FROM node:18 AS builder`)\n- Place stages in logical order: dependencies → build → test → runtime\n\n## Base Images\n\n- Start with official, minimal base images when possible\n- Specify exact version tags to ensure reproducible builds (e.g., `python:3.11-slim` not just `python`)\n- Consider distroless images for runtime stages where appropriate\n- Use Alpine-based images for smaller footprints when compatible with your application\n- Ensure the runtime image has the minimal necessary dependencies\n\n## Layer Optimization\n\n- Organize commands to maximize layer caching\n- Place commands that change frequently (like code changes) after commands that change less frequently (like dependency installation)\n- Use `.dockerignore` to prevent unnecessary files from being included in the build context\n- Combine related RUN commands with `&&` to reduce layer count\n- Consider using COPY --chown to set permissions in one step\n\n## Security Practices\n\n- Avoid running containers as root - use `USER` instruction to specify a non-root user\n- Remove build tools and unnecessary packages from the final image\n- Scan the final image for vulnerabilities\n- Set restrictive file permissions\n- Use multi-stage builds to avoid including build secrets in the final image\n\n## Performance Considerations\n\n- Use build arguments for configuration that might change between environments\n- Leverage build cache efficiently by ordering layers from least to most frequently changing\n- Consider parallelization in build steps when possible\n- Set appropriate environment variables like NODE_ENV=production to optimize runtime behavior\n- Use appropriate healthchecks for the application type with the HEALTHCHECK instruction\n","Your goal is to help me create efficient multi-stage Dockerfiles that follow best practices, resulting in smaller, more secure container images.\n\n## Multi-Stage Structure\n\n- Use a builder stage for compilation, dependency installation, and other build-time operations\n- Use a separate runtime stage that only includes what's needed to run the application\n- Copy only the necessary artifacts from the builder stage to the runtime stage\n- Use meaningful stage names with the `AS` keyword (e.g., `FROM node:18 AS builder`)\n- Place stages in logical order: dependencies → build → test → runtime\n\n## Base Images\n\n- Start with official, minimal base images when possible\n- Specify exact version tags to ensure reproducible builds (e.g., `python:3.11-slim` not just `python`)\n- Consider distroless images for runtime stages where appropriate\n- Use Alpine-based images for smaller footprints when compatible with your application\n- Ensure the runtime image has the minimal necessary dependencies\n\n## Layer Optimization\n\n- Organize commands to maximize layer caching\n- Place commands that change frequently (like code changes) after commands that change less frequently (like dependency installation)\n- Use `.dockerignore` to prevent unnecessary files from being included in the build context\n- Combine related RUN commands with `&&` to reduce layer count\n- Consider using COPY --chown to set permissions in one step\n\n## Security Practices\n\n- Avoid running containers as root - use `USER` instruction to specify a non-root user\n- Remove build tools and unnecessary packages from the final image\n- Scan the final image for vulnerabilities\n- Set restrictive file permissions\n- Use multi-stage builds to avoid including build secrets in the final image\n\n## Performance Considerations\n\n- Use build arguments for configuration that might change between environments\n- Leverage build cache efficiently by ordering layers from least to most frequently changing\n- Consider parallelization in build steps when possible\n- Set appropriate environment variables like NODE_ENV=production to optimize runtime behavior\n- Use appropriate healthchecks for the application type with the HEALTHCHECK instruction\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fmulti-stage-dockerfile",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add github\u002Fawesome-copilot --skill multi-stage-dockerfile",{"tool":49,"command":50},"bunx","bunx skills add github\u002Fawesome-copilot --skill multi-stage-dockerfile",{"tool":52,"command":53},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill multi-stage-dockerfile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fmulti-stage-dockerfile\u002FSKILL.md",true,[],[58,93,120,150,184,201],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":72,"publishedAt":28},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[64,69],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":70,"categoryName":71,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000023","Skill与智能体开发",[73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"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":100,"publishedAt":28},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[99],{"categoryNo":70,"categoryName":71,"taxonomyType":67,"taxonomyTypeDesc":68},[101,102,103,104,105,106,27,107,108,109,110,111,112,113,114,115,116,117,118,119],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":132,"publishedAt":28},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[133,134,135,136,137,138,27,77,139,140,141,142,143,144,145,89,146,147,148,149],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":161,"publishedAt":28},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[157,160],{"categoryNo":158,"categoryName":159,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},[162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,78,177,178,179,180,181,27,182,183],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":188,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":197,"publishedAt":28},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[192,193,196],{"categoryNo":158,"categoryName":159,"taxonomyType":67,"taxonomyTypeDesc":68},{"categoryNo":194,"categoryName":195,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":70,"categoryName":71,"taxonomyType":67,"taxonomyTypeDesc":68},[198,104,171,199,200],"resemble detect","https","identity",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":188,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":212,"publishedAt":28},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":70,"categoryName":71,"taxonomyType":67,"taxonomyTypeDesc":68},[213,214,215,216,134,79,9,103,217,218,199,219,220,221,222,223,224,225,226,227,228,229,87,230,231,232,233],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]