chore(skills): refresh from context-hub (HTML scrapes → clean markdown)

skills/instrumentation/discover-event-surfaces/references/best-practices.md

@@ -324,7 +324,7 @@ These standards apply when helping customers design new events, add properties,
 - **Past tense is the Amplitude standard** — events, by definition, record things that have already happened. However, if the project is consistently using another tense, prefer consistency over the ideal.
 - Event names can be descriptive without over-specifying. A vague name like `Page Viewed` is preferable to creating a separate event for every page — use a `page_path` property to break it down. Similarly, `Error Encountered` paired with an `error_type` property is better than separate events per error. Avoid names so specific they create taxonomy noise (`Home Page Hero Banner Clicked on iPad`).
 - Use identical names across all platforms (iOS, Android, Web, server-side). Platform differences belong in a `platform` property, not the event name.
-- **Autocapture covers several common events** — do not recommend instrumenting precision tracked events for anything already captured by Autocapture: `Page Viewed`, `Element Clicked`, `Element Changed`, `Form Started`, and others. Autocapture events include additional configuration options, out-of-the-box charts, and a rich set of tested properties that precision tracked events lack.
+- **Autocapture covers a fixed set of events** — do not recommend precision-tracked equivalents for events already emitted by Amplitude Browser SDK Autocapture. The full excluded list: `[Amplitude] Page Viewed`, `[Amplitude] Start Session`, `[Amplitude] End Session`, `[Amplitude] Form Started`, `[Amplitude] Form Submitted`, `[Amplitude] File Downloaded`, `[Amplitude] Element Clicked`, `[Amplitude] Element Changed`, `[Amplitude] Rage Click`, `[Amplitude] Dead Click`, `[Amplitude] Error Click`, `[Amplitude] Thrashed Cursor`, `[Amplitude] Network Request`, and `[Amplitude] Web Vitals`. Also avoid conceptual duplicates (e.g., `Button Clicked`, `Session Started`, `Link Clicked`) — they duplicate Autocapture even without the `[Amplitude]` prefix. Autocapture events include additional configuration options, out-of-the-box charts, and a rich set of tested properties that precision-tracked events lack. Canonical source: `skills/taxonomy/amplitude-quickstart-taxonomy-agent/SKILL.md` — keep both in sync.
 
 **Property naming:**
 - Use identical property names across all events when they capture the same concept. `product_name` must be `product_name` everywhere — not `name`, `product_name`, or `prod_name` on different events.

skills/instrumentation/instrument-events/references/best-practices.md

@@ -324,7 +324,7 @@ These standards apply when helping customers design new events, add properties,
 - **Past tense is the Amplitude standard** — events, by definition, record things that have already happened. However, if the project is consistently using another tense, prefer consistency over the ideal.
 - Event names can be descriptive without over-specifying. A vague name like `Page Viewed` is preferable to creating a separate event for every page — use a `page_path` property to break it down. Similarly, `Error Encountered` paired with an `error_type` property is better than separate events per error. Avoid names so specific they create taxonomy noise (`Home Page Hero Banner Clicked on iPad`).
 - Use identical names across all platforms (iOS, Android, Web, server-side). Platform differences belong in a `platform` property, not the event name.
-- **Autocapture covers several common events** — do not recommend instrumenting precision tracked events for anything already captured by Autocapture: `Page Viewed`, `Element Clicked`, `Element Changed`, `Form Started`, and others. Autocapture events include additional configuration options, out-of-the-box charts, and a rich set of tested properties that precision tracked events lack.
+- **Autocapture covers a fixed set of events** — do not recommend precision-tracked equivalents for events already emitted by Amplitude Browser SDK Autocapture. The full excluded list: `[Amplitude] Page Viewed`, `[Amplitude] Start Session`, `[Amplitude] End Session`, `[Amplitude] Form Started`, `[Amplitude] Form Submitted`, `[Amplitude] File Downloaded`, `[Amplitude] Element Clicked`, `[Amplitude] Element Changed`, `[Amplitude] Rage Click`, `[Amplitude] Dead Click`, `[Amplitude] Error Click`, `[Amplitude] Thrashed Cursor`, `[Amplitude] Network Request`, and `[Amplitude] Web Vitals`. Also avoid conceptual duplicates (e.g., `Button Clicked`, `Session Started`, `Link Clicked`) — they duplicate Autocapture even without the `[Amplitude]` prefix. Autocapture events include additional configuration options, out-of-the-box charts, and a rich set of tested properties that precision-tracked events lack. Canonical source: `skills/taxonomy/amplitude-quickstart-taxonomy-agent/SKILL.md` — keep both in sync.
 
 **Property naming:**
 - Use identical property names across all events when they capture the same concept. `product_name` must be `product_name` everywhere — not `name`, `product_name`, or `prod_name` on different events.

skills/integration/integration-android/SKILL.md

@@ -14,15 +14,15 @@ This skill helps you add Amplitude analytics to Android applications.
 
 Follow these steps in order to complete the integration:
 
-1. `basic-integration-1.0-begin.md` - Amplitude Setup - Begin ← **Start here**
-2. `basic-integration-1.1-edit.md` - Amplitude Setup - Edit
-3. `basic-integration-1.2-revise.md` - Amplitude Setup - Revise
-4. `basic-integration-1.3-conclude.md` - Amplitude Setup - Conclusion
+1. `references/basic-integration-1.0-begin.md` - Amplitude Setup - Begin ← **Start here**
+2. `references/basic-integration-1.1-edit.md` - Amplitude Setup - Edit
+3. `references/basic-integration-1.2-revise.md` - Amplitude Setup - Revise
+4. `references/basic-integration-1.3-conclude.md` - Amplitude Setup - Conclusion
 
 ## Reference files
 
 - `references/EXAMPLE.md` - Android example project code
-- `references/android.md` - Amplitude documentation for Android
+- `references/android.md` - Android
 - `references/amplitude-quickstart.md` - Amplitude documentation for Amplitude Quickstart
 - `references/basic-integration-1.0-begin.md` - Amplitude setup - begin
 - `references/basic-integration-1.1-edit.md` - Amplitude setup - edit