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

game.integrate

Connect a standalone browser game.

Goal

Make a standalone game use config, payments, sessions, scores and leaderboards.

Read First

  • STANDALONE_GAME_INTEGRATION.md
  • API.md
  • FUNCTION_CATALOG.md

Steps

  • Register game config.
  • Add NoderunnersArcadeClient.
  • Fetch config and leaderboard.
  • Create payment for paid games.
  • Start session.
  • Submit score.

Acceptance Checks

  • Free game can submit score.
  • Paid game rejects unpaid payment_id.
  • Leaderboard updates.

CLI

php spark product:slacker game.integrate

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