acquire-codebase-knowl…
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like…
Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project.
Claude Code
$ npx -y skills add github/awesome-copilot --skill containerize-aspnet-framework --agent claude-code
Codex
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a codex -y
Cursor
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a cursor -y
Gemini CLI
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a gemini-cli -y
GitHub Copilot
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a github-copilot -y
OpenCode
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a opencode -y
Windsurf
$ npx skills add github/awesome-copilot --skill containerize-aspnet-framework -a windsurf -y
name: containerize-aspnet-framework description: 'Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project.'
Containerize the ASP.NET (.NET Framework) project specified in the containerization settings below, focusing **exclusively** on changes required for the application to run in a Windows Docker container. Containerization should consider all settings specified here.
**REMEMBER:** This is a .NET Framework application, not .NET Core. The containerization process will be different from that of a .NET Core application.
This section of the prompt contains the specific settings and configurations required for containerizing the ASP.NET (.NET Framework) application. Prior to running this prompt, ensure that the settings are filled out with the necessary information. Note that in many cases, only the first few settings are required. Later settings can be left as defaults if they do not apply to the project being containerized.
Any settings that are not specified will be set to default values. The default values are provided in `[square brackets]`.
1. Project to containerize:
2. Windows Server SKU to use:
3. Windows Server version to use:
4. Custom base image for the build stage of the Docker image ("None" to use standard Microsoft base image):
5. Custom base image for the run stage of the Docker image ("None" to use standard Microsoft base image):
1. Ports that must be exposed in the container image:
2. User account the container should run as:
3. IIS settings that must be configured in the container image:
1. Custom build steps that must be performed before building the container image:
2. Custom build steps that must be performed after building the container image:
1. .NET assemblies that should be registered in the GAC in the container image:
2. MSIs that must be copied to the container image and installed:
3. COM components that must be registered in the container image:
1. Registry keys and values that must be added to the container image:
2. Environment variables that must be set in the container image:
3. Windows Server roles and features that must be installed in the container image:
1. Files/directories that need to be copied to the container image:
2. Files/directories to exclude from containerization:
1. Patterns to include in the `.dockerignore` file (.dockerignore will already have common defaults; these are additional patterns):
1. Health check endpoint:
2. Health check interval and timeout:
1. Other instructions that must be followed to containerize the project:
2. Known issues to address:
1. Review the containerization settings above to understand the containerization requirements 2. Create a `progress.md` file to track changes with check marks 3. Determine the .NET Framework version from the project's .csproj file by checking the `TargetFrameworkVersion` element 4. Select the appropriate Windows Server container image based on:
5. Ensure that required NuGet packages are installed. **DO NOT** install these if they are missing. If they are not installed, the user must install them manually. If they are not installed, pause executing this prompt and ask the user to install them using the Visual Studio NuGet Package Manager or Visual Studio package manager console. The following packages are require
A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like…
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps…
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default,…
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks,…
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like…
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…