arta

Use during the DESIGN phase of building a new app/feature, instead of dumping a wall of text. ALWAYS brainstorm the idea into an agreed direction first (questions one at a time, like superpowers:brainstorming) — never jump straight to a spec or prototype. Then drive Claude Code to build a shared, live design canvas (.arta/state.json) that the dev watches in the Arta viewer — spec, prototype, data model, flow, plan — iterating from the dev's clicks and feedback. Trigger when the user wants to "design", "wireframe", "prototype", "sketch the data model/flow", "plan a feature visually", or says "open Arta / let's design this in the studio".

Use when releasing / shipping a new version of Arta (this repo) — triggers on "release", "ship it", "publish the plugin", "cut a new version", "ปล่อยเวอร์ชันใหม่", "release arta". Runs preflight (build + validate), commits and pushes to main, waits for CI to auto-bump the version and refresh the MCP bundle, confirms the new version landed on origin, then reports the exact update steps for users. Maintainer tool — it does NOT ship inside the plugin.