adding-framework-support

Automate adding framework integrations to the PostHog wizard with configs, registry entries, and detection logic.

180|40|Updated Feb 25, 2025
One-click install
npx skills add https://github.com/PostHog/wizard --skill adding-framework-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-framework-support
Source: https://github.com/PostHog/wizard/tree/main/.claude/skills/adding-framework-support
Command: npx skills add https://github.com/PostHog/wizard --skill adding-framework-support

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add a new framework integration to the PostHog wizard. Use when adding support for a new language or framework (e.g. Ruby on Rails, Go, Angular). Covers creating the agent config, detection logic, registry entry, and enum/label additions.

Core Features & Use Cases

  • Add to the Integration enum and labels
  • Create the agent config file
  • Register in the framework registry
  • Create framework utilities (if needed)

Quick Start

Follow the steps above to implement a new framework integration.

Frequently Asked Questions about adding-framework-support

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new framework integration to the PostHog wizard?

To add a framework integration to the PostHog wizard, you create the agent config file, add an entry to the Integration enum and labels, and register the new framework in the framework registry.

What is framework detection logic and how does it work in the wizard?

Framework detection logic in the PostHog wizard identifies the target project environment using a data-driven architecture with detection hooks and optional utilities, enabling automatic project type detection.

Can I use the wizard to add support for languages like Go or Ruby on Rails?

Yes, the wizard supports adding integration for languages and frameworks such as Go, Ruby on Rails, and Angular by updating the FrameworkConfig metadata and registry mappings.

What's the best way to configure FrameworkConfig metadata for a new integration?

The best way to configure FrameworkConfig metadata is to follow the wizard's data-driven architecture, creating configuration files and detection hooks while adding the necessary enum and label entries.

Do I need to create framework utilities when adding an integration?

Creating framework utilities is an optional step when adding an integration, used specifically for advanced project type detection and environment handling if required by the new framework.