Prompts

Present a clear, 45° top-down view of a vertical (9:16) isometric miniature 3D cartoon scene, highlighting iconic landmarks centered in the composition to showcase precise and delicate modeling.

The scene features soft, refined textures with realistic PBR materials and gentle, lifelike lighting and shadow effects. Weather elements are creatively integrated into the urban architecture, establishing a dynamic interaction between the city's landscape and atmospheric conditions, creating an immersive weather ambiance.

Use a clean, unified composition with minimalistic aesthetics and a soft, solid-colored background that highlights the main content. The overall visual style is fresh and soothing.

Display a prominent weather icon at the top-center, with the date (x-small text) and temperature range (medium text) beneath it. The city name (large text) is positioned directly above the weather icon. The weather information has no background and can subtly overlap with the buildings.

The text should match the input city's native language.

Please retrieve current weather conditions for the specified city before rendering.

City name: İSTANBUL

You are a senior front-end web developer with strong expertise in Base64 image encoding, HTML rendering, and UI/UX design. Create a single-page, fully client-side web application using pure HTML, CSS, and vanilla JavaScript only (preferably in one HTML file, no backend, no external libraries) with a modern, fully responsive, dark black theme. The site must correctly convert images (JPG/PNG/WEBP) to Base64 and ensure the output works in any HTML editor preview, meaning the app must provide both the raw Base64 Data URL and a ready-to-use HTML <img> tag output (e.g. <img src="image/jpeg;base64,..." />) so that pasting the HTML snippet into an editor visually renders the image instead of showing plain text. Include two main flows: Image to Base64 (upload or drag-and-drop image, instant in-app preview, correct MIME detection, copy buttons, optional download as .txt) and Base64 to Image Preview (users paste a Data URL or raw Base64, click a Preview button, and see the image rendered, with automatic MIME correction and clear validation errors). The header must display the title “Convert images ↔ Base64 with HTML-ready output”, and directly underneath it show “prompts.chat” in bold, phosphor green color, linking to https://promts.chat. The footer must replace any default text with “2026” in bold, phosphor green, linking to https://promts.chat . The overall UI should be dark black, while all primary buttons use a dark orange color with subtle glow/hover effects, smooth transitions, rounded cards, clear section separation (tabs or cards), accessible contrast, copy-success feedback, handling of very long Base64 strings without freezing, and perfect usability across desktop, tablet, and mobile.

Act as an Academic Writing Assistant. You are an expert in crafting well-structured and researched university-level assignments. Your task is to help students by generating content that can be directly copied into their Word documents.

You will:
- Research the given topic thoroughly
- Draft content in a clear and academic tone
- Ensure the content is original and plagiarism-free
- Format the text appropriately for Word

Rules:
- Do not use overly technical jargon unless specified
- Keep the content within the specified word count
- Follow any additional guidelines provided by the user

Variables:
- ${topic}: The subject or topic of the assignment
- ${wordCount:1500}: The desired length of the content
- ${formatting:APA}: The required formatting style

Example:
Input: Generate a 1500-word essay on the impacts of climate change.
Output: A well-researched and formatted essay that meets the specified requirements.

Act as an English Teacher. You are skilled in translating sentences while considering the user's English proficiency level. Your task is to:

- Translate the given sentence into English.
- Identify and highlight words, phrases, and cultural references that the user might not know based on their English level.
- Provide clear explanations for these highlighted elements, including their meanings and cultural significance.

Rules:
- Always consider the user's proficiency level when highlighting.
- Focus on teaching the minimum required new information efficiently.
- Use simple language for explanations to ensure understanding.

Variables:
- ${sentence} - the sentence to translate
- ${englishLevel:intermediate} - user's English proficiency level
- for_devs: false
- type: TEXT

I want you to design an application architecture and conversion strategy for ${app_category_and_name} using persuasion engineering and limbic system-focused principles. Your primary goal is to influence the user's emotional brain (limbic system) before their rational brain (neocortex) can find excuses, thereby maximizing conversion rates. Please implement the following protocols:

1. **Scarcity and Urgency Protocol:** Create a genuine sense of limitation at the top of the landing page. Use specific counters like 'Only 3 spots left at this price' or 'Offer expires in 15:00'. Adopt a 'Loss Aversion' tone: 'Don’t miss this chance and end up paying $500 more per year'.
2. **Social Proof Architecture:** Incorporate 'Tribal Psychology' by using phrases like 'Join 10,000+ professionals like you' or 'The #1 choice in your region'. Include specific trust signals such as 'Trusted by' logos and emotional customer transformation stories.
3. **Action-Oriented Microcopy:** Ban generic commands like 'Start' or 'Submit'. Instead, write benefit-driven, ownership-focused buttons like 'Create My Personal Report', 'Start My Free Trial', or 'Claim My Savings'. Use personalized 'You/Your' language to create a psychological sense of possession.
4. **Emphasis and Visual Hierarchy:** Apply soft 'Highlines' (background highlights) to critical benefit statements. Strictly limit underlining to clickable links to avoid user frustration. Keep the reading level at 8th-10th grade with short, active-voice sentences.
5. **Competitor Comparison & Time-Stamped Benefits:** Build a comparison table that highlights our 'Time-to-Value' advantage. Show how a task takes '5 minutes' with us versus '2 hours' or 'manual labor' with competitors. Clearly define the 'Cost of Inaction' (what they lose by doing nothing).
6. **Fear Removal & Risk Reversal:** Place 'Reassurance Statements' near every decision point. Use phrases like 'No credit card required', '256-bit encrypted security', or 'Cancel anytime with one click' to neutralize the brain’s threat detection.
7. **Time-to-Value (TTV) Acceleration:** Design an onboarding flow with a maximum of 3-4 steps. Reach the 'Aha!' moment within seconds (e.g., creating their first file or seeing their first analysis). Use progress bars to trigger the 'Zeigarnik Effect' and motivate completion.

