docs: Add handbook page on contributing to docs for CS team by ceyniustranberg · Pull Request #15320 · PostHog/posthog.com

ceyniustranberg · 2026-02-26T09:09:46Z

Explains the context flywheel, wizard, and skills architecture so CS team members understand how their handbook contributions power AI-assisted customer onboarding.

Changes

Please describe.

Add screenshots or screen recordings for visual / UI-focused changes.

Checklist

I've read the docs and/or content style guides.
Words are spelled using American English
Use relative URLs for internal links
I've checked the pages added or changed in the Vercel preview build
If I moved a page, I added a redirect in vercel.json

Explains the context flywheel, wizard, and skills architecture so CS team members understand how their handbook contributions power AI-assisted customer onboarding. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

vercel · 2026-02-26T09:09:51Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
posthog	Ready	Preview	Feb 26, 2026 4:54pm

github-actions · 2026-02-26T09:10:00Z

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Feb 26, 2026 04:56PM

github-actions · 2026-02-26T09:10:43Z

Vale prose linter → found 6 errors, 7 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/handbook/growth/sales/contributing-to-docs.md — 6 errors, 7 warnings, 0 suggestions

Line	Severity	Message	Rule
7:73	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`
9:120	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`
13:72	warning	Use 'InKeep' instead of 'Inkeep'.	`Vale.Terms`
20:114	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`
74:51	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`
78:3	warning	Capitalize 'Product Analytics' for PostHog's product. Use 'Product analytics' for the general industry concept.	`PostHogBase.ProductNames`
80:3	warning	Capitalize 'Session Replay' for PostHog's product. Use 'Session replay' for the general industry concept.	`PostHogBase.ProductNames`
81:3	warning	Capitalize 'Error Tracking' for PostHog's product. Use 'Error tracking' for the general industry concept.	`PostHogBase.ProductNames`
83:14	warning	Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept.	`PostHogBase.ProductNames`
83:29	warning	Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept.	`PostHogBase.ProductNames`
83:61	warning	Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept.	`PostHogBase.ProductNames`
97:63	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`
106:70	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	`PostHogBase.EnDash`

gewenyu99

Awesome!

Just a note that the Wizard is a proper noun to us 😆 🧙

gewenyu99 · 2026-02-26T20:18:24Z

contents/handbook/growth/sales/contributing-to-docs.md

+showTitle: true
+---
+
+Our documentation is a critical piece of PostHog's **context flywheel** — a system that connects our codebase to our docs, which then feeds into our AI agents and the [wizard](/handbook/docs-and-wizard/developing-the-wizard). When documentation is outdated, the agents that help customers integrate PostHog become outdated too.


Suggested change

Our documentation is a critical piece of PostHog's **context flywheel** — a system that connects our codebase to our docs, which then feeds into our AI agents and the [wizard](/handbook/docs-and-wizard/developing-the-wizard). When documentation is outdated, the agents that help customers integrate PostHog become outdated too.

Our documentation is a critical piece of PostHog's **context flywheel** — a system that connects our codebase to our docs, which then feeds into our AI agents and the [Wizard](/handbook/docs-and-wizard/developing-the-wizard). When documentation is outdated, the agents that help customers integrate PostHog become outdated too.

I know it's not out yet, but Twig (or what ever it's called later) is also a consumer

gewenyu99 · 2026-02-26T20:24:48Z

contents/handbook/growth/sales/contributing-to-docs.md

+- **Show examples**: Real code snippets and configurations help
+- **Explain the "why"**: Context about when to use something helps the AI apply it correctly
+- **Use clear structure**: Headers, bullet points, and numbered steps work better than walls of text
+


Good to attach an example, such as logs.

It's as simple as a root prompt:
https://github.com/PostHog/context-mill/blob/main/transformation-config/skills/logs/description.md
and some reference material:
https://github.com/PostHog/context-mill/blob/main/transformation-config/skills/logs/config.yaml

gewenyu99 · 2026-02-26T20:25:50Z

contents/handbook/growth/sales/contributing-to-docs.md

+
+When you write something down, ask: "Could an agent do this automatically?"
+
+For example, if you write a playbook for gathering a customer dossier, that could become an automated web search agent task. If you document how to identify cross-sell opportunities, that becomes a skill the wizard can use.


YES. We can ship these so fast that sometimes it's easier to ship a skill and send that to your customer to run in the afternoon.

That's the vision at least ;)

gewenyu99 · 2026-02-26T20:42:03Z

contents/handbook/growth/sales/contributing-to-docs.md

+- Session replay
+- Error tracking
+
+Coming soon: feature flags, experiments, LLM analytics, and logs.


I think LLMA and Logs support is already out. @daniloc Is it a separate skill rn or does it happen in the main loop?

gewenyu99 · 2026-02-26T20:42:19Z

contents/handbook/growth/sales/contributing-to-docs.md

+
+### Close the gap in customer conversations
+
+The wizard and skills architecture lets you close the gap between customer-facing hypotheticals and technical diagnostics without needing engineering present. If a customer asks "how would I track X?", you can point them to the wizard or a specific skill.


Suggested change

The wizard and skills architecture lets you close the gap between customer-facing hypotheticals and technical diagnostics without needing engineering present. If a customer asks "how would I track X?", you can point them to the wizard or a specific skill.

The Wizard and skills architecture lets you close the gap between customer-facing hypotheticals and technical diagnostics without needing engineering present. If a customer asks "how would I track X?", you can point them to the wizard or a specific skill.

;)

gewenyu99 · 2026-02-26T20:47:19Z

contents/handbook/growth/sales/contributing-to-docs.md

+
+If customers are hesitant to run an agent on their codebase, they can receive the open-source skills package directly. This gives them 80-95% of the wizard's functionality to run locally with their own tools.
+
+### Better onboarding


I propose something like:

Run the Wizard first

Review what ever it did together with the customer

Come up with a plan + tweaks.

I think the best value here is to get past that blank page. It's much easier to iterate!

edwinyjlim

let's gooo

we'll need to update this handbook page again when #team-docs-and-wizard gives y'all proper tools to create and experiment with skills! coming soon!

edwinyjlim · 2026-02-27T19:09:13Z

contents/handbook/growth/sales/contributing-to-docs.md

+
+## Why your contributions matter
+
+The docs team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:


Suggested change

The docs team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:

The <SmallTeam slug="docs-wizard" /> team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:

edwinyjlim · 2026-02-27T19:15:47Z

contents/handbook/growth/sales/contributing-to-docs.md

@@ -0,0 +1,108 @@
+---
+title: Contributing to docs


I'd make the title skill oriented, kind of like actionable writing

Suggested change

title: Contributing to docs

title: Creating agents skills from docs

Suggested change

title: Contributing to docs

title: Turning knowledge into agent skills

edwinyjlim · 2026-02-27T19:20:57Z

contents/handbook/growth/sales/contributing-to-docs.md

+## The wizard and how it helps customers
+
+The [AI wizard](/handbook/docs-and-wizard/developing-the-wizard) is a one-line `npx` command that runs an agent to integrate PostHog:
+
+```bash
+npx -y @posthog/wizard@latest
+```
+
+Here's what it does automatically:
+- Installs the right SDKs for their stack
+- Scans their codebase to understand their product
+- Creates 10-15 custom events based on product flows it identifies
+- Writes both client-side and server-side code for full-stack implementations
+- Creates an insight and dashboard in PostHog
+
+This dramatically reduces manual integration work — what might take 3-5 hours happens in minutes. And it produces customized code tailored to each customer's setup.


This transition is a bit abrupt. I think we need a brief sentence or two that explains how the wizard uses the skills we produce at PostHog! It's a great example of agentic software that runs on our docs. We can just write things down and the wizard can execute skill as software. It's like magic!

docs: Add handbook page on contributing to docs for CS team

ea0e90f

Explains the context flywheel, wizard, and skills architecture so CS team members understand how their handbook contributions power AI-assisted customer onboarding. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

ceyniustranberg requested review from daniloc, edwinyjlim, gewenyu99 and sarahxsanders February 26, 2026 09:09

vercel bot deployed to Preview February 26, 2026 09:20 View deployment

Reorganize 'Contributing to docs' link in navigation

2d5c6d9

vercel bot deployed to Preview February 26, 2026 16:54 View deployment

gewenyu99 approved these changes Feb 26, 2026

View reviewed changes

edwinyjlim approved these changes Feb 27, 2026

View reviewed changes

	Our documentation is a critical piece of PostHog's context flywheel — a system that connects our codebase to our docs, which then feeds into our AI agents and the [wizard](/handbook/docs-and-wizard/developing-the-wizard). When documentation is outdated, the agents that help customers integrate PostHog become outdated too.
	Our documentation is a critical piece of PostHog's context flywheel — a system that connects our codebase to our docs, which then feeds into our AI agents and the [Wizard](/handbook/docs-and-wizard/developing-the-wizard). When documentation is outdated, the agents that help customers integrate PostHog become outdated too.


		When you write something down, ask: "Could an agent do this automatically?"

		For example, if you write a playbook for gathering a customer dossier, that could become an automated web search agent task. If you document how to identify cross-sell opportunities, that becomes a skill the wizard can use.


		### Close the gap in customer conversations

		The wizard and skills architecture lets you close the gap between customer-facing hypotheticals and technical diagnostics without needing engineering present. If a customer asks "how would I track X?", you can point them to the wizard or a specific skill.


		If customers are hesitant to run an agent on their codebase, they can receive the open-source skills package directly. This gives them 80-95% of the wizard's functionality to run locally with their own tools.

		### Better onboarding


		## Why your contributions matter

		The docs team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:

	The docs team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:
	The <SmallTeam slug="docs-wizard" /> team has automated writing documentation from PR merges using Inkeep, which indexes our codebase and docs to create first-pass drafts. But there's knowledge that only comes from working directly with customers:

	title: Contributing to docs
	title: Creating agents skills from docs

	title: Contributing to docs
	title: Turning knowledge into agent skills

Conversation

ceyniustranberg commented Feb 26, 2026

Changes

Checklist

Uh oh!

vercel bot commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploy preview

Uh oh!

github-actions bot commented Feb 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gewenyu99 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

edwinyjlim left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vercel bot commented Feb 26, 2026 •

edited

Loading

github-actions bot commented Feb 26, 2026 •

edited

Loading

github-actions bot commented Feb 26, 2026 •

edited

Loading