Complete iOS/macOS/iPadOS development workflow plugin for Claude Code
npx claudepluginhub n0rvyn/indie-toolkit --plugin apple-devUse this agent when the user requests a code review of Swift or Apple platform (iOS/macOS/watchOS/tvOS) code. Only use when the target files are .swift or the project is an Xcode project. Do NOT use for non-Apple codebases (TypeScript, Python, Rust, Go, etc.). Performs read-only review for quality, correctness, and Apple platform-specific issues. Examples: <example> Context: User completed a feature and wants review of Swift code. user: "Review the changes I just made to NodeDetailView" assistant: "I'll use the apple-reviewer agent to review your changes." </example> <example> Context: User is about to merge a branch in a Swift/iOS project. user: "Review before I merge into main" assistant: "Let me have the apple-reviewer agent examine the changes." </example> <example> Context: User is working on a TypeScript/Node.js project. user: "Review these changes" assistant: DO NOT use apple-reviewer — this is not an Apple platform project. </example>
Performs design quality review (visual hierarchy, color, spacing) of SwiftUI files. Fresh context — evaluates visual quality independently of implementation decisions. Examples: <example> Context: User completed a SwiftUI page and wants visual polish feedback. user: "Review the design of my settings page" assistant: "I'll use the design-reviewer agent to evaluate the visual quality." </example> <example> Context: run-phase completed a phase that created new UI components. user: "Check the visual quality of the new dashboard" assistant: "I'll use the design-reviewer agent for a fresh-context design review." </example>
Performs product + UX completeness review from user journey perspective. Fresh context — validates feature completeness against user scenarios independently. Examples: <example> Context: User completed implementing a feature with full user journey. user: "Review the expense tracking feature for completeness" assistant: "I'll use the feature-reviewer agent to validate the user journey." </example> <example> Context: run-phase completed a phase that delivered a user-facing feature. user: "Check if the onboarding flow covers all scenarios" assistant: "I'll use the feature-reviewer agent for product+UX completeness review." </example>
Performs UI + UX compliance review of SwiftUI files. Use when run-phase completes a phase that modified UI files. Fresh context review — no implementation memory. Examples: <example> Context: User finished modifying several SwiftUI views. user: "Run a UI review on the views I just changed" assistant: "I'll use the ui-reviewer agent to check UI compliance." </example> <example> Context: run-phase completed a phase that modified UI files. user: "Check UI compliance for the updated screens" assistant: "I'll use the ui-reviewer agent for a fresh-context compliance review." </example>
Use when working on Swift, iOS, macOS, iPadOS, SwiftUI, or SwiftData code, editing .swift files, planning Apple platform features, fixing Swift bugs, or reviewing Swift code. Provides essential development rules including build cycle, constraints, concurrency, UI rules, and plan execution principles.
Use when preparing for App Store submission, or the user says 'ASC review', 'prepare submission'. Performs item-by-item App Store Connect submission material check and guidance. Keywords: ASC, App Store Connect, submission, privacy labels, screenshots, review.
Use before refactoring legacy code, or when the user says 'characterization test', 'lock behavior', '特征测试', 'write characterization tests', 'snapshot behavior'. Generates Swift Testing test cases that capture current behavior as a safety net before refactoring.
Use when the user says 'code audit', 'audit code', '代码审计', 'report card', 'security scan', or wants a comprehensive code quality assessment. Scans for security issues, concurrency safety, accessibility gaps, performance anti-patterns, and SwiftUI anti-patterns in iOS/macOS Swift projects.
Use after completing a page/module UI, before visual optimization, or when the user says 'review design' or 'check visual quality'. Reviews visual hierarchy, color strategy, spacing rhythm, and overall polish. Complements /ui-review (code compliance) and /feature-review (user journey).
Use after executing a plan, or when the user says 'execution review', 'review implementation', 'check implementation completeness'. Compares plan vs code execution results, verifies implementation completeness and identifies deviations. Performs Apple platform Swift code scan (localization, concurrency, abstraction, error handling) and doc update checks.
Use after completing a feature implementation, or when the user says 'feature review', 'review user journey'. Performs product+UX comprehensive review validating feature completeness from user journey perspective. Complements /ui-review (code compliance) and /design-review (visual quality).
Use when the user wants to check for latest Swift/SwiftUI API changes, or says 'fetch API updates', 'check WWDC changes'. Fetches latest Swift/SwiftUI API changes from WWDC session notes and updates project references.
Use when the user needs to generate SwiftUI Design System code from token specifications, or says 'generate design system'. Creates Apple HIG-compliant design tokens and component styles.
Use when the user wants to generate UI with Google Stitch for the current project, or needs a Stitch prompt based on actual project functionality.
Use when setting up localization for a new project, adding new language support, or answering questions about String Catalogs, pluralization, or variable handling. Provides interactive guidance on iOS localization based on the reference guide.
Use when the user asks about performance profiling, os_signpost instrumentation, MetricKit integration, Instruments workflow, performance anti-patterns, hitch detection, or the user says 'profiling', 'performance analysis', '性能分析'. Provides interactive guidance on iOS/macOS profiling based on the reference guide.
Use when starting a new iOS/macOS project, or the user says 'kickoff', 'new project setup'. Runs the project kickoff flow to clarify requirements, converge scope, and produce execution recommendations.
Use when setting up CI/CD for the first time, or the user says 'setup CI', 'configure CI', 'Xcode Cloud', 'auto version', '版本自动化', '配置 CI'. Configures Xcode Cloud build number management and GitHub Actions automatic version bumping based on conventional commits.
Use before submitting to App Store, or when the user says 'submission preview', 'pre-submit check', 'will this pass review'. Checks app code against Apple's App Review Guidelines to catch common rejection reasons.
Use when the user asks about SwiftData usage, designing data models, or has questions about relationships, queries, migrations, or concurrency issues with SwiftData. Provides interactive guidance on SwiftData best practices based on the reference guide.
Use when the user asks about testing approaches, setting up unit tests or basic UI tests (Page Object, wait strategies), mocking strategies, TDD workflow, or test coverage strategies. For performance tests (measure, XCTMetric), use /profiling instead. For advanced XCUITest (E2E flows, network stub, snapshot, accessibility audit, CI), use /xc-ui-test instead. Provides interactive guidance on iOS testing best practices based on the reference guide.
Use after completing a module, or when the user says 'ui review', 'check UI compliance'. Performs Apple platform SwiftUI UI and interaction compliance review for quality checks. Validates accessibility, state completeness, interaction guards, and platform conventions.
Use when preparing for App Store submission or the user says 'update ASC docs'. Audits codebase for privacy frameworks, permissions, third-party services, then updates legal and marketing documents.
Use when the user says 'validate tokens', 'check design tokens', or after modifying design-related code. Validates SwiftUI code compliance with Design Token standards for spacing, colors, fonts, and corner radius.
Use when the user asks about advanced XCUITest patterns, E2E testing, multi-screen user journey tests, network stubbing for UI tests, snapshot/visual regression testing, accessibility testing with performAccessibilityAudit, or CI integration for UI tests. Provides interactive guidance based on the reference guide.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Battle-tested Claude Code plugin for engineering teams — 38 agents, 156 skills, 72 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, and 16+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.