Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Autonomous evolutionary code improvement engine with tournament selection. Activate when user says: self-improve, self improve, evolve code, improve iteratively, tournament, benchmark loop, optimize code.
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.
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).
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".
Adds a feature flag and fences off code with it
AST-aware Java refactoring using OpenRewrite. Use when asked to structurally refactor Java code, change class names, change method signatures/overloads, replace builder patterns, modify annotations, or perform cross-file structural replacements. Note: Renaming fields or local variables/parameters is not supported natively via simple YAML recipes in the standard openrewrite modules.
Every Apple framework, indexed locally, with deprecation analysis and an MCP server no other Apple-docs tool has. Trigger phrases: `look up an Apple API`, `what's deprecated in iOS`, `find a SwiftUI symbol`, `port this from UIKit to SwiftUI`, `what changed at WWDC`, `use apple-docs`, `run apple-docs-pp-cli`.
Assesses the impact of API changes before implementation to understand what code would break and plan appropriate migration paths. Use when removing methods, changing interfaces, or planning deprecations.
Scaffolds new and reviews existing Git::Commands::* classes with unit tests, integration tests, and YARD docs using the Base architecture. Use when creating a new command class from scratch, updating an existing command class, or reviewing a command class for correctness.
Migrates a direct #command call in Git::Lib to a Git::Commands::* class as part of the architectural redesign. Use when extracting a specific command during the Strangler Fig migration.