These are starting points, not rigid templates. Copy them, fill in the brackets, and adapt them to your idea. Save your versions as you ship more apps. Over time you’ll build a personal prompt library that reflects how you think and what you build. Each starter covers all five parts of the prompt anatomy.Documentation Index
Fetch the complete documentation index at: https://mayson.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Marketplace
App name: [Name]. A marketplace where [sellers: describe who they are] can list [what they're selling] and [buyers: describe who they are] can browse and purchase.
Seller side: create a listing with [fields: e.g. title, description, price, images, category], manage their listings, view incoming orders, track earnings.
Buyer side: browse all listings, filter by [attributes: e.g. category, price range, location], view a listing detail page, complete a purchase, leave a review after the order is complete.
Shared features: auth for both roles, messaging between buyer and seller, order status tracking.
Design: [visual direction].
SaaS tool / dashboard
App name: [Name]. A [category: e.g. project management / analytics / CRM] tool for [target user: e.g. solo freelancers / small teams / content creators].
The core job: [one sentence on the primary action the app enables].
Dashboard: shows [key metrics or summary] and [recent activity or quick actions].
Core workflow: [describe the primary feature step by step, what the user does, what the app does, what they see].
Settings: users can update [what, e.g. profile, notification preferences, connected accounts].
Design: [visual direction].
Internal operations tool
App name: [Name]. An internal tool for [team or company type] to [manage what, e.g. track support tickets / manage inventory / review applicants].
Not customer-facing. All routes require login.
Roles:
- [Role A]: can [specific actions].
- [Role B]: can [specific actions].
Core workflow: [describe the end-to-end process this tool manages].
Data tracked: [list the main entities, e.g. tickets, agents, users, products].
Design: functional and dense, optimized for frequent use. [Light/dark] background, [color accent], data tables where relevant.
Landing page + waitlist
Marketing landing page for [App name], [one-sentence description of what the product does and who it's for].
Sections (in order):
1. Hero: headline "[your headline]", subheading "[your subheading]", CTA button "[button text]"
2. Feature grid: three columns, [feature 1 name + one sentence], [feature 2], [feature 3]
3. How it works: three steps, [step 1], [step 2], [step 3]
4. Social proof: [testimonials / logos / stat callouts, or leave this out]
5. Waitlist signup: email input + submit button. On submit: save the email, show a success message inline. No redirect.
Design: [visual direction].
No backend dashboard needed. Just capture waitlist signups.
Browser game
App name: [Name]. A [game type: e.g. puzzle / arcade / strategy] game.
Core mechanic: [one sentence, what the player does and what makes it a game].
Rules:
- Win condition: [what triggers a win]
- Lose condition: [what ends the game]
- Scoring: [how points are earned]
Controls: [keyboard arrows / WASD / mouse clicks / touch, specify what]
Screens:
- Start screen: game title, high score, Start button
- Game screen: [describe the play area and key UI elements like score and lives]
- Game over screen: final score, Play Again button
Design: [visual direction, e.g. retro pixel art, dark neon, clean minimal].
E-commerce store
App name: [Name]. An online store where customers can browse [product category] and complete a purchase.
Product catalog: each product has a name, price, description, [number] images, category tags, and stock status. Products can be filtered by [attributes: e.g. category, price range, size, color].
Customer flow: browse catalog, view product detail, add to cart, checkout with shipping details and payment, receive order confirmation.
Account: customers can create an account to track orders and save their shipping address. Guest checkout also supported.
[Optional admin panel: manage products (add, edit, archive), view and update order status, track inventory.]
Design: [visual direction, e.g. clean and editorial, product-photography-forward, white background with strong typographic hierarchy].
Community / social app
App name: [Name]. A community platform where [describe who] can [core action: post, share, discuss, connect].
User profiles: display name, avatar, bio, [optional: location, expertise tags, join date]. Users can follow each other.
Content: users can create [content type: posts, questions, reviews, builds]. Each [post/item] has [fields]. Other users can [interact: like, comment, reply, bookmark, share].
Feed: the main feed shows [what: recent posts / posts from followed users / trending]. Users can filter or sort by [attributes].
Notifications: users are notified when someone [triggers: likes, comments, follows, mentions them].
Design: [visual direction].
AI assistant / chatbot tool
App name: [Name]. An AI-powered [assistant / advisor / tool] for [target user] that helps with [specific job to be done].
Chat interface: users type a message and receive a response. Conversation history is preserved in the current session. Users can start a new conversation or continue a previous one from a sidebar list.
Context (if needed): [describe any context the AI should use, e.g. the user's uploaded documents, their stored preferences, previously saved data].
Output format: responses should appear as [plain text / formatted with markdown / structured steps / a card-based layout].
Saved outputs: users can [save, export, copy] individual responses to [where: their library, clipboard, a file].
Conversation sidebar: lists past sessions with auto-generated titles from the first message. Users can rename or delete sessions.
Design: [visual direction, e.g. clean minimal dark mode, terminal-inspired with monospace type, or warm and approachable with a centered chat layout].
Mobile app
App name: [Name]. A mobile app for [target user] to [core job in one sentence].
Navigation: [bottom tab bar with [number] tabs: [Tab 1 name], [Tab 2 name], [Tab 3 name]] OR [side drawer] OR [top tab bar with swipe between screens].
Core screen: [name and describe the screen users spend the most time on, what they see and what they can do].
Secondary screens: [list key screens and their purpose, e.g. "Profile: edit name, avatar, notification settings"].
Mobile interactions: [specify any touch-native behaviors, e.g. pull-to-refresh on the feed, swipe to dismiss notifications, long-press to open a context menu on list items].
Auth: [describe login method, e.g. phone number + OTP, email + password, or Sign in with Google].
Design: [visual direction suited for mobile, e.g. native-feeling with system typography and bottom-anchored CTAs, or branded with custom type and a defined color system. Specify light, dark, or auto mode].