Back to all skills
Analytics
Heatmap Review Analyst
Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas.
Skill summary
Difficultybeginner
Assistants12
Config files5
Copy-ready skill file
Paste this into your assistant rules file
Recommended targets: AGENTS.md, CLAUDE.md, .cursorrules, .windsurfrules, .clinerules
# Heatmap Review Analyst ## Purpose Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## When to Use Activate this skill when the user's request matches one of these scenarios: - **"heatmap review"** — Apply the Heatmap Review Analyst workflow to address this request. - **"scroll map"** — Apply the Heatmap Review Analyst workflow to address this request. - **"click map"** — Apply the Heatmap Review Analyst workflow to address this request. - **"session replay"** — Apply the Heatmap Review Analyst workflow to address this request. ## Installation ### Quick Start 1. Choose the rules file format for your AI coding assistant from the list below. 2. Copy the entire skill definition into that file. 3. Save the file in your project root directory. 4. The assistant will automatically load the rules on next interaction. ### Assistant-Specific Setup ### Claude 1. Open your project root directory. 2. Create or edit `CLAUDE.md`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Cursor 1. Open your project root directory. 2. Create or edit `.cursorrules`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Windsurf 1. Open your project root directory. 2. Create or edit `.windsurfrules`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### OpenCode 1. Open your project root directory. 2. Create or edit `AGENTS.md`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Cline 1. Open your project root directory. 2. Create or edit `.clinerules`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### GitHub Copilot 1. Open your project root directory. 2. Create or edit `.github/copilot-instructions.md`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Continue 1. Open your project root directory. 2. Create or edit `.continuerc.json`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Aider 1. Open your project root directory. 2. Create or edit `.aider.conf.yml`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Cody 1. Open your project root directory. 2. Create or edit `.cody.json`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Amazon Q 1. Open your project root directory. 2. Create or edit `.amazon-q.json`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### CodeGPT 1. Open your project root directory. 2. Create or edit `.codegpt.json`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Replit 1. Open your project root directory. 2. Create or edit `.replit`. 3. Copy the full skill definition below into that file. 4. The assistant will automatically detect and apply these rules when relevant triggers are used. ### Configuration Files - `AGENTS.md` - `CLAUDE.md` - `.cursorrules` - `.windsurfrules` - `.clinerules` ### AGENTS.md ```markdown # Heatmap Review Analyst — AI Assistant Rules # Place this file in your project root as AGENTS.md Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## Trigger Phrases # - "heatmap review" # - "scroll map" # - "click map" # - "session replay" ## Operating Mode When the user's request matches any trigger phrase above, activate the Heatmap Review Analyst workflow defined in AGENTS.md or the equivalent rules file for your assistant. ``` ### CLAUDE.md ```markdown # Heatmap Review Analyst — AI Assistant Rules # Place this file in your project root as CLAUDE.md Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## Trigger Phrases # - "heatmap review" # - "scroll map" # - "click map" # - "session replay" ## Operating Mode When the user's request matches any trigger phrase above, activate the Heatmap Review Analyst workflow defined in AGENTS.md or the equivalent rules file for your assistant. ``` ### .cursorrules ```markdown # Heatmap Review Analyst — AI Assistant Rules # Place this file in your project root as .cursorrules Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## Trigger Phrases # - "heatmap review" # - "scroll map" # - "click map" # - "session replay" ## Operating Mode When the user's request matches any trigger phrase above, activate the Heatmap Review Analyst workflow defined in AGENTS.md or the equivalent rules file for your assistant. ``` ### .windsurfrules ```markdown # Heatmap Review Analyst — AI Assistant Rules # Place this file in your project root as .windsurfrules Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## Trigger Phrases # - "heatmap review" # - "scroll map" # - "click map" # - "session replay" ## Operating Mode When the user's request matches any trigger phrase above, activate the Heatmap Review Analyst workflow defined in AGENTS.md or the equivalent rules file for your assistant. ``` ### .clinerules ```markdown # Heatmap Review Analyst — AI Assistant Rules # Place this file in your project root as .clinerules Turns click, scroll, and movement heatmaps into UX hypotheses, friction findings, and experiment ideas. ## Trigger Phrases # - "heatmap review" # - "scroll map" # - "click map" # - "session replay" ## Operating Mode When the user's request matches any trigger phrase above, activate the Heatmap Review Analyst workflow defined in AGENTS.md or the equivalent rules file for your assistant. ``` ## Operating Instructions When this skill is activated: 1. **Clarify scope** — Confirm the user's specific goal, audience, constraints, and success criteria before proceeding. 2. **Gather context** — Inspect the relevant files, pages, analytics, or interfaces to understand the current state. 3. **Apply standards** — Evaluate against established best practices for analytics. 4. **Produce concrete output** — Deliver actionable results: edited code, rewritten copy, audit findings, or implementation plans. 5. **Verify quality** — Include validation steps, edge case handling, and success metrics with every deliverable. 6. **Document decisions** — Note what was changed, why, and what trade-offs were made for future reference. ## Workflow ### Phase 1: Discovery - Identify the task type and confirm this skill is the right fit. - Gather minimum context: project type, existing conventions, user goals. - List assumptions and missing information before proceeding. ### Phase 2: Analysis - Examine the current state against analytics best practices. - Identify gaps, opportunities, and risks. - Prioritize findings by impact and effort. ### Phase 3: Execution - Produce the primary deliverable (code, copy, audit, plan). - Follow project conventions and maintain consistency. - Include before/after comparisons where relevant. ### Phase 4: Verification - Run quality checks appropriate to the deliverable type. - Confirm the output meets the user's stated goals. - Surface any remaining risks or follow-up items. ## Example Prompts - `"heatmap review"` - `"scroll map"` - `"click map"` ## Example Interaction **User:** "I need help with turns click, scroll, and movement heatmaps into ux hypotheses, friction findings, and experiment ideas." **Assistant (with Heatmap Review Analyst activated):** "I'd be happy to help with that. Let me start by understanding your specific needs: 1. What type of project or content are we working with? 2. What's the primary goal or outcome you're targeting? 3. Are there any existing constraints or conventions I should follow? 4. What's the timeframe or priority level? Once I have this context, I'll apply the Heatmap Review Analyst framework to deliver actionable results." **User:** [Provides context] **Assistant:** [Applies the skill workflow and produces concrete, verified output] ## Integration Guide Combine with **Copywriter** to A/B test analytics-driven messaging, or with **CRO Optimizer** to optimize conversion funnels. ## Verification Checklist - [ ] The assistant correctly activates this skill when relevant trigger phrases are used. - [ ] All recommendations follow the operating instructions and constraints defined. - [ ] Output includes concrete, actionable deliverables — not just analysis. - [ ] The skill file is placed in the correct location: `AGENTS.md`. - [ ] Tested with Claude to verify rule detection and behavior. - [ ] Edge cases and failure modes are documented and handled. ## Customization Guide ### Adjusting for Your Project - **Tone and voice**: Update the operating instructions to match your brand voice or technical writing style. - **Constraint specificity**: Add project-specific constraints (e.g., "Use TypeScript strict mode", "Follow BEM naming"). - **Toolchain references**: Replace generic tool references with your actual stack (e.g., "Submit a PR" → "Create a GitLab MR"). - **Success criteria**: Add custom quality checks that matter to your team. ### Scaling Across Teams Share the `AGENTS.md` file across all repositories in your organization to standardize analytics workflows. Each team can customize the trigger phrases and operating instructions without changing the core skill structure. ## Primary Use Cases - Review behavior - Find friction - Generate experiments ## Compatible Assistants - Claude - Cursor - Windsurf - OpenCode - Cline - GitHub Copilot - Continue - Aider - Cody - Amazon Q - CodeGPT - Replit ## Recommended Files - AGENTS.md - CLAUDE.md - .cursorrules - .windsurfrules - .clinerules ## Trigger Phrases - heatmap review - scroll map - click map - session replay ## Difficulty **Beginner** — No prior expertise required. Suitable for all skill levels.
Primary use cases
- Review behavior
- Find friction
- Generate experiments
Trigger phrases
heatmap reviewscroll mapclick mapsession replay
Installation guide
- 1Create a rules file in your project root:
AGENTS.md - 2Copy the skill definition (below) into that file using the Copy skill file button.
- 3The assistant will auto-detect the rules on the next interaction when trigger phrases are used.
- 4Optionally add to
AGENTS.md, CLAUDE.md, .cursorrulesfor multi-assistant support.
Compatible assistants
This skill works with 12 assistants:
ClaudeCursorWindsurfOpenCodeClineGitHub CopilotContinueAiderCodyAmazon QCodeGPTReplit
How it works
When you use a trigger phrase, the assistant activates a specialized workflow:
- Discovery — Clarifies your goal, audience, and constraints
- Analysis — Inspects current state against best practices
- Execution — Produces concrete, actionable output
- Verification — Validates quality and completeness
Best practices
- Place the rules file in every project that needs this behavior
- Customize trigger phrases to match your team's vocabulary
- Combine with complementary skills for end-to-end workflows
- Review and update rules quarterly as your processes evolve
Configuration targets
Add this skill to any of these configuration files:
AGENTS.mdCLAUDE.md.cursorrules.windsurfrules.clinerulesDifficulty level
beginner — No prior expertise required. Suitable for all skill levels.
The skill file includes trigger phrases, workflow instructions, use cases, and quality checks appropriate for this level.