In brief
PostHog integration for Astro with client view transitionsRouter
What it does
- Workflow
- Reference files
- Basic principles
Who it is for, and an example
People whose task corresponds: PostHog integration for Astro with ClientRouter viewing transitionss
Example request: « PostHog Integration for Astro (See Transitions): PostHog Integration for Astro with Client View TransitionsRouter »
PostHog integration for Astro with client view transitionsRouter Example written by iadujour.fr from the SKILL.md, not tested.
Install
Claude Code : /plugin marketplace add PostHog/skills, puis /plugin install posthog-all@posthog-skills (README).
/plugin marketplace add PostHog/skills/plugin install posthog-all@posthog-skillsWorks with
- Claude Code
Source: K0: marketplace K1: K2: Other agents are not appointed.
Level: Intermediate
Supposes a project already in place at the publisher and the tools described in the K0.
Good to know
SKILL.md excerpt
The original description, which the agent reads to decide whether to load the skill (in English):
PostHog integration for Astro with ClientRouter view transitions
Quoted from SKILL.md at commit 445764b . The folder also contains 7 extra files (references/).
The SKILL.md has 57 lines and 6 main sections:
- Workflow
- Reference files
- Key principles
- Framework guidelines
- Identifying users
- Error tracking
Licence: MIT
Checked on 13 November 2026 : fichier de licence du dépôt.
The licence allows reuse: the full SKILL.md text is reproduced below, unmodified, with its licence notice.
Full SKILL.md text
Reproduced unmodified from PostHog/skills (commit 445764b) , © PostHog, under licence MIT (original licence file ).
Show the original SKILL.md (57 lines, in English)
---
name: integration-astro-view-transitions
description: PostHog integration for Astro with ClientRouter view transitions
metadata:
author: PostHog
version: 1.9.4
---
# 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.
Comments.
A field note, a question, a precision on this skill? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.