amplitude-instrumentation
Amplitude Analytics
Use this capability whenever you wire Amplitude into an application, review an integration that already exists, or answer a question about how Amplitude behaves. It owns the mechanism: which package, what init takes, how identity resolves, what an operator does, what a limit costs when you cross it.
It does not own what to track, how to name it, or where the call site goes. Those are vendor-neutral decisions that a product-event-tracking capability in a software-instrumentation skill owns, and this skill defers to it rather than restating it. Nor does it cover the analyst's half of the subject — reading a funnel, a retention curve, or an experiment result — or Amplitude's product and organization administration: charts, dashboards, alerts, RBAC, SSO, billing. Those are where this skill stops.
Version posture. Amplitude renames configuration surfaces between minors — defaultTracking became autocapture in Browser SDK 2.10.0, and fetchRemoteConfig is documented in two places at once — and a wrong option key is ignored rather than raising an error. Every reference names the upstream page it was checked against and the date of that check. Treat each as verified-at-that-date, and look it up in the installed version's own documentation before depending on it. Where a surface moves faster than it can usefully be frozen, the reference prescribes a lookup instead of a value.
Platform scope. Browser SDK 2 and the React Native SDK are first-class. iOS, Android, Flutter, Unity, Unreal, and Node are named as families with a prescribed lookup: the concepts carry across them, the method names do not.
This skill stands alone. Amplitude's own MCP servers, published skills, and .amplitude/ configuration are covered where they change what you should do, but nothing here requires any of them to be installed.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
SDK and Wrapper
See sdk-and-wrapper.md for: