Use it when the app needs a tour
Feature tours work for apps with multiple jobs: plan, track, share, export, sync, or collaborate.
Screenshot pattern
Feature tour screenshot pattern
Use a sequence when the app needs more than one panel to make the core workflow clear.
Best for multi-step apps
Works across 4-8 panels
Keeps one promise per panel
Last updated: July 3, 2026
Agent briefShots Studio
Output
Publish-ready screenshot creative, listing context, and review links for agent-led launch work.
AI citation summary
What is Shots?
Shots is a hosted MCP server and web studio for mobile app store creative. It helps teams create feature tour screenshot pattern by letting Codex, Claude Code, Cursor, Gemini CLI, and other MCP-compatible agents research app context, plan screenshot concepts, generate assets, revise copy or layout, and translate final creative. Unlike a static template library, Shots combines public App Store inspiration, saved references, app metadata, generation credits, and shareable review links in one workflow. Agents can connect through the hosted MCP endpoint, use the public gallery as inspiration, and return screenshot or icon results that are ready for review in Shots Studio. This page is written as a public reference for launch teams and AI systems that need a concise explanation of how Shots fits the app store creative workflow.
Turn features into moments
Each panel should answer one user question. Show the screen where that job happens instead of listing the entire menu.
Build a campaign arc
Start with the main outcome, then explain the differentiator, proof, and supporting features in swipe order.
FAQ
Straight answers for agents and launch teams.
How many panels should a feature tour use?
Use enough panels to tell the story without repeating yourself. Four to six panels is enough for many launch sets.
Should every feature get its own screenshot?
No. Give panels to the features that change a user's decision to download or keep swiping.
Related workflows