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.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- dot-ai-changelog-fragmentSkill
- dot-ai-generate-cicdSkill
- dot-ai-generate-dockerfileSkill
- dot-ai-impact_analysisSkill
- dot-ai-manageKnowledgeSkill
- dot-ai-manageOrgDataSkill
- dot-ai-operateSkill
- dot-ai-prd-closeSkill
- dot-ai-prd-createSkill
- dot-ai-prd-doneSkill
- dot-ai-prd-fullSkill
- dot-ai-prd-nextSkill
- dot-ai-prds-getSkill
- dot-ai-prd-startSkill
- dot-ai-prd-update-decisionsSkill
- dot-ai-prd-update-progressSkill
- dot-ai-process-feature-requestSkill
- dot-ai-projectSetupSkill
- dot-ai-query-dot-aiSkill
- dot-ai-querySkill
- dot-ai-recommendSkill
- dot-ai-remediateSkill
- dot-ai-request-dot-ai-featureSkill
- dot-aiSkill
- dot-ai-tag-releaseSkill
- dot-ai-usersSkill
- dot-ai-versionSkill
- dot-ai-worktree-prdSkill
- dot-ai-write-docsSkill
- infographic-generatorSkill
- write-docsSkill
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
- Very specific: line 57
After publishing, consumers (like dot-ai-ui) can use:
- Distinctive: line 69
Run this skill when:
≈ “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.
Files
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 dockerif your user is not in thedockergroup) - Authenticated to ghcr.io. The simplest path is to reuse the
ghtoken (needswrite:packagesscope):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).
Set up a multi-arch builder (one-time per machine)
The default
dockerdriver cannot push a multi-platform manifest, and buildingarm64on anamd64host 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 --bootstrapBuild and push multi-arch Docker image
Tag both
latestand the current dot-ai release version (so downstream repos can pin to a contract version instead of a digest). Derive the version from the rootpackage.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-serverVerify 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:latestNote 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
latestplus an immutable version tag matching the dot-ai release (e.g.1.22.0).latestis 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)
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
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.

