@apex-inc/mcp-server 0.23.3 → 0.24.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/api-client.d.ts +7 -0
- package/dist/api-client.d.ts.map +1 -1
- package/dist/api-client.js +16 -0
- package/dist/api-client.js.map +1 -1
- package/dist/tools.d.ts +206 -0
- package/dist/tools.d.ts.map +1 -1
- package/dist/tools.js +240 -13
- package/dist/tools.js.map +1 -1
- package/package.json +1 -1
- package/skills/apex-communications/SKILL.md +11 -0
package/package.json
CHANGED
|
@@ -179,6 +179,17 @@ Cart-recovery is a Journey (multi-step sequence with a wait) — not a single co
|
|
|
179
179
|
|
|
180
180
|
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.
|
|
181
181
|
|
|
182
|
+
## Theme vs Template
|
|
183
|
+
|
|
184
|
+
**Template** is the job: event, attributes, slots, copy. Activate from the library. There is no extra theme step.
|
|
185
|
+
|
|
186
|
+
**Theme** is the look: fonts, sizes, colors, plus Title / Body / Button roles. New activations wear the workspace default theme.
|
|
187
|
+
|
|
188
|
+
- `list_communication_themes` before restyling a series.
|
|
189
|
+
- `create_communication_theme` / `update_communication_theme` to save a look. Style saves do not rewrite other emails.
|
|
190
|
+
- `apply_communication_theme` stamps a look onto chosen emails. Default is draft (merchant still publishes). Pass `apply=live` for the next send.
|
|
191
|
+
- Never group communications by `experiment-*` catalog id. A shop's "Order updates" series is the same object as Apex's own status emails.
|
|
192
|
+
|
|
182
193
|
## Exit Rules: The Quiet Half of Lifecycle Messaging
|
|
183
194
|
|
|
184
195
|
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.
|