// Cross-platform codebase exploration for Pocket Casts. Use when asked about Web, iOS, or Android implementation of a feature, or when comparing implementations across platforms.
Address PR review comments by fixing code, replying to each comment, and re-requesting review. Use this skill when the user wants to handle, fix, resolve, or address PR feedback, review comments, or code review suggestions. Also use when the user says things like "fix the PR comments", "handle review feedback", "address the review", or "respond to PR feedback".
Create a pull request using the repository template and current branch changes
Expert guidance for Dynamic Type support for Pocket Casts iOS development with Swift, UIKit, and SwiftUI. Use this skill when the user asks about Dynamic Type, content size categories, accessibility text size, font scaling, or making text/UI elements respond to the user's preferred text size (e.g., using preferredContentSizeCategory, adjustsFontForContentSizeCategory, UIFontMetrics, or related APIs in SwiftUI and UIKit).
Adds a feature flag and fences off code with it
| name | cross-platform |
| description | Cross-platform codebase exploration for Pocket Casts. Use when asked about Web, iOS, or Android implementation of a feature, or when comparing implementations across platforms. |
Other platform repos are siblings of the root iOS repo (not worktrees):
| Platform | Relative to project root | Trunk Branch |
|---|---|---|
| Web | ../pocket-casts-webplayer/ | develop |
| Android | ../pocket-casts-android/ | main |
If working in a worktree, first find the root iOS repo:
# Get root repo path (works in both root and worktree)
# --porcelain output is stable for scripting; first entry is always the main worktree
ROOT=$(git worktree list --porcelain | head -n 1 | awk '{print $2}')
# Platform repos are siblings of the root
WEB_REPO="$ROOT/../pocket-casts-webplayer"
ANDROID_REPO="$ROOT/../pocket-casts-android"
Each repository contains a CLAUDE.md at its root. Read it first to understand architecture and conventions.
Before exploring code:
Navigate to repo and check current state:
cd "$WEB_REPO" # or $ANDROID_REPO
git status --short
git branch --show-current
If uncommitted/unstaged changes exist → ask the user: stash them, discard, or abort?
Determine target branch:
develop (Web) main (Android) or trunk (iOS) → pull latestSync the branch:
git checkout <branch> # if switching
git pull
When comparing or describing implementations:
Avoid language-specific syntax unless necessary to explain behavior.