AutoGineer
Generated banner for Integration Astro Static
Generated logo for Integration Astro Static

Integration Astro Static

PostHogOfficialCreated by PostHog

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

From the author

PostHog integration for static Astro sites using SSG
— 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 adding PostHog analytics, session replay, and error tracking to static Astro (SSG) applications. It emphasizes a modular implementation using a dedicated Astro component to manage the PostHog web snippet, ensuring proper initialization and avoiding common framework-specific issues like TypeScript errors during build time.

What it does

  • Provides a step-by-step workflow for PostHog integration
  • Defines a reusable posthog.astro component for initialization
  • Demonstrates user identification patterns for login flows
  • Shows how to capture custom events and track errors
  • Includes guidance on managing session resets during logout
  • Enforces best practices for environment variable usage

When to use it

  • When you need to add PostHog analytics to an Astro static site
  • When you want to implement session replay or error tracking in Astro
  • When you need a standardized pattern for user identification in Astro
  • When you are setting up a new Astro project and require analytics integration

Advantages

  • Prevents build-time errors using the is:inline directive
  • Promotes clean code through reusable component architecture
  • Ensures secure handling of project tokens via environment variables
  • Provides clear patterns for both frontend and backend correlation

Usage examples

“How do I initialize PostHog in my static Astro project?”
The agent will guide you to create a src/components/posthog.astro file using the is:inline directive to safely embed the PostHog snippet.
“How should I track user logins in my Astro app?”
The agent will show you how to use window.posthog.identify() and window.posthog.capture() within your login page logic.

Install

  1. Download the skill as a ZIP:

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

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

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

Documentation by PostHog

PostHog integration for Astro (Static)

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

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.0-begin.md

title: PostHog Setup - Begin description: Start the event tracking setup process by analyzing the project and creating an event tracking plan

We're making an event tracking plan for this project.

Before proceeding, find any existing posthog.capture() code. Make note of event name formatting.

From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events. Also look for additional files related to login that could be used for identifying users, along with error handling. Read the files. If a file is already well-covered by PostHog events, replace it with another option. Do not spawn subagents.

Look for opportunities to track client-side events.

IMPORTANT: Server-side events are REQUIRED if the project includes any instrumentable server-side code. If the project has API routes (e.g., app/api/**/route.ts) or Server Actions, you MUST include server-side events for critical business operations like:

  • Payment/checkout completion

  • Webhook handlers

  • Authentication endpoints

Do not skip server-side events - they capture actions that cannot be tracked client-side.

Create a new file with a JSON array at the root of the project: .posthog-events.json. It should include one object for each event we want to add: event name, event description, and the file path we want to place the event in. If events already exist, don't duplicate them; supplement them.

Track actions only, not pageviews. These can be captured automatically. Exceptions can be made for "viewed"-type events that correspond to the top of a conversion funnel.

As you review files, make an internal note of opportunities to identify users and catch errors. We'll need them for the next step.

Status

Before beginning a phase of the setup, you will send a status message with the exact prefix '[STATUS]', as in:

[STATUS] Checking project structure.

Status to report in this phase:

  • Checking project structure

  • Verifying PostHog dependencies

  • Generating events based on project

Upon completion, continue with: basic-integration-1.1-edit.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-static · 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-static.zip