metrics-tagging

# Metrics Tagging Skill Analyze a UI mockup or screenshot and produce a complete analytics event taxonomy, ready for handoff to a tag implementation team. ## Mental Model: Three Levels of Tagging Before generating the table, always frame the output across three levels. This helps designers understand *why* each tag matters — not just *what* it is. | Level | What it answers | Example | |-------|----------------|---------| | **Page** | What happened on screen | User clicked "Save" button | | **App** | What workflow is this part of | Account setup flow completion | | **Business** | Which KPI does this feed | Task completion rate, time-on-task, abandonment rate | ## Input Accept any of: - Screenshot or photo of a UI mockup - Prototype frame image - Annotated design screenshot - Description of a screen with listed components The designer may also provide: - The flow name (e.g. "Onboarding", "Checkout", "Settings", "Profile Edit") - The product type (e.g. SaaS, e-commerce, internal tool, consumer app) - Existing event naming conventions already in use - Business KPIs this flow relates to If the designer does not provide product or flow context, ask for it before generating the table. The "Purpose" column cannot be filled accurately without knowing what the flow is trying to accomplish. ## Naming Convention Use camelCase. Follow this pattern: `noun + Verb` **Format:** `[object/screen][Action]` **General examples:** - `checkoutViewed` — page load on checkout screen - `car...