harbor: Skill for Claude Code

Adding a New Service to Harbor

Subagent instruction: Before doing any work, read this skill file in full using the read_file tool at path /home/everlier/code/harbor/.agents/skills/new-service/SKILL.md. Do not proceed until the file has been read.

Harbor is a modular Docker Compose project. Each service is a self-contained unit: a compose file, a service directory, environment variables, app metadata, and documentation. The detailed technical reference lives in .github/copilot-new-service.md — consult it for edge cases or patterns not covered here.

Workflow Overview

Gather Info → Scaffold → Compose Config → Env Vars → Metadata → Documentation → Integrations → Test

Every step has validation criteria. Do not advance until the current step passes.

Step 0: Gather Information

Before writing any files, understand what you're building.

Required inputs:

• Service name or GitHub repo URL (from user)
• Docker deployment method: pre-built image, Dockerfile, or docker-compose in repo
• Service category: backend (inference), frontend (web UI), or satellite (tool/utility)
• Ports the service exposes internally
• Persistent data directories (volumes)
• Environment variables the service accepts

Research the repo. Look for:

• docker-compose.yml, Dockerfile, or docker/ directory
• README sections on Docker deployment, environment variables, configuration
• The service's default ports and data paths

If the repo has its own docker-compose, study the service definitions — you'll adapt them to Harbor's conventions, not copy them verbatim.

If ambiguous, ask the user. Don't guess the category or deployment method.

Step 1: Select a Handle

The handle is the service's identifier everywhere in Harbor.

Rules:

• Lowercase letters, numbers, hyphens only
• Short, memorable, representative
• Must be unique

Validate:

ls services/compose.${handle}.yml 2>/dev/null && echo "TAKEN" || echo "OK"
grep -q "\"${handle}\"\\|'${handle}'\\|${handle}:" app/src/serviceMetadata.ts && echo "TAKEN" || echo "OK"