@thinkingai/ae-cli 6.1.5 → 6.1.7

package/skills/ae-experiment/references/query_experiment_list_archived.md

@@ -0,0 +1,15 @@
+# experiment experiment list-archived
+
+Query archived experiments in a project.
+
+This command reuses the existing experiment list API and hardcodes `status=archive`.
+It only accepts `--project-id`; it does not expose additional filters.
+
+```bash
+ae-cli experiment experiment list-archived --project-id <id>
+```
+
+Flags:
+- `--project-id`, `-p`: Project ID.
+
+Response shape: `data.items` contains the archived experiments, `data.total` contains the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_experiment_metric_trend.md

@@ -1,16 +1,12 @@
-# +query_experiment_metric_trend
+# capability run experiment.report.metric-trend
 
 Query experiment metric trend report.
 
 ```bash
-ae-cli experiment +query_experiment_metric_trend --project_id <id> --exp_id <expId> --metric_id <metricId> --start_time 2026-07-01 --end_time 2026-07-07 [--request_id <id>] [--force_refresh true]
+ae-cli capability run experiment.report.metric-trend --input '{"project_id":1,"exp_id":"exp_123","metric_id":"metric_1","start_time":"2026-07-01","end_time":"2026-07-07"}'
 ```
 
-Flags:
-- `--project_id`, `-p`: Project ID.
-- `--exp_id`: Experiment ID.
-- `--metric_id`: Metric ID.
-- `--start_time`: Start date, `yyyy-MM-dd`.
-- `--end_time`: End date, `yyyy-MM-dd`.
-- `--request_id`: Optional request ID for query tracking.
-- `--force_refresh`: Optional boolean for report refresh.
+Required input: `project_id`, `exp_id`, `metric_id`, `start_time`, `end_time`.
+Optional input: `request_id`, `force_refresh`.
+
+Response shape: `data.report`, with recursively snake_case keys. Preserve `request_id` for cancellation.

package/skills/ae-experiment/references/query_experiment_operation_log.md

@@ -0,0 +1,17 @@
+# experiment operation-log query
+
+Query full operation logs for one experiment.
+
+Returns the complete Atlas experiment operation-log payload, including `remark`,
+`operation_content`, and structured `changes` when present. No field projection.
+
+```bash
+ae-cli experiment operation-log query --project-id <id> --exp-id <exp-id>
+```
+
+Flags:
+- `--project-id`, `-p`: Project ID.
+- `--exp-id`: Experiment ID.
+
+Response shape: `data.items` contains the full log records, `data.total` contains
+the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_experiment_report_summary.md

@@ -1,12 +1,11 @@
-# +query_experiment_report_summary
+# capability run experiment.report.summary
 
 Query experiment report summary.
 
 ```bash
-ae-cli experiment +query_experiment_report_summary --project_id <id> --exp_id <expId> [--force_refresh true]
+ae-cli capability run experiment.report.summary --input '{"project_id":1,"exp_id":"exp_123","force_refresh":false}'
 ```
 
-Flags:
-- `--project_id`, `-p`: Project ID.
-- `--exp_id`: Experiment ID.
-- `--force_refresh`: Optional boolean for report refresh.
+Required input: `project_id`, `exp_id`. Optional input: `force_refresh`.
+
+Response shape: `data.report`, with recursively snake_case keys.

package/skills/ae-experiment/references/query_experiment_sample_size_report.md

@@ -1,16 +1,12 @@
-# +query_experiment_sample_size_report
+# capability run experiment.report.sample-size
 
 Query experiment sample-size report.
 
 ```bash
-ae-cli experiment +query_experiment_sample_size_report --project_id <id> --exp_id <expId> --start_time 2026-07-01 --end_time 2026-07-07 [--request_id <id>] [--force_refresh true] [--by_hour true]
+ae-cli capability run experiment.report.sample-size --input '{"project_id":1,"exp_id":"exp_123","start_time":"2026-07-01","end_time":"2026-07-07","by_hour":false}'
 ```
 
