@apex-inc/mcp-server 0.23.4 → 0.25.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apex-inc/mcp-server",
-  "version": "0.23.4",
+  "version": "0.25.0",
   "description": "MCP server for Apex \u2014 currently in private beta.",
   "type": "module",
   "main": "dist/index.js",

package/skills/apex-communications/SKILL.md

@@ -19,7 +19,7 @@ Use these tools to help users build a communication program that sends the right
 ### First-time setup (user has no communications)
 
 1. **`recommend_communications`** — get the recommended communications for the user's vertical. Review the list with the user.
-2. **`generate_communications`** — create the selected communications with pre-written copy.
+2. **`generate_communications`** — create the selected communications with pre-written copy. Each letter wears the workspace default Theme (look is snapshotted; you do not set per-block align).
 3. **`get_event_taxonomy`** — show the user what `apex.track()` calls they need to add to their code.
 4. **`list_communications`** — confirm everything was created.
 
@@ -27,8 +27,9 @@ Use these tools to help users build a communication program that sends the right
 
 1. **`list_communications`** — see what exists, and check `controlState` before you edit.
 2. **`edit_communication`** — update subject, body, CTA, channels, or status. Pass `intent` when the control is protected (see below).
-3. **`preview_communication`** — render the email with the user's brand.
-4. **`send_test_communication`** — send a test to verify it looks right.
+3. **`preview_communication`** — render the email with the user's brand. Also reports Theme Title/Body/Button roles and which blocks override them.
+4. **`add_communication_variant`** — clone Control into a new column (Variant A, …) so you can run a content experiment.
+5. **`send_test_communication`** — send a test to verify it looks right.
 
 ## Replace versus compete — the one rule that protects results
 
@@ -179,6 +180,17 @@ Cart-recovery is a Journey (multi-step sequence with a wait) — not a single co
 
 The key is that the **journey** owns the wait, the branching on cart state, and the exit semantics. The **communications** are just the payloads the journey fires.
 
+## Theme vs Template
+
+**Template** is the job: event, attributes, slots, copy. Activate from the library. There is no extra theme step.
+
+**Theme** is the look: fonts, sizes, colors, plus Title / Body / Button roles. New activations wear the workspace default theme.
+
+- `list_communication_themes` before restyling a series.
+- `create_communication_theme` / `update_communication_theme` to save a look. Style saves do not rewrite other emails.
+- `apply_communication_theme` stamps a look onto chosen emails. Default is draft (merchant still publishes). Pass `apply=live` for the next send.
+- Never group communications by `experiment-*` catalog id. A shop's "Order updates" series is the same object as Apex's own status emails.
+
 ## Exit Rules: The Quiet Half of Lifecycle Messaging
 
 A communication is only as good as its non-sends. The user who returns to the app 30 seconds after abandoning their cart should never receive the "you forgot something" push — sending it makes Apex look broken, annoys the customer, and burns trust in the brand.