taptap-maker-locallisted

# TapTap Maker Local Workflow Use this skill as the workflow layer for Maker local development. The Maker CLI owns one-time initialization; MCP tools own the high-frequency development loop. This skill decides the sequence, asks the user for choices, and explains local state in plain language. ## Scope This skill covers: - initialize local Maker development - run the Maker CLI initialization flow - clone a Maker project - prepare local AI dev kit after project checkout - choose a Maker app from the CLI app list - explain PAT, Git, project binding, and editor reloads - inspect local changes - pull remote changes - submit local changes - push local commits - explain and resolve conflicts with user approval Build, submit, push, preview, and verify behavior belongs to the single Maker MCP build tool. The post-build runtime log polling loop belongs to the local Maker CLI watcher. Do not infer or set a service environment from preview, build, test, or local-development intent. Do not add environment parameters to Maker tool calls or user MCP config; use the default Maker service configuration. For multiplayer builds, use `maker_build_current_directory` structured parameters instead of editing project JSON directly. `entry_client` / `entry_server` map to `project.json` `entry@client` / `entry@server`; `multiplayer.enabled`, `max_players`, `background_match`, `match_info`, and `persistent_world` map to `.project/settings.json` `@runtime.multiplayer`. On the first multiplayer b