-Flags:
-- `--project_id`, `-p`: Project ID.
-- `--exp_id`: Experiment ID.
-- `--start_time`: Start date, `yyyy-MM-dd`.
-- `--end_time`: End date, `yyyy-MM-dd`.
-- `--request_id`: Optional request ID for query tracking.
-- `--force_refresh`: Optional boolean for report refresh.
-- `--by_hour`: Optional boolean to show results by hour.
+Required input: `project_id`, `exp_id`, `start_time`, `end_time`.
+Optional input: `request_id`, `force_refresh`, `by_hour`.
+
+Response shape: `data.report`, with recursively snake_case keys. Preserve `request_id` for cancellation.

package/skills/ae-experiment/references/query_feature_detail.md

@@ -1,12 +1,14 @@
-# +query_feature_detail
+# experiment feature get
 
 Query Feature detail by key and optional version.
 
 ```bash
-ae-cli experiment +query_feature_detail --project_id <id> --feature_key <key> [--version <versionId>]
+ae-cli experiment feature get --project-id <id> --feature-key <key> [--version <versionId>]
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
-- `--feature_key`: Feature key.
+- `--project-id`, `-p`: Project ID.
+- `--feature-key`: Feature key.
 - `--version`: Optional Feature version ID.
+
+Response shape: the Feature is in `data.item`, with recursively snake_case keys such as `feature_key` and `target_platform`.

package/skills/ae-experiment/references/query_feature_list.md

@@ -1,10 +1,12 @@
-# +query_feature_list
+# experiment feature list
 
 Query Features in a project.
 
 ```bash
-ae-cli experiment +query_feature_list --project_id <id>
+ae-cli experiment feature list --project-id <id>
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
+
+Response shape: `data.items` contains Features, `data.total` contains the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_feature_operation_log.md

@@ -0,0 +1,19 @@
+# experiment feature operation-log query
+
+Query Feature operation logs for one Feature key.
+
+Reuses Hermes `GET /v1/atlas/feature/operationLogs` and returns the generic Atlas
+operation-log payload (`operation_type`, `operation_type_name`, `operator_name`,
+`operation_content`, `operate_time`). This is separate from
+`experiment operation-log query` and does not include experiment-side `changes`.
+
+```bash
+ae-cli experiment feature operation-log query --project-id <id> --feature-key <feature-key>
+```
+
+Flags:
+- `--project-id`, `-p`: Project ID.
+- `--feature-key`: Feature key.
+
+Response shape: `data.items` contains the full log records, `data.total` contains
+the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_feature_version_list.md

@@ -0,0 +1,20 @@
+# experiment feature version-list
+
+List Feature version history for one Feature key.
+
+Reuse the existing Hermes `GET /v1/atlas/feature/versions` API and return the full
+version records, including `version_snapshot`.
+
+Use with `experiment feature get --version <featureVersionId>` to inspect one version.
+
+```bash
+ae-cli experiment feature version-list --project-id <id> --feature-key <feature-key>
+ae-cli experiment feature get --project-id <id> --feature-key <feature-key> --version <featureVersionId>
+```
+
+Flags:
+- `--project-id`, `-p`: Project ID.
+- `--feature-key`: Feature key.
+
+Response shape: `data.items` contains version history records, `data.total` contains
+the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_metric_detail.md

@@ -1,11 +1,13 @@
-# +query_metric_detail
+# experiment metric get
 
 Query metric detail.
 
 ```bash
-ae-cli experiment +query_metric_detail --project_id <id> --metric_id <metricId>
+ae-cli experiment metric get --project-id <id> --metric-id <metricId>
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
-- `--metric_id`: Metric ID.
+- `--project-id`, `-p`: Project ID.
+- `--metric-id`: Metric ID.
+
+Response shape: the metric is in `data.item`, with recursively snake_case keys.

package/skills/ae-experiment/references/query_metric_list.md

@@ -1,10 +1,12 @@
-# +query_metric_list
+# experiment metric list
 
 Query metrics in a project.
 
 ```bash
-ae-cli experiment +query_metric_list --project_id <id>
+ae-cli experiment metric list --project-id <id>
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
+
+Response shape: `data.items` contains metrics, `data.total` contains the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/query_traffic_layer_detail.md

@@ -1,11 +1,13 @@
-# +query_traffic_layer_detail
+# experiment traffic-layer get
 
 Query traffic layer detail.
 
 ```bash
-ae-cli experiment +query_traffic_layer_detail --project_id <id> --layer_id <layerId>
+ae-cli experiment traffic-layer get --project-id <id> --layer-id <layerId>
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
-- `--layer_id`: Traffic layer ID.
+- `--project-id`, `-p`: Project ID.
+- `--layer-id`: Traffic layer ID.
+
+Response shape: the traffic layer is in `data.item`, with recursively snake_case keys.

package/skills/ae-experiment/references/query_traffic_layer_list.md

@@ -1,10 +1,12 @@
-# +query_traffic_layer_list
+# experiment traffic-layer list
 
 Query traffic layers in a project.
 
 ```bash
-ae-cli experiment +query_traffic_layer_list --project_id <id>
+ae-cli experiment traffic-layer list --project-id <id>
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
+
+Response shape: `data.items` contains traffic layers, `data.total` contains the count, and item keys are recursively snake_case.

package/skills/ae-experiment/references/save_experiment.md

@@ -1,17 +1,156 @@
-# +save_experiment
+# experiment experiment save
 
-Create or update an experiment draft.
+Progressively create or patch an experiment draft.
 
 ```bash
-ae-cli experiment +save_experiment --project_id <id> --req '<json>'
+ae-cli experiment experiment save --project-id <id> --req '<json>'
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
 - `--req`: Experiment save request JSON object.
 
-Notes:
-- Blank `req.expId` creates a draft and returns an experiment ID.
-- Non-blank `req.expId` patches the existing draft.
-- `req.projectId` is overwritten from `--project_id`.
-- Use `+check_experiment_ready` before moving to `pending`, `testing`, or `running`.
+## Contract
+
+- Call shape is top-level `projectId` plus a non-empty `req` object. In CLI form, `--project-id` supplies the top-level project ID.
+- Capability input uses outer `project_id`; nested `req` fields remain native camelCase. Hermes overwrites `req.projectId` with the outer project ID.
+- Never call this with `req=null`, `req={}`, or a modify payload containing only `expId`; those are terminal validation failures.
+- On `valid=false`, do not retry the same payload. Fix the reported field(s) or ask the user for missing input.
+
+Response shape is `data.result`. Object keys inside the result are recursively snake_case. A create commonly returns the new experiment ID as `data.result`; a patch commonly returns `true`.
+
+## Payload Type Contract
+
+Nested payload fields must match the server DTO types, not just the visible CLI dry-run body shape.
+
+| Field | Correct shape | Incorrect shape |
+| --- | --- | --- |
+| `featureKeyList` | `["payment_color"]` | `[{"featureKey":"payment_color"}]` |
+| `groups[].expGroupValue` | `"[\"green\"]"` | `["green"]` |
+| `metrics` | `[{"metricId":"payment","metricRole":"primary"}]` | `["payment"]` |
+
+- `featureKeyList` is an array of Feature key strings, not Feature objects. For feature experiments, pass one Feature key string.
+- `groups[].expGroupValue` is a JSON-encoded string of a string array. Pass a string whose content is a JSON array, not a native JSON array.
+- `metrics` is an array of metric binding objects. Each object contains `metricId` and `metricRole`.
+
+## Modes
+
+### Create Draft
+
+Blank or missing `req.expId` creates a draft.
+
+Required:
+- `expName`
+
+Optional while drafting:
+- `expType` (blank defaults to `feature`)
+- `groupId`
+- `trafficLayerId`
+- `allocation`
+- `expSalt`
+- `expSupposition`
+- `expDesc`
+- `isExpSharing`
+- `bucketId`
+- `expCycle`
+- `groups`
+- `featureKeyList`
+- `metrics`
+- `targeting`
+
+Success returns the created `expId`.
+
+```bash
+ae-cli experiment experiment save --project-id 1 --req '{"expName":"Homepage CTA draft"}'
+```
+
+### Patch Draft
+
+Non-blank `req.expId` patches an existing draft by merging the request with current experiment detail.
+
+Required:
+- `expId`
+- At least one changed field besides `expId`
+
+Merge behavior:
+- Omitted fields keep their current values.
+- Non-null scalar/object fields replace current values.
+- Non-empty `groups`, `featureKeyList`, `metrics`, and non-null `targeting` replace saved values.
+- Empty lists are not a reliable clear operation. Do not use empty arrays to clear bindings unless the backend contract is confirmed separately.
+
+Success returns `true`; continue using the input `expId`.
+
+```bash
+ae-cli experiment experiment save --project-id 1 --req '{"expId":"exp_123","allocation":20}'
+```
+
+## Field Notes
+
+- `isExpSharing=1` uses a shared traffic layer from `experiment traffic-layer list`; pick a `trafficLayerId` whose available idle traffic can cover `allocation`.
+- `isExpSharing=0` uses exclusive traffic with `bucketId`; select the bucket with `experiment bucket list`.
+- `allocation` is optional during draft construction, but before readiness it must be greater than `0` and no more than `100`.
+- `expCycle.cycleType` can be `day` or `sample`; when `cycleType=day`, `dayNum` is `1..90`. Blank cycle defaults to day + 30.
+- Before readiness, `groups` must be non-empty, contain exactly one control group, total allocation must equal `100`, and each `expGroupValue` must be a non-empty JSON string array.
+- Feature experiments must bind `featureKeyList` before readiness. `featureKeyList` contains Feature key strings, not Feature objects. The MCP currently supports one `featureKey` for feature experiments.
+- Metrics use `metricRole=primary|secondary|guardrail|observation`; before readiness at least one primary metric is required.
+- `targeting` replaces the saved targeting object when provided.
+
+## Payload Examples
+
+Patch a Feature binding. `featureKeyList` is a string array:
+
+```bash
+ae-cli experiment experiment save --project-id 2 --req '{"expId":"e024","featureKeyList":["payment_color"]}'
+```
+
+Patch groups. `expGroupValue` is a JSON-encoded string, not a native array:
+
+```bash
+ae-cli experiment experiment save --project-id 2 --req '{"expId":"e024","groups":[{"expGroupName":"control","isControl":1,"allocation":50,"expGroupValue":"[\"green\"]"},{"expGroupName":"variant","isControl":0,"allocation":50,"expGroupValue":"[\"red\"]"}]}'
+```
+
+Patch metrics. `metrics` is an object array:
+
+```bash
+ae-cli experiment experiment save --project-id 2 --req '{"expId":"e024","metrics":[{"metricId":"payment","metricRole":"primary"}]}'
+```
+
+## Dry-run Limitation
+
+`--dry-run` calls the Capability Gateway preview endpoint. It validates the outer input contract but does not guarantee that every nested DTO business rule will pass execution.
+
+If execution reports a DTO type mismatch after a clean dry-run, inspect nested field types first:
+
+- `featureKeyList` must be a string array.
+- `groups[].expGroupValue` must be a JSON-encoded string.
+- `metrics` must be an object array with `metricId` and `metricRole`.
+
+## Verified Related CLI Commands
+
+Use only these confirmed ae-cli commands when composing or checking a save payload:
+
+- `experiment experiment get`: optional; use only when patching an existing `expId` and you need to inspect saved fields.
+- `experiment bucket list`: find `bucketId`.
+- `experiment traffic-layer list`: find shared `trafficLayerId`.
+- `experiment feature list`: find `featureKey`.
+- `experiment metric list`: find `metricId`.
+- `experiment traffic-layer save`: create a missing traffic layer.
+- `experiment feature save`: create a missing Feature.
+- `experiment metric save`: create a missing metric.
+- `experiment experiment ready-check`: verify completeness before moving to `pending`, `testing`, or `running`.
+
+## Completion
+
+After a successful save, output the experiment detail link in this form, substituting the returned or input `expId` and actual project ID:
+
+```markdown
+[View experiment](/#/atlas/experiment/detail?expId=<expId>&currentProjectId=<projectId>)
+```
+
+After every successful save, call:
+
+```bash
+ae-cli experiment experiment ready-check --project-id <id> --exp-id <expId>
+```
+
+Use readiness failures to decide the next patch. Do not report the experiment save work as complete until readiness has been checked.

package/skills/ae-experiment/references/save_feature.md

@@ -1,13 +1,13 @@
-# +save_feature
+# experiment feature save
 
 Create or update a Feature.
 
 ```bash
-ae-cli experiment +save_feature --project_id <id> --req '<json>'
+ae-cli experiment feature save --project-id <id> --req '<json>'
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
 - `--req`: Feature save request JSON object.
 
 Create mode requires `featureKey`, `type`, and `targetPlatform`. Modify mode uses `id` or `update=true`.

package/skills/ae-experiment/references/save_metric.md

@@ -1,13 +1,13 @@
-# +save_metric
+# experiment metric save
 
 Create or update a metric.
 
 ```bash
-ae-cli experiment +save_metric --project_id <id> --req '<json>'
+ae-cli experiment metric save --project-id <id> --req '<json>'
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
 - `--req`: Metric save request JSON object.
 
 Create mode requires metric identifiers and metric configuration. Modify mode uses `update=true`.

package/skills/ae-experiment/references/save_submit_experiment.md

@@ -1,13 +1,13 @@
-# +save_submit_experiment
+# capability run experiment.experiment.save-submit
 
 Create or update a complete experiment and submit it in one call.
 
 ```bash
-ae-cli experiment +save_submit_experiment --project_id <id> --req '<json>'
+ae-cli capability run experiment.experiment.save-submit --input '{"project_id":1,"req":{...}}'
 ```
 
-Flags:
-- `--project_id`, `-p`: Project ID.
-- `--req`: Save-and-submit request JSON object.
+Input fields: `project_id` and `req`. The outer input is snake_case; fields inside `req` keep the native camelCase DTO shape.
 
-Prefer `+save_experiment` for progressive draft construction.
+Response shape: `data.result`, with object keys recursively converted to snake_case.
+
+Prefer `experiment experiment save` for progressive draft construction.

package/skills/ae-experiment/references/save_traffic_layer.md

@@ -1,13 +1,13 @@
-# +save_traffic_layer
+# experiment traffic-layer save
 
 Create or update a traffic layer.
 
 ```bash
-ae-cli experiment +save_traffic_layer --project_id <id> --req '<json>'
+ae-cli experiment traffic-layer save --project-id <id> --req '<json>'
 ```
 
 Flags:
-- `--project_id`, `-p`: Project ID.
+- `--project-id`, `-p`: Project ID.
 - `--req`: Traffic layer save request JSON object.
 
 Create mode requires `bucketId`, `layerName`, and `layerType` in the request. Modify mode requires `layerId`.

package/skills/ae-experiment/references/update_experiment_group.md

@@ -0,0 +1,20 @@
+# experiment experiment update-group
+
+Update only the business group of one experiment.
+
+Reuses Hermes `POST /v1/atlas/experiment/updateGroup`. This dedicated endpoint
+updates `group_id` only and does not go through full experiment `modify`, so it
+will not rewrite traffic, variants, metrics, or other fields.
+
+```bash
+ae-cli experiment experiment update-group --project-id <id> --exp-id <exp-id> --group-id <group-id>
+ae-cli experiment experiment update-group --project-id <id> --exp-id <exp-id> --group-id 0 --dry-run
+```
+
+Flags:
+- `--project-id`, `-p`: Project ID.
+- `--exp-id`: Experiment ID.
+- `--group-id`: Target business group ID. Use `0` for ungrouped.
+
+Response shape: `data.result` is `true` when the update succeeds. Blank
+`--group-id` is normalized to `0` on the server.

package/skills/ae-generate-tracking-code/SKILL.md

@@ -34,7 +34,7 @@ description: "Interactive generation of AE tracking code, LogBus2 configuration,
 | LogBus2 配置 | LogBus2 Configuration | `daemon.json` for LogBus2 log sync tool |
 | LoggerConsumer | LoggerConsumer | Server SDK consumer that writes events to local log files |
 | BatchConsumer | BatchConsumer | Server SDK consumer that uploads events in batches |
-| 公共属性 | Super Property | Properties attached to all events automatically |
+| 公共属性 | Super Property | Properties attached to all events automatically. ⚠️ The correct Chinese AE term is "公共属性" or "公共事件属性". Never translate "Super Property" as "超级属性" — that is NOT a valid AE term. |
 | 预置属性 | Preset Property | System properties prefixed with `#` (e.g. `#device_id`, `#time`) |
 | 事件属性 | Event Property | Custom properties on specific events |
 | 用户属性 | User Property | Properties set on the user profile |
@@ -91,12 +91,12 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 **⚠️ Key: SERVER_URL and APP_ID are independent config items. Even if draft.json has project_id and host, you MUST resolve and confirm them. `project_id` ≠ `APP_ID`, `host` ≠ `SERVER_URL`.**
 
 1. **APP_ID** — Prefer automatic lookup before asking:
-   - If `meta.project_id` is known, run `ae-cli analysis_common +list_projects` once for the current host.
+   - If `meta.project_id` is known, run `ae-cli analysis project info list` once for the current host.
    - Find the project whose `projectId` matches `meta.project_id`.
    - If the matched project has `appId`, ask: **"I found APP_ID `<appId>` for project `<projectId>`. Use it? yes / enter new value"**
    - If the project is missing, ambiguous, or has no `appId`, ask the user to copy APP_ID from AE Admin → "Project Settings" → "Integration Config".
 2. **SERVER_URL** — Data ingestion endpoint (**different from web URL**; go to AE Admin → "Project Settings" → "Integration Config" → fill in "Public URL")
-   - If `meta.project_id` is known, you may try `ae-cli analysis_meta +get_project_config --project_id <project_id>` once.
+   - If `meta.project_id` is known, you may try `ae-cli analysis project info get --project-id <project_id>` once.
    - Use the returned value only if the response explicitly contains a receiver URL field such as `serverUrl`, `pushUrl`, `push_url`, `receiverUrl`, `publicUrl`, `publicReceiverAddress`, `privateReceiverAddress`, or equivalent ingestion endpoint field.
    - If both `publicReceiverAddress` and `privateReceiverAddress` are present, prefer `publicReceiverAddress` as `SERVER_URL` for generated snippets unless the user explicitly needs an internal/private-network receiver.
    - If a value is found, ask: **"I found SERVER_URL `<url>` for project `<projectId>`. Use it? yes / enter new value"**
@@ -646,6 +646,7 @@ Validation steps:
 - Including `platform === "server"` exclusive events in client code
 - Including `platform === "client"` exclusive events in server code (unless `platform === "both"`)
 - **Skipping SDK main doc read and guessing integration method** — each SDK has different integration approaches; must read wiki main doc's "Integrate SDK" section first, and choose the correct method based on project characteristics (with/without build tools)
+- **Translating "Super Property" as "超级属性" in any user-facing output (code comments, interaction prompts, markdown) — the correct AE Chinese term is "公共事件属性" or "公共属性"**
 - **Entering Phase 1 before Phase 0.5 is complete** — SDK integration must be confirmed before inserting code, otherwise generated track() calls won't work
 
 ---

package/skills/ae-generate-tracking-code/references/client-sdk-insert.md

@@ -1,6 +1,6 @@
 # Mode A — Client SDK Code Insertion
 
-> **Terminology**: 客户端 SDK = client SDK | 代码插入 = code insertion/injection | 前置检查 = pre-check | 集成方式 = integration method | 埋点 = tracking/event tracking | 业务触发点 = business trigger point | 公共属性 = super property | 用户属性 = user property | 自动采集事件 = auto-track event | 插入位置预览 = insertion site preview | 语言风格校验 = language style check
+> **Terminology**: 客户端 SDK = client SDK | 代码插入 = code insertion/injection | 前置检查 = pre-check | 集成方式 = integration method | 埋点 = tracking/event tracking | 业务触发点 = business trigger point | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 自动采集事件 = auto-track event | 插入位置预览 = insertion site preview | 语言风格校验 = language style check
 
 ## ⚠️ Mandatory Pre-checks (do not skip)
 

package/skills/ae-generate-tracking-code/references/server-sdk-insert.md

@@ -1,6 +1,6 @@
 # Server-side Code Insertion (LoggerConsumer + LogBus2)
 
-> **Terminology**: 服务端 SDK = server-side SDK | 代码插入 = code insertion/injection | LoggerConsumer = writes events to local log files (recommended for production) | LogBus2 = log sync tool that reads local logs and uploads to TE | 架构 = architecture | 异步上报 = async upload | 批量上传 = batch upload | 重试策略 = retry strategy | 公共属性 = super property | 用户属性 = user property | 依赖管理 = dependency management
+> **Terminology**: 服务端 SDK = server-side SDK | 代码插入 = code insertion/injection | LoggerConsumer = writes events to local log files (recommended for production) | LogBus2 = log sync tool that reads local logs and uploads to TE | 架构 = architecture | 异步上报 = async upload | 批量上传 = batch upload | 重试策略 = retry strategy | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 依赖管理 = dependency management
 
 ## Architecture
 

package/skills/ae-generate-tracking-code/references/snippet-delivery.md

@@ -1,6 +1,6 @@
 # Snippet Output Mode
 
-> **Terminology**: 片段/代码片段 = snippet/code snippet | 产物 = deliverable/output | markdown 响应 = markdown response | 初始化 = initialization | 公共属性 = super property | 用户属性 = user property | 事件组 = event group | 触发时机 = trigger timing | 验证步骤 = verification steps | 设备绑定 = device binding | 自动采集事件 = auto-track event | 占位值 = placeholder value | 属性类型 = property type
+> **Terminology**: 片段/代码片段 = snippet/code snippet | 产物 = deliverable/output | markdown 响应 = markdown response | 初始化 = initialization | 公共属性 = super property (公共事件属性; never "超级属性") | 用户属性 = user property | 事件组 = event group | 触发时机 = trigger timing | 验证步骤 = verification steps | 设备绑定 = device binding | 自动采集事件 = auto-track event | 占位值 = placeholder value | 属性类型 = property type
 
 ## Deliverables
 

package/skills/ae-generate-tracking-plan/SKILL.md

@@ -29,7 +29,7 @@ description: "Interactive generation of an AE tracking plan and upload. Trigger
 | 货币体系 | Currency System | Hard currency (diamonds), soft currency (gold), etc. |
 | 事件 | Event | Named user action or system occurrence (`event_name`) |
 | 事件属性 | Event Property | Data attached to an event (`prop_names`) |
-| 公共事件属性 | Common/Super Property | Property attached to every event automatically |
+| 公共事件属性 | Common/Super Property | Property attached to every event automatically. ⚠️ The correct Chinese AE term is "公共事件属性" or "公共属性". Never translate "Super Property" as "超级属性" — that is NOT a valid AE term. |
 | 用户属性 | User Property | Property on the user profile (persistent state) |
 | 预置属性 | Preset Property | System property prefixed with `#` (`#device_id`, `#time`, etc.) |
 | 自动采集事件 | Auto-track Event | SDK auto-collected events (`ta_app_start`, `ta_page_show`, etc.) |
@@ -700,7 +700,10 @@ Based on SDK integration mode collected in Phase 0, decide whether to inject aut
 3. Auto-track event `event_tag` set to `"System Event"`
 4. Auto-track events only carry preset properties (`prop_names` is empty or contains only preset property names)
 5. Preset properties prefixed with `#` are not added to `event_properties` pool (auto-collected by SDK)
-6. **Deduplication**: Templates may already contain same-name auto-track events (e.g. `ta_app_start` marked `source: "template"`); CLI deduplicates by event name globally and will not inject duplicates
+6. **Cleanup + Deduplication**: The CLI will:
+   - **Remove** auto-track events inherited from templates or existing plans that don't match the user's selected SDKs. For example: if a template built for Android/iOS contains `ta_app_install`, `ta_app_start`, `ta_app_end` but the user selects JavaScript SDK, those `ta_app_*` events will be automatically removed since JavaScript SDK does not support them.
+   - **Inject** the correct auto-track events for the user's selected SDKs.
+   - **Deduplicate** by event name globally — won't inject events that already exist in the draft (correct auto-track events inherited from templates are kept).
 
 **SDK type → Recommended events** (see `references/autotrack-events.md` for details):
 
@@ -1300,6 +1303,7 @@ The tracking plan has been uploaded successfully. Would you like to generate tra
 - Asking all anchor questions at once
 - Skipping Phase 3 and uploading directly
 - Manually assembling xlsx bypassing `.ae-cli/draft.json`
+- Translating "Super Property" as "超级属性" in any user-facing output (interaction prompts, plan summaries, event/property descriptions) — the correct AE Chinese term is "公共事件属性" or "公共属性"
 - Calling `fetch` AE API directly within the skill — all AE communication must go through project scripts / CLI
 
 ---