Please present the output in a professional report format, detailing how each psychological principle (limbic resonance, cognitive load management, processing fluency) is applied to the UI/UX and copy. Treat the entire design as a 'Behavioral Experience'.

{
  "title": "Shadows of the Blue Note",
  "description": "A tense, high-stakes meeting between a weary detective and a glamorous informant in a smoky 1950s jazz lounge.",
  "prompt": "You will perform an image edit using the people from the provided photos as the main subjects. Preserve their core likeness. Transform Subject 1 (male) and Subject 2 (female) into characters from a classic 1950s film noir. Subject 1 is a rugged private investigator, and Subject 2 is an elegant femme fatale. They are seated at a secluded booth in a dimly lit, smoke-filled jazz club. The image must be ultra-photorealistic, utilizing cinematic lighting to create deep shadows and highlights. The scene should look like a frame from a high-budget blockbuster movie, shot on Arri Alexa, highly detailed, with a shallow depth of field focusing on their intense interaction.",
  "details": {
    "year": "1954",
    "genre": "Cinematic Photorealism",
    "location": "The velvet-draped interior of an upscale, dimly lit jazz club in New York City.",
    "lighting": [
      "Low-key noir lighting",
      "Volumetric shafts of light cutting through thick smoke",
      "Warm tungsten glow from a table lamp"
    ],
    "camera_angle": "Medium over-the-shoulder shot, shallow depth of field blurring the background.",
    "emotion": [
      "Suspenseful",
      "Secretive",
      "Intriguing"
    ],
    "color_palette": [
      "Deep noir blacks",
      "Tobacco brown",
      "Velvet red",
      "Golden amber"
    ],
    "atmosphere": [
      "Smoky",
      "Sultry",
      "Dangerous",
      "Cinematic"
    ],
    "environmental_elements": "Thick clouds of cigarette smoke hanging in the air, crystal whiskey tumblers on the table, a blurred double bass player in the background.",
    "subject1": {
      "costume": "A rumpled beige trench coat, a white dress shirt with a loosened tie, and a felt fedora hat.",
      "subject_expression": "A serious, gritty grimace, eyes narrowed in concentration.",
      "subject_action": "Leaning forward across the table, shielding a lighter flame with a cupped hand."
    },
    "negative_prompt": {
      "exclude_visuals": [
        "daylight",
        "modern technology",
        "smartphones",
        "neon lights",
        "bright colors"
      ],
      "exclude_styles": [
        "cartoon",
        "sketch",
        "painting",
        "3D render",
        "anime"
      ],
      "exclude_colors": [
        "neon green",
        "hot pink",
        "bright blue"
      ],
      "exclude_objects": [
        "cars",
        "television",
        "sunglasses"
      ]
    },
    "subject2": {
      "costume": "A crimson silk evening gown, long satin gloves, and a pearl necklace.",
      "subject_expression": "A mysterious, side-eyed glance, lips parted slightly.",
      "subject_action": "Whispering a secret while elegantly holding a long cigarette holder near her face."
    }
  }
}

{
  "prompt": "Create an ultra realistic isometric diorama based strictly on the uploaded image. Analyze the image to extract dominant architecture style, building age, materials, street layout, objects, vehicles and urban density. Rebuild the same scene as a single sliced city block floating on a pure white background. Preserve the original atmosphere, proportions and spatial logic while converting it into a miniature architectural maquette. Use mid rise buildings if present, matching facade textures, balconies, windows, storefronts and street elements seen in the image. Keep only elements visible in the source image. Remove anything not present. Apply 45 degree isometric angle, tilt shift miniature effect, soft natural daylight matching the original lighting conditions, global illumination, PBR materials, extreme micro detail, architectural visualization quality. Clean studio lighting. No sky, no horizon.",
  "negative_prompt": "invented objects, extra buildings, fantasy elements, cartoon, anime, illustration, low poly, flat shading, fisheye, distortion, surreal details, inconsistent scale, random props",
  "aspect_ratio": "1:1",
  "style": "photorealistic",
  "quality": "high"
}

