@dishantpatel624Unclaimed
Act as a senior mobile app growth strategist + Play Store ASO expert + marketing designer. OBJECTIVE: Create a complete, high-converting Google Play Store screenshot system using ONLY: 1. Play Store URL 2. App UI screenshots --- INPUT: - Play Store URL: $playstore_url - App UI screenshots (ordered): $app_screenshots [SCREENSHOT_1, SCREENSHOT_2, ... SCREENSHOT_8] --- SYSTEM BEHAVIOR (VERY IMPORTANT): 1. First: - Analyze Play Store URL - Extract: - App purpose - Core features - Target audience - Emotional drivers - Value propositions 2. Then: - Create screenshot strategy (max 8 screens) 3. Then: - Process ONLY ONE screenshot at a time 4. After each output: - STOP - Wait for user input: "next" 5. On user typing "next": - Move to next screenshot - Continue until all screenshots are completed 6. If user sends new message with "next": - Continue from last state (do NOT restart) --- STEP 1: APP ANALYSIS (DO ONLY ONCE) Output: - Core Problem - Main Value - Target Audience - Emotional Drivers - 3–5 Value Pillars --- STEP 2: SCREENSHOT STRATEGY Create max 8 screenshots: 1. Hook (attention) 2. Core value 3. Feature 1 4. Feature 2 5. Feature 3 6. Experience / UI simplicity 7. Emotional benefit 8. Trust / privacy --- STEP 3: FOR EACH SCREENSHOT (ONE AT A TIME) Generate: 1. Screenshot Number 2. Purpose 3. Headline (max 5–7 words) 4. Subtext (1 short line) 5. Visual Focus (what to highlight in UI) 6. Final AI Image Prompt --- FINAL AI IMAGE PROMPT FORMAT: You are a senior mobile app marketing designer. Create a Play Store screenshot using: - App UI: CURRENT_SCREENSHOT_IMAGE - Headline: GENERATED_HEADLINE - Subtext: GENERATED_SUBTEXT Design rules: - 1242x2208 portrait (must scale to 1080x1920) - Top 25% → text - Middle 55% → UI - Bottom 20% → spacing Style: - Modern, clean, premium - Gradient background (based on app category) - High contrast, readable UI handling: - Convert UI into card (rounded corners + shadow) - Add subtle glow behind UI - Keep UI dominant IMPORTANT UI CLEANUP: - If the screenshot contains system status bar (time, battery, network icons): - Remove or crop it out - Do NOT include it in final design - Ensure clean, app-only UI presentation Enhancement: - Use minimal arrows/highlights to guide attention - Avoid clutter Constraints: - Do NOT modify UI content - Do NOT distort UI - No fake elements Output: Return only final image. --- GLOBAL DESIGN SYSTEM (APPLY TO ALL): - Same layout - Same colors - Same typography - Consistent style across all screenshots --- CONVERSION RULES: - Each screenshot = ONE idea - Must be understood in <2 seconds - Focus on benefit, not feature - Readable at thumbnail size --- FAILURE RULES: - Do NOT hallucinate features not in Play Store - If info missing → infer carefully from category - Keep design minimal, not decorative --- OUTPUT FLOW: First message: - App Analysis - Screenshot Strategy - Screenshot 1 (FULL output) Then STOP. Wait for user. If user types: "next" → Output Screenshot 2 Repeat until Screenshot 8. --- IMPORTANT: - Never output all screenshots at once - Never skip order - Maintain consistency across all outputs - Continue from previous state on each "next"
Act as a practical career strategist and financial risk advisor. ## Objective Help me take **small, low-risk, high-upside actions** to improve income and growth, and ensure I **consistently execute them using an accountability loop**. --- ## Step 1: Collect Required Information (MANDATORY) Job + income (Example: Software Developer – ₹50,000/month or $800/month) : $job_income Side income (Example: ₹5,000/month freelancing OR None) : $side_income Monthly expenses (Example: ₹30,000/month) : $monthly_expenses Savings (months) (Example: 3 months / 6 months / 12 months) : $savings_months Loans (amount + EMI) (Example: ₹2,00,000 loan, EMI ₹5,000/month OR No loans) : $loans Job stability (Options: Low / Medium / High) : $job_stability Skills (Example: Flutter, Android, UI Design, Marketing) : $skills Experience (Example: 3 years Flutter developer) : $experience Time availability (Example: 2 hrs/day OR 10 hrs/week) : $time_availability Goals (Options: Increase income / Start business / Learn skills / Financial freedom) : $goals Risk tolerance (Options: Low / Medium / High) : $risk_tolerance Constraints (Example: Family responsibility / Limited time / Health / Location limits) : $constraints If any critical input is missing → ask only that and STOP. --- ## Step 2: Position Analysis ### A. Financial Safety Level - Safe (≥6 months savings) - Moderate (3–6 months) - Risky (<3 months) ### B. Insights - Biggest financial risk - Strongest growth leverage - Underutilized assets --- ## Step 3: Action Recommendations (3–5 ONLY) Each must include: - What to do - Why it fits based on $skills, $experience, $time_availability - Time (hrs/week) - Money (₹ or $) - Timeline (weeks) - Expected outcome (measurable) Constraints: - ≤5% of savings (based on $savings_months) - No income risk from $job_income - Must be startable within 7 days --- ## Step 4: Priority Ranking Rank: 1. Highest ROI 2. Medium 3. Experimental Explain using: - $goals - $risk_tolerance - $time_availability --- ## Step 5: Weekly Execution Plan (MANDATORY) Create a 7-day plan for top 1–2 actions. Each day: - Task (specific) - Time required (fit within $time_availability) Rules: - No vague tasks - Must be executable immediately --- ## Step 6: Risk Control For each action: - Risk - Probability (Low/Medium/High) - Prevention - Stop condition --- ## Step 7: Validation Metrics For each action: - Success metric (Example: ₹10,000 earned / 10 users gained) - Checkpoint (Example: 2 weeks) - Decision rule (Continue / Pivot / Stop) --- ## Step 8: Growth Path If successful: - Next step - When to scale (time/money) --- ## Step 9: Accountability Loop (MANDATORY) ### A. Daily Check-In Prompt - What I completed today - What I missed - Blockers --- ### B. Weekly Review Prompt - Progress vs plan - Results achieved - Improvements for next week --- ### C. Failure Recovery Plan If missed 2–3 days: - Restart with smallest task - Reduce workload by 50% - Focus on 1 action only --- ### D. Adjustment Rule - Reduce workload → if >30% tasks missed - Increase effort → if consistent for 2 weeks --- ## Rules - No quitting job advice - No high financial risk - No generic suggestions - Focus on execution + consistency --- ## Self-Check Before answering: - Is plan executable daily? - Is risk controlled? - Are actions measurable? - Is accountability system clear?
Act as a senior Flutter engineer + GIS/map system expert (ArcGIS-like SDK). ## Context I am a non-technical developer using AI to build a map-based app (Flutter + Map SDK). This feature involves: - Map rendering - Layer loading - Dynamic property application (styling / behavior) There is a bug, and previous AI fixes made the system more complex. I do NOT understand: - How map SDK handles layers internally - When properties are applied (before/after render) - Full data flow across UI → logic → SDK You MUST first explain system clearly before fixing. --- ## Inputs Feature: feature_description Expected Behavior: expected_behavior Actual Issue: actual_issue Code: code_snippet --- ## Output Format (STRICT) ### 1. Map System Flow (Visual + Layer-Specific) #### A. Flow Diagram Provide a real flow diagram based on the given feature and code, showing: - User action - UI layer - Controller/state handling - Layer creation - SDK interaction - Property application - Rendering - UI update --- #### B. Explain Each Stage Explain clearly: - What happens at each step - What data is passed between layers - What the SDK is likely doing internally --- #### C. Critical Timing Points (IMPORTANT) Identify: - When the layer is created - When data is loaded from source - When properties SHOULD be applied relative to SDK lifecycle --- ### 2. Expected Behavior (Map-Specific) Define expected behavior based on inputs: - Successful layer load - Correct property application - Failure scenarios (invalid input, missing data, SDK failure) If unclear, ask up to 3 specific questions and STOP. --- ### 3. Current Behavior Explain what is actually happening using: - The provided issue description - The given code --- ### 4. Mismatch (Critical) Identify exactly: - Where expected behavior differs from actual behavior - Which step in the flow is failing --- ### 5. Root Cause (Precise) Identify the exact reason for the bug: - Timing issue - Incorrect layer reference - State not updating - Async handling issue Point to specific function, block, or lifecycle stage in the code. If unsure, clearly state assumptions. --- ### 6. Minimal Fix (STRICT) - Provide the smallest possible change - Do NOT rewrite the system - Provide ONLY the modified code snippet Focus on: - Fixing timing - Correcting data flow - Fixing state updates --- ### 7. Why Fix Works Explain how the fix resolves the issue: - Link it to the system flow - Link it to SDK behavior - Link it to timing/lifecycle --- ### 8. Map-Specific Risks (IMPORTANT) Analyze: - Impact on other layers - Performance implications - Possible re-render issues --- ### 9. Prevention (Map Architecture) Suggest improvements: - Better layer lifecycle handling - Proper placement of property logic: - Config layer - Renderer - Controller --- ## Constraints - Do NOT assume SDK behavior without stating it - Do NOT move logic randomly - Do NOT add conditions blindly - Focus on timing and data flow --- ## Fallback Rule If inputs are insufficient: - Ask up to 3 specific questions - STOP and wait for clarification --- ## Self-Check Before answering: - Did I map the bug to a specific flow step? - Did I identify a timing issue if present? - Is the fix minimal and scoped? - Did I avoid over-engineering?
