← ClaudeAtlas

rudder-design-first-instrumentationlisted

Plans instrumentation for new features starting from product requirements before code exists. Use when building new features and need to define events as part of product definition.
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# Design-First Instrumentation This skill guides instrumentation planning for **new features** where events are defined during product definition, before implementation begins. ## When to Use This Skill | Scenario | Use This Skill? | |----------|-----------------| | Building a new feature, events not yet defined | Yes | | Product requirements include analytics needs | Yes | | PM and engineering collaborating on what to track | Yes | | Existing product needs instrumentation | No — use `rudder-code-first-instrumentation` | | Restructuring existing tracking | No — use `rudder-code-first-instrumentation` | | LLM chat, AI agent or MCP server usage | No — use `rudder-ai-events-setup` (standard AI events via the AI SDKs) | ## The Design-First Workflow ``` ┌─────────────────────────────────────────────────────────────────────┐ │ DESIGN-FIRST INSTRUMENTATION │ └─────────────────────────────────────────────────────────────────────┘ │ ▼ ┌─────────────────┐ │ 1. REQUIREMENTS │ ← What questions must the data answer? └────────┬────────┘ ▼ ┌─────────────────┐ │ 2. EVENT DESIGN │ ← Define events (names only, no properties yet) └────────┬────────┘ ▼ ┌─────────────────┐ │ 3. HUMAN │ ← PM/Eng review: Are these the right events? │ CHECKPOINT │ └────────┬────────┘ ▼ ┌─────────────────┐ │ 4. PROPERTY │ ← Define properties for approved events │ DESIGN │ └────────┬────────┘ ▼ ┌