product-tracking-generate-implementation-guide

Name: product-tracking-generate-implementation-guide
Author: Accoil

24installs4forks

How to install product-tracking-generate-implementation-guide?

accoil/product-tracking-skills/product-tracking-generate-implementation-guide

$npx -y skills add Accoil/product-tracking-skills --skill product-tracking-generate-implementation-guide

Installs into the current project.

Summary

Translate a tracking plan into an SDK-specific instrumentation guide. Shows how to make identify, group, and track calls using the target analytics SDK with real template code, architecture guidance, and constraint documentation. Outputs .telemetry/instrument.md. Covers 24 analyt

Files · 1

View on GitHub

SKILL.md

1	# Instrument
2
3	You are a product telemetry engineer producing an SDK-specific instrumentation guide. You show how to make the three core analytics calls — identify, group, track — using the target SDK, with real template code and group hierarchy guidance.
4
5	This is a how-to guide, not a catalog. You don't repeat every event from the tracking plan. You show the patterns, the SDK syntax, and the constraints — then the implementation phase applies those patterns to the full event list.
6
7	## References
8
9	Read the matching destination reference before producing anything. References are organized by category.
10
11	### Product Analytics & CDPs (full identify → group → track support)
12
13	- Segment: [references/segment.md](references/segment.md)
14	- Amplitude: [references/amplitude.md](references/amplitude.md)
15	- Mixpanel: [references/mixpanel.md](references/mixpanel.md)
16	- PostHog: [references/posthog.md](references/posthog.md)
17	- RudderStack: [references/rudderstack.md](references/rudderstack.md)
18
19	### B2B Engagement Platforms
20
21	- Accoil: [references/accoil.md](references/accoil.md)
22	- Intercom: [references/intercom.md](references/intercom.md)
23	- Journy: [references/journy.md](references/journy.md)
24
25	### Full-Stack & Web Analytics
26
27	- Google Analytics (GA4): [references/google-analytics.md](references/google-analytics.md)
28	- Usermaven: [references/usermaven.md](references/usermaven.md)
29	- Plausible: [references/plausible.md](references/plausible.md)
30	- Fathom: [references/fathom.md](references/fathom.md)
31	- Simple Analytics: [references/simple-analytics.md](references/simple-analytics.md)
32	- Beam Analytics: [references/beam-analytics.md](references/beam-analytics.md)
33	- Microanalytics: [references/microanalytics.md](references/microanalytics.md)
34	- Cabin (WithCabin): [references/withcabin.md](references/withcabin.md)
35	- Cloudflare Web Analytics: [references/cloudflare-web-analytics.md](references/cloudflare-web-analytics.md)
36
37	### Error & Performance Monitoring
38
39	- Sentry: [references/sentry.md](references/sentry.md)
40	- New Relic: [references/new-relic.md](references/new-relic.md)
41	- Azure Application Insights: [references/azure-application-insights.md](references/azure-application-insights.md)
42
43	### Feature Flags & Experimentation
44
45	- LaunchDarkly: [references/launchdarkly.md](references/launchdarkly.md)
46	- Statsig: [references/statsig.md](references/statsig.md)
47
48	### Session & Behavior Tools
49
50	- HotJar: [references/hotjar.md](references/hotjar.md)
51	- UserPilot: [references/userpilot.md](references/userpilot.md)
52
53	### Tag Management
54
55	- Google Tag Manager: [references/google-tag-manager.md](references/google-tag-manager.md)
56
57	### Platform & Architecture
58
59	- Forge platform: [references/forge-platform.md](references/forge-platform.md)
60	- Generic HTTP architecture: [references/generic-http-architecture.md](references/generic-http-architecture.md)
61
62	Not every destination supports the full identify → group → track model. Web analytics tools (Plausible, Fathom, etc.) track page views and simple events only. Error monitoring tools (Sentry, New Relic) provide user context for debugging, not product analytics. Feature flag tools (LaunchDarkly, Statsig) manage targeting context and experiment exposure. Each reference file documents what the tool supports and what it doesn't.
63
64	### Supporting Files
65
66	- Output template: [references/output-template.md](references/output-template.md)
67	- Behavioral rules: [references/behavioral-rules.md](references/behavioral-rules.md)
68	- Destination reference template: [references/destination-reference-template.md](references/destination-reference-template.md) — follow this when adding new destinations
69
70	## Goal
71
72	Produce `.telemetry/instrument.md` — an SDK-specific guide covering the three core calls (identify, group, track) with real template code. This file becomes the contract that the implementation phase follows.
73
74	## Prerequisites
75
76	Check before starting:
77
78	1. `.telemetry/tracking-plan.yaml` (required) — The tracking plan defines entities, groups, and events. If it doesn't exist, stop and tell the user: *"I need a tracking plan to generate instrumentation guidanc

People who liked this also viewed

6 picks

Type