archon-docker-extend

Create gitignored Dockerfile.user and docker-compose.override.yml for personal Docker customization.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-docker-extend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archon-docker-extend
Source: https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI/tree/main/payload/claw-code/.claw/skills/archon-docker-extend
Command: npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-docker-extend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users extend Docker with personal tools and configurations without touching maintainer files or committing user-specific changes to Git.

Core Features & Use Cases

  • Interactive setup of Dockerfile.user and docker-compose.override.yml to keep personal changes local and gitignored.
  • Context-aware detection to distinguish DEV_MODE (root) and DEPLOY_MODE (deploy/) and apply overrides in the correct location.
  • Step-by-step guidance to copy example files, add tools, and rebuild the environment for your workflow.

Quick Start

Run archon-docker-extend to begin interactive Docker personalization.

Frequently Asked Questions about archon-docker-extend

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

FAQPage Schema
How do I customize Docker with personal tools without modifying maintainer files?

To customize Docker without touching maintainer files, you can use gitignored Dockerfile.user and docker-compose.override.yml files to keep personal changes local and separate from the main repository.

What is the best way to add personal configurations to a Docker environment?

The best way to add personal configurations is setting up a Dockerfile.user and docker-compose.override.yml, which are automatically gitignored to preserve repository integrity while applying your custom tools.

How do I apply Docker overrides differently in development and deployment contexts?

To apply Docker overrides correctly, the system detects DEV_MODE in the root directory and DEPLOY_MODE in the deploy/ directory, ensuring configurations are applied in the correct location for each context.

Can I add tools to my Docker environment without committing user-specific changes to Git?

Yes, you can add tools without committing to Git by using a Dockerfile.user which is automatically gitignored, allowing you to install personal tools while keeping the repository history clean.

What are the steps to set up a personalized Docker compose override?

Setting up a personalized Docker compose override involves copying example files, interactively adding your desired tools to the override configuration, and then rebuilding the environment to apply the changes step by step.

Why does my Docker compose override not work in the deploy directory?

Your Docker compose override may not work in the deploy directory if context detection fails to identify DEPLOY_MODE in the deploy/ layout, which is required to apply overrides correctly instead of the root DEV_MODE layout.