Add Events Agent with Figma MCP integration

CLAUDE.md

@@ -12,6 +12,7 @@ When the user makes a request, identify which agent should handle it, read its S
 |---|---|---|
 | Create a dashboard, build a dashboard, set up analytics for a feature | **Dashboard Builder** | `agents/dashboard-builder/SKILL.md` |
 | Create a Linear issue, track work in Linear, file a bug/task | **Linear Issue Manager** | `agents/linear/SKILL.md` |
+| Find events, discover events, document events, validate event tracking | **Events Agent** | `agents/events-agent/SKILL.md` |
 
 If the request doesn't clearly match an agent, ask the user which they need.
 

README.md

@@ -180,10 +180,36 @@ Creates feature dashboards in Hex Threads with a 4-phase workflow:
 
 See `agents/dashboard-builder/SKILL.md` for full workflow.
 
+### Events Agent
+
+**Status:** NEW | **Trigger:** "Find events for {feature}", "Document events", "Validate event tracking"
+
+Discovers, documents, and validates events across three sources:
+- **Event Registry** — `shared/event-registry.yaml` (documented events)
+- **Codebase** — GitHub/local search for tracking code
+- **Production** — `ltxstudio_user_all_actions` table (actual events firing)
+
+**Key Features:**
+- ✓ Multi-source event discovery (registry, code, production)
+- ✓ Event schema inspection and property analysis
+- ✓ Validation reports (registry vs production comparison)
+- ✓ New event detection (events firing in last 7 days not seen before)
+- ✓ Event usage statistics (users, volume, recency)
+- ✓ Event registry documentation formatting
+
+**Common Tasks:**
+- Find all events for a feature
+- Document new events in registry format
+- Validate existing event tracking
+- Detect deprecated or missing events
+- Inspect event properties and schemas
+
+See `agents/events-agent/SKILL.md` for full workflow.
+
 ---
 
 | Agent | Status | What it does |
 |-------|--------|-------------|
-| Dashboard Builder | WIP | Creates feature dashboards in Hex Threads |
-| Linear Issue Manager | Ready | Creates and manages Linear issues for analytics work across PA teams |
 | Dashboard Builder | WIP | Creates feature dashboards in Hex Threads with automated data quality validation |
+| Linear Issue Manager | Ready | Creates and manages Linear issues for analytics work across PA teams |
+| Events Agent | NEW | Discovers, documents, and validates events from registry, code, and production data |

agents/events-agent/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: events-agent
+description: Routes event-related requests to specialized sub-agents for mapping events from designs/features or validating event tracking in production.
+tags: [events, router]
+---
+
+# Events Agent
+
+## When to use
+
+- "Map events for {feature}"
+- "Find events in design"
+- "Validate event tracking"
+- "Check if events are firing"
+- "Document events for {feature}"
+
+## What it does
+
+Routes event-related requests to specialized sub-agents:
+
+| Task Type | Sub-Agent | File |
+|-----------|-----------|------|
+| Map events from designs/features | **Map Events** | `agents/events-agent/map-events/SKILL.md` |
+| Validate event tracking in production | **Validate Events** | `agents/events-agent/validate-events/SKILL.md` |
+
+## How to route
+
+1. **Identify task type** from user request
+2. **Read the appropriate sub-agent SKILL.md**
+3. **Follow that sub-agent's workflow**
+
+## Examples
+
+| User says... | Route to... |
+|-------------|-------------|
+| "Map events for camera angle feature" | Map Events |
+| "Find events in Figma design" | Map Events |
+| "Validate timeline events are firing" | Validate Events |
+| "Check if generate_video event is tracked correctly" | Validate Events |
+| "Document events for new feature" | Map Events |
+
+## Reference files
+
+All event agents use:
+
+| File | Read when |
+|------|-----------|
+| `shared/event-registry.yaml` | Before documenting or validating events |
+| `shared/bq-schema.md` | Before querying production data |
+| `shared/product-context.md` | Before investigating features |
+
+## Rules
+
+- DO identify the task type before routing
+- DO read the sub-agent's SKILL.md completely before executing
+- DO NOT mix mapping and validation in one workflow — route separately
+- DO check event registry first before mapping or validating