indie-app-copywriting/SKILL.md
Conversion-focused copywriting for indie app developers. Use when the user needs to write App Store descriptions, landing page copy, email sequences, social media announcements, or any marketing text for their app. Triggers on phrases like "write copy", "App Store description", "landing page", "conversion copy", "marketing text", "headline", "CTA", "email sequence", or requests to write persuasive text for app promotion.
npx skillsauth add abanoub-ashraf/manus-skills-import indie-app-copywritingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Conversion-focused copywriting formulas and templates for indie app marketing.
Benefits over features: Features describe what the app does. Benefits describe what the user gets. Always lead with benefits.
One reader, one message, one action: Every piece of copy targets one specific person, communicates one core message, and drives one action.
Clarity beats cleverness: Puns and wordplay confuse. Clear, specific language converts.
Proof beats claims: Anyone can claim "best." Specific numbers, testimonials, and demonstrations prove value.
Before writing any copy, define:
One Reader: The specific person you're writing for (not a demographic, a human). What keeps them up at night? What would make them say "this is exactly what I need"?
One Problem: The specific pain point this copy addresses. What situation triggers them to seek a solution?
One Promise: The single most compelling outcome. If you could only promise one thing, what converts?
One Action: The single thing you want them to do. Click, download, subscribe—pick one.
Headlines carry 80% of your marketing weight. 8 of 10 people read headlines; only 2 of 10 read body copy.
Effective headlines hit at least 3 of 4:
Useful: Clear benefit to reader Urgent: Reason to act now Ultra-specific: Concrete numbers/details Unique: Different from competitors
Example evolution:
How-To: "How to [Achieve Desired Outcome] Without [Common Pain Point]"
Number + Trigger Word: "[Number] [Trigger Word] to [Desired Outcome]"
Question: "Do You Make These [Number] [Mistakes] in [Activity]?"
Direct Benefit: "[Get Result] in [Timeframe]"
Curiosity Gap: "The [Unexpected Thing] That [Surprising Outcome]"
Social Proof: "[Number] [People] Can't Be Wrong"
See references/headline-swipes.md for 50+ proven headline formulas.
Problem: Name the specific pain the reader experiences Agitate: Twist the knife—show consequences of inaction Solve: Present your app as the relief
Example:
Tracking expenses manually is tedious. (Problem)
Most people give up after a week, then wonder where
their money went at month's end. (Agitate)
[App Name] automatically categorizes every transaction
so you always know exactly where you stand. (Solve)
Attention: Hook with compelling headline/opener Interest: Build curiosity with unique mechanism or story Desire: Stack benefits and proof until they want it Action: Clear, single CTA
Pain: Address the pain point Resonate: Show you understand what it feels like Educate: Explain that solutions exist Simplify: Position your app as the easy path Testify: Add social proof Offer: Make a compelling, specific offer
Before: Current painful state After: Desired future state Bridge: Your app is the path between them
Example:
Before: You wake up anxious, mind racing through
tomorrow's endless tasks.
After: You wake up calm, knowing exactly what matters
today and trusting nothing will slip through.
Bridge: [App Name] captures everything so you can focus
on doing, not remembering.
First Line (Most important—visible before "more"): "[Primary Benefit Statement with Social Proof]"
Second Paragraph (What it does): "[App Name] helps you [core function] by [unique mechanism]."
Feature-Benefit Pairs (NOT feature lists): Each feature followed by "so you can [benefit]"
Social Proof: Reviews, press mentions, user count
CTA: "Download now and [specific first benefit]"
Join 500,000+ people sleeping better with [App Name].
Trouble falling asleep? [App Name] uses science-backed
soundscapes designed to quiet your mind in under 10 minutes.
Unlike generic sleep apps, [App Name] learns your patterns
and adapts to help you fall asleep faster each night.
WHAT YOU GET:
• 200+ sleep sounds – so you find the perfect match
for your sleep style
• Smart Sleep Timer – so you never worry about
battery drain
• Sleep Tracking – so you see your progress over time
• Offline Mode – so you sleep well anywhere, even
without wifi
"I've tried every sleep app. This is the only one that
actually worked." – Sarah M.
Featured by Apple, recommended by sleep specialists.
Download now and fall asleep faster tonight.
[Headline: Primary benefit + specificity]
[Subheadline: How it works or secondary benefit]
[Social proof indicator: "Trusted by X" or rating]
[CTA Button: Action verb + immediate benefit]
[Hero image/video: App in action showing value]
Weak: "Submit" / "Sign Up" / "Learn More" Better: "Get Started" / "Try Free" / "Download" Best: "[Action] + [Outcome]" format
Examples:
See references/landing-page-templates.md for complete page templates.
Email 1 (Immediate): Confirm + quick win
Email 2 (Day 2): Deepen engagement
Email 3 (Day 5): Social proof + upgrade (if freemium)
Curiosity: "The [surprising thing] about [topic]" Benefit: "[Get result] in [timeframe]" Story: "How [Person] went from [before] to [after]" Question: "Do you [common mistake/behavior]?" Personal: "[Name], your [thing] is waiting" Urgency: "[Hours] left to [get benefit]"
🚀 [App Name] is live!
[One-line value prop]
After [timeframe/journey context]:
• [Key feature/benefit 1]
• [Key feature/benefit 2]
• [Key feature/benefit 3]
[Link]
[Specific ask for feedback or sharing]
#buildinpublic #[relevant hashtags]
[Milestone/metric] update:
[What happened]:
[What I learned]:
[What's next]:
[Optional: Screenshot or visual proof]
Weak: "Great app, love it!" (Generic, no specifics)
Strong: "I went from forgetting half my tasks to completing everything on my list. The 2-minute daily review changed everything for me." (Specific transformation, mechanism, result)
Hi [Name],
I noticed you've been using [App] for [time period] and
[specific behavior like upgraded/active use].
Would you mind sharing a quick answer to:
"What was happening before [App], and what's different now?"
Even 2-3 sentences would be incredibly helpful. Your
words might be exactly what someone else needs to hear.
Thanks so much,
[Your name]
Take raw feedback and structure as: "[Before state/problem] → [After state/result] + [Specific mechanism/feature that helped]"
Feature-first writing: "Our app has AI-powered categorization" vs. "Never manually sort receipts again"
Vague benefits: "Save time" vs. "Get 2 hours back every week"
Weak CTAs: "Learn more" vs. "Start your free trial"
Wall of text: Long paragraphs kill mobile conversion
Assuming context: Reader knows nothing about your app until you tell them
Multiple CTAs: Confusion kills conversion—pick one action
No specificity: "Many users" vs. "50,000+ users"
Passive voice: "Your habits are tracked" vs. "Track your habits"
See references/copy-audit-checklist.md for self-review protocol.
development
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
data-ai
Design and implement SwiftUI views, components, and app architecture. Use when creating new SwiftUI views, implementing MVVM/TCA patterns, managing state with @Observable, @State, @Binding, or @Environment, designing navigation flows, or structuring iOS app architecture. Triggers on SwiftUI, view model, state management, navigation, coordinator pattern.
development
Implement, review, or improve SwiftUI animations and transitions. Use when adding implicit or explicit animations with withAnimation, configuring spring animations (.smooth, .snappy, .bouncy), building phase or keyframe animations with PhaseAnimator/KeyframeAnimator, creating hero transitions with matchedGeometryEffect or matchedTransitionSource, adding SF Symbol effects (bounce, pulse, variableColor, breathe, rotate, wiggle), implementing custom Transition or CustomAnimation types, or ensuring animations respect accessibilityReduceMotion.
testing
Audit SwiftUI views for accessibility (iOS + macOS) with patch-ready fixes