AutoGineer
Generated banner for Integration Astro Hybrid
Generated logo for Integration Astro Hybrid

Integration Astro Hybrid

PostHogOfficialCreated by PostHog

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

From the author

PostHog integration for Astro hybrid rendering with both static and server-rendered pages
— 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 implementing PostHog analytics in Astro projects using hybrid rendering. It covers both client-side tracking via the PostHog web snippet and server-side event tracking using posthog-node. The guide emphasizes maintaining session continuity between static and server-rendered pages, proper environment variable management, and the use of singleton patterns for server-side clients.

What it does

  • Configures PostHog for Astro hybrid rendering environments.
  • Implements client-side tracking using a reusable Astro component.
  • Sets up server-side event tracking in API routes using posthog-node.
  • Provides patterns for maintaining session IDs across client and server boundaries.
  • Guides the configuration of Astro hybrid mode with per-page SSR opt-in.
  • Includes best practices for environment variable usage and script directive handling.

When to use it

  • When you need to add analytics to an Astro project using hybrid rendering.
  • When you require both client-side browser analytics and server-side API event tracking.
  • When you need to maintain consistent user sessions across static and SSR pages.
  • When you want to follow established patterns for PostHog integration in Astro 5.

Advantages

  • Ensures consistent tracking across hybrid rendering modes.
  • Prevents common Astro-specific integration errors like script processing issues.
  • Promotes clean code through singleton patterns and reusable components.
  • Maintains session correlation between frontend and backend events.

Usage examples

“How do I set up PostHog in my Astro hybrid project?”
The agent will guide you through creating a posthog.astro component, configuring your environment variables, and setting up the posthog-node singleton for server-side tracking.
“How do I track events from an Astro API route?”
The agent will show you how to import the posthog-node singleton and use it within your API route handlers to capture server-side events.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/posthog/integration-astro-hybrid/download

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

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

Documentation by PostHog

PostHog integration for Astro (Hybrid)

This skill helps you add PostHog analytics to Astro (Hybrid) 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 (Hybrid) 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

  • Use posthog-node in API routes under src/pages/api/ for server-side event tracking

  • Store the posthog-node client instance in a singleton pattern (src/lib/posthog-server.ts) to avoid creating multiple clients

  • In Astro 5, use output static (the default) with an adapter - pages are prerendered by default

  • Use export const prerender = false to opt specific pages into SSR when they need server-side rendering

  • Only pages that need server-side PostHog tracking (like API-backed forms) should opt out of prerendering

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.1-edit.md

title: PostHog Setup - Edit description: Implement PostHog event tracking in the identified files, following best practices and the example project

For each of the files and events noted in .posthog-events.json, make edits to capture events using PostHog. Make sure to set up any helper files needed. Carefully examine the included example project code: your implementation should match it as closely as possible. Do not spawn subagents.

Use environment variables for PostHog keys. Do not hardcode PostHog keys.

If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it.

For each event, add useful properties, and use your access to the PostHog source code to ensure correctness. You also have access to documentation about creating new events with PostHog. Consider this documentation carefully and follow it closely before adding events. Your integration should be based on documented best practices. Carefully consider how the user project's framework version may impact the correct PostHog integration approach.

Remember that you can find the source code for any dependency in the node_modules directory. This may be necessary to properly populate property names. There are also example project code files available via the PostHog MCP; use these for reference.

Where possible, add calls for PostHog's identify() function on the client side upon events like logins and signups. Use the contents of login and signup forms to identify users on submit. If there is server-side code, pass the client-side session and distinct ID to the server-side code to identify the user. On the server side, make sure events have a matching distinct ID where relevant.

It's essential to do this in both client code and server code, so that user behavior from both domains is easy to correlate.

You should also add PostHog exception capture error tracking to these files where relevant.

Remember: Do not alter the fundamental architecture of existing files. Make your additions minimal and targeted.

Remember the documentation and example project resources you were provided at the beginning. Read them now.

Status

Status to report in this phase:

  • Inserting PostHog capture code

  • A status message for each file whose edits you are planning, including a high level summary of changes

  • A status message for each file you have edited

Upon completion, continue with: basic-integration-1.2-revise.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.

Needs: Needs Node.js

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-hybrid · 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.

Download ZIP

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