rudder-code-first-instrumentationlisted
Install: claude install-skill rudderlabs/rudder-agent-skills
# Code-First Instrumentation
This skill guides instrumentation planning for **existing products** where you derive tracking plans from the codebase's existing types and structures.
## When to Use This Skill
| Scenario | Use This Skill? |
|----------|-----------------|
| Existing product needs instrumentation | Yes |
| Codebase has domain types (enums, interfaces) you want to track | Yes |
| Restructuring messy existing tracking | Yes |
| Building new feature, events not yet defined | No — use `rudder-design-first-instrumentation` |
| LLM chat, AI agent or MCP server usage | No — use `rudder-ai-events-setup` (standard AI events via the AI SDKs) |
## Why Code-First?
When a product already exists, the code contains valuable type information:
- **Enums** define valid values (billing plans, user roles, feature types)
- **Interfaces** define object shapes (product, user, workspace)
- **Domain models** define relationships and constraints
Deriving tracking plans from code types:
- Eliminates translation/mapping layers
- Ensures warehouse data matches code semantics
- Enables compile-time validation of instrumentation
- Keeps tracking plan in sync with product evolution
> "If I say plan, that cannot mean many things. It's the plan. I have to be specific."
## The Code-First Workflow
```
┌─────────────────────────────────────────────────────────────────────┐
│ CODE-FIRST INSTRUMENTATION │
└─────────────────────────────────────────────