القائمة
Search Apple Dev Search for Swift, SwiftUI, Xcode, iOS, macOS, and Apple-platform community articles, tutorials, blogs, and write-ups.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apple firmware and binary reverse engineering with the `ipsw` CLI: IPSW/kernelcache download/extraction, dyld_shared_cache disassembly, private headers, entitlements, Mach-O analysis, Apple internals, KEXTs, and security research.
Use when App Store listing text must be translated or market-adapted across locales, including descriptions, keywords, What's New, subtitles, names, privacy text, and App Store Connect languages. Not for non-translation metadata edits, release-note drafting, or subscription/IAP display-name localization.
Use when App Store listing metadata in canonical `./metadata` JSON needs field edits, validation, push, keyword sync, or legacy fastlane migration. Not for translation-first localization, release-note drafting, or subscription/IAP display-name localizations.
Use for the concrete macOS Developer ID notarization command path with xcodebuild export plus `asc notarization` submit, status, log, and stapling. Not for broad packaging readiness review or signing-only diagnosis.
Set territory-specific subscription and IAP pricing with `asc` setup, pricing summary, CSV import, price-point, availability, and schedule commands. Use for PPP or localized pricing strategies.
End-to-end iOS App Store publishing from local repo to App Store Connect readiness, upload, TestFlight, App Review submission/resubmission, or review issue triage, including signing, metadata, privacy, icons, screenshots, subscriptions, and release evidence.
| name | apple-dev-research |
| description | Search Apple Dev Search for Swift, SwiftUI, Xcode, iOS, macOS, and Apple-platform community articles, tutorials, blogs, and write-ups. |
Bundled commands use $PLUGIN_ROOT ($env:PLUGIN_ROOT in PowerShell; same path suffix) for the plugin root. Set it once: use the host's plugin-root variable when defined (Claude Code: PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"), otherwise the absolute path of this plugin's root directory.
Use Apple Dev Search for Apple-platform community content when the user wants articles, tutorials, or reading material rather than official docs or generic web results. Do not hard-code service counts; query --counts when counts matter.
--title-only and tighter terms.|, -, *, ~1, parentheses.--recent.python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query 'build speed' --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query '"incremental builds" | "compile time"' --title-only --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --query 'swift testing -uikit' --limit 5
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --recent --limit 8
python3 "$PLUGIN_ROOT/skills/apple-dev-research/scripts/appledevsearch.py" --counts
Use full text for errors/API/framework names; title-only for broad topics. Keep user terminology in at least one query before expanding synonyms.
Reusable search URL:
https://appledevsearch.com/#q=<urlencoded query>&titleOnly=true|false
Mention exact queries used, separate title-only vs full-text results, prefer direct article links, and say when results are weak or empty.