Bolt Prompts

Prompt Bolt.new to build a complete SaaS MVP for [PRODUCT_NAME]: a [INDUSTRY] tool where users can [CORE_ACTION_1] and [CORE_ACTION_2]. Specify the stack: [FRAMEWORK] frontend with Tailwind, Supabase for auth and Postgres database with tables [TABLE_1] and [TABLE_2], and Stripe for the [PRICE]/month plan. Ask Bolt to scaffold auth, the dashboard, billing, and a landing page in one pass, then iterate on the [FEATURE] screen using diff-based editing. Preview everything in the browser before deploying.

Import my Figma design for [PROJECT_NAME] directly into Bolt.new chat and have it build the app from the visual reference. The design covers [NUMBER] screens: [SCREEN_1], [SCREEN_2], [SCREEN_3]. Tell Bolt to match the design tokens ([COLOR_1], [FONT_NAME]), implement the [COMPONENT] as a reusable component, and wire the [BUTTON] to [ACTION]. Review the generated code for hardcoded values and replace them with the theme variables in [THEME_FILE].

Have Bolt.new add Stripe payments to my app [APP_NAME]. Requirements: [PLAN_1] at $[PRICE_1]/month and [PLAN_2] at $[PRICE_2]/month, a checkout flow from the [PAGE] page, webhook handling for subscription events in [WEBHOOK_FILE], and a customer portal link on the [SETTINGS] page. Ask Bolt to use the v2 automated Stripe integration, store keys in environment variables (never hardcoded), and test the flow with Stripe test mode before going live.

Prompt Bolt.new to build an SEO-optimized landing page for [PRODUCT_NAME] targeting the keyword '[KEYWORD]'. Requirements: semantic HTML with proper heading hierarchy, meta title '[META_TITLE]' and description '[META_DESCRIPTION]', Open Graph tags for [SOCIAL_PLATFORM], a [LOAD_TIME]-second load budget, and schema markup for [SCHEMA_TYPE]. Ask Bolt to use its v2 SEO boosting, generate the sitemap and robots.txt, and verify the page scores [SCORE]+ on [SEO_TOOL].

Refine my Bolt.new app [APP_NAME] using diff-based editing so every change is visible before I accept it. The backlog: 1) restyle the [COMPONENT] to [DESIGN_CHANGE], 2) add [FEATURE] to the [PAGE] page, 3) fix the bug where [BUG_DESCRIPTION]. Tackle them one at a time in chat, review each diff for unintended changes to [SENSITIVE_FILE], and reject any diff that touches more than [NUMBER] files without explanation. Export to GitHub on the Pro plan when the iteration is stable.

Have Bolt.new wire Supabase authentication into [APP_NAME] with [AUTH_METHODS, e.g. email magic link and Google OAuth]. Create the [TABLE] table with row-level security policies so users only see their own rows, and have Bolt generate the migration SQL explicitly so I can review it. Ask it to add a protected [ROUTE] page, a login screen matching the [BRAND] style, and session handling that survives page reloads. Test with [NUMBER] test users before launch.

Turn my Bolt.new project [PROJECT_NAME] into a reusable team template for [TEAM_NAME]. Strip out client-specific content, keep the [STACK] stack, the [COMPONENT_LIBRARY] component library, and the standard [FOLDER] folder structure. Document the template in [README_FILE] with setup steps, the environment variables in [ENV_EXAMPLE], and the naming conventions. Save it as a team template so every new [PROJECT_TYPE] project starts from this exact foundation.

Configure Bolt.new model settings for my project [PROJECT_NAME] in [PHASE, e.g. rapid prototyping]. Use the lighter reasoning setting for UI iteration on [PAGE_1] and [PAGE_2] to save tokens, and switch to deeper reasoning (Opus 4.6 class) for the complex [FEATURE] implementation. Save the project context in claude.md so settings persist across sessions. Track token usage against the free tier ([TOKENS_PER_MONTH]/month, [TOKENS_PER_DAY]/day cap) or the [PLAN] plan.

Use Bolt.new Expo integration to prepare a mobile version of [APP_NAME]. Requirements: the [SCREEN_1] and [SCREEN_2] screens adapted for mobile layouts, touch-friendly [COMPONENT] components, and offline caching for [DATA_TYPE]. Have Bolt generate the Expo configuration, test the build in Expo Go on [DEVICE_1] and [DEVICE_2], and list every web-only dependency in [WEB_ONLY_FILE] that needs a native replacement before app store submission.

Plan my Bolt.new token budget for building [PROJECT_NAME] over [WEEKS] weeks. The free tier gives [TOKENS_PER_MONTH] tokens/month with a [TOKENS_PER_DAY] daily cap, which covers roughly [PROMPTS] meaningful prompts per day. Allocate tokens: [PCT]% for initial scaffolding, [PCT]% for iteration, [PCT]% for bug fixes. Define the escalation rule: when the daily cap hits, continue in [FALLBACK_TOOL] or upgrade to the [PLAN] plan at $[PRICE]/month.