survey-sdk-audit

Some features only make sense on web: • URL targeting: No concept of "current URL" in native apps → issue: false for all mobile • CSS selector targeting: No DOM in native apps → issue: false for all mobile • Custom fonts via CSS: May need native implementation or may not be applicable

Use this skill when auditing survey feature support across PostHog SDKs for surveyVersionRequirements.ts. Feature to audit: $ARGUMENTS

Before starting, verify the SDK paths are accessible. Run ls on each path: • $POSTHOG_JS_PATH • $POSTHOG_IOS_PATH • $POSTHOG_ANDROID_PATH • $POSTHOG_FLUTTER_PATH If any path is empty or doesn't exist, ask the user: "I need the path to [SDK repo] on your machine. Where is it located?" Once you have all paths, ask the user if they'd like to save them for future sessions by adding to .claude/settings.local.json: `json { "env": { "POSTHOG_JS_PATH": "/path/to/posthog-js", "POSTHOG_IOS_PATH": "/path/to/posthog-ios", "POSTHOG_ANDROID_PATH": "/path/to/posthog-android", "POSTHOG_FLUTTER_PATH": "/path/to/posthog-flutter" }, "permissions": { "allow": [ "Read(/path/to/posthog-js/**)", "Read(/path/to/posthog-ios/**)", "Read(/path/to/posthog-android/**)", "Read(/path/to/posthog-flutter/**)", "Grep(/path/to/posthog-js/**)", "Grep(/path/to/posthog-ios/**)", "Grep(/path/to/posthog-android/**)", "Grep(/path/to/posthog-flutter/**)" ] } } ` Note: The Read and Grep permissions grant Claude access to these external SDK repositories without prompting each time.

IMPORTANT: Environment variables like $POSTHOG_JS_PATH do NOT expand reliably in Bash tool commands. Instead of bash commands, prefer: • Use the Read tool to read files (works with permissions) • Use the Grep tool to search files (works with permissions) If you must use bash, first expand the variable: `bash echo $POSTHOG_JS_PATH ` Then use the echoed path directly in subsequent commands.