rudder-instrumentation-planninglisted
Install: claude install-skill rudderlabs/rudder-agent-skills
# Instrumentation Planning
This skill guides you through designing an **instrumentation strategy** - the systematic approach to deciding what events and properties to track in your application.
LLM chat, AI agents and MCP servers have a standard event set; for those surfaces use `rudder-ai-events-setup` instead of designing custom events.
## Why Planning Matters
Poor instrumentation leads to:
- **Data gaps** - Can't answer business questions
- **Data bloat** - Too many events, high costs, noise
- **Inconsistency** - Same action tracked differently across teams
- **Technical debt** - Constant schema changes breaking dashboards
Good instrumentation provides:
- **Complete funnel visibility** - Every step from acquisition to retention
- **Consistent naming** - Clear conventions everyone follows
- **Maintainable schema** - Easy to extend, hard to break
- **Actionable insights** - Data that drives decisions
## Choose Your Workflow
Different starting points require different approaches:
| Your Situation | Recommended Skill |
|----------------|-------------------|
| Building new feature, events not yet defined | `rudder-design-first-instrumentation` |
| Existing product needs instrumentation | `rudder-code-first-instrumentation` |
| Restructuring existing tracking | `rudder-code-first-instrumentation` |
| General planning guidance | Continue with this skill |
### Design-First vs Code-First
**Design-First:** Start from product requirements → define events → define properties