Integration Astro View Transitions
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/integration-astro-view-transitions/downloadUnzip 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:
basic-integration-1.0-begin.md- PostHog Setup - Begin ← Start herebasic-integration-1.1-edit.md- PostHog Setup - Editbasic-integration-1.2-revise.md- PostHog Setup - Revisebasic-integration-1.3-conclude.md- PostHog Setup - Conclusion
Reference files
references/EXAMPLE.md- Astro (View Transitions) example project codereferences/astro.md- Astro - docsreferences/identify-users.md- Identify users - docsreferences/basic-integration-1.0-begin.md- PostHog setup - beginreferences/basic-integration-1.1-edit.md- PostHog setup - editreferences/basic-integration-1.2-revise.md- PostHog setup - revisereferences/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
- ATTRIBUTION.mdAdded by AutoGineer1002 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.8 KiB
- references/EXAMPLE.md23.1 KiB
- references/astro.md8.3 KiB
- references/basic-integration-1.0-begin.md2.1 KiB
- references/basic-integration-1.1-edit.md2.5 KiB
- references/basic-integration-1.2-revise.md937 B
- references/basic-integration-1.3-conclude.md1.6 KiB
- references/identify-users.md8.1 KiB
SKILL.md
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:
basic-integration-1.0-begin.md- PostHog Setup - Begin ← Start herebasic-integration-1.1-edit.md- PostHog Setup - Editbasic-integration-1.2-revise.md- PostHog Setup - Revisebasic-integration-1.3-conclude.md- PostHog Setup - Conclusion
Reference files
references/EXAMPLE.md- Astro (View Transitions) example project codereferences/astro.md- Astro - docsreferences/identify-users.md- Identify users - docsreferences/basic-integration-1.0-begin.md- PostHog setup - beginreferences/basic-integration-1.1-edit.md- PostHog setup - editreferences/basic-integration-1.2-revise.md- PostHog setup - revisereferences/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.
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.
Related skills
Claude API
AnthropicOfficial
Comprehensive reference for integrating Anthropic's Claude API, SDKs, and Managed Agents into your applications.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0Medium riskHas scriptsGitHub stars of the source repository188.6k
Transformers
K-Dense· Community
Integrate Hugging Face Transformers for model loading, inference, and fine-tuning across NLP, vision, and audio tasks.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskGitHub stars of the source repository56.4k
Open Notebook
K-Dense· Community
Integrate with the self-hosted Open Notebook platform to automate research ingestion, context-aware chat, and AI-driven analysis.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository56.4k
Vision Sft
Seth Hobson· Community
A structured workflow for supervised fine-tuning of vision-language models, focusing on adapter configuration and silent failure prevention.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
LLM Evaluation
Seth Hobson· Community
A comprehensive framework for evaluating LLM application performance using automated metrics, human feedback, and LLM-as-a-judge techniques.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Lora Qlora Recipes
Seth Hobson· Community
Provides configuration recipes and best-practice hyperparameters for LoRA and QLoRA supervised fine-tuning.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download integration-astro-view-transitions.zip