feat(agents): add agents content type, built and served alongside skills

context/agents/README.md

@@ -0,0 +1,37 @@
+# Agent prompts
+
+One `<type>.md` per orchestrator task — the WHAT of the task. The frontmatter
+carries the artifacts the executor configures the run with: the model, the
+mini-skills to load (the HOW), the tools the task may and may not use, and the
+tasks it depends on. `flow` names the program the agent belongs to — the
+wizard's registry is scoped per flow, so audit or migration agents live
+alongside these — and one prompt per flow is marked `seed: true`: the planner
+that seeds the queue, not an enqueueable task type.
+
+The body is intent only — what to do and what done looks like. The client
+injects the basics (project context, how to report, how to surface progress),
+so a prompt never restates them.
+
+This README is documentation, not data: the build serves every other `.md` in
+this folder as an agent prompt.
+
+```markdown
+---
+type: example
+flow: my-flow
+model: claude-haiku-4-5-20251001
+skills: []
+allowedTools: [Read, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: []
+---
+
+## Goal
+
+What this task does, in plain prose.
+
+## How you know you succeeded
+
+Plain-text success criteria live here. State what done looks like, and what to
+do when the task cannot be completed.
+```

context/agents/build.md

@@ -0,0 +1,25 @@
+---
+type: build
+flow: posthog-integration
+label: Install dependencies and build
+model: claude-sonnet-4-6
+skills: [basic-integration-build]
+allowedTools: [Read, Edit, Glob, Grep, Bash]
+disallowedTools: [enqueue_task]
+dependsOn: [install, init, identify, error-tracking, capture]
+---
+
+## Goal
+
+Bring the integration together: install the dependencies the earlier steps
+declared, then verify the project builds, lints, and passes its tests. Until now
+the steps only edited code and the manifest — this is where it actually installs
+and is checked.
+
+## How you know you succeeded
+
+The install completes and the build, lint, and tests pass. If you hit a conflict
+you cannot cleanly resolve — a dependency clash, a build error from the new code —
+fix what you safely can, then report it: put a one-line summary in your handoff's
+`conflict` field and the full detail in what you did. The user sees the one-liner
+in the outro and the detail in the report.

context/agents/capture.md

@@ -0,0 +1,22 @@
+---
+type: capture
+flow: posthog-integration
+label: Capture events
+model: claude-sonnet-4-6
+skills: [basic-integration-capture]
+allowedTools: [Read, Edit, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: [install, init]
+---
+
+## Goal
+
+Decide which events are worth capturing in this app, then instrument them in the
+same pass — read each file once, choose the events, and add the capture calls
+while the file is already open.
+
+## How you know you succeeded
+
+The meaningful user actions across the app have capture calls that fire on the
+real action, not on page load, and `.posthog-wizard-cache/.posthog-events.json`
+lists the events you instrumented.

context/agents/dashboard.md

@@ -0,0 +1,20 @@
+---
+type: dashboard
+flow: posthog-integration
+label: Create a starter dashboard
+model: claude-sonnet-4-6
+skills: [basic-integration-dashboard]
+allowedTools: [Read, Glob, Grep]
+disallowedTools: [Write, Edit, Bash, enqueue_task]
+dependsOn: [build]
+---
+
+## Goal
+
+Create a starter PostHog dashboard with a few insights built on the events this
+integration instruments, using the PostHog MCP.
+
+## How you know you succeeded
+
+A dashboard exists with a handful of insights on the captured events, and you hand
+off its URL for the report to link.

context/agents/error-tracking.md

@@ -0,0 +1,28 @@
+---
+type: error-tracking
+flow: posthog-integration
+label: Add error tracking
+model: claude-sonnet-4-6
+skills: [basic-integration-error-tracking-step]
+allowedTools: [Read, Write, Edit, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: [install, init]
+---
+
+## Goal
+
+Set up the framework's single global error boundary so uncaught errors reach
+PostHog. One place — the init or app entry — following the docs and the reference
+example, not manual capture calls sprinkled across files. The SDK is already
+installed and initialized (see the context from previous steps); build on that,
+do not re-check it.
+
+This is an instrument-only task. Do not install dependencies, run the build, run
+tests, or start the app — a later `build` step does all verification. Stay inside
+this project's directory and edit the one global handler; that is the whole job.
+
+## How you know you succeeded
+
+A global error handler forwards exceptions to PostHog. You did not install
+anything, run a build or tests, search outside the project, or read through the
+whole app or hand-wrap individual components or routes.

context/agents/identify.md

@@ -0,0 +1,20 @@
+---
+type: identify
+flow: posthog-integration
+label: Wire user identification
+model: claude-sonnet-4-6
+skills: [basic-integration-identify]
+allowedTools: [Read, Edit, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: [install, init]
+---
+
+## Goal
+
+Wire user identification: call PostHog identify wherever the app establishes who
+the user is, typically at login and signup.
+
+## How you know you succeeded
+
+An identify call fires at the point the user becomes known, with a stable
+distinct id. If the app has no auth or user concept, say so and stop.

context/agents/init.md

@@ -0,0 +1,21 @@
+---
+type: init
+flow: posthog-integration
+label: Set up PostHog initialization
+model: claude-haiku-4-5-20251001
+skills: [basic-integration-init]
+allowedTools: [Read, Write, Edit, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: []
+---
+
+## Goal
+
+Initialize PostHog: create the framework's init point so the SDK is configured
+once and available across the app, and set the PostHog environment variables
+through the wizard tools.
+
+## How you know you succeeded
+
+The init file exists and the PostHog env keys are present. Keys live in the env
+file, never hardcoded in source.

context/agents/install.md

@@ -0,0 +1,21 @@
+---
+type: install
+flow: posthog-integration
+label: Add the PostHog SDK to the manifest
+model: claude-haiku-4-5-20251001
+skills: [basic-integration-install]
+allowedTools: [Read, Edit, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: []
+---
+
+## Goal
+
+Declare the PostHog SDK in the project's package manifest. Do not run the package
+manager and do not build — the build task installs and verifies everything at the
+end.
+
+## How you know you succeeded
+
+The SDK is listed in the manifest's dependencies at a sensible version. If it is
+already declared, leave it and say so.

context/agents/integrate-posthog.md

@@ -0,0 +1,31 @@
+---
+type: integrate-posthog
+flow: posthog-integration
+seed: true
+model: claude-sonnet-4-6
+skills: []
+allowedTools: [Read, Glob, Grep]
+disallowedTools: [Write, Edit, Bash, complete_task]
+dependsOn: []
+---
+
+## Goal
+
+Plan a PostHog integration and seed the task queue with this graph:
+
+- `install` and `init`, independent of each other.
+- `identify`, `capture`, and `error-tracking`, each after `install` and `init`
+  and independent of one another, so they run in parallel. `capture` decides the
+  events and instruments them; `error-tracking` wires the single global error
+  boundary — it needs the SDK installed and initialized, not the events.
+- `build`, after `install`, `init`, `identify`, `capture`, and `error-tracking` —
+  it installs the dependencies and verifies the project builds, lints, and passes
+  its tests.
+- `dashboard`, after `build` — only once the integration is confirmed building,
+  linting, and testing cleanly.
+- `report`, after `dashboard` — it writes the setup report last.
+
+## How you know you succeeded
+
+Every task in the graph is queued with that dependency shape, the report last,
+and the first task runnable. Keep labels short — the action in a few words.

context/agents/report.md

@@ -0,0 +1,23 @@
+---
+type: report
+flow: posthog-integration
+label: Write the setup report
+model: claude-sonnet-4-6
+skills: [basic-integration-report]
+allowedTools: [Read, Write, Glob, Grep]
+disallowedTools: [enqueue_task]
+dependsOn: [dashboard]
+---
+
+## Goal
+
+Write the setup report summarizing what this integration did, drawing only on the
+run's queue log and event plan in `.posthog-wizard-cache/` (`queue.json` and
+`.posthog-events.json`).
+
+## How you know you succeeded
+
+`posthog-setup-report.md` exists at the project root: what was installed and
+initialized, the events captured, whether identify was wired or skipped, error
+tracking added, the dashboard link, any build conflict in full, and the next
+steps for the user.

context/docs.yaml

@@ -8,6 +8,7 @@ docs:
     tags: [core, users, identity]
     urls:
       - https://posthog.com/docs/getting-started/identify-users.md
+      - https://posthog.com/docs/product-analytics/identity-resolution.md
 
   - id: cloudflare-workers
     display_name: Cloudflare Workers

context/skills/basic-integration/build/config.yaml

@@ -0,0 +1,9 @@
+type: docs-only
+template: description.md
+description: Install dependencies and verify the project builds
+tags: [orchestrator, build]
+variants:
+  - id: all
+    display_name: PostHog build step
+    tags: [orchestrator, build]
+    docs_urls: []

context/skills/basic-integration/build/description.md

@@ -0,0 +1,35 @@
+# Install and build
+
+Install the declared dependencies, then verify the project builds. Be quick and
+decisive — this step must not spiral.
+
+## Install
+
+Detect the package manager from the project's lockfile and run its install once,
+in this project directory. The manifest already declares PostHog. If install is
+slow, errors, or can't resolve a package, do not retry with offline flags and do
+not poke the package manager's global store or cache — a failed install is a
+conflict to report (below), not a problem to fight.
+
+## Build and verify
+
+Run the project's build (or typecheck), lint, and test scripts if they exist
+(check the manifest's scripts). Only errors in the files this integration changed
+are yours to fix — a missing import, a wrong call shape.
+An error in a file the integration never touched is pre-existing: note it and
+move on (below). Do not re-run build, typecheck, or lint hoping a pre-existing
+failure clears — it will not, and each re-run is slow.
+
+## Flag out-of-scope conflicts and move on
+
+Work only inside this project's own directory. Never read, search, or write
+anywhere outside it — not other repos, not the OS, not the package manager's
+global store or cache.
+
+A build or install you can't cleanly finish is a perfectly acceptable outcome —
+**as long as you report it.** If you hit a conflict that is excessively difficult
+or outside the scope of this integration — a dependency clash, a pre-existing
+build break, an install that won't resolve, an environment issue unrelated to the
+PostHog code — stop fighting it: put a one-line summary in your handoff `conflict`
+field and the full detail in `did`, then complete the task. The user sees it in
+the outro and the report; reporting it and moving on is the right outcome.