featuring-nomination
Generates App Store featuring nomination pitches with all required fields, compelling narratives, and Apple editorial angles. Use when submitting your app for App Store editorial featuring or preparing a self-nomination.
Best use case
featuring-nomination is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generates App Store featuring nomination pitches with all required fields, compelling narratives, and Apple editorial angles. Use when submitting your app for App Store editorial featuring or preparing a self-nomination.
Teams using featuring-nomination should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/featuring-nomination/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How featuring-nomination Compares
| Feature / Agent | featuring-nomination | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates App Store featuring nomination pitches with all required fields, compelling narratives, and Apple editorial angles. Use when submitting your app for App Store editorial featuring or preparing a self-nomination.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Featuring Nomination Generator Generate a compelling App Store featuring nomination ready for submission, including all required fields, narrative pitch, and strategic timing. ## When This Skill Activates Use this skill when the user: - Asks to "get featured" or "submit for App Store featuring" - Mentions "featuring nomination" or "editorial feature" - Wants help with "App Store editorial" pitch - Is preparing a major launch or update and wants visibility - Asks about "Today tab" or "Apps We Love" ## How App Store Featuring Works Apple's editorial team hand-picks apps for featuring based on: - **Quality**: Design, performance, and polish - **Innovation**: Novel use of Apple technologies - **Relevance**: Timely content or seasonal alignment - **Story**: Compelling developer or user narrative ### Featuring Placements | Placement | Visibility | Requirements | |-----------|-----------|-------------| | Today tab story | Highest | Exceptional quality + narrative | | App of the Day | Very high | Outstanding app + timing | | Collection feature | High | Fits a themed collection | | Category feature | Medium | Top quality in category | | Search result boost | Medium | Relevance + quality | ### Submission Timeline - Submit **6-8 weeks** before desired featuring date - Apple reviews and plans editorial calendar in advance - Seasonal features are planned months ahead - No guarantee of featuring — but quality nominations increase odds significantly ## Configuration Questions Ask user via AskUserQuestion: 1. **Reason for nomination?** - New app launch - Major update with new features - Seasonal relevance (holiday, back-to-school, etc.) - Apple technology showcase (new API adoption) - Milestone (anniversary, user count, award) 2. **Apple technologies used?** (multi-select) - SwiftUI - WidgetKit / Live Activities - App Intents / Shortcuts - Apple Intelligence / Foundation Models - ARKit / RealityKit - HealthKit / ActivityKit - SharePlay - StoreKit 2 - Apple Watch complications - visionOS support - Other (specify) 3. **Target featuring date?** - Within 2 weeks (too late for editorial, but can try) - 4-6 weeks from now (ideal timing) - 8+ weeks from now (best chance for planning) - Seasonal window (specify season) ## Generation Process ### Step 1: Gather App Details Collect comprehensive information: - App name, description, and category - What's new in this version (if update) - Apple technologies used with specific details - Developer story (indie, team, background) - User impact stories or metrics - Visual design highlights - Accessibility features - Privacy stance ### Step 2: Identify Featuring Angles Read `nomination-template.md` for the angle selection framework. Strong angles by category: - **Accessibility**: Apps that serve underserved communities - **Health**: Mental health, physical wellness, therapy tools - **Education**: Learning innovation, kids' safety - **Sustainability**: Environmental impact, eco-friendly - **Creativity**: Novel creative tools or expression - **Apple Tech**: Deep integration with latest Apple APIs - **Cultural**: Apps celebrating cultural moments or diversity ### Step 3: Generate Nomination Produce the complete nomination document. ## Output Format Read `nomination-template.md` and fill all fields. ```markdown # App Store Featuring Nomination ## App Information | Field | Value | |-------|-------| | App Name | [Name] | | Developer | [Developer/Company Name] | | App Store URL | [URL] | | Category | [Primary Category] | | Platforms | [iOS / macOS / watchOS / visionOS] | | App Store Connect Contact | [Email] | ## Nomination Reason [One of: New Launch / Major Update / Seasonal / Technology / Milestone] ## Desired Featuring Window [Date range, aligned with launch or seasonal opportunity] ## App Overview (2-3 sentences) [Compelling summary of what the app does and why it matters] ## What Makes This App Special (3-5 bullet points) - [Unique value proposition] - [Design or UX innovation] - [Technical excellence] - [User impact] - [Cultural or social significance] ## Apple Technology Integration | Technology | How It's Used | |-----------|--------------| | [SwiftUI] | [Specific usage details] | | [WidgetKit] | [Specific usage details] | | [etc.] | [etc.] | ## Developer Story (2-3 sentences) [Personal or team narrative that makes the app relatable] ## User Impact [Metrics, testimonials, or stories showing real-world impact] ## Design Highlights [What makes the visual design noteworthy — animations, interactions, aesthetics] ## Accessibility Features [VoiceOver support, Dynamic Type, color accessibility, etc.] ## Privacy Commitment [How the app respects user privacy — on-device processing, minimal data collection, etc.] ## Media Kit [Links to: screenshots, app preview video, press kit, developer photos] ## Social Proof (optional) [Press mentions, awards, notable reviews, download milestones] ``` ## References - **nomination-template.md** — Detailed nomination form and angle framework - Related: `app-store/marketing-strategy` — Featuring as part of broader strategy - Related: `app-store/app-description-writer` — Compelling app copy - Related: `generators/in-app-events` — Pair featuring with events - Apple: [Nominate your app for featuring](https://developer.apple.com/app-store/discoverability/)
Related Skills
watchOS
watchOS development guidance including SwiftUI for Watch, Watch Connectivity, complications, and watch-specific UI patterns. Use for watchOS code review, best practices, or Watch app development.
visionos-widgets
visionOS widget patterns including mounting styles, glass/paper textures, proximity-aware layouts, and spatial widget families. Use when creating or adapting widgets for visionOS.
test-data-factory
Generate test fixture factories for your models. Builder pattern and static factories for zero-boilerplate test data. Use when tests need sample data setup.
test-contract
Generate protocol/interface test suites that any implementation must pass. Define the contract once, test every implementation. Use when designing protocols or swapping implementations.
tdd-refactor-guard
Pre-refactor safety checklist. Verifies test coverage exists before AI modifies existing code. Use before asking AI to refactor anything.
tdd-feature
Red-green-refactor scaffold for building new features with TDD. Write failing tests first, then implement to pass. Use when building new features test-first.
tdd-bug-fix
Fix bugs using red-green-refactor — reproduce the bug as a failing test first, then fix it. Use when fixing bugs to ensure they never regress.
snapshot-test-setup
Set up SwiftUI visual regression testing with swift-snapshot-testing. Generates snapshot test boilerplate and CI configuration. Use for UI regression prevention.
integration-test-scaffold
Generate cross-module test harness with mock servers, in-memory stores, and test configuration. Use when testing networking + persistence + business logic together.
characterization-test-generator
Generates tests that capture current behavior of existing code before refactoring. Use when you need a safety net before AI-assisted refactoring or modifying legacy code.
testing
TDD and testing skills for iOS/macOS apps. Covers characterization tests, TDD workflows, test contracts, snapshot tests, and test infrastructure. Use for test-driven development, adding tests to existing code, or building test infrastructure.
webkit-integration
WebKit integration in SwiftUI using WebView and WebPage for embedding web content, navigation, JavaScript interop, and customization. Use when embedding web content in SwiftUI apps.