app-store-optimisation-codex
App Store Optimisation (Codex)
Overview
Provide end-to-end ASO support for App Store and Play Store listings, from research to execution. Use bundled Python modules for structured analysis and planning, and use browsing or user-provided inputs for live data.
Quick Start
- Identify the task: keyword research, metadata optimization, competitor analysis, review analysis, ASO scoring, A/B testing, localization, or launch planning.
- Request required inputs (platforms, markets, current metadata, target keywords, metrics).
- Use the matching script from
scripts/to generate analysis or plans. - Validate character limits and platform rules, then deliver actionable recommendations.
Core Tasks
Keyword research
Use scripts/keyword_analyzer.py.
Request:
- Candidate keywords
- Estimated search volume and competition (user-provided or inferred)
- Relevance score per keyword
Deliver:
- Ranked keywords (primary, secondary, long-tail)
- Difficulty and potential scores
Metadata optimisation
Use scripts/metadata_optimizer.py.
Request:
- Current metadata (title, subtitle, descriptions)
- Target keywords and value proposition
- Platform(s) and markets
Deliver:
- Optimized titles and descriptions with character counts
- Keyword density guidance
Default character limits (verify current limits before final output):
- Apple App Store: title 30, subtitle 30, promo text 170, description 4000, keywords 100
- Google Play: title 50, short description 80, full description 4000
Competitor analysis
Use scripts/competitor_analyzer.py.
Request:
- Competitor names or IDs
- Platform and market
Optional data collection:
- Use
scripts/itunes_api.pyfor Apple metadata - Use browsing with prompt templates from
scripts/scraper.py
Deliver:
- Keyword overlap, metadata patterns, visual asset notes, and gaps
Review analysis
Use scripts/review_analyzer.py.
Request:
- Review text, ratings, and date range
Deliver:
- Sentiment split, top issues, feature requests, response templates
ASO scoring
Use scripts/aso_scorer.py.
Request:
- Metadata quality inputs, ratings data, keyword ranking counts, conversion metrics
Deliver:
- Overall score with category breakdown and prioritized recommendations
A/B testing
Use scripts/ab_test_planner.py.
Request:
- Baseline conversion rate and traffic
- Variants and test goal
Deliver:
- Sample size, duration guidance, and success metrics
Localization planning
Use scripts/localization_helper.py.
Request:
- Current markets and target locales
- Budget and priority markets
Deliver:
- Localization priority order and draft localized metadata
Launch and update checklists
Use scripts/launch_checklist.py.
Request:
- Platform(s), launch date, category, and key features
Deliver:
- Pre-launch checklist and post-launch monitoring plan
Data Sources
See references/data_sources.md for API and browsing guidance.
Resources
scripts/
keyword_analyzer.pymetadata_optimizer.pycompetitor_analyzer.pyreview_analyzer.pyaso_scorer.pyab_test_planner.pylocalization_helper.pylaunch_checklist.pyitunes_api.pyscraper.py
references/
data_sources.mdsample_input.jsonexpected_output.json
More from vladimirbrejcha/ios-ai-skills
swiftui-simulator-ui
Run SwiftUI apps in iOS Simulator and capture screenshots for visual verification. Use when building UI, reviewing layouts, validating designs, or when you need to see what SwiftUI code looks like. Essential for any UI work requiring visual feedback.
9apple-docs-research
Use when researching or implementing anything related to Apple platforms (iOS, iPadOS, macOS, watchOS, tvOS, visionOS), Swift/Objective-C APIs, Apple frameworks, WWDC sessions, or Apple Developer Documentation. Triggers include: \"find Apple's docs\", \"latest API guidance\", \"WWDC session\", \"platform availability\", \"SwiftUI/UIKit/AppKit/Combine/AVFoundation/etc.\", or any Apple SDK coding question where authoritative docs are needed. Always use the apple-docs MCP tools for discovery and citations instead of general web search.
8apple-doc-research
Use when researching or implementing anything related to Apple platforms (iOS, iPadOS, macOS, watchOS, tvOS, visionOS), Swift/Objective-C APIs, Apple frameworks, WWDC sessions, or Apple Developer Documentation. Triggers include: \"find Apple's docs\", \"latest API guidance\", \"WWDC session\", \"platform availability\", \"SwiftUI/UIKit/AppKit/Combine/AVFoundation/etc.\", or any Apple SDK coding question where authoritative docs are needed. Always use the apple-docs MCP tools for discovery and citations instead of general web search.
5ios-xcodegen
XcodeGen workflows for iOS/iPadOS apps: generate projects from project.yml/project.yaml, fix build/test destination issues, wire asset catalogs, configure test hosts, manage SwiftPM resolution in CI, and resolve App Store packaging errors related to embedded static libraries.
5code-review
Review pull requests, commits, or diffs for high-signal engineering issues and merge risk. Use when asked to review code, audit a patch, find bugs, or provide merge readiness feedback. Focus on defects introduced by the proposed changes (correctness, security, performance, reliability, and maintainability) and report actionable findings with severity, confidence, and precise code locations.
4copywriting
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
4