OpenSkillIndex← back to search
claude-codedevelopment

Claude-skill-registry fusion-api

Design and compare alternative API shapes; use when deciding on endpoints, request or response formats, or versioning.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/fusion-api" ~/.claude/skills/majiayu000-claude-skill-registry-fusion-api && rm -rf "$T"
manifest: skills/data/fusion-api/SKILL.md
tags
#api-design#endpoint-creation#versioning#format-comparison
source content

Fusion API

Overview

Use an F-thread: three workers in separate worktrees propose competing API designs. The queen evaluates ergonomics and tradeoffs.

Inputs

  • API description and constraints

Workflow

  1. Verify 
    git
    and 
    mprocs
    .
  2. Create session variables and worktrees.
  3. Write 
    tasks.json
    , worker prompts, and queen prompt.
  4. Launch mprocs.

Worktree Commands

git worktree add "{WORKTREE_ROOT}/impl-a" -b fusion/{SESSION_ID}/impl-a
git worktree add "{WORKTREE_ROOT}/impl-b" -b fusion/{SESSION_ID}/impl-b
git worktree add "{WORKTREE_ROOT}/impl-c" -b fusion/{SESSION_ID}/impl-c

Worker Prompt Outline

  • Worker A: REST-first, simple endpoints
  • Worker B: resource-oriented with versioning
  • Worker C: alternative (GraphQL or RPC-style)

Queen Prompt Outline

  • Compare consistency, usability, versioning, and backward compatibility

mprocs Launch

mprocs --config .hive/mprocs.yaml

Output

  • API design comparison and chosen spec