Cross Platform Skill for Claude

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.

602 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1811

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Automattic/pocket-casts-ios --skill cross-platform

The instruction itself

7 sections, as written by the author

Cross-Platform Codebase Exploration

Repository Locations

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 |

Finding Repos (Worktree-Safe)

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"

Before Exploring

Each repository contains a CLAUDE.md at its root. Read it first to understand architecture and conventions.

Branch Sync Procedure

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:
If user specified a PR → check out that PR's branch
If on develop (Web) main (Android) or trunk (iOS) → pull latest
If on a different branch → ask the user: switch to main/trunk, or stay on current branch?

Sync the branch:

   git checkout <branch>  # if switching
   git pull

What to Focus On

When comparing or describing implementations:

Logic flow and feature architecture
State transitions
DTOs / data models
API usage, endpoints, request/response structures
Feature flags and configuration patterns
Cross-platform differences and similarities

Avoid language-specific syntax unless necessary to explain behavior.

Example Queries

"How does iOS handle Up Next syncing?"
"Compare podcast following between Android and Web"
"What endpoints does the Server use for Up Next sync?"
"How are feature flags structured on iOS vs Android?"

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take automattic/cross-platform from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.