Command catalog for humans building the split-payments product.

Slacker-style commands for reading docs, integrating games, connecting marketplaces, designing split rules and checking deploys. If we later build a real Slack app, these commands become the first slash-command map.

Test game.integrate Test marketplace.integrate Test split.design Slack API docs

split.design

Design a split-payment rule.

Goal

Define who gets sats, when, and how errors are handled.

Read First

  • SPLIT_PAYMENTS_PRODUCT.md
  • FUNCTION_CATALOG.md

Steps

  • Define gross source.
  • Define platform fee.
  • Define destinations.
  • Ensure amounts fit gross.
  • Define retry behavior.

Acceptance Checks

  • Every split has role, rule, destination and status.

CLI

php spark product:slacker split.design

Slack Or Slacker?

The current implementation is Slacker-style: a human command catalog and Spark CLI command. Slack's own platform provides Web API, Events API, Status API and app tooling. If we want this inside Slack later, these commands can become slash commands or Slack app actions.

Open Slack API docs Open command JSON