Integration Astro Hybrid — Agent Skill by PostHog

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

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/integration-astro-hybrid/download

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:

basic-integration-1.0-begin.md - PostHog Setup - Begin ← Start here
basic-integration-1.1-edit.md - PostHog Setup - Edit
basic-integration-1.2-revise.md - PostHog Setup - Revise
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

ATTRIBUTION.mdAdded by AutoGineer972 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md2.9 KiB
references/EXAMPLE.md26.8 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

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.

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 more
Apache-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 more
MITLow 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 more
MITLow 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 more
MITGitHub 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 more
MITGitHub 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 more
MITGitHub 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-hybrid.zip