Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

isolating-product-facade-contracts

Migrate a PostHog product to a facade plus contracts layer, splitting internals from presentation.

When to use it

Your product still lives under products/<name>/ but core code imports its models, logic, or views directly, and you need a step-by-step migration plan.

For example

You say

Use isolating-product-facade-contracts to migrate the web_analytics product to a facade and contracts layer, starting from a fresh scan.

You get
  • Migration phase assessment
  • Caller sweep checklist
  • PR strategy recommendation

How it works

  • Runs product:maturity, product:lint, and product:isolate:scan first to decide which migration phase you're in.
  • Covers coupling the import scan misses, like reverse accessors, signals, test fixtures, and HogQL system tables.
  • Defaults to one PR with reviewable commits, slicing by owning team only when core coupling is large.

Before installing

The product must already live under products/<name>/; moving code out of posthog/, ee/, or shared directories is out of scope.