@clix-so/clix-agent-skills 0.1.3 → 0.1.4

package/README.md

@@ -1,14 +1,17 @@
 # Agent Skills for Clix
 
+[![npm version](https://img.shields.io/npm/v/%40clix-so%2Fclix-agent-skills.svg?logo=npm&label=npm)](https://www.npmjs.com/package/@clix-so/clix-agent-skills)
+[![npm downloads](https://img.shields.io/npm/dm/%40clix-so%2Fclix-agent-skills.svg)](https://www.npmjs.com/package/@clix-so/clix-agent-skills)
+
 This repository contains a collection of **Agent Skills for Clix**. Each skill
 is a self-contained package that can be loaded and executed by AI clients.
 
 ## Installing Skills
 
-Agents skills on this repository are built on the
+Agent skills in this repository are built on the
 [open agent skills standard](https://agentskills.io/home). Please refer to the
 [official documentation](https://agentskills.io/home#adoption) for up-to-date
-information of support AI clients. Depending on the AI client you are using, you
+information on supported AI clients. Depending on the AI client you are using, you
 can install skills in different ways.
 
 ### Universal CLI (Recommended)
@@ -18,11 +21,24 @@ For **Cursor**, **VS Code**, **Claude Desktop**, **OpenCode**, **Goose**,
 and configure the Clix MCP Server automatically:
 
 ```bash
+# Install a specific skill
 npx @clix-so/clix-agent-skills@latest install <skill-name> --client <your-client>
-# For example, to install integration skill on Cursor:
-# npx @clix-so/clix-agent-skills@latest install integration --client cursor
+# For example, to install a skill on Cursor:
+npx @clix-so/clix-agent-skills@latest install integration --client cursor
+
+# Install all available skills at once
+npx @clix-so/clix-agent-skills@latest install --all --client cursor
+# This will install: integration, event-tracking, user-management
 ```
 
+### Available Skills
+
+- **clix-integration**: Integrate Clix Mobile SDK and MCP server setup
+- **clix-event-tracking**: Implement `Clix.trackEvent` with naming/schema best
+  practices and campaign-ready validation
+- **clix-user-management**: Implement `Clix.setUserId` + user properties with
+  logout best practices, personalization (`user.*`), and audience targeting
+
 **Supported Clients:**
 
 | Client         | Flag                | Default Path       |
@@ -47,17 +63,19 @@ following command:
 
 To install specific skills:
 
-1. Select `Browse and install plugins`
-2. Select `clix-agent-skills` from the list
+1. Visit the Marketplace section in `/plugin`
+2. Select `Browse plugins`
 3. Choose the skills you wish to install
-4. Click `Install` to proceed
+4. Install skill
 
 Alternatively, you can install a single skill directly by running:
 
 ```bash
 /plugin install <plugin-name>@<marketplace-name>
 # For example
-# /plugin install clix-integration@clix-agent-skills
+/plugin install clix-integration@clix-agent-skills
+/plugin install clix-event-tracking@clix-agent-skills
+/plugin install clix-user-management@clix-agent-skills
 ```
 
 Remember to restart Claude Code after installation to load the new skills.
@@ -70,7 +88,9 @@ configuration directory:
 
 Or install a specific skill using the command line:
 
-```
+```bash
+$skill-installer install <link-to-skill-folder>
+# For example
 $skill-installer install https://github.com/clix-so/skills/tree/main/skills/integration
 ```
 
@@ -78,12 +98,11 @@ Ensure you restart Codex after installation to detect the new skills.
 
 ## Disclaimer
 
-Please be aware that **these skills may occasionally fail or execute
-incorrectly** due to the non-deterministic nature of AI.
-
-It is critical that you **carefully review and verify all actions** performed by
-these skills. While they are designed to be helpful, you remain responsible for
-checking their output before use. Please use them with caution and supervision.
+Please be aware that these skills may occasionally fail or execute incorrectly
+due to the non-deterministic nature of AI. It is critical that you carefully
+review and verify all actions performed by these skills. While they are designed
+to be helpful, you remain responsible for checking their output before use.
+Please use them with caution and supervision.
 
 ## License
 

package/dist/bin/cli.js

@@ -23,16 +23,26 @@ program
     .description("CLI to manage and install Clix Agent Skills")
     .version(package_json_1.version);
 program
-    .command("install <skill>")
-    .description("Install a specific agent skill")
+    .command("install [skill]")
+    .description("Install agent skill(s)")
     .option("-c, --client <client>", "Target AI client (cursor, claude, vscode, amp, kiro, amazonq, codex, opencode, manual)")
     .option("-p, --path <path>", "Custom installation path (default: .clix/skills)")
+    .option("-a, --all", "Install all available skills")
     .action(async (skill, options) => {
     try {
-        await (0, install_1.installSkill)(skill, options);
+        if (options.all) {
+            await (0, install_1.installAllSkills)(options);
+        }
+        else if (skill) {
+            await (0, install_1.installSkill)(skill, options);
+        }
+        else {
+            console.error(chalk_1.default.red("Error: Please specify a skill name or use --all flag"));
+            process.exit(1);
+        }
     }
     catch (error) {
-        console.error(chalk_1.default.red("Error installing skill:"), getErrorMessage(error));
+        console.error(chalk_1.default.red("Error installing skill(s):"), getErrorMessage(error));
         process.exit(1);
     }
 });

package/dist/bin/commands/install.js

@@ -4,6 +4,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.installSkill = installSkill;
+exports.installAllSkills = installAllSkills;
 const path_1 = __importDefault(require("path"));
 const fs_extra_1 = __importDefault(require("fs-extra"));
 const chalk_1 = __importDefault(require("chalk"));
@@ -121,3 +122,59 @@ async function installSkill(skillName, options) {
     console.log(`  - Docs: ${path_1.default.join(destPath, "SKILL.md")}`);
     console.log(`  - Instruct your agent to read these docs to start working.`);
 }
+/**
+ * Find all available skills in the skills directory
+ */
+async function findAllSkills() {
+    // Find package root (same logic as installSkill)
+    let packageRoot = __dirname;
+    while (!fs_extra_1.default.existsSync(path_1.default.join(packageRoot, "package.json"))) {
+        const parent = path_1.default.dirname(packageRoot);
+        if (parent === packageRoot) {
+            packageRoot = process.cwd();
+            break;
+        }
+        packageRoot = parent;
+    }
+    const skillsDir = path_1.default.join(packageRoot, "skills");
+    if (!fs_extra_1.default.existsSync(skillsDir)) {
+        return [];
+    }
+    const entries = await fs_extra_1.default.readdir(skillsDir, { withFileTypes: true });
+    return entries
+        .filter((entry) => entry.isDirectory())
+        .filter((entry) => fs_extra_1.default.existsSync(path_1.default.join(skillsDir, entry.name, "SKILL.md")))
+        .map((entry) => entry.name);
+}
+/**
+ * Install all available skills
+ */
+async function installAllSkills(options) {
+    const spinner = (0, ora_1.default)("Discovering available skills...").start();
+    const skills = await findAllSkills();
+    if (skills.length === 0) {
+        spinner.fail("No skills found to install.");
+        return;
+    }
+    spinner.succeed(`Found ${chalk_1.default.bold(skills.length)} skill(s): ${skills.join(", ")}`);
+    console.log();
+    let successCount = 0;
+    let failCount = 0;
+    for (const skillName of skills) {
+        try {
+            await installSkill(skillName, options);
+            successCount++;
+        }
+        catch (error) {
+            console.error(chalk_1.default.red(`\n✗ Failed to install ${chalk_1.default.bold(skillName)}: ${getErrorMessage(error)}`));
+            failCount++;
+        }
+    }
+    console.log();
+    if (failCount === 0) {
+        console.log(chalk_1.default.green(`\n✔ Successfully installed all ${chalk_1.default.bold(successCount)} skill(s)!`));
+    }
+    else {
+        console.log(chalk_1.default.yellow(`\n⚠ Installed ${chalk_1.default.bold(successCount)} skill(s), ${chalk_1.default.bold(failCount)} failed.`));
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clix-so/clix-agent-skills",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "An open collection of agent skills for Clix.",
   "main": "dist/index.js",
   "bin": {

package/skills/event-tracking/LICENSE.txt

@@ -0,0 +1,203 @@
+Copyright (c) 2026 Clix (https://clix.so/)
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (c) 2026 Clix (https://clix.so/)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/event-tracking/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: clix-event-tracking
+description:
+  Implements Clix event tracking (Clix.trackEvent) with consistent naming, safe
+  property schemas, and campaign-ready validation. Use when adding, reviewing,
+  or debugging event tracking; when configuring event-triggered campaigns; or
+  when the user mentions events, tracking, funnels, or properties.
+---
+
+# Tracking Clix Events
+
+Use this skill to help developers design and implement **Clix event tracking**
+via `Clix.trackEvent(...)` so events can drive **event-triggered campaigns**,
+**audience filters**, and **personalization**.
+
+## What the official docs guarantee (high-signal)
+
+- **When to track**: identify the user action/system event, then attach
+  meaningful properties (funnel checkpoints, milestones, button taps).
+- **Property normalization**: booleans/numbers/strings map directly; date-like
+  values serialize to ISO 8601; unsupported objects become strings.
+- **Error handling**: event tracking calls can throw—always handle errors so the
+  app stays robust.
+
+## MCP-first (source of truth)
+
+If Clix MCP tools are available, treat them as the **source of truth**:
+
+- `clix-mcp-server:search_docs` for conceptual behavior (campaign triggers,
+  personalization)
+- `clix-mcp-server:search_sdk` for exact SDK signatures per platform
+
+If MCP tools are not available, use the bundled references:
+
+- Event API contract + pitfalls → `references/trackevent-contract.md`
+- Naming + schemas + privacy → `references/naming-and-schema.md`
+- Implementation patterns → `references/implementation-patterns.md`
+- Campaign mapping → `references/campaign-mapping.md`
+- Debugging checklist → `references/debugging.md`
+
+## Workflow (copy + check off)
+
+```
+Event tracking progress:
+- [ ] 1) Confirm platform(s) and goals (analytics vs campaign triggers)
+- [ ] 2) Propose event plan (names, when fired, properties, where in code)
+- [ ] 3) Validate plan (names, keys, types, PII constraints)
+- [ ] 4) Implement trackEvent calls (platform-correct)
+- [ ] 5) Verify: events fire once, serialize cleanly, match campaign configs
+```
+
+## 1) Confirm the minimum inputs
+
+Ask only what’s needed:
+
+- **Platform**: iOS / Android / React Native / Flutter
+- **Goal**: analytics only, event-triggered campaigns, or both
+- **Top flows** (1–3): e.g., onboarding, checkout, subscription
+- **PII policy**: what must never be sent (email/phone/name/free-text, etc.)
+
+## 2) Propose an “Event Plan” (before touching code)
+
+Return a compact table the user can approve:
+
+- **event_name** (stable, `snake_case`)
+- **when** (exact moment the event fires)
+- **properties** (key + type, mark required vs optional)
+- **location** (file/function/UI handler/network response)
+- **purpose** (campaign trigger / analytics / both)
+
+If campaigns are involved, remind: **event names and property keys must match
+exactly** in the Clix console.
+
+## 3) Validate the plan (fast feedback loop)
+
+Create `event-plan.json` in `.clix/` directory (recommended) or project root:
+
+**Recommended location**: `.clix/event-plan.json`
+
+- Organized: keeps tooling configs together
+- Hidden: doesn't clutter project root
+- Committable: planning document for team review
+
+**Alternative**: `event-plan.json` in project root (simpler, but less organized)
+
+**For agents**: Locate `scripts/validate-event-plan.sh` in the installed skill
+directory, then run it:
+
+```bash
+# From project root:
+bash <skill-dir>/scripts/validate-event-plan.sh .clix/event-plan.json
+# Or if in root:
+bash <skill-dir>/scripts/validate-event-plan.sh event-plan.json
+```
+
+The skill directory is typically:
+
+- `.cursor/skills/event-tracking/` (Cursor)
+- `.claude/skills/event-tracking/` (Claude Desktop)
+- `.vscode/skills/event-tracking/` (VS Code/Amp)
+- Or check where this skill was installed
+
+If validation fails: fix the plan first, then implement.
+
+## 4) Implement tracking (platform-correct)
+
+Use MCP to fetch the exact `trackEvent` signature for the platform; then:
+
+- **Place calls at stable boundaries** (action confirmed, request succeeded,
+  state updated)
+- **Avoid duplicates** (don’t fire on every render; debounce where needed)
+- **Avoid null/complex values** (prefer primitives; serialize dates to ISO)
+- **Do not track PII by default**
+
+See `references/implementation-patterns.md` for placement heuristics and code
+patterns.
+
+## 5) Verify
+
+Minimum verification:
+
+- Event fires **exactly once** per user action (or the intended cadence)
+- Properties are **primitive + stable** (no null surprises)
+- For campaigns: console trigger conditions match **exact names/keys**
+
+For troubleshooting steps, see `references/debugging.md`.

package/skills/event-tracking/references/campaign-mapping.md

@@ -0,0 +1,29 @@
+# Campaign Mapping (Event-triggered)
+
+## Contents
+
+- What matters for event-triggered campaigns
+- Mapping checklist
+- Common mistakes
+
+## What matters
+
+- Triggers only apply to **new incoming events**
+- Campaign trigger config must match:
+  - **event name** exactly
+  - **property keys** exactly
+  - (often) **property types** as expected
+
+## Mapping checklist
+
+- Confirm the app sends `event_name` with the exact spelling used in the console
+- Confirm property keys are stable and `snake_case` (recommended)
+- If filtering on properties in the console, ensure:
+  - values are present (not null)
+  - value types are consistent (number vs string)
+
+## Common mistakes
+
+- Tracking `productId` but filtering on `product_id`
+- Sending numbers as strings (`"14"` vs `14`)
+- Tracking too early (before the action is truly completed)

package/skills/event-tracking/references/debugging.md

@@ -0,0 +1,30 @@
+# Debugging Event Tracking
+
+## Contents
+
+- Quick triage
+- Common causes
+- Verification checklist
+
+## Quick triage
+
+1. Confirm `Clix.initialize(...)` is called before any tracking.
+2. Confirm the event is fired exactly once (no render loops).
+3. Confirm properties are primitive and non-null.
+4. If using campaigns: confirm console trigger matches event name + property
+   keys exactly.
+
+## Common causes
+
+- **Not initialized**: tracking called before init completes.
+- **Duplicate events**: track call placed in render/recomposition or repeated
+  listeners.
+- **Bad property types**: objects/arrays, inconsistent types, nulls.
+- **Mismatch with campaigns**: name/key mismatch, different casing.
+
+## Verification checklist
+
+- Add temporary logs around the tracking call (and remove after verification)
+- Use a stable test flow to reproduce (single tap, single request)
+- Verify in Clix console that events appear (and that campaigns fire when
+  expected)

package/skills/event-tracking/references/implementation-patterns.md

@@ -0,0 +1,45 @@
+# Implementation Patterns
+
+## Contents
+
+- Where to place trackEvent calls
+- De-duplication guidance
+- Property hygiene
+- Platform notes
+
+## Where to place trackEvent calls
+
+Prefer stable boundaries (low risk of duplicate firing):
+
+- **User action confirmed**: button tap handler, after local validation passes
+- **Network success**: after API responds 2xx / mutation completes
+- **State change**: after the app updates state that the user can observe
+
+Avoid:
+
+- Render functions / recompositions
+- Generic “screen mounted” hooks without guards
+
+## De-duplication guidance
+
+Ensure “once per action”:
+
+- Debounce rapid taps where relevant
+- Track on success callbacks rather than optimistic UI (unless intentional)
+- For navigation-based events, ensure one event per screen transition
+
+## Property hygiene
+
+- Remove `null` values before sending (recommended across platforms)
+- Keep property values small and stable
+- Prefer enums/known strings over arbitrary user text
+
+## Platform notes (what the skill should remember)
+
+- **iOS**: properties are coerced to primitives; `Date` → ISO; other objects →
+  string.
+- **Android**: unknown objects become ISO (if recognized) else string; avoid
+  nulls.
+- **React Native**: `Date` is serialized to ISO; other values pass through.
+- **Flutter**: null properties are filtered out; supports `messageId` in event
+  API.