What problem does it solve?
PostHog data warehouse source docs on posthog.com often become inconsistent, incomplete, or broken (404s, missing rendered fields) because each doc is written ad hoc. This Skill enforces one canonical structure so every source doc renders correctly and stays in sync with the source code.
Core Features & Use Cases
- Canonical doc template: Provides the required frontmatter (including the
sourceId that must match the ExternalDataSourceType enum) and the standard section order from intro through Troubleshooting.
- Auto-rendered components: Explains how
<SourceParameters /> and <SourceTables /> pull connection fields and table lists from the public_source_configs API, so authors never hand-write them.
- Slug and docsUrl consistency: Defines the kebab-case slug rule linking filename,
docsUrl, and listing links, plus the audit_source_docs management command that catches broken docs.
- Use Case: When adding a new Stripe-like connector, use this Skill to create
contents/docs/cdp/sources/<slug>.md with the correct snippets, frontmatter, and sections, then run the audit to verify nothing 404s.
Quick Start
Write a new documentation page for the Postgres data warehouse source following the canonical template and verify it with the audit_source_docs command.
