Multica Artifact Backend

Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.

279 stars 33 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add it235/multica-best-practices --skill multica-artifact-backend
Manual install
git clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/en_US/skills/backend/multica-artifact-backend ~/.claude/skills/multica-artifact-backend

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Artifact · API Contract Sync

## Purpose

Land API contract artifacts to the team's unified API platform and let downstream (frontend / test) retrieve them via a stable reference.

> This skill decouples "platform integration" from "role prompt": the role prompt only says "produce API contract", not which platform. Changing companies (Swagger / Postman / YApi / internal gateway) means editing only this skill, not the @BackendDev prompt.

## Default platform: Apifox

- Output: API contract (endpoints, in/out params, error codes, auth, state-machine boundaries).
- Upload: maintain interface definitions in Apifox, export / sync, then use the **project / interface-group link** as the artifact reference.
- Retrieve: downstream @FrontendDev / @Tester read via the link — the link is the stable reference.

## Content spec (platform-independent part)

Per the stage convention, the API contract at least contains: endpoint list, request/response schema, error-code table, auth method, mapping to BR- business rules.

## Usage (role side writes only this line)

> @BackendDev: "Produce API contract, land it via `multica-artifact-backend` skill to the team API platform, and return the link."

## Swap platform (no role-prompt change)

Replace this skill's "default platform" section with your tool (Swagger / YApi / Postman / internal gateway), keeping the "upload + return stable link" interface unchanged.

## Why it works
Read the full skill on GitHub

Details

Skill name
multica-artifact-backend
Path
templates/en_US/skills/backend/multica-artifact-backend/SKILL.md
License
MIT
Repo updated
4 November 2026

FAQ

What does the Multica Artifact Backend skill do?

Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.

How do I install the Multica Artifact Backend skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-artifact-backend. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Multica Artifact Backend popular?

It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.