- Home
- Skills
- Translation & Localization
- App Store Screenshot UI Planner
More screenshots
Works with the AI Agents you already use
App Store Screenshot UI Planner
The agent then selects a strategic screenshot narrative.
$7.99
App Store Screenshot UI Planner
Example session with this skill installed
App name
FocusNest
App category
Productivity and task-management application
Platforms
Apple App Store and Google Play
Target devices
iPhone
Android phone
iPad
Android tablet
Primary audience
Busy professionals
Freelancers
Remote workers
Small-business owners
Secondary audiences
Students
Creators
Small teams
Primary install motivation
Organize daily work, focus on high-priority tasks, and reduce planning friction.
Primary user outcome
Finish important work with a clear daily plan.
Core differentiation
Combines daily planning, focus sessions, project organization, lightweight habit tracking, and progress summaries in one calm interface.
Top features
Today planning
Priority tasks
Focus timer
Project boards
Quick task capture
Weekly progress
Recurring tasks
Calendar integration
Cross-device synchronization where verified
Strongest proof
Current verified rating
Approved user testimonials
Existing product UI
Exact values require verification before publication
Current screenshots
Six raw phone screenshots with no headlines
Same layout on every frame
UI appears small
No clear narrative
No tablet-specific assets
No localization system
Current app UI
Light and dark modes
Minimal interface
Large task cards
Calm blue and lavender accents
Simple charts
Bottom-tab navigation
Brand style
Calm
Premium
Focused
Modern
Trustworthy
Minimal but warm
Color palette
Deep navy
White
Soft blue
Lavender
Warm gray
Green for completed states
Typography
Modern sans-serif
High readability
Medium-to-bold headlines
Tone
Clear
Supportive
Confident
Calm
No exaggerated promises
Screenshot count
Six phone screenshots
Five tablet screenshots
Orientation
Portrait for phones
Landscape for tablets
Device mockup preference
Simplified premium frames
Large readable UI
Limited device chrome
No excessive reflections
Markets
United States
United Kingdom
Germany
France
Spain
Brazil
Languages
English
German
French
Spanish
Portuguese
Subscription model
Monthly and annual premium plans
Limited free access
Exact pricing, trial availability, billing cadence, renewal terms, and cancellation conditions require verification
Claims available
Verified product features
Approved testimonials
Verified ratings where current
No performance-time claims
No guaranteed productivity claims
Ratings or reviews available
Current verified store rating
Approved review excerpts
Exact values and wording require verification
Competitor context
Crowded productivity category
Many competitors use generic claims, dense UI, oversized devices, and repetitive blue gradients
Need output
Complete App Store and Google Play screenshot strategy
First-frame strategy
First-three narrative
Six phone screenshot specifications
Five tablet screenshot specifications
Headline system
Supporting copy
UI-screen selection
UI-crop plan
Device-mockup strategy
Composition system
Typography
Color
Backgrounds
Trust and proof
Subscription messaging
Localization plan
Audience variants
Creative-test roadmap
Asset inventory
Designer handoff
Export plan
Acceptance criteria
QA checklist
Risk assessment
Need variations
Outcome-Led Productivity
Calm Focus
Professional Work Management
Special constraints
Do not invent ratings.
Do not invent user counts.
Do not invent time-saving claims.
Do not imply guaranteed productivity.
Do not hide subscription terms.
Do not use fake urgency.
Do not use unapproved testimonials.
Do not use iPhone frames in Google Play assets.
Do not enlarge phone layouts for tablets.
Do not shrink translated text below the approved minimum.
- Read your context and instructions
- Compiled the app store screenshot
=== APP STORE SCREENSHOT PLAN ===
App
FocusNest
Platforms
Apple App Store and Google Play
Primary Audience
Busy professionals, freelancers, remote workers, and small-business owners.
Primary Install Motivation
Create a clear daily plan, protect focus time, and keep important work organized.
Primary Promise
Plan Your Day. Focus on What Matters.
Narrative Model
Outcome-led
=== EXECUTIVE SUMMARY ===
The current screenshot set shows the interface but does not explain why FocusNest is valuable.
The redesigned sequence should
- Lead with the daily-planning outcome.
- Demonstrate the focus workflow.
- Show project organization.
- Show quick task capture.
- Show progress and recurring work.
- Reinforce trust and cross-device continuity where verified.
The first three screenshots should function as a miniature landing page:
- Promise
- Mechanism
- Broader product value
=== FIRST-SCREENSHOT STRATEGY ===
Strategic Role
Primary promise
Headline
Plan Your Day. Focus on What Matters.
Supporting Copy
Organize priorities and build a realistic plan for today.
UI Screen
Today view with three prioritized tasks and one visible focus action.
UI Crop
Enlarge the central task list and primary action.
Remove secondary navigation details that do not support the first message.
Device Mockup
Simplified platform-appropriate phone frame.
Composition
Large device occupying the lower two-thirds of the frame.
Headline aligned in the upper region.
One subtle background shape behind the device.
Background
Deep navy with a restrained soft-blue gradient.
Feature Highlight
Today planning and priority clarity.
Verification
Confirm the displayed tasks, product labels, and synchronization indicators are current.
=== FIRST-THREE NARRATIVE ===
Screenshot 1:
Plan Your Day. Focus on What Matters.
Purpose
Communicate the primary outcome.
Screenshot 2:
Turn Priorities Into Focused Work
Purpose
Show how the focus timer connects planning to action.
Screenshot 3:
Keep Every Project Moving
Purpose
Expand the perceived product value beyond daily tasks.
=== PHONE SCREENSHOT 1 ===
Strategic Role
Primary promise
Headline
Plan Your Day. Focus on What Matters.
UI
Today view
Composition
Centered device with enlarged task content
Primary Focus
Priority tasks
=== PHONE SCREENSHOT 2 ===
Strategic Role
Product mechanism
Headline
Turn Priorities Into Focused Work
Supporting Copy
Start a focused session directly from your daily plan.
UI
Focus timer connected to an active task
Composition
Offset device with a magnified timer detail
Primary Focus
Planning-to-focus workflow
=== PHONE SCREENSHOT 3 ===
Strategic Role
Feature depth
Headline
Keep Every Project Moving
UI
Project board
Composition
Large cropped board with two visible columns and a floating project summary
Primary Focus
Project organization
=== PHONE SCREENSHOT 4 ===
Strategic Role
Speed and convenience
Headline
Capture Tasks Before You Forget
UI
Quick-add flow
Composition
Full-width UI crop with keyboard-safe framing
Primary Focus
Fast task creation
Avoid
Unsupported claims such as “in one second.”
=== PHONE SCREENSHOT 5 ===
Strategic Role
Progress and retention
Headline
See Your Progress Week by Week
UI
Weekly progress
Composition
Large chart area with limited supporting annotation
Primary Focus
Visible progress
Verification
Confirm chart values and labels are fictional, masked, or approved.
=== PHONE SCREENSHOT 6 ===
Strategic Role
Trust and ecosystem reinforcement
Headline
Stay Organized Across Your Devices
UI
Phone and tablet views
Use Only If
Cross-device synchronization is verified.
Alternative Headline
Your Work, Organized in One Place
Use the alternative when cross-device behavior is not fully verified.
=== TABLET STRATEGY ===
Orientation
Landscape
Principle
Use real tablet layouts rather than enlarged phone screens.
Tablet Frame 1:
Daily workspace with split navigation and task planning
Tablet Frame 2:
Project board with multi-column layout
Tablet Frame 3:
Focus session with task context
Tablet Frame 4:
Weekly progress with larger analytical view
Tablet Frame 5:
Multi-project overview or calendar integration where verified
=== HEADLINE SYSTEM ===
Voice
Clear, calm, practical, and benefit-led.
Rules
- Keep headlines concise.
- Use sentence case.
- Avoid exaggerated promises.
- Avoid unsupported timing.
- Avoid repeating the same sentence structure.
- Keep localization flexibility.
Approved Direction
- Plan Your Day. Focus on What Matters.
- Turn Priorities Into Focused Work.
- Keep Every Project Moving.
- Capture Tasks Before You Forget.
- See Your Progress Week by Week.
- Your Work, Organized in One Place.
=== DEVICE STRATEGY ===
Apple App Store
Use simplified iPhone and iPad frames with accurate iOS UI.
Google Play
Use platform-appropriate Android phone and tablet treatments.
Rules
- Keep device scale consistent.
- Avoid mixing device generations without purpose.
- Avoid heavy reflections.
- Keep important UI readable.
- Do not use iPhone frames in Google Play assets.
=== COMPOSITION SYSTEM ===
Frame Types
- Centered device
- Offset device with enlarged UI detail
- Cropped product interface
- Wide tablet workspace
- Controlled multi-device ecosystem frame
Consistency Rules
- Maintain stable headline placement.
- Use one dominant product area.
- Use one background language.
- Limit floating decorations.
- Keep device shadows restrained.
- Use one visual accent per frame.
=== TYPOGRAPHY ===
Headline
Bold modern sans-serif
Supporting Copy
Regular or medium sans-serif
Rules
- Test at thumbnail size.
- Avoid thin weights.
- Keep text away from unsafe edges.
- Limit headline line count.
- Recompose localized layouts.
- Do not reduce translated text below the approved minimum.
=== COLOR SYSTEM ===
Primary Background
Deep navy
Secondary Backgrounds
White
Warm gray
Soft blue
Accent
Lavender
Completion Highlight
Green
Rules
- Reserve strong contrast for headlines and product focus.
- Avoid using every brand color in one frame.
- Preserve readable UI.
- Avoid decorative gradients that weaken text contrast.
=== TRUST AND PROOF ===
Possible Proof
- Current verified store rating
- Approved user testimonial
- Current platform availability
- Verified synchronization
- Approved privacy feature
Requirements
- Verify exact wording.
- Verify current numerical values.
- Record proof owner.
- Record approval status.
- Do not use outdated ratings.
=== SUBSCRIPTION MESSAGING ===
Possible Screenshot Role
Explain premium value through features rather than pressure.
Display Only When Relevant
- Premium project capacity
- Advanced progress
- Calendar integration
- Cross-device access
- Other verified paid benefits
Do Not
- Hide price or recurring terms when displayed.
- Invent trial availability.
- Invent discounts.
- Imply lifetime access.
- Use false countdowns.
=== LOCALIZATION PLAN ===
Languages
English
German
French
Spanish
Portuguese
Process
- Approve English source copy.
- Create translation context.
- Complete linguistic review.
- Review cultural relevance.
- Recompose layouts.
- Capture localized UI.
- Complete platform-specific export.
- Perform final QA.
German
Allow greater expansion and wider headline zones.
French
Review punctuation and line breaks.
Spanish
Preserve natural benefit language rather than literal translation.
Portuguese
Review Brazilian market terminology and UI localization.
Do Not
Shrink text until it fits.
=== CREATIVE TEST ROADMAP ===
Test 1:
Primary Headline
Control
Plan Your Day. Focus on What Matters.
Variation
Bring Clarity to Every Workday
Primary Variable
Value proposition
Test 2:
Device Scale
Control
Full simplified device
Variation
Larger cropped UI
Primary Variable
Product readability
Test 3:
First-Three Order
Control
Plan → Focus → Projects
Variation
Plan → Projects → Progress
Primary Variable
Narrative order
Test 4:
Background
Control
Deep navy
Variation
Light warm-gray system
Primary Variable
Visual tone
Guardrails
Brand consistency
Claim accuracy
Thumbnail readability
Localization quality
=== ASSET INVENTORY ===
Required
- Current app icon
- Current iOS screenshots
- Current Android screenshots
- Current tablet screenshots
- Approved device frames
- Brand colors
- Approved fonts
- Approved testimonials
- Verified rating evidence
- Translated copy
- Localized UI captures
- Export templates
Every asset should record
- source
- owner
- license
- version
- language
- approval status
=== DESIGNER HANDOFF ===
Provide
- narrative
- sequence
- approved copy
- device strategy
- UI crops
- composition rules
- background rules
- typography
- color
- proof
- localization
- asset links
- export naming
- platform requirements
- QA checklist
=== ACCEPTANCE CRITERIA ===
First Screenshot
Given the first screenshot is viewed at store thumbnail size,
when a prospective user scans it,
then the product category and primary value remain understandable without reading the store description.
First Three
Given the first three screenshots are viewed in order,
when the user moves through them,
then the story progresses from planning to focused execution to broader project organization.
UI Readability
Given a screenshot includes a phone interface,
when the final asset is previewed at store-listing scale,
then the primary UI content remains readable and the device frame does not overpower the product.
Localization
Given the German version is produced,
when the approved translation is inserted,
then hierarchy, spacing, device scale, and headline readability remain intact without reducing text below the approved minimum.
Proof
Given a screenshot includes a rating or testimonial,
when production begins,
then the exact proof has documented evidence, approval, and an identified owner.
=== QA CHECKLIST ===
Product
- Verify app version.
- Verify current interface.
- Verify feature availability.
- Verify accurate platform UI.
- Verify realistic content.
Copy
- Verify spelling.
- Verify grammar.
- Verify claims.
- Verify localization.
- Verify line breaks.
Design
- Verify hierarchy.
- Verify text size.
- Verify contrast.
- Verify device scale.
- Verify UI crop.
- Verify background consistency.
- Verify safe spacing.
Assets
- Verify licenses.
- Verify approvals.
- Verify correct versions.
- Verify app icon.
- Verify device frames.
Export
- Verify platform.
- Verify device family.
- Verify dimensions.
- Verify orientation.
- Verify file format.
- Verify file naming.
- Verify locale code.
- Verify screenshot order.
=== RISKS ===
Risk
The first screenshot remains too generic.
Mitigation
Use a specific daily-planning outcome and visible product proof.
Risk
UI becomes unreadable.
Mitigation
Use larger crops and reduced device chrome.
Risk
Localized layouts lose hierarchy.
Mitigation
Recompose every language rather than shrinking text.
Risk
Cross-device claims are published before verification.
Mitigation
Use the approved alternative final screenshot until synchronization is confirmed.
Risk
Store creatives become outdated after a UI release.
Mitigation
Add screenshot-version ownership and release QA.
=== KNOWN LIMITATIONS ===
- Platform specifications require current verification.
- Claims require documented approval.
- Asset licensing requires confirmation.
- Localization requires professional review.
- Final visual quality depends on professional production.
- Creative-test conclusions require sufficient traffic.
- The plan does not guarantee install conversion, rankings, revenue, or retention.
=== FINAL INTEGRITY NOTE ===
All ratings, reviews, awards, pricing, subscription terms, trials, discounts, feature availability, performance claims, health claims, financial claims, security claims, privacy claims, device support, regional availability, customer proof, and platform statements must be verified before publication.
Store screenshots should accurately represent the current or approved product experience.
The screenshot plan is designed to improve message clarity, product understanding, visual storytelling, and install-conversion readiness. It does not guarantee higher conversion, rankings, revenue, retention, or acquisition efficiency.
Connects securely to your tools. The creator never sees your data.
About this skill
App Store Screenshot UI Planner helps mobile app developers, indie creators, SaaS mobile teams, ASO specialists, app marketing agencies, product marketers, growth teams, and visual designers turn product interfaces and feature lists into persuasive store-listing screenshot systems.
The skill is designed for Apple App Store and Google Play campaigns across iPhone, iPad, Android phones, Android tablets, portrait layouts, landscape layouts, localized markets, subscription products, freemium apps, paid apps, product launches, redesigns, rebrands, major feature releases, and creative-testing programs.
It begins by defining the app category, target audience, primary install motivation, user outcome, product differentiation, strongest proof, major hesitation, platform, target devices, markets, and available claims.
The agent then selects a strategic screenshot narrative. Supported narrative models include outcome-led, feature-led, use-case-led, trust-led, transformation-led, subscription-value-led, and audience-specific sequences.
The first screenshot is treated as the most important frame. It should communicate what the app does, why the target user should care, and which benefit matters most.
The first three screenshots are planned as a miniature landing page. A typical sequence may communicate the primary promise, explain the product mechanism, and present proof or the strongest secondary benefit.
Every screenshot receives one clear strategic role. Possible roles include opener, core benefit, flagship feature, workflow explanation, personalization, trust, social proof, ecosystem, subscription value, use case, or final reinforcement.
The skill creates screenshot-by-screenshot specifications covering headline, supporting copy, selected app screen, UI crop, device mockup, composition, background, feature highlight, proof, CTA-style line, localization risk, asset requirements, and verification status.
Headline systems are designed to remain short, specific, readable at thumbnail size, easy to localize, and connected to a real user outcome.
The agent avoids generic claims such as “The Best App for You” and replaces them with specific, supportable language based on the app’s real value.
Supporting copy is included only when it adds meaning. It should clarify the headline, explain the product mechanism, or provide evidence without repeating the same message.
The skill plans UI-screen selection based on product proof, current feature availability, visual clarity, differentiation, data privacy, content quality, platform accuracy, and adaptability to the screenshot composition.
It identifies which interface regions should be displayed in full, enlarged, cropped, isolated, layered, or supported by minimal annotations.
Device-mockup planning can use realistic device frames, simplified frames, borderless crops, floating screens, offset devices, layered screens, or multi-device systems.
The device strategy is adapted to the target platform. iPhone mockups should not automatically be reused for Google Play, and phone compositions should not simply be enlarged for tablet listings.
Composition systems can include centered-device layouts, offset-device layouts, full-bleed product UI, cropped interface details, floating UI panels, multi-device compositions, transformation frames, comparison layouts, and controlled visual sequences.
The agent defines hierarchy so one element clearly dominates each screenshot. The dominant element may be the headline, the product interface, or an approved proof point depending on the strategic role of the frame.
Typography planning covers headline family, weight, alignment, capitalization, line length, line breaks, supporting copy, app UI preservation, safe spacing, and localization behavior.
Color planning covers brand colors, backgrounds, text, accents, proof highlights, device frames, semantic highlights, and decorative elements.
Background systems may use solid brand fields, restrained gradients, abstract shapes, neutral studio environments, blurred product extensions, contextual illustrations, or full-bleed product UI.
The skill prevents decorative overload by reducing unnecessary gradients, stickers, icons, badges, floating cards, shadows, or patterns that compete with the message or product interface.
Feature highlights can be communicated through headlines, supporting lines, enlarged UI details, minimal annotations, comparisons, visual sequences, or approved floating detail cards.
Trust and proof can include verified ratings, review counts, testimonials, customer counts, awards, certifications, privacy features, expert endorsements, integrations, or measurable product outcomes.
All proof must be verified. The skill never invents ratings, awards, testimonials, download counts, user counts, press mentions, customer logos, performance improvements, health outcomes, financial results, or platform approval.
For subscription products, the agent can plan screenshots that explain premium value, plan flexibility, content access, ongoing benefits, trial context, billing cadence, or cancellation access.
Subscription messaging must not hide pricing, recurring terms, limitations, renewal conditions, or cancellation availability.
App Store planning can address iPhone and iPad separation, portrait and landscape strategy, screenshot order, target device families, iOS interface fidelity, current app version, and platform-safe composition.
Google Play planning can address Android UI fidelity, phone and tablet assets, screenshot order, device diversity, listing experiments, feature-graphic relationships, localization, and platform-specific creative adaptation.
Platform specifications can change, so final dimensions, formats, device requirements, and store rules must be verified before production export.
Tablet planning treats tablets as a distinct experience. It can account for split views, landscape layouts, multi-column interfaces, tablet navigation, denser workspaces, keyboard use, and tablet-specific screens.
The skill supports audience segmentation for beginners, professionals, teams, students, creators, travelers, buyers, sellers, subscribers, or other meaningful segments.
Each audience variant can receive its own primary problem, promise, feature proof, trust strategy, headline system, screenshot order, and visual emphasis.
Localization planning begins before the final layout. The skill defines source-copy approval, translation briefs, linguistic review, cultural review, layout recomposition, localized UI, market-specific claims, export ownership, and QA.
Localized screenshots should not be created by shrinking translated text until it fits. Layouts should be recomposed to preserve readability, hierarchy, device scale, and safe spacing.
The agent can plan for German expansion, Spanish, French, Portuguese, long compound words, right-to-left languages, different capitalization systems, locale-specific numerals, currencies, dates, and region-specific product claims.
Accessibility and readability review covers text size, contrast, type weight, line length, color dependence, clutter, reading order, language simplicity, and thumbnail-scale comprehension.
The skill can audit existing store screenshots across strategic clarity, first-frame strength, first-three narrative, headline quality, benefit clarity, UI proof, product fidelity, composition, device mockups, typography, contrast, background, brand consistency, feature priority, trust, screenshot order, localization, platform fit, production quality, and conversion readiness.
Audit findings can include the affected screenshot, observed issue, likely install-decision impact, brand impact, localization impact, evidence, recommendation, priority, effort, confidence, and validation requirement.
The skill creates creative-testing plans for headline variants, screenshot order, first-frame concepts, device treatments, UI crops, backgrounds, proof placement, feature priority, audience positioning, visual density, and color systems.
Each experiment can define the observation, hypothesis, control, variation, tested variable, target audience, market, primary metric, guardrail, sample requirement, risk, and decision rule.
The agent also creates production asset inventories covering app icons, product captures, device frames, backgrounds, illustrations, logos, approved badges, testimonials, fonts, translated copy, legal approvals, and export templates.
Each asset can be documented with source, owner, license, format, resolution, language, approval state, and risk.
Designer handoff can include strategy, audience, narrative, screenshot order, approved copy, UI crop instructions, device treatment, composition rules, typography, color, backgrounds, proof, localization, assets, export plan, verification requirements, and QA.
Export planning can define platform, device family, orientation, dimensions, format, file naming, locale code, app version, export owner, and QA owner.
The skill creates measurable acceptance criteria, production checklists, conversion-leak reports, risk assessments, open-question lists, and structured JSON specifications.
It prioritizes message clarity, product fidelity, readable UI proof, truthful claims, strategic sequencing, brand consistency, localization readiness, platform fit, testability, and production quality.
The core commercial promise is: transform app screens and feature lists into a professional store-screenshot system that helps prospective users understand the product quickly and gives designers a complete plan for producing persuasive App Store and Google Play assets.
This skill creates screenshot strategy, visual storytelling, copy direction, device-mockup planning, localization guidance, creative-testing plans, production specifications, audits, and designer handoff documentation.
It does not directly create guaranteed platform-approved visual assets, guarantee install-conversion improvement, guarantee store-ranking improvement, verify current platform requirements, verify product claims, verify asset licenses, or guarantee localization quality.
Current App Store and Google Play dimensions, file formats, screenshot counts, device-family rules, tablet requirements, listing features, experimentation tools, and review policies may change and must be verified before export.
Screenshot planning cannot compensate for a weak product proposition, outdated app interface, poor product quality, incorrect positioning, unverified claims, or incomplete localization.
A screenshot may look persuasive at full size but fail at store-listing thumbnail scale. Final assets require realistic preview testing.
Device mockups can create misleading impressions when they do not match the actual platform, device family, interface, or supported product experience.
Ratings, reviews, awards, testimonials, customer counts, performance improvements, health outcomes, financial results, security claims, privacy claims, pricing, trials, discounts, and regional availability require documented evidence and approval.
Localization recommendations require professional translation, linguistic review, cultural review, localized interface captures, market-specific claim validation, font coverage, and final-layout QA.
Accessibility and readability recommendations do not constitute accessibility certification. Final screenshots require contrast, text-size, clutter, and thumbnail-legibility review.
Creative-testing recommendations require reliable store instrumentation, sufficient traffic, representative markets, stable product positioning, meaningful guardrails, and sound statistical interpretation.
The skill cannot guarantee that store visitors will view the screenshot sequence in the intended order or inspect every frame.
Final screenshot sets require product verification, platform-specification review, legal and brand approval, design production, localization review, asset-rights confirmation, device review, export QA, and live store validation.
The skill does not replace qualified ASO strategy, legal review, localization review, brand approval, professional visual design, platform compliance review, or production QA.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
Permissions
File Scopes
This skill uses file access to read user-provided App Store listings, Google Play listings, current screenshots, app interface captures, screen recordings, Figma exports, app UI mockups, launch briefs, ASO briefs, product-positioning documents, feature lists, user personas, store descriptions, metadata, keyword research, verified user reviews, ratings, testimonials, conversion reports, A/B test summaries, competitor references, brand guidelines, color systems, typography systems, app icons, logos, approved device mockups, localization requirements, platform specifications, legal guidance, client feedback, and QA notes. It uses write access to create structured Markdown, text, CSV-style, JSON-style, YAML-style, and production-oriented outputs such as complete App Store screenshot plans, Google Play screenshot plans, screenshot narratives, headline systems, screenshot-by-screenshot specifications, device-mockup strategies, UI-crop plans, composition systems, localization plans, audience variants, creative-testing roadmaps, screenshot audits, conversion-leak reports, asset inventories, designer handoffs, export plans, acceptance criteria, QA checklists, risk assessments, and SKILL.md files. Browser access is useful when the host environment permits current App Store and Google Play specification review, public platform-guideline review, public ASO research, approved competitor listing research, public localization guidance, public accessibility guidance, or authorized asset-source review. The skill should clearly distinguish: Observed: Directly supported by supplied screenshots, product captures, store listings, product documentation, approved claims, brand files, analytics, or test results. Inferred: A likely audience response, install-decision issue, hierarchy problem, or production requirement suggested by available evidence but not directly confirmed. Recommended: A proposed narrative, headline, screenshot order, composition, UI crop, device strategy, localization adaptation, creative test, or production decision. Requires Verification: Any rating, review, testimonial, award, price, trial, discount, feature state, performance claim, privacy statement, security claim, health outcome, financial claim, customer proof, device support, regional availability, platform statement, or asset license that must be confirmed before publication. Conceptual: A proposed store-creative direction that requires product, marketing, design, legal, localization, platform, brand, and user validation. All public examples, screenshots, accounts, user names, messages, payments, addresses, health information, files, and product data should use fictional, anonymized, masked, or approved content. Store screenshots should accurately represent the current or approved product experience. Future-state or conceptual interfaces must not be published as existing functionality without explicit approval. Use only owned, licensed, approved, or properly attributed images, illustrations, icons, fonts, logos, device frames, testimonials, and third-party marks.