agentleFS
vfarcicvfarcic/dot-ai/.claude/skills/publish-mock-server/SKILL.md

publish-mock-server

Skill336 starsChanged 10 months agoMITView on GitHub

Build and publish the mock-server Docker image to GitHub Container Registry. Use when mock server fixtures or code have changed and need to be published.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After publishing, consumers (like dot-ai-ui) can use:

    line 57
  2. Distinctive:

    Run this skill when:

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publish Mock Server

Build and publish the mock-server Docker image to ghcr.io/vfarcic/dot-ai-mock-server:latest.

Prerequisites

  • Docker is installed and running (use sudo docker if your user is not in the docker group)
  • Authenticated to ghcr.io. The simplest path is to reuse the gh token (needs write:packages scope):
    gh auth token | docker login ghcr.io -u vfarcic --password-stdin

Steps

Run all commands from the repository root. The build context is the mock-server/ directory (relative — do NOT hardcode an absolute path).

  1. Set up a multi-arch builder (one-time per machine)

    The default docker driver cannot push a multi-platform manifest, and building arm64 on an amd64 host needs QEMU. Register the emulator and create a container-driver builder:

    docker run --privileged --rm tonistiigi/binfmt --install arm64
    docker buildx create --name mockbuilder --driver docker-container --use --bootstrap
  2. Build and push multi-arch Docker image

    Tag both latest and the current dot-ai release version (so downstream repos can pin to a contract version instead of a digest). Derive the version from the root package.json:

    VERSION=$(node -p "require('./package.json').version")
    docker buildx build --builder mockbuilder \
      --platform linux/amd64,linux/arm64 \
      -t ghcr.io/vfarcic/dot-ai-mock-server:latest \
      -t ghcr.io/vfarcic/dot-ai-mock-server:$VERSION \
      --push mock-server
  3. Verify the push

    Confirm both tags resolve to the same digest and carry both platforms:

    docker buildx imagetools inspect ghcr.io/vfarcic/dot-ai-mock-server:latest

    Note the manifest-list digest (sha256:…) — downstream repos pin to it.

Usage

After publishing, consumers (like dot-ai-ui) can use:

services:
  mock-api:
    image: ghcr.io/vfarcic/dot-ai-mock-server:latest
    ports:
      - "3001:3001"

When to Publish

Run this skill when:

  • Fixtures are added or modified in mock-server/fixtures/
  • Mock server code changes (server.ts, routes.ts)
  • API schemas change that affect mock responses

Notes

  • Publishes latest plus an immutable version tag matching the dot-ai release (e.g. 1.22.0). latest is mutable; downstream repos should pin to the version tag or the digest for reproducible tests.
  • Publishing is manual (not wired into CI/release), so re-run this skill after merging any change that affects the mock contract — cutting a dot-ai release does NOT rebuild the image.
  • Image is ~230MB (Node.js alpine + fixtures)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.