Prompts / tracking_plan
Tracking plan for a design or product Free
Turns a flow or a product into an analytics tracking plan with named events, properties, funnels and the questions each answers, then lints it.
Run it
- Claude Code:
/mcp__designers__tracking_plan - Claude Desktop and claude.ai: plus menu, Add from Designers, Tracking plan for a design or product
- Any app: Use the tracking_plan prompt from the Designers server on the product or flow, or a figma link.
Arguments
| Name | Meaning |
|---|---|
product * | The product or flow, or a Figma link |
questions | The questions the team wants analytics to answer |
type | saas, ecommerce, marketplace, content or mobile |
* required
What your assistant is told to do
The full instructions, so you can see exactly what you are asking for:
Write a tracking plan. Start from the questions, then name the events.
Product or flow: <product>
Questions: <questions>
Type: <type>
Method:
1. Read resource designers://reference/tracking-plan-naming. If the person gave a product type, call lint_tracking_plan with productType for a starter and adapt it; do not paste it unchanged.
2. If given a Figma link: If the input is a Figma link: parse it (figma.com/design/:fileKey/..., node-id=1-2 means nodeId "1:2"), call get_metadata to see the frames, get_screenshot for each frame you will judge, and get_design_context for layout, text and tokens. Read the picture before the code. If the Figma tools are not connected, say so and ask for screenshots or exported frames instead; do not guess at what is in the file. Mark on each frame the moments worth recording and the states (empty, error, success).
3. List the questions the business will ask (activation, drop-off between steps, which feature predicts retention). If none were given, propose five and ask for confirmation.
4. For each question list the events and properties needed. Name events object then past-tense verb in snake_case; put variation in properties; no UI element names; no personal data in properties.
5. Produce the table: event, exact trigger, properties with type and allowed values, question it answers.
6. Call lint_tracking_plan on the event list and fix every high and medium finding.
7. Add: the funnels to build first, the standard properties to attach everywhere, and what is deliberately not tracked and why.