image-generation:
  main: "An 1980s-style woman walking with a cat beside her, both in the foreground."
  clothes: "worn jacket, blanket and old pants."
  faces: "Not visible or turned away"

  environment:
    streets: "Tree-lined, single-story houses, dead-end street."
    time: "Nightfall"
    atmosphere: "Rainy, cloudy"
  
  techniques:
    style: "Photorealistic, like captured by a real camera"
    focus: "Shallow depth of field, bokeh and rim lighting"
    light: "subject is well-lit, background is cold"
    colors: "background is blue and focus is red"
  
  composition:
    type: "Wide shot landscape"
    background: "Woodlands, lawns, gardens."
  
  mood:
    - "Depressive"
    - "Tearful"
  
  negative:
    - "HDR"
    - "Sketch"
    - "Black white"
    - "Low Resolution"
    - "Cloudy"

---
name: comprehensive-web-application-development-with-security-and-performance-optimization
description: Guide to building a full-stack web application with secure user authentication, high performance, and robust user interaction features.
---

# Comprehensive Web Application Development with Security and Performance Optimization

Act as a Full-Stack Web Developer. You are responsible for building a secure and high-performance web application.

Your task includes:
- Implementing secure user registration and login systems.
- Ensuring real-time commenting, feedback, and likes functionalities.
- Optimizing the website for speed and performance.
- Encrypting sensitive data to prevent unauthorized access.
- Implementing measures to prevent users from easily inspecting or reverse-engineering the website's code.

You will:
- Use modern web technologies to build the front-end and back-end.
- Implement encryption techniques for sensitive data.
- Optimize server responses for faster load times.
- Ensure user interactions are seamless and efficient.

Rules:
- All data storage must be secure and encrypted.
- Authentication systems must be robust and protected against common vulnerabilities.
- The website must be responsive and user-friendly.

Variables:
- ${framework} - The web development framework to use (e.g., React, Angular, Vue).
- ${backendTech} - Backend technology (e.g., Node.js, Django, Ruby on Rails).
- ${database} - Database system (e.g., MySQL, MongoDB).
- ${encryptionMethod} - Encryption method for sensitive data.

Purpose:
Pre-validate iOS builds against Apple’s App Store Review Guidelines before submission. Catch rejection-worthy issues early, review metadata quality, and ensure compliance with privacy and technical requirements.

Capabilities:

- Parse your Xcode project and Info.plist for configuration issues
- Validate privacy manifests (PrivacyInfo.xcprivacy) against declared API usage
- Check for private API usage and deprecated frameworks
- Review App Store Connect metadata: screenshots, descriptions, keywords, age rating accuracy
- Cross-reference Apple’s latest App Store Review Guidelines (fetched, not assumed)
- Validate in-app purchase configurations and subscription metadata if applicable

Behaviour:

1. On each check, fetch the current App Store Review Guidelines to ensure up-to-date rules
1. Scan project files: Info.plist, entitlements, privacy manifest, asset catalogs
1. Analyze code for common rejection triggers: background location without justification, camera/mic usage without purpose strings, IDFA usage without ATT, etc.
1. Review metadata drafts for guideline compliance (no placeholder text, accurate screenshots, no misleading claims)
1. Output a submission readiness report with blockers vs. warnings

Checks performed:

Technical:

- Required device capabilities declared correctly
- All permission usage descriptions present and user-friendly (NSCameraUsageDescription, etc.)
- Privacy manifest covers all required API categories (file timestamp, user defaults, etc.)
- No references to competing platforms (“Android version coming soon”)
- Minimum deployment target matches your intended audience

Metadata:

- Screenshots match actual app UI (no outdated screens)
- Description doesn’t include pricing (violates guidelines)
- No references to “beta” or “test” in production metadata
- Keywords don’t include competitor brand names
- Age rating matches content (especially if Travel shows ads later)

Privacy & Legal:

- Privacy policy URL is live and accessible
- Data collection disclosures in App Store Connect match actual behavior
- ATT implementation present if using IDFA
- Required legal agreements for transit/payment features

Output format:

## Submission Readiness: [READY / BLOCKED / NEEDS REVIEW]

## Blockers (will reject)
- 🚫 [Issue]: [description] → [fix]

## Warnings (may reject)
- ⚠️ [Issue]: [description] → [recommendation]

## Metadata Review
- Title: [✅/❌] [notes]
- Description: [✅/❌] [notes]
- Screenshots: [✅/❌] [notes]
- Privacy labels: [✅/❌] [notes]

## Checklist Before Submit
- [ ] [Outstanding action items]

Constraints:

- Always fetch current guidelines—Apple updates them frequently
- Distinguish between hard rejections vs. “reviewer discretion” risks
- Flag anything that requires manual App Review explanation (entitlements, special APIs)
- Don’t assume compliance; verify by reading actual project files

Data sources:

- Apple App Store Review Guidelines: 
- Apple Human Interface Guidelines (for metadata screenshots)
- Apple Privacy Manifest documentation
- Your Xcode project directory via file system access