build-publish

Build and publish the Feirb .NET application as container images for NAS deployment.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/mamu7211/feirb-mailclient --skill build-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-publish
Source: https://github.com/mamu7211/feirb-mailclient/tree/main/.claude/skills/build-publish
Command: npx skills add https://github.com/mamu7211/feirb-mailclient --skill build-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the complex process of building and packaging the Feirb mail client, ensuring consistent deployment artifacts for NAS environments.

Core Features & Use Cases

  • Automated Builds: Compiles the .NET solution into a production-ready state.
  • Container Packaging: Generates Docker images via .NET Aspire for simplified deployment.
  • Use Case: Use this skill to prepare the application for a production release on your NAS, ensuring all dependencies are correctly bundled and the output is ready for containerization.

Quick Start

Execute the build and publish command to generate the production-ready application artifacts in the local output directory.

Frequently Asked Questions about build-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a .NET Aspire build for NAS deployment?

To automate a .NET Aspire build for NAS deployment, this skill compiles the Feirb .NET solution and generates Docker container images, creating production-ready artifacts in your local output directory.

Do I need the .NET 10 SDK and Docker installed to publish my application?

Yes, you need the .NET 10 SDK and Docker installed on your host machine. These prerequisites are required to compile the solution and generate the container images via .NET Aspire.

What is the best way to package a .NET application into a Docker image for a NAS system?

Packaging a .NET application for a NAS system is handled by compiling the solution into a production-ready state and using .NET Aspire to generate Docker images, ensuring all dependencies are bundled.

How does container packaging work with .NET Aspire for production releases?

Container packaging with .NET Aspire works by compiling the Feirb .NET application into a production-ready state and generating Docker images, which simplifies deployment on NAS environments by bundling dependencies correctly.

Can I use this build process if I don't have Docker installed on my host machine?

No, Docker is explicitly required on the host machine. Without Docker, the skill cannot generate the container images needed to package the .NET application for NAS deployment.

Why does my .NET application deployment fail on my NAS without containerization?

Deployment may fail because dependencies are not bundled. Generating Docker images via .NET Aspire ensures all dependencies are correctly bundled, providing consistent deployment artifacts for NAS environments.