
This one gets you set up with Segment's customer data platform, covering both Analytics.js for browser tracking and server-side implementation with Node. It includes patterns for tracking plan design using Object + Action naming conventions and connecting to Protocols for validation. The anti-patterns section warns against common mistakes like dynamic event names and forgetting to identify users before tracking events. The sharp edges table flags eight known issues ranging from low to high severity, though the specifics aren't detailed here. Useful if you're implementing Segment and want to avoid the usual pitfalls around identity resolution and event schema design.
$ npx -y skills add davila7/claude-code-templates --skill segment-cdp --agent claude-codeInstalls into .claude/skills of the current project.
Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user.
High-performance server-side tracking using @segment/analytics-node. Non-blocking with internal batching. Essential for backend events, webhooks, and sensitive data.
Design event schemas using Object + Action naming convention. Define required properties, types, and validation rules. Connect to Protocols for enforcement.
| Issue | Severity | Solution |
|---|---|---|
| Issue | medium | See docs |
| Issue | high | See docs |
| Issue | medium | See docs |
| Issue | high | See docs |
| Issue | low | See docs |
| Issue | medium | See docs |
| Issue | medium | See docs |
| Issue | high | See docs |
Sponsors