AutoGineer
Generated banner for Integration Astro View Transitions
Generated logo for Integration Astro View Transitions

Integration Astro View Transitions

PostHogOfficialCreated by PostHog

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • No issues found
Download ZIP

From the author

PostHog integration for Astro with ClientRouter view transitions
— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to integrating PostHog analytics into Astro projects that utilize the ClientRouter for view transitions. It addresses common challenges such as preventing initialization stack overflows during soft navigation and ensuring accurate pageview tracking. The guide includes best practices for component-based initialization, environment variable management, and user identification patterns.

What it does

  • Provides a reusable PostHog initialization component for Astro
  • Implements an initialization guard to prevent stack overflow errors during soft navigation
  • Configures automatic pageview tracking for SPA-like transitions
  • Outlines patterns for identifying users and tracking custom events
  • Demonstrates how to capture exceptions and errors within the application
  • Guides the setup of environment variables for secure API key management

When to use it

  • When adding PostHog analytics to an Astro project using ClientRouter
  • When you need to ensure analytics persist correctly across soft page transitions
  • When you need to track user behavior, custom events, or errors in an Astro app
  • When you want to follow established patterns for Astro and PostHog integration

Advantages

  • Prevents common initialization errors associated with Astro's view transitions
  • Ensures consistent analytics data collection across client-side navigation
  • Promotes clean, modular code through component-based integration
  • Follows security best practices by using environment variables

Usage examples

“How do I initialize PostHog in my Astro project with View Transitions?”
The agent will guide you to create a posthog.astro component with an initialization guard and import it into your layout.
“How can I track pageviews automatically during soft navigation in Astro?”
The agent will instruct you to set the capture_pageview option to 'history_change' within your PostHog initialization script.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/posthog/integration-astro-view-transitions/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip integration-astro-view-transitions.zip -d .agents/skills

Documentation by PostHog

PostHog integration for Astro (View Transitions)

This skill helps you add PostHog analytics to Astro (View Transitions) applications.

Workflow

Follow these steps in order to complete the integration:

  1. basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here

  2. basic-integration-1.1-edit.md - PostHog Setup - Edit

  3. basic-integration-1.2-revise.md - PostHog Setup - Revise

  4. basic-integration-1.3-conclude.md - PostHog Setup - Conclusion

Reference files

  • references/EXAMPLE.md - Astro (View Transitions) example project code

  • references/astro.md - Astro - docs

  • references/identify-users.md - Identify users - docs

  • references/basic-integration-1.0-begin.md - PostHog setup - begin

  • references/basic-integration-1.1-edit.md - PostHog setup - edit

  • references/basic-integration-1.2-revise.md - PostHog setup - revise

  • references/basic-integration-1.3-conclude.md - PostHog setup - conclusion

The example project shows the target implementation pattern. Consult the documentation for API details.

Key principles

  • Environment variables: Always use environment variables for PostHog keys. Never hardcode them.

  • Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.

  • Match the example: Your implementation should follow the example project's patterns as closely as possible.

Framework guidelines

  • Always use the is:inline directive on PostHog script tags to prevent Astro from processing them and causing TypeScript errors

  • Use PUBLIC_ prefix for client-side environment variables in Astro (e.g., PUBLIC_POSTHOG_PROJECT_TOKEN)

  • Create a posthog.astro component in src/components/ for reusable initialization across pages

  • Import the PostHog component in a Layout and wrap all pages with that layout

  • Wrap PostHog initialization with a window.__posthog_initialized guard to prevent stack overflow during soft navigation

  • Set capture_pageview option to 'history_change' for automatic pageview tracking during soft navigation

  • Use the astro page-load event instead of just DOMContentLoaded to re-run scripts after soft navigation

Identifying users

Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID headers to maintain correlation.

Error tracking

Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.

Files

references/basic-integration-1.2-revise.md

title: PostHog Setup - Revise description: Review and fix any errors in the PostHog integration implementation

Check the project for errors. Read the package.json file for any type checking or build scripts that may provide input about what to fix. Remember that you can find the source code for any dependency in the node_modules directory. Do not spawn subagents.

Ensure that any components created were actually used.

Once all other tasks are complete, run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Do not run formatting or linting across the entire project's codebase.

Status

Status to report in this phase:

  • Finding and correcting errors

  • Report details of any errors you fix

  • Linting, building and prettying

Upon completion, continue with: basic-integration-1.3-conclude.md

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
PostHog
Publisher
PostHog (Official)
Source
PostHog/skills · skills/posthog/integration/skills/astro-view-transitions · commit a5d30e7
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Also distributed in
PostHog/skills

AutoGineer is not affiliated with or endorsed by PostHog or PostHog.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download integration-astro-view-transitions.zip