You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/storybook-stories/SKILL.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
name: storybook-stories
3
-
description: Write Storybook stories for PostHog Code UI components. Covers the provider stack stories run inside, the key gotcha that tRPC/useHostTRPC queries never resolve in Storybook (so data-fetching components render empty), and the pure-presentational split that makes a component storyable. Use when adding or fixing a *.stories.tsx file under packages/ui.
3
+
description: Write Storybook stories for PostHog UI components. Covers the provider stack stories run inside, the key gotcha that tRPC/useHostTRPC queries never resolve in Storybook (so data-fetching components render empty), and the pure-presentational split that makes a component storyable. Use when adding or fixing a *.stories.tsx file under packages/ui.
4
4
---
5
5
6
-
# Storybook stories in PostHog Code
6
+
# Storybook stories in PostHog
7
7
8
8
Stories live next to components as `*.stories.tsx` and are collected by
Copy file name to clipboardExpand all lines: .claude/skills/test-electron-app/SKILL.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
name: test-electron-app
3
-
description: Drive the real running PostHog Code Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, snapshot the accessibility tree to verify changes, click/type/navigate, and screenshot the actual desktop app only when explicitly asked. Use when asked to test, verify, dogfood, screenshot or interact with the running app. For regression specs use the Playwright E2E suite.
3
+
description: Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, snapshot the accessibility tree to verify changes, click/type/navigate, and screenshot the actual desktop app only when explicitly asked. Use when asked to test, verify, dogfood, screenshot or interact with the running app. For regression specs use the Playwright E2E suite.
Drive the actual running app over the Chrome DevTools Protocol with
10
10
[agent-browser](https://github.com/vercel-labs/agent-browser). The dev app
@@ -186,7 +186,7 @@ When the user asked for a screenshot, they want to look at it, so close the loop
186
186
default debugging port; if `connect` attaches to the wrong target, list and
187
187
pick the PostHog window: `agent-browser tab` then `agent-browser tab --url "*"`.
188
188
-**Multiple targets:** the app has a main renderer window (page title contains
189
-
"PostHog Code") plus possible webviews/devtools. `agent-browser tab` lists them;
189
+
"PostHog") plus possible webviews/devtools. `agent-browser tab` lists them;
190
190
switch with `agent-browser tab <index>`.
191
191
-**Never pass `--color-scheme dark`:** that global flag makes agent-browser apply
192
192
device emulation that forces a 1280x720 viewport and renders this Electron window
@@ -201,7 +201,7 @@ When the user asked for a screenshot, they want to look at it, so close the loop
201
201
202
202
## Running alongside prod
203
203
204
-
PostHog Code orchestrates the agent, so the usual loop is: **prod** (the installed app) runs the agent, and the **dev** build (`pnpm dev`) is the system under test. They coexist by design (`apps/code/src/main/bootstrap.ts`): dev runs as `posthog-code-dev` with its own app name, userData and single-instance lock, so it never collides with prod.
204
+
PostHog orchestrates the agent, so the usual loop is: **prod** (the installed app) runs the agent, and the **dev** build (`pnpm dev`) is the system under test. They coexist by design (`apps/code/src/main/bootstrap.ts`): dev runs as `posthog-code-dev` with its own app name, userData and single-instance lock, so it never collides with prod.
205
205
206
206
-**agent-browser always targets dev.** Only the dev build exposes CDP on `:9222`; prod has no debug port, so `connect 9222` can't accidentally drive prod.
207
207
-**Separate auth/state.** The dev instance has its own `posthog-code-dev` profile; it is not signed in just because prod is. Sign into the dev window once; its state persists.
@@ -220,6 +220,6 @@ PostHog Code orchestrates the agent, so the usual loop is: **prod** (the install
220
220
check the `pnpm dev:code` output. Note `pnpm dev` cannot run headlessly at all — its
221
221
`phrocs` TUI needs a TTY; use `pnpm dev:code`.
222
222
-**Snapshot is empty / wrong window:** you're on the wrong target. Run
223
-
`agent-browser tab` and switch to the "PostHog Code" page.
223
+
`agent-browser tab` and switch to the "PostHog" page.
224
224
-**Can't type into an input:** try `agent-browser keyboard type "text"` (types at
225
225
current focus) or `agent-browser keyboard inserttext "text"` to bypass key events.
description: Restore-only turbo cache. warm-caches.yml seeds it on main pushes; PR workflows never save, so per-PR entries don't pollute the cache store.
0 commit comments