AE Experiment Design and Integration

Turn a business objective into an evidence-backed experiment design, an implementation contract, and, when requested and supported, an AE experiment draft.

Hard boundaries

• Use ae-cli for every AE/TE platform interaction. Do not substitute raw HTTP, browser automation, direct database queries, or application SDKs.
• Do not infer an SDK request from the fact that an experiment needs implementation. Load SDK references only when the user explicitly asks about an A/B experiment SDK or client SDK integration.
• Do not copy general tracking SDK documentation into this Skill. Route generic initialization, event reporting, track, user identity, user properties, data upload, LogBus, and REST questions to ae-data-integration-helper when that Skill is available.
• Use only the event-metric calculation contracts defined in metric-readiness.md. Bind one confirmed primary event metric and do not add unsupported metric roles.
• Never claim that a platform asset exists, was created, passed a check, or generated project code without a successful ae-cli response.
• Never invent platform IDs, schemas, SDK APIs, versions, defaults, or behavior.

Progressive disclosure router

Read only the references needed for the current request: