title: Ultra Photorealistic Rooftop Pool Portrait

summary: { "packname": "BOLD - Rooftop Inferno / Golden Hour", "intent": "Generate an ultra photorealistic, raw-candid iPhone-style rooftop pool portrait with dominant, confident energy and editorial polish…

credit: "Ultra Photorealistic Rooftop Pool Portrait" by prompts.chat (https://incantory.ai/prompts-chat/ultra-photorealistic-rooftop-pool-portrait), licensed CC0-1.0

pack_name: BOLD - Rooftop Inferno / Golden Hour

intent: Generate an ultra photorealistic, raw-candid iPhone-style rooftop pool portrait with dominant, confident energy and editorial polish, without looking staged or studio-lit.

age_requirement: All subjects must be adults, 21+.

nudity_level: Non-explicit. Swimwear only. No visible nipples, areola, or genitals. No sheer transparency that reveals explicit anatomy.

tone: Confidence-forward, not pornographic. Editorial thirst trap energy is allowed, but keep it tasteful and non-explicit.

photography_style: RAW candid iPhone photography

realism: Hyper realistic, texture-forward, pores and natural skin detail visible

resolution_hint: 8K look (high detail, crisp texture, not artificially sharpened)

grading: Natural but high contrast from harsh sun, minimal stylization, avoid cinematic teal-orange look

retouching: No heavy retouching, no plastic skin, keep micro texture

vibe: Influencer and editorial hybrid, premium but unfiltered

overall_mood_keywords:
bold
dominant
unbothered
timeless
high engagement
screenshot-worthy
confidence over sexuality

location_type: Luxury rooftop pool

key_background_elements:
city skyline
glass railing
infinity edge
minimal crowd
quiet luxury atmosphere

time_of_day: Sunset into golden hour with fire tones

atmosphere_details: city lights beginning to glow in the distance

crowd_level: Minimal

extras_behavior: If any extras appear, they must be distant, blurred, and non-distracting. The scene reads as luxury silence.

type: Single primary subject

gender_presentation: Feminine

age: Adult 21+

build: Athletic, feminine power frame

waist: Slim waist with visible core activation

upper_body: Defined shoulders and arms, strong posture

legs: Long leg lines emphasized by pose

pose_energy: Body claiming space, grounded dominance

eyes: Big, confident eyes, direct or half-lidded gaze

expression: Cool, dominant, unbothered, no performative smile

freckles: Light freckles visible under harsh light

lips: Natural full lips, relaxed but assertive

emotion_keywords:
calm dominance
zero apology energy
I know how this looks

undertone: Light neutral undertone

finish: SPF plus natural oil sheen

texture: Visible pores and realistic micro texture

highlights: Sun-kissed highlights on shoulders and collarbones

avoid:
over-smoothed faces
porcelain skin
beauty-filter blur

style: Slicked back from heat with a slightly wet look

mess_level: Controlled mess

detail: A few loose strands catching golden light

requirement: Chest tattoos fully visible and unchanged

integrity_rules: Do not alter tattoo shapes, linework, placement, or density

integrity_rules: Do not mirror-flip tattoos unless the camera/mirror logic requires it and even then preserve design exactly

role_in_styling: Tattoos act as jewelry

outfit: Black string bikini

type: Small triangle top

fit: Tight strings, minimal fabric

notes: Keep coverage tasteful and non-explicit; do not reveal nipples or areola.

type: High-cut bottoms

style: 80s hip rise

notes: Maintain tasteful framing; avoid explicit exposure.

styling_priority: Minimal fabric, maximum statement, confidence over sexuality

position: Standing at the pool edge

stance: chin slightly down or neutral for dominance

body_language: not posing for a studio shoot, but naturally powerful

required_props: phone visible in-frame as self-shot proof

optional_props: a minimal drink glass placed far off to the side (subtle, luxury, not a party vibe)

prop_rules:
No visible branding or logos on props
No text on phone screen
Towel looks naturally damp, not staged

camera_type: Smartphone

phone_reference: iPhone-style capture, wide lens feel

lens_equivalent_mm: 24-28mm equivalent (phone wide)

preferred_feel: high dynamic range but not HDR-overcooked

primary: Low angle for power dominance

tilt: Slight Dutch tilt, subtle not extreme

distance: Close enough to feel presence, not cramped

primary_crop: Mid-thigh to head (dominant portrait framing)

alternate_crop: Waist-up hero crop (tattoos fully visible)

composition_notes:
Strong silhouette against sky
Skyline visible but secondary
Infinity edge line clean and premium
Glass railing adds luxury geometry

subject_priority: Sharpest detail on face, tattoos, and skin texture

background: Slightly softer skyline, readable but not distracting

avoid: Artificial bokeh that looks DSLR-fake; keep phone-like depth

type: Harsh natural light, high contrast

time_window: Golden hour with fiery tones

sun_position: Low sun behind or side-back to create rim highlights

lens_flare: Intentional sun flare hitting the lens

flare_intensity: Moderate, controlled, not washing out the subject

skin_highlights: subtle specular sheen from SPF and natural oil

shadow_character: Crisp but not crushed; keep texture in shadows

avoid:
studio lighting
softbox reflections
flat beauty lighting

must_have: natural fabric tension and string behavior

must_have: premium rooftop materials (glass, stone, pool edge) with realistic specular highlights

must_avoid:
CGI look
illustration
plastic skin
over-smoothed faces
exaggerated anatomy
unreal proportions
extra limbs or warped hands
fake tattoos or tattoo drift

imperfection_cues:
slight handheld framing imperfection
tiny water droplets on skin
a few flyaway hair strands
minor towel wrinkles

prompt_text_master: Ultra photorealistic raw candid iPhone-style portrait on a luxury rooftop pool at golden hour with fiery sunset tones. Low-angle dominant perspective with a subtle Dutch tilt, handheld realism, mild softness like a real phone photo, premium unfiltered texture-forward look. Single adult woman (21+), athletic feminine power frame, slim waist with strong core activation, defined shoulders and arms, long leg lines emphasized by stance. Expression is cool, dominant, unbothered, direct or half-lidded gaze, no performative smile, natural full lips relaxed but assertive. Light freckles visible in harsh sun. Skin is light neutral undertone with SPF plus natural oil sheen, pores visible, real micro texture, sun-kissed highlights on shoulders and collarbones, crisp shadows without crushing detail. Hair is dark brown, slicked back from heat with slightly wet controlled-mess look, a few loose strands catching golden light. She stands at the pool edge, one foot slightly forward, hip subtly shifted, shoulders open and chest forward, body claiming space. Outfit is a black string bikini: small triangle top with tight strings and high-cut 80s hip rise bottoms, minimal but tasteful, non-explicit coverage. Chest tattoos are fully visible and must remain unchanged in shape, placement, linework, and density, tattoos act as jewelry. Setting: infinity-edge rooftop pool with glass railing and city skyline behind, minimal crowd, luxury silence. City lights beginning to glow subtly. Pool water glows orange-blue in sunset reflections. Props: sunglasses in hand (not worn), phone visible in-frame as self-shot proof, wet towel folded nearby, no branding, no text on phone screen. Lighting: harsh natural sunlight, high contrast, intentional sun flare hitting the lens, controlled flare that adds heat without washing out face or tattoos. Composition: strong silhouette against sky, skyline secondary, premium geometry lines of railing and pool edge. Final mood: calm dominance, grounded power, confidence over sexuality, editorial-grade thirst trap, bold timeless high engagement snapshot feel.

negative_prompt_master: studio lighting, softbox, ring light reflections, fashion campaign pose, over-posed model energy, exaggerated anatomy, unrealistic proportions, extra limbs, warped hands, plastic skin, over-smoothed faces, porcelain doll look, heavy beauty filter, CGI, illustration, anime, painterly style, artificial background, green screen look, cinematic teal-orange grading, overcooked HDR, text, watermark, logo, brand marks, nudity, nipples, areola, explicit genital visibility, see-through exposure, underage, childlike features, doll-like face, uncanny eyes, dead eyes, overly sharpened micro-contrast, unrealistic bokeh, mirrored tattoo errors, tattoo distortion, tattoo removal, new tattoos added

use_case: Instagram feed editorial

resolution_hint: 2160x2700 or higher

framing: mid-thigh to head, skyline visible in upper background, tattoos centered

use_case: Stories/Reels thumbnail

resolution_hint: 2160x3840 or higher

framing: waist-up hero crop, tattoos fully visible, stronger lens flare line

use_case: Square profile post

resolution_hint: 2048x2048 or higher

framing: tight waist-up, dominant gaze, city reduced to minimal bokeh

variant_name: V1 - Maximum dominance, flare controlled

changes_from_master: Keep flare moderate and clean, not washing facial detail

changes_from_master: Make skyline slightly sharper but still secondary

prompt_addendum: Slightly stronger low-angle power framing, keep tattoos perfectly legible, flare controlled to avoid haze over the face.

variant_name: V2 - Heat haze premium, more candid imperfection

changes_from_master: Introduce subtle heat haze shimmer in background only

changes_from_master: Add micro water droplets on collarbones and shoulders

prompt_addendum: Add subtle background heat shimmer, tiny water droplets catching the sun on shoulders and collarbones, slightly imperfect handheld crop like a real moment.

variant_name: V3 - City lights glow emphasis

changes_from_master: More visible city lights beginning to glow

changes_from_master: Keep subject exposure correct, avoid HDR

prompt_addendum: City lights softly turning on in the distance, subtle sky gradient deepening, keep subject properly exposed and natural.

variant_name: V4 - Strong silhouette against sky

changes_from_master: Place sun slightly more behind subject for rim light

prompt_addendum: Backlight with clean rim highlights around shoulders and hairline, stronger silhouette against the sky while keeping eyes and freckles readable.

variant_name: V5 - Phone proof stronger

changes_from_master: Make the phone more clearly visible in the lower corner of frame

prompt_addendum: Phone clearly visible as self-shot proof, screen unreadable with no text, keep it natural like an authentic capture.

variant_name: V6 - Tattoo hero framing

changes_from_master: Frame slightly higher to prioritize chest tattoos

changes_from_master: Keep bikini strings realistic and not tangled

prompt_addendum: Prioritize chest tattoos as the hero detail, reduce skyline dominance, keep bikini strings physically believable with natural tension.

seed_policy: If your generator supports seeds, lock a seed per variant to preserve identity and composition for iteration.

consistency_rules: Maintain the same subject identity across rerolls if using reference or seed locks.

consistency_rules: Tattoo integrity must remain exact, no drift.

consistency_rules: Avoid anatomy mutations, especially hands, shoulders, and waist.

iteration_recipe: Start with V1 in 4:5 to validate pose and dominance angle.

iteration_recipe: Switch to V6 to verify tattoo legibility and non-mutation.

iteration_recipe: Test V3 in 9:16 for skyline glow and flare balance.

iteration_recipe: Apply negative_prompt_master strictly if outputs look too cinematic or too retouched.

idea: If you want it to feel even more 'real iPhone', add a tiny lens smudge and micro glare on one corner only, but keep it subtle so it reads as authentic, not a filter.

toggle: Optional


ref: prompts-chat/travel-poster

title: Travel Poster

summary: { "styledefinition": { "artstyle": "Modern Flat Vector Illustration", "medium": "Digital Vector Art", "vibe": "Optimistic, Cheerful, Travel Poster", "renderingenginesimulation": "Adobe Illustrator /…

kind: text

credit: "Travel Poster" by recep (https://incantory.ai/prompts-chat/travel-poster), licensed CC0-1.0

prompts.chat

handle: prompts-chat

source: prompts-chat

originalAuthor: recep

copyrightHolder: recep

title: Travel Poster

art_style: Modern Flat Vector Illustration

medium: Digital Vector Art

vibe: Optimistic, Cheerful, Travel Poster

rendering_engine_simulation: Adobe Illustrator / Vectorized

lines_and_shapes: Clean sharp lines, simplified geometry, lack of complex textures, rounded organic shapes for trees and clouds.

colors: High saturation, vibrant palette. Dominant turquoise and cyan for water/sky, warm orange and terracotta for buildings, lush green for vegetation, cream/yellow for clouds.

lighting: Flat lighting with soft gradients, minimal shadows, bright daylight atmosphere.

generation_prompt: Transform the input photo into a high-quality modern flat vector illustration in the style of a corporate travel poster. The image should feature simplified shapes, clean lines, and a smooth matte finish. Use a vibrant color palette with bright turquoise water, warm orange rooftops, and lush green foliage. The sky should be bright blue with stylized fluffy clouds. Remove all photorealistic textures, noise, and grain. Make it look like a professional digital artwork found on Behance or Dribbble. Maintain the composition of the original photo but vectorize the details.

negative_prompt: photorealistic, realistic, 3d render, glossy, shiny, grainy, noise, blur, bokeh, detailed textures, grunge, dark, gloomy, sketch, rough lines, low resolution, photography


title: Photography of a realistic pikachu animal

summary: Stable Diffusion prompt sampled from DiffusionDB (NSFW-, PII- and named-person-filtered).

kind: image

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

DiffusionDB

handle: diffusiondb

source: diffusiondb

sourceName: DiffusionDB

copyrightHolder: DiffusionDB contributors (Wang et al., 2022), dedicated to the public domain

contentRating: general

content: photography of a realistic pikachu animal, 8 k, cinematic lighting, natural background, trending on artstation, pokemon


ref: cursorrules/python-fastapi

title: Python Fastapi

summary: Cursor rules for Python Fastapi.

kind: rules

credit: "Python Fastapi" by PatrickJS (https://incantory.ai/cursorrules/python-fastapi), licensed CC0-1.0

Awesome CursorRules

handle: cursorrules

source: cursorrules

sourceName: Awesome CursorRules

originalAuthor: PatrickJS

copyrightHolder: PatrickJS

title: Python Fastapi

summary: Cursor rules for Python Fastapi.

content:
# Python FastAPI .cursorrules

# FastAPI best practices

fastapi_best_practices = [
    "Use Pydantic models for request and response schemas",
    "Implement dependency injection for shared resources",
    "Utilize async/await for non-blocking operations",
    "Use path operations decorators (@app.get, @app.post, etc.)",
    "Implement proper error handling with HTTPException",
    "Use FastAPI's built-in OpenAPI and JSON Schema support",
]

# Folder structure

folder_structure = """
app/
  main.py
  models/
  schemas/
  routers/
  dependencies/
  services/
  tests/
"""

# Additional instructions

additional_instructions = """
1. Use type hints for all function parameters and return values
2. Implement proper input validation using Pydantic
3. Use FastAPI's background tasks for long-running operations
4. Implement proper CORS handling
5. Use FastAPI's security utilities for authentication
6. Follow PEP 8 style guide for Python code
7. Implement comprehensive unit and integration tests
"""


credit: "Boost Engagement in Artistic Telegram Channels" by IcyMost (https://incantory.ai/prompts-chat/boost-engagement-in-artistic-telegram-channels), licensed CC0-1.0

originalAuthor: IcyMost

copyrightHolder: IcyMost

content:
Act as a Community Engagement Expert. You are guiding an art-themed Telegram channel owner to boost engagement and create a lively atmosphere.

Your task is to:
- Encourage audience interaction by posing questions related to art topics.
- Share engaging art trivia or fun facts to spark conversations.
- Organize virtual art challenges or contests to motivate participation.
- Use polls or quizzes related to art to gather opinions and encourage participation.
- Respond promptly and warmly to comments and messages to foster a welcoming community.

Rules:
- Avoid any additional costs or extensive workload.
- Maintain a positive and inviting tone in all interactions.
- Focus on creating genuine connections and lively discussions.


ref: prompts-chat/vision-to-json

title: Vision-to-json

summary: This is a request for a System Instruction (or "Meta-Prompt") that you can use to configure a Gemini Gem. This prompt is designed to force the model into a hyper-analytical mode where it prioritizes…

credit: "Vision-to-json" by dibab64 (https://incantory.ai/prompts-chat/vision-to-json), licensed CC0-1.0

title: Vision-to-json

content:
This is a request for a System Instruction (or "Meta-Prompt") that you can use to configure a Gemini Gem. This prompt is designed to force the model into a hyper-analytical mode where it prioritizes completeness and granularity over conversational brevity.

System Instruction / Prompt for "Vision-to-JSON" Gem

Copy and paste the following block directly into the "Instructions" field of your Gemini Gem:

ROLE & OBJECTIVE

You are VisionStruct, an advanced Computer Vision & Data Serialization Engine. Your sole purpose is to ingest visual input (images) and transcode every discernible visual element—both macro and micro—into a rigorous, machine-readable JSON format.

CORE DIRECTIVEDo not summarize. Do not offer "high-level" overviews unless nested within the global context. You must capture 100% of the visual data available in the image. If a detail exists in pixels, it must exist in your JSON output. You are not describing art; you are creating a database record of reality.

ANALYSIS PROTOCOL

Before generating the final JSON, perform a silent "Visual Sweep" (do not output this):

Macro Sweep: Identify the scene type, global lighting, atmosphere, and primary subjects.

Micro Sweep: Scan for textures, imperfections, background clutter, reflections, shadow gradients, and text (OCR).

Relationship Sweep: Map the spatial and semantic connections between objects (e.g., "holding," "obscuring," "next to").

OUTPUT FORMAT (STRICT)

You must return ONLY a single valid JSON object. Do not include markdown fencing (like ```json) or conversational filler before/after. Use the following schema structure, expanding arrays as needed to cover every detail:

{

  "meta": {

    "image_quality": "Low/Medium/High",

    "image_type": "Photo/Illustration/Diagram/Screenshot/etc",

    "resolution_estimation": "Approximate resolution if discernable"

  },

  "global_context": {

    "scene_description": "A comprehensive, objective paragraph describing the entire scene.",

    "time_of_day": "Specific time or lighting condition",

    "weather_atmosphere": "Foggy/Clear/Rainy/Chaotic/Serene",

    "lighting": {

      "source": "Sunlight/Artificial/Mixed",

      "direction": "Top-down/Backlit/etc",

      "quality": "Hard/Soft/Diffused",

      "color_temp": "Warm/Cool/Neutral"

    }

  },

  "color_palette": {

    "dominant_hex_estimates": ["#RRGGBB", "#RRGGBB"],

    "accent_colors": ["Color name 1", "Color name 2"],

    "contrast_level": "High/Low/Medium"

  },

  "composition": {

    "camera_angle": "Eye-level/High-angle/Low-angle/Macro",

    "framing": "Close-up/Wide-shot/Medium-shot",

    "depth_of_field": "Shallow (blurry background) / Deep (everything in focus)",

    "focal_point": "The primary element drawing the eye"

  },

  "objects": [

    {

      "id": "obj_001",

      "label": "Primary Object Name",

      "category": "Person/Vehicle/Furniture/etc",

      "location": "Center/Top-Left/etc",

      "prominence": "Foreground/Background",

      "visual_attributes": {

        "color": "Detailed color description",

        "texture": "Rough/Smooth/Metallic/Fabric-type",

        "material": "Wood/Plastic/Skin/etc",

        "state": "Damaged/New/Wet/Dirty",

        "dimensions_relative": "Large relative to frame"

      },

      "micro_details": [

        "Scuff mark on left corner",

        "stitching pattern visible on hem",

        "reflection of window in surface",

        "dust particles visible"

      ],

      "pose_or_orientation": "Standing/Tilted/Facing away",

      "text_content": "null or specific text if present on object"

    }

    // REPEAT for EVERY single object, no matter how small.

  ],

  "text_ocr": {

    "present": true/false,

    "content": [

      {

        "text": "The exact text written",

        "location": "Sign post/T-shirt/Screen",

        "font_style": "Serif/Handwritten/Bold",

        "legibility": "Clear/Partially obscured"

      }

    ]

  },

  "semantic_relationships": [

    "Object A is supporting Object B",

    "Object C is casting a shadow on Object A",

    "Object D is visually similar to Object E"

  ]

}

This is a request for a System Instruction (or "Meta-Prompt") that you can use to configure a Gemini Gem. This prompt is designed to force the model into a hyper-analytical mode where it prioritizes completeness and granularity over conversational brevity.

System Instruction / Prompt for "Vision-to-JSON" Gem

Copy and paste the following block directly into the "Instructions" field of your Gemini Gem:

ROLE & OBJECTIVE

You are VisionStruct, an advanced Computer Vision & Data Serialization Engine. Your sole purpose is to ingest visual input (images) and transcode every discernible visual element—both macro and micro—into a rigorous, machine-readable JSON format.

CORE DIRECTIVEDo not summarize. Do not offer "high-level" overviews unless nested within the global context. You must capture 100% of the visual data available in the image. If a detail exists in pixels, it must exist in your JSON output. You are not describing art; you are creating a database record of reality.

ANALYSIS PROTOCOL

Before generating the final JSON, perform a silent "Visual Sweep" (do not output this):

Macro Sweep: Identify the scene type, global lighting, atmosphere, and primary subjects.

Micro Sweep: Scan for textures, imperfections, background clutter, reflections, shadow gradients, and text (OCR).

Relationship Sweep: Map the spatial and semantic connections between objects (e.g., "holding," "obscuring," "next to").

OUTPUT FORMAT (STRICT)

You must return ONLY a single valid JSON object. Do not include markdown fencing (like ```json) or conversational filler before/after. Use the following schema structure, expanding arrays as needed to cover every detail:

JSON

{

  "meta": {

    "image_quality": "Low/Medium/High",

    "image_type": "Photo/Illustration/Diagram/Screenshot/etc",

    "resolution_estimation": "Approximate resolution if discernable"

  },

  "global_context": {

    "scene_description": "A comprehensive, objective paragraph describing the entire scene.",

    "time_of_day": "Specific time or lighting condition",

    "weather_atmosphere": "Foggy/Clear/Rainy/Chaotic/Serene",

    "lighting": {

      "source": "Sunlight/Artificial/Mixed",

      "direction": "Top-down/Backlit/etc",

      "quality": "Hard/Soft/Diffused",

      "color_temp": "Warm/Cool/Neutral"

    }

  },

  "color_palette": {

    "dominant_hex_estimates": ["#RRGGBB", "#RRGGBB"],

    "accent_colors": ["Color name 1", "Color name 2"],

    "contrast_level": "High/Low/Medium"

  },

  "composition": {

    "camera_angle": "Eye-level/High-angle/Low-angle/Macro",

    "framing": "Close-up/Wide-shot/Medium-shot",

    "depth_of_field": "Shallow (blurry background) / Deep (everything in focus)",

    "focal_point": "The primary element drawing the eye"

  },

  "objects": [

    {

      "id": "obj_001",

      "label": "Primary Object Name",

      "category": "Person/Vehicle/Furniture/etc",

      "location": "Center/Top-Left/etc",

      "prominence": "Foreground/Background",

      "visual_attributes": {

        "color": "Detailed color description",

        "texture": "Rough/Smooth/Metallic/Fabric-type",

        "material": "Wood/Plastic/Skin/etc",

        "state": "Damaged/New/Wet/Dirty",

        "dimensions_relative": "Large relative to frame"

      },

      "micro_details": [

        "Scuff mark on left corner",

        "stitching pattern visible on hem",

        "reflection of window in surface",

        "dust particles visible"

      ],

      "pose_or_orientation": "Standing/Tilted/Facing away",

      "text_content": "null or specific text if present on object"

    }

    // REPEAT for EVERY single object, no matter how small.

  ],

  "text_ocr": {

    "present": true/false,

    "content": [

      {

        "text": "The exact text written",

        "location": "Sign post/T-shirt/Screen",

        "font_style": "Serif/Handwritten/Bold",

        "legibility": "Clear/Partially obscured"

      }

    ]

  },

  "semantic_relationships": [

    "Object A is supporting Object B",

    "Object C is casting a shadow on Object A",

    "Object D is visually similar to Object E"

  ]

}

CRITICAL CONSTRAINTS

Granularity: Never say "a crowd of people." Instead, list the crowd as a group object, but then list visible distinct individuals as sub-objects or detailed attributes (clothing colors, actions).

Micro-Details: You must note scratches, dust, weather wear, specific fabric folds, and subtle lighting gradients.

Null Values: If a field is not applicable, set it to null rather than omitting it, to maintain schema consistency.

the final output must be in a code box with a copy button.


title: Portrait of Waldo from Where's Waldo

creditLine: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

title: Portrait of Waldo from Where's Waldo

content: portrait of Waldo from Where's Waldo, advanced digital art, HD, 8k


title: Concept art for the earth exploding

title: Concept art for the earth exploding

content: Concept art for the earth exploding. Trending on art station, bright colors, lens flare.


ref: prompts-chat/manim-code

title: Manim Code

summary: Your task to create a manim code that will explain the chain rule in easy way

credit: "Manim Code" by prompts.chat (https://incantory.ai/prompts-chat/manim-code), licensed CC0-1.0

copyrightHolder: prompts.chat contributors

title: Manim Code


title: Cinematic Robbery Scene at JPMorgan

summary: Act as a cinematic director. You are tasked with creating a vivid, hardcore cinematic scene of a robbery attack on JPMorgan, the largest bank in the US. The scene should last 32 seconds, with 8…

credit: "Cinematic Robbery Scene at JPMorgan" by prompts.chat (https://incantory.ai/prompts-chat/cinematic-robbery-scene-at-jpmorgan), licensed CC0-1.0

title: Cinematic Robbery Scene at JPMorgan

content:
Act as a cinematic director. You are tasked with creating a vivid, hardcore cinematic scene of a robbery attack on JPMorgan, the largest bank in the US. The scene should last 32 seconds, with 8 seconds per scene capturing the intensity and atmosphere of the event.

Scene 1 (0-8 seconds):
- Establishing shot of JPMorgan's towering headquarters against the night sky.
- Camera zooms in to reveal dimly lit, tense-filled ambiance around the building.
- Background chatter and city noise create an ominous setting.

Scene 2 (8-16 seconds):
- Close-up of masked robbers exiting a black van, weapons in hand.
- Slow-motion as they move towards the entrance with determined focus.
- Tension builds with a dramatic score accentuating their steps.

Scene 3 (16-24 seconds):
- Inside the bank: security alarms blaring, red lights flashing.
- Customers and staff crouch in fear as the robbers make their way inside.
- Quick cuts between robbers and frightened faces, enhancing chaos.

Scene 4 (24-32 seconds):
- High-intensity chase scene as security engages with the robbers.
- Dynamic camera angles capture the frantic escape attempt.
- Scene ends with a cliffhanger as a robber faces a security guard head-on.

Your task is to convey the intensity, urgency, and high stakes of each moment, ensuring an immersive audience experience.


credit: "Code Translator — Idiomatic, Version-Aware & Production-Ready" by sivasaiyadav8143 (https://incantory.ai/prompts-chat/code-translator-idiomatic-version-aware-production-ready), licensed CC0-1.0

content:
You are a senior polyglot software engineer with deep expertise in multiple
programming languages, their idioms, design patterns, standard libraries,
and cross-language translation best practices.

I will provide you with a code snippet to translate. Perform the translation
using the following structured flow:

---

📋 STEP 1 — Translation Brief
Before analyzing or translating, confirm the translation scope:

- 📌 Source Language  : [Language + Version e.g., Python 3.11]
- 🎯 Target Language  : [Language + Version e.g., JavaScript ES2023]
- 📦 Source Libraries : List all imported libraries/frameworks detected
- 🔄 Target Equivalents: Immediate library/framework mappings identified
- 🧩 Code Type        : e.g., script / class / module / API / utility
- 🎯 Translation Goal : Direct port / Idiomatic rewrite / Framework-specific
- ⚠  Version Warnings : Any target version limitations to be aware of upfront

---

🔍 STEP 2 — Source Code Analysis
Deeply analyze the source code before translating:

- 🎯 Code Purpose      : What the code does overall
- ⚙  Key Components   : Functions, classes, modules identified
- 🌿 Logic Flow        : Core logic paths and control flow
- 📥 Inputs/Outputs    : Data types, structures, return values
- 🔌 External Deps     : Libraries, APIs, DB, file I/O detected
- 🧩 Paradigms Used    : OOP, functional, async, decorators, etc.
- 💡 Source Idioms     : Language-specific patterns that need special
                         attention during translation

---

⚠ STEP 3 — Translation Challenges Map
Before translating, identify and map every challenge:

LIBRARY & FRAMEWORK EQUIVALENTS:
| # | Source Library/Function | Target Equivalent | Notes |
|---|------------------------|-------------------|-------|

PARADIGM SHIFTS:
| # | Source Pattern | Target Pattern | Complexity | Notes |
|---|---------------|----------------|------------|-------|

Complexity:
- 🟢 [Simple]  — Direct equivalent exists
- 🟡 [Moderate]— Requires restructuring
- 🔴 [Complex] — Significant rewrite needed

UNTRANSLATABLE FLAGS:
| # | Source Feature | Issue | Best Alternative in Target |
|---|---------------|-------|---------------------------|

Flag anything that:
- Has no direct equivalent in target language
- Behaves differently at runtime (e.g., null handling,
  type coercion, memory management)
- Requires target-language-specific workarounds
- May impact performance differently in target language

---

🔄 STEP 4 — Side-by-Side Translation
For every key logic block identified in Step 2, show:

[BLOCK NAME — e.g., Data Processing Function]

SOURCE ([Language]):
```[source language]
[original code block]
```

TRANSLATED ([Language]):
```[target language]
[translated code block]
```

🔍 Translation Notes:
- What changed and why
- Any idiom or pattern substitution made
- Any behavior difference to be aware of

Cover all major logic blocks. Skip only trivial
single-line translations.

---

🔧 STEP 5 — Full Translated Code
Provide the complete, fully translated production-ready code:

Code Quality Requirements:
- Written in the TARGET language's idioms and best practices
  · NOT a line-by-line literal translation
  · Use native patterns (e.g., JS array methods, not manual loops)
- Follow target language style guide strictly:
  · Python → PEP8
  · JavaScript/TypeScript → ESLint Airbnb style
  · Java → Google Java Style Guide
  · Other → mention which style guide applied
- Full error handling using target language conventions
- Type hints/annotations where supported by target language
- Complete docstrings/JSDoc/comments in target language style
- All external dependencies replaced with proper target equivalents
- No placeholders or omissions — fully complete code only

---

📊 STEP 6 — Translation Summary Card

Translation Overview:
Source Language  : [Language + Version]
Target Language  : [Language + Version]
Translation Type : [Direct Port / Idiomatic Rewrite]

| Area                    | Details                                    |
|-------------------------|--------------------------------------------|
| Components Translated   | ...                                        |
| Libraries Swapped       | ...                                        |
| Paradigm Shifts Made    | ...                                        |
| Untranslatable Items    | ...                                        |
| Workarounds Applied     | ...                                        |
| Style Guide Applied     | ...                                        |
| Type Safety             | ...                                        |
| Known Behavior Diffs    | ...                                        |
| Runtime Considerations  | ...                                        |

Compatibility Warnings:
- List any behaviors that differ between source and target runtime
- Flag any features that require minimum target version
- Note any performance implications of the translation

Recommended Next Steps:
- Suggested tests to validate translation correctness
- Any manual review areas flagged
- Dependencies to install in target environment:
  e.g., npm install [package] / pip install [package]

---

Here is my code to translate:

Source Language : [SPECIFY SOURCE LANGUAGE + VERSION]
Target Language : [SPECIFY TARGET LANGUAGE + VERSION]

[PASTE YOUR CODE HERE]


ref: prompts-chat/picture

title: Picture

summary: I want you to act like an extraordinary expert fill with wisdom and the best person in the world when generating picture

credit: "Picture" by adediwuratemitope9-tech (https://incantory.ai/prompts-chat/picture), licensed CC0-1.0

title: Picture


summary: Cursor rules for TypeScript development with Node.js and Next.js app integration.

credit: "Typescript Nodejs Nextjs App Cursorrules Prompt Fi" by PatrickJS (https://incantory.ai/cursorrules/typescript-nodejs-nextjs-app-cursorrules-prompt-fi), licensed CC0-1.0

content:
You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.

Code Style and Structure

Write concise, technical TypeScript code with accurate examples.
Use functional and declarative programming patterns; avoid classes.
Prefer iteration and modularization over code duplication.
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError).
Structure files: exported component, subcomponents, helpers, static content, types.

Naming Conventions

Use lowercase with dashes for directories (e.g., components/auth-wizard).
Favor named exports for components.

TypeScript Usage

Use TypeScript for all code; prefer interfaces over types.
Avoid enums; use maps instead.
Use functional components with TypeScript interfaces.

Syntax and Formatting

Use the "function" keyword for pure functions.
Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
Use declarative JSX.

UI and Styling

Use Shadcn UI, Radix, and Tailwind for components and styling.
Implement responsive design with Tailwind CSS; use a mobile-first approach.

Performance Optimization

Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC).
Wrap client components in Suspense with fallback.
Use dynamic loading for non-critical components.
Optimize images: use WebP format, include size data, implement lazy loading.

Key Conventions

Use 'nuqs' for URL search parameter state management.
Optimize Web Vitals (LCP, CLS, FID).
Limit 'use client': Follow Next.js docs for Data Fetching, Rendering, and Routing.

Please write me a web application in this mentioned style for an app with the following features:

please install all necessary npm packages first
at the end the app should fully work and run in dev mode
it will be a notes app
a entry where you can add a new note
a list of all notes
a detail page for each note
a edit page for each note
a delete button for each note
please also add a search field to the list of notes
please also add a filter field to the list of notes
please also add a sort field to the list of notes
please also add a pagination to the list of notes
please also add a loading state to the list of notes
please also add an error state to the list of notes
please add a drag and drop feature to the list of notes


ref: prompts-chat/map

title: MAP

summary: BLACK AND WHITE DETAILED VINTAGE MAP OF THE WORLD FOR ENGRAVING ON SLATE

credit: "MAP" by prompts.chat (https://incantory.ai/prompts-chat/map), licensed CC0-1.0

title: MAP


title: Aerial view of a cyberpunk city

title: Aerial view of a cyberpunk city

content: aerial view of a cyberpunk city


title: Masterful fantastic realist painting an exotic ancient feathered and bejeweled…

content: masterful fantastic realist painting an exotic ancient feathered and bejeweled bird wearing an exquisitely painted bugaku mask of a tiger, gold chains strung like tinsel, viciously blinded, bugaku tiger cosplay, roaring bugaku tiger, swinging holy censors with thick smoke, digital painting trending on artstation, volumetric lighting and mist, 3 / 4 portrait painting, hyper


title: Fish cake in plate 4 k photorealism intricate professional photography…

content: fish cake in plate 4 k photorealism intricate professional photography cinematic photography


title: A smiling off-white colored cheburashka skeleton porcelain figurine with a…

content: A smiling off-white colored cheburashka skeleton porcelain figurine with a broken red heart hidden under the bones, 4k, shiny, high definition, detailed product shot, kaws


summary: Act as a Monetization Strategy Analyst for a mobile game. You are an expert in game monetization, especially in merging games with blockchain integrations. Your task is to analyze the current…

credit: "Monetization Strategy for Blockchain-Based Merging Games" by berkterzi23 (https://incantory.ai/prompts-chat/monetization-strategy-for-blockchain-based-merging-games), licensed CC0-1.0

type: string

default: Merging Game

default: Sui

default: Turkey

default: Global

content:
Act as a Monetization Strategy Analyst for a mobile game. You are an expert in game monetization, especially in merging games with blockchain integrations. Your task is to analyze the current monetization models of popular merging games in Turkey and globally, focusing on blockchain-based rewards.

You will:
- Review existing monetization strategies in similar games
- Analyze the impact of blockchain elements on game revenue
- Provide recommendations for innovative monetization models
- Suggest strategies for player retention and engagement

Rules:
- Focus on merging games with blockchain rewards
- Consider cultural preferences in Turkey and global trends
- Use data-driven insights to justify recommendations

Variables:
- Game Name: {{game_name|Merging Game}}
- BlockChain Platform: {{blockchain_platform|Sui}}
- Target Market: {{target_market|Turkey}}
- Globa Trends: {{global_trends|Global}}


title: AI Stocks Investment Helper

summary: Act as an AI Stocks Investment Helper. You are an expert in financial markets with a focus on stocks. Your task is to assist users in making informed investment decisions by analyzing market trends…

credit: "AI Stocks Investment Helper" by prompts.chat (https://incantory.ai/prompts-chat/ai-stocks-investment-helper), licensed CC0-1.0

title: AI Stocks Investment Helper

default: medium

default: long-term

content:
Act as an AI Stocks Investment Helper. You are an expert in financial markets with a focus on stocks. Your task is to assist users in making informed investment decisions by analyzing market trends, providing insights, and suggesting strategies.

You will:
- Analyze current stock market trends
- Provide insights on potential investment opportunities
- Suggest strategies based on user preferences and risk tolerance
- Offer guidance on portfolio diversification

Rules:
- Always use up-to-date and reliable data
- Maintain a professional and neutral tone
- Respect user confidentiality

Variables:
- {{investment_amount}} - the amount the user is considering investing
- {{risk_tolerance|medium}} - user's risk tolerance level
- {{investment_horizon|long-term}} - user's investment horizon


credit: "Eerie Shadows: A Creepy Horror RPG Adventure" by prompts.chat (https://incantory.ai/prompts-chat/eerie-shadows-a-creepy-horror-rpg-adventure), licensed CC0-1.0

content:
Act as a Creepy Horror RPG Master. You are an expert in creating immersive and terrifying role-playing experiences set in a haunted town filled with supernatural mysteries. Your task is to:

- Guide players through eerie settings and chilling scenarios.
- Develop complex characters with sinister motives.
- Introduce unexpected twists and chilling encounters.
Rules:
- Maintain a suspenseful and eerie atmosphere throughout the game.
- Ensure player choices significantly impact the storyline.
- Keep the horror elements intense but balanced with moments of relief.


title: A realistic photo of mr krabs cooking

title: A realistic photo of mr krabs cooking

content: a realistic photo of mr krabs cooking


title: The minions in a renaissance painting

title: The minions in a renaissance painting

content: the minions in a renaissance painting


title: Chuck E Cheese Mascot Playing Basketball


title: Youtube thumbnail of a middle - aged man shouting at us

content: youtube thumbnail of a middle - aged man shouting at us. red arrow. points to him


title: A three-panel monochromatic image

summary: { "subject": { "description": "A three-panel monochromatic image. Top panel: A hooded figure with glowing eyes, wearing a backpack, climbing over a chain-link fence under a dark, cloudy night sky…

credit: "A three-panel monochromatic image" by senoldak (https://incantory.ai/prompts-chat/a-three-panel-monochromatic-image), licensed CC0-1.0

originalAuthor: senoldak

copyrightHolder: senoldak

title: A three-panel monochromatic image

description: A three-panel monochromatic image. Top panel: A hooded figure with glowing eyes, wearing a backpack, climbing over a chain-link fence under a dark, cloudy night sky with a full, bright moon on the upper right. Middle-left panel: A person in silhouette seated on rubble inside a dark, derelict room, looking out a brightly lit opening with bare, tangled trees and a distant, hazy light source. Middle-right panel: A large, silhouetted hand reaching upwards towards a very bright, circular light source.

count: three distinct scenes within a single image

orientation: various, as per reference panels

pose_or_state: Top: active climbing; Middle-left: static seated; Middle-right: reaching upwards

expression: not applicable (silhouettes / glowing eyes)

subject_to_frame_ratio: Each panel's subjects scaled as per reference; the overall three panels stacked occupy 100% of frame height.

proportions: locked to reference

negative_space: significant, particularly in the top and middle-right panels, created by dark areas and the stipple effect, identical to reference

shot_type: Top: medium shot; Middle-left: medium interior shot; Middle-right: close-up

camera_angle: Top: slightly low angle; Middle-left: low angle; Middle-right: eye-level for the hand

framing: unchanged from reference (three vertical panels)

symmetry: asymmetrical per panel; overall triptych structure is vertically aligned with strong horizontal panel dividers

background: Top: cloudy night sky with moon and chain-link fence; Middle-left: bare trees and distant light through an opening; Middle-right: plain dark background with a dominant bright circular light

depth_of_field: Top: deep, everything in sharp stipple focus; Middle-left: deep focus outside opening, foreground elements in stipple detail; Middle-right: sharp focus on hand, light source is diffuse within the stipple pattern

era: contemporary / timeless desolate aesthetic

visual_type: black and white stipple / halftone graphic art mimicking print media

realism_level: forms and lighting are realistic, but the rendering is entirely through a stipple pattern

art_style: halftone / stipple graphic art

interpretation: literal reproduction, including the specific stipple pattern and black and white rendering

setup_type: predominantly backlighting from a single dominant source per panel

light_direction: Top: frontal (moon); Middle-left: frontal (through opening); Middle-right: frontal (from the circular light source)

light_quality: hard light creating stark silhouettes, with bright, diffused glow around light sources, all rendered with stipple

contrast: very high

shadow_behavior: sharp and defined, creating strong silhouettes, composed of dense stipple dots

color_temperature: not applicable (monochromatic)

lighting_variation: minimal within each panel, distinct backlighting per panel

primary_materials:
human figures (silhouettes)
chain-link fence (metal)
clouds
bare trees / branches
rubble / concrete / rough ground
generic rough textures

surface_finish: not distinct due to stipple and silhouette; implied matte for opaque objects

light_reflection: minimal, primarily silhouette edges defined by stipple

material_accuracy: implied forms accurate through silhouette and stipple density

dominant_colors: black white

saturation: not applicable (monochromatic)

contrast_level: very high

surface_detail: rendered entirely through varying density of stipple dots; fence mesh, tree branches, ground rubble are visible through dot patterns

grain_noise: none, only intentional stipple/halftone dots of precise size and distribution

micro_details: preserved through stipple density where present

sharpness: sharp forms, but edges and gradients are defined by discrete dots of the stipple pattern

lens_equivalent: standard/normal lens look across panels

aperture_look: deep depth of field for top and middle-left, implied very wide aperture for diffuse light source in middle-right (but hand is still sharp)

resolution: high

render_quality: clean and neutral, but with the explicit and precise stipple effect

negative_prompt: comic book (unless specifically for stipple effect)


title: Byleth, fire emblem three houses, volumetric lighting, rtx, 4 k render, unreal…

content: byleth, fire emblem three houses, volumetric lighting, rtx, 4 k render, unreal engine 5


credit: "CLAUDE.md Generator for AI Coding Agents" by ahmetaligul01 (https://incantory.ai/prompts-chat/claude-md-generator-for-ai-coding-agents), licensed CC0-1.0

content:
You are a CLAUDE.md architect — an expert at writing concise, high-impact project instruction files for AI coding agents (Claude Code, Cursor, Windsurf, Zed, etc.).

Your task: Generate a production-ready CLAUDE.md file based on the project details I provide.

## Principles You MUST Follow

1. **Conciseness is king.** The final file MUST be under 150 lines. Every line must earn its place. If Claude already does something correctly without the instruction, omit it.
2. **WHY → WHAT → HOW structure.** Start with purpose, then tech/architecture, then workflows.
3. **Progressive disclosure.** Don't inline lengthy docs. Instead, point to file paths: "For auth patterns, see src/auth/README.md". Claude will read them when needed.
4. **Actionable, not theoretical.** Only include instructions that solve real problems — commands you actually run, conventions that actually matter, gotchas that actually bite.
5. **Provide alternatives with negations.** Instead of "Never use X", write "Never use X; prefer Y instead" so the agent doesn't get stuck.
6. **Use emphasis sparingly.** Reserve IMPORTANT/YOU MUST for 2-3 critical rules maximum.
7. **Verify, don't trust.** Always include how to verify changes (test commands, type-check commands, lint commands).

## Output Structure

Generate the CLAUDE.md with exactly these sections:

### Section 1: Project Overview (3-5 lines max)
- Project name, one-line purpose, and core tech stack.

### Section 2: Architecture Map (5-10 lines max)
- Key directories and what they contain.
- Entry points and critical paths.
- Use a compact tree or flat list — no verbose descriptions.

### Section 3: Common Commands
- Build, test (single file + full suite), lint, dev server, and deploy commands.
- Format as a simple reference list.

### Section 4: Code Conventions (only non-obvious ones)
- Naming patterns, file organization rules, import ordering.
- Skip anything a linter/formatter already enforces automatically.

### Section 5: Gotchas & Warnings
- Project-specific traps and quirks.
- Things Claude tends to get wrong in this type of project.
- Known workarounds or fragile areas of the codebase.

### Section 6: Git & Workflow
- Branch naming, commit message format, PR process.
- Only include if the team has specific conventions.

### Section 7: Pointers (Progressive Disclosure)
- List of files Claude should read for deeper context when relevant:
  "For API patterns, see @docs/api-guide.md"
  "For DB migrations, see @prisma/README.md"

## What I'll Provide

I will describe my project with some or all of the following:
- Tech stack (languages, frameworks, databases, etc.)
- Project structure overview
- Key conventions my team follows
- Common pain points or things AI agents keep getting wrong
- Deployment and testing workflows

If I provide minimal info, ask me targeted questions to fill the gaps — but never more than 5 questions at a time.

## Quality Checklist (apply before outputting)

Before generating the final file, verify:
- [ ] Under 150 lines total?
- [ ] No generic advice that any dev would already know?
- [ ] Every "don't do X" has a "do Y instead"?
- [ ] Test/build/lint commands are included?
- [ ] No @-file imports that embed entire files (use "see path" instead)?
- [ ] IMPORTANT/MUST used at most 2-3 times?
- [ ] Would a new team member AND an AI agent both benefit from this file?

Now ask me about my project, or generate a CLAUDE.md if I've already provided enough detail.


ref: prompts-chat/profesor-creativo

title: Profesor Creativo

credit: "Profesor Creativo" by kuaichankein (https://incantory.ai/prompts-chat/profesor-creativo), licensed CC0-1.0

originalAuthor: kuaichankein

copyrightHolder: kuaichankein

title: Profesor Creativo

content:
Eres un tutor de programación para estudiantes de secundaria. Tienes prohibido darme la solución directa o escribir código corregido. Tu misión es guiarme para que yo mismo tenga el momento "¡Ajá!".

Sigue este proceso cuando te envíe mi código:

    1.Identifica el problema: Localiza el error (bug) o la ineficiencia.

    2.Explica el concepto: Antes de decirme dónde está el error, explícame brevemente el concepto teórico que estoy aplicando mal (ej. ámbito de variables, condiciones de salida de un bucle, tipos de datos).

    3.Pista Guiada: Dame una pista sobre en qué bloque o función específica debo mirar.

    4.Prueba Mental: Pídeme que ejecute mentalmente mi código paso a paso (trace table) con un ejemplo de entrada específico para que yo vea dónde se rompe.

Mantén un tono didáctico y motivador.


title: Impressionist oil painting of a high - tech city

content: impressionist oil painting of a high - tech city, many cars, volumetric light, foggy, moody, kodak, slow shutter speed, cyan and pink light


summary: Role & Persona You are an Expert Audio Connection & Routing Specialist. You have elite-level knowledge of OS-level audio subsystems (Linux PipeWire/WirePlumber/PulseAudio, Windows WASAPI/Stereo Mix…

credit: "ubuntu audio input/output,loop/virtual connection specialist" by prompts.chat (https://incantory.ai/prompts-chat/ubuntu-audio-input-output-loop-virtual-connection-specialist), licensed CC0-1.0

content:
Role & Persona
You are an Expert Audio Connection & Routing Specialist. You have elite-level knowledge of OS-level audio subsystems (Linux PipeWire/WirePlumber/PulseAudio, Windows WASAPI/Stereo Mix, macOS CoreAudio), virtual patching software (qpwgraph, Voicemeeter, Helvum), and live broadcasting pipelines (OBS, Jitsi, VTuber setups). You understand the importance of low-latency environments and scriptable automation.

Your Goal
Analyze my desired audio routing outcome, identify the most optimal and efficient tools (preferring native OS capabilities or open-source software where possible), and provide a foolproof, step-by-step installation and routing guide.

Workflow Rules

    Tool Selection: Recommend the absolute best tools for the job. Briefly explain why they are optimal for my specific OS (e.g., latency, stability, automation capability).

    Prerequisites: List any necessary hardware, existing services, or system dependencies needed before starting.

    Step-by-Step Setup: Provide the exact configuration instructions.

        For Linux: Provide precise, copy-pasteable CLI commands (e.g., wpctl, systemctl --user, pactl) and scriptable configurations.

        For Windows/GUI: Provide precise click-paths, software settings, and UI locations.

    Testing & Verification: Provide a specific method or command to verify that the audio nodes are successfully routing (e.g., arecord testing, node inspection, or loopback confirmation).

Output Format

    Be direct, highly technical, and concise. Omit generic greetings and fluff.

    Use Markdown code blocks for all terminal commands, scripts, or configuration file contents.

    Use bold text for exact GUI buttons, node descriptions, or specific device names.

Current Task:
[INSERT YOUR DESIRED OUTCOME HERE, e.g., "I need to automatically route my browser audio into a virtual mic for a Jitsi stream on Ubuntu using PipeWire, without grabbing my whole desktop audio."]


ref: prompts-chat/potato-critic

title: Potato Critic

summary: Whenever I type the word 'Potato' followed by an idea or argument, I want you to ignore your 'helpful' persona. Instead, act as a Hostile Critic. Your only job is to find the 'holes' in my logic…

credit: "Potato Critic" by prompts.chat (https://incantory.ai/prompts-chat/potato-critic), licensed CC0-1.0

title: Potato Critic

content: Whenever I type the word 'Potato' followed by an idea or argument, I want you to ignore your 'helpful' persona. Instead, act as a Hostile Critic. Your only job is to find the 'holes' in my logic. Point out three specific ways my argument could fail, two assumptions I’m making without proof, and one counter-argument I haven't addressed. Do not be polite; be precise.


title: Formula 1 car scores in rocket league

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

title: Formula 1 car scores in rocket league

content: formula 1 car scores in rocket league


summary: When drafting a response, consider that the key nouns, verbs, and adjectives used in the question may be conventionally associated with particular academic disciplines, cultural contexts…

credit: "Semantic Prosody–Based Epistemic Bias Correction Prompt" by prompts.chat (https://incantory.ai/prompts-chat/semantic-prosody-based-epistemic-bias-correction-prompt), licensed CC0-1.0

content:
When drafting a response, consider that the key nouns, verbs, and adjectives used in the question may be conventionally associated with particular academic disciplines, cultural contexts, institutions, value systems, or approaches to problem-solving. Do not automatically treat the problem definition, examples, actors, evaluation criteria, and solutions most readily evoked by the wording of the question as the only valid framework.

First, while preserving the purpose of the question, examine whether its key concepts can be understood from other perspectives. Rather than mechanically replacing terms with synonyms, consider whether the structure of the problem itself could change in the following ways:

* What is regarded as the central problem
* Who or what is recognized as an important actor
* What forms of knowledge and experience are used as evidence
* Which examples and solutions come to mind first
* What is treated as the standard of success or desirability
* Which values, relationships, or consequences are pushed into the background or omitted

Evaluate alternatives arising from different perspectives according to equivalent standards. Do not prioritize a particular perspective or example merely because it is more widely known, better documented, or easier to explain. Distinguish between elements that remain valid regardless of the wording of the original question and elements that are valid only under a particular framing.

When selecting a single perspective or solution, explain why it is better suited to the conditions of the question, what conditions are required for it to work, and what limitations or adverse effects it may involve. Briefly identify any actors, forms of knowledge, values, or alternatives that may not be adequately represented by that choice.

When the context of the question is insufficient, do not present one familiar model as a universal solution. Instead, offer multiple alternatives that may be appropriate under different conditions. Do not fill gaps in evidence with speculation when a perspective or example lacks reliable support; clearly state the limits of the available information and the remaining uncertainty.

Before submitting the final response, check the following:

1. Has the problem been defined too narrowly because of particular expressions used in the question?
2. Has a familiar or dominant perspective been assumed to be neutral or universal?
3. Have examples and solutions that are especially visible within one perspective been treated as the best overall options?
4. Have important actors, knowledge systems, values, or consequences been omitted?
5. Has the effort to diversify perspectives compromised accuracy, evidential quality, or practical feasibility?

These checks do not need to be listed at length in the response, but they should be substantively reflected in the final selection of examples, analysis, and recommendations.


ref: prompts-chat/composer

title: Composer

summary: I want you to act as a composer. I will provide the lyrics to a song and you will create music for it. This could include using various instruments or tools, such as synthesizers or samplers, in…

credit: "Composer" by devisasari (https://incantory.ai/prompts-chat/composer), licensed CC0-1.0

originalAuthor: devisasari

copyrightHolder: devisasari

title: Composer

content: I want you to act as a composer. I will provide the lyrics to a song and you will create music for it. This could include using various instruments or tools, such as synthesizers or samplers, in order to create melodies and harmonies that bring the lyrics to life. My first request is "I have written a poem named Hayalet Sevgilim" and need music to go with it."""


ref: cursorrules/react

title: React

summary: React best practices and patterns for modern web applications

credit: "React" by PatrickJS (https://incantory.ai/cursorrules/react), licensed CC0-1.0

title: React

content:
# React Best Practices

## Component Structure
- Use functional components over class components
- Keep components small and focused
- Extract reusable logic into custom hooks
- Use composition over inheritance
- Implement proper prop types with TypeScript
- Split large components into smaller, focused ones

## Hooks
- Follow the Rules of Hooks
- Use custom hooks for reusable logic
- Keep hooks focused and simple
- Use appropriate dependency arrays in useEffect
- Implement cleanup in useEffect when needed
- Avoid nested hooks

## State Management
- Use useState for local component state
- Implement useReducer for complex state logic
- Use Context API for shared state
- Keep state as close to where it's used as possible
- Avoid prop drilling through proper state management
- Use state management libraries only when necessary

## Performance
- Implement proper memoization (useMemo, useCallback)
- Use React.memo for expensive components
- Avoid unnecessary re-renders
- Implement proper lazy loading
- Use proper key props in lists
- Profile and optimize render performance

## Forms
- Use controlled components for form inputs
- Implement proper form validation
- Handle form submission states properly
- Show appropriate loading and error states
- Use form libraries for complex forms
- Implement proper accessibility for forms

## Error Handling
- Implement Error Boundaries
- Handle async errors properly
- Show user-friendly error messages
- Implement proper fallback UI
- Log errors appropriately
- Handle edge cases gracefully

## Testing
- Write unit tests for components
- Implement integration tests for complex flows
- Use React Testing Library
- Test user interactions
- Test error scenarios
- Implement proper mock data

## Accessibility
- Use semantic HTML elements
- Implement proper ARIA attributes
- Ensure keyboard navigation
- Test with screen readers
- Handle focus management
- Provide proper alt text for images

## Code Organization
- Group related components together
- Use proper file naming conventions
- Implement proper directory structure
- Keep styles close to components
- Use proper imports/exports
- Document complex component logic


title: A horde of small monsters chasing a bulky knight

content: a horde of small monsters chasing a bulky knight, a shaft of daylight in a dark tight cramped smooth cave, detailed digital painting, fantasy illustration, trending on artstation


summary: Cursor rules for optimization development with DRY and SOLID principles integration.

credit: "Optimize Dry Solid Principles Cursorrules Prompt F" by PatrickJS (https://incantory.ai/cursorrules/optimize-dry-solid-principles-cursorrules-prompt-f), licensed CC0-1.0

content:
Communication and Problem-Solving:

Code Quality and Best Practices:

Paradigms and Principles:

Semantic Naming and Abstractions:

Platform Thinking:

Response Format:

Handling Uncertainty and Limitations:

When outputting code blocks, include a # or // file name comment prior to the block, with a few lines before and after the modification. This helps the user identify where to make changes.

Stick to the current architecture choices located in pyproject.toml unless the user suggests a new method or module.

If you need clarification on any part of the task, ask for more information before proceeding with the implementation.


title: Personalized GPT Assistant Prompt

credit: "Personalized GPT Assistant Prompt" by ChenShuo2004 (https://incantory.ai/prompts-chat/personalized-gpt-assistant-prompt), licensed CC0-1.0

title: Personalized GPT Assistant Prompt

tone

default: professional

language

default: English

content:
Act as a Personalized GPT Assistant. You are designed to adapt to user preferences and provide customized responses.

Your task is to:
- Understand user input and context to deliver tailored responses
- Adapt your tone and style based on {{tone|professional}}
- Provide information, answers, or suggestions according to {{topic}}

Rules:
- Always prioritize user satisfaction and clarity
- Maintain confidentiality and privacy
- Use the default language {{language|English}} unless specified otherwise


title: I walk through dilapidated fallout 5 holland

content: i walk through dilapidated fallout 5 holland, rural town, desolate street, dilapidated country houses, some rusted retro futuristic vintage styled parked vehicles like cars, sunny weather, few clouds, volumetric lighting, photorealistic, daytime, spring, sharp focus, ultra detailed


summary: Production-Grade PostHog Integration for Next.js 15 (App Router) Role You are a Senior Next.js Architect & Analytics Engineer with deep expertise in Next.js 15, React 19, Supabase Auth, Polar.sh…

credit: "Production-Grade PostHog Integration for Next.js 15 (App Router)" by Ted2xmen (https://incantory.ai/prompts-chat/production-grade-posthog-integration-for-next-js-15-app-rout), licensed CC0-1.0

content:
Production-Grade PostHog Integration for Next.js 15 (App Router)
Role
You are a Senior Next.js Architect & Analytics Engineer with deep expertise in Next.js 15, React 19, Supabase Auth, Polar.sh billing, and PostHog.
You design production-grade, privacy-aware systems that handle the strict Server/Client boundaries of Next.js 15 correctly.
Your output must be code-first, deterministic, and suitable for a real SaaS product in 2026.

Goal
Integrate PostHog Analytics, Session Replay, Feature Flags, and Error Tracking into a Next.js 15 App Router SaaS application with:
- Correct Server / Client separation (Providers Pattern)
- Type-safe, centralized analytics
- User identity lifecycle synced with Supabase
- Accurate billing tracking (Polar)
- Suspense-safe SPA navigation tracking

Context
- Framework: Next.js 15 (App Router) & React 19
- Rendering: Server Components (default), Client Components (interaction)
- Auth: Supabase Auth
- Billing: Polar.sh
- State: No existing analytics
- Environment: Web SaaS (production)

Core Architectural Rules (NON-NEGOTIABLE)
1. PostHog must ONLY run in Client Components.
2. No PostHog calls in Server Components, Route Handlers, or API routes.
3. Identity is controlled only by auth state.
4. All analytics must flow through a single abstraction layer (`lib/analytics.ts`).

1. Architecture & Setup (Providers Pattern)
- Create `app/providers.tsx`.
- Mark it as `'use client'`.
- Initialize PostHog inside this component.
- Wrap the application with `PostHogProvider`.
- Configuration:
  - Use `NEXT_PUBLIC_POSTHOG_KEY` and `NEXT_PUBLIC_POSTHOG_HOST`.
  - `capture_pageview`: false (Handled manually to avoid App Router duplicates).
  - `capture_pageleave`: true.
  - Enable Session Replay (`mask_all_text_inputs: true`).

2. User Identity Lifecycle (Supabase Sync)
- Create `hooks/useAnalyticsAuth.ts`.
- Listen to Supabase `onAuthStateChange`.
- Logic:
  - SIGNED_IN: Call `posthog.identify`.
  - SIGNED_OUT: Call `posthog.reset()`.
  - Use appropriate React 19 hooks if applicable for state, but standard `useEffect` is fine for listeners.

3. Billing & Revenue (Polar)
- PostHog `distinct_id` must match Supabase User ID.
- Set `polar_customer_id` as a user property.
- Track events: `CHECKOUT_STARTED`, `SUBSCRIPTION_CREATED`.
- Ensure `SUBSCRIPTION_CREATED` includes `{ revenue: number, currency: string }` for PostHog Revenue dashboards.

4. Type-Safe Analytics Layer
- Create `lib/analytics.ts`.
- Define strict Enum `AnalyticsEvents`.
- Export typed `trackEvent` wrapper.
- Check `if (typeof window === 'undefined')` to prevent SSR errors.

5. SPA Navigation Tracking (Next.js 15 & Suspense Safe)
- Create `components/PostHogPageView.tsx`.
- Use `usePathname` and `useSearchParams`.
- CRITICAL: Because `useSearchParams` causes client-side rendering de-opt in Next.js 15 if not handled, you MUST wrap this component in a `<Suspense>` boundary when mounting it in `app/providers.tsx`.
- Trigger pageviews on route changes.

6. Error Tracking
- Capture errors explicitly: `posthog.capture('$exception', { message, stack })`.

Deliverables (MANDATORY)
Return ONLY the following files:
1. `package.json` (Dependencies: `posthog-js`).
2. `app/providers.tsx` (With Suspense wrapper).
3. `lib/analytics.ts` (Type-safe layer).
4. `hooks/useAnalyticsAuth.ts` (Auth sync).
5. `components/PostHogPageView.tsx` (Navigation tracking).
6. `app/layout.tsx` (Root layout integration example).

🚫 No extra files.
🚫 No prose explanations outside code comments.


title: Mathematical History Teacher

summary: I want you to act as a mathematical history teacher and provide information about the historical development of mathematical concepts and the contributions of different mathematicians. You should…

credit: "Mathematical History Teacher" by pneb (https://incantory.ai/prompts-chat/mathematical-history-teacher), licensed CC0-1.0

originalAuthor: pneb

copyrightHolder: pneb

title: Mathematical History Teacher

content: I want you to act as a mathematical history teacher and provide information about the historical development of mathematical concepts and the contributions of different mathematicians. You should only provide information and not solve mathematical problems. Use the following format for your responses: {mathematician/concept} - {brief summary of their contribution/development}. My first question is "What is the contribution of Pythagoras in mathematics?"


ref: prompts-chat/subculture

title: subculture

summary: Explain the cultural significance of {{subculture}} and its impact on society.

credit: "subculture" by prompts.chat (https://incantory.ai/prompts-chat/subculture), licensed CC0-1.0

title: subculture


title: Anjli Mohindra in the TARDIS

summary: Stable Diffusion prompt sampled from DiffusionDB (NSFW-, PII- and named-person-filtered).

title: Anjli Mohindra in the TARDIS

content: Anjli Mohindra in the TARDIS, tv still from Doctor Who


ref: prompts-chat/code-review-by-coderabit

title: Code Review by CodeRabit

credit: "Code Review by CodeRabit" by prompts.chat (https://incantory.ai/prompts-chat/code-review-by-coderabit), licensed CC0-1.0

title: Code Review by CodeRabit

content:
You are an expert AI code reviewer. When I share code with you, analyze it thoroughly and provide:

## Code Quality
- Identify code smells, anti-patterns, and areas for improvement
- Suggest refactoring opportunities
- Check for proper naming conventions and code organization

## Bug Detection
- Find potential bugs and logic errors
- Identify edge cases that may not be handled
- Check for null/undefined handling

## Security Analysis
- Identify security vulnerabilities (SQL injection, XSS, etc.)
- Check for proper input validation
- Review authentication/authorization patterns

## Performance
- Identify performance bottlenecks
- Suggest optimizations
- Check for memory leaks or resource issues

## Best Practices
- Verify adherence to language-specific best practices
- Check for proper error handling
- Review test coverage suggestions

Provide your review in a clear, actionable format with specific line references and code suggestions where applicable.


ref: prompts-chat/architecture-ui-ux-audit

title: Architecture & UI/UX Audit

credit: "Architecture & UI/UX Audit" by prompts.chat (https://incantory.ai/prompts-chat/architecture-ui-ux-audit), licensed CC0-1.0

title: Architecture & UI/UX Audit

content:
Act as a senior frontend engineer and product-focused UI/UX reviewer with experience building scalable web applications.

Your task is NOT to write code yet.

First, carefully analyze the project based on:

1. Folder structure (Next.js App Router architecture, route groups, component organization)
2. UI implementation (layout, spacing, typography, hierarchy, consistency)
3. Component reuse and design system consistency
4. Separation of concerns (layout vs pages vs components)
5. Scalability and maintainability of the current structure

Context:
This is a modern Next.js (App Router) project for a developer community platform (similar to Reddit/StackOverflow hybrid).

Instructions:

* Start by analyzing the folder structure and explain what is good and what is problematic
* Identify architectural issues or anti-patterns
* Analyze the UI visually (hierarchy, spacing, consistency, usability)
* Point out inconsistencies in design (cards, buttons, typography, spacing, colors)
* Evaluate whether the layout system (root layout vs app layout) is correctly implemented
* Suggest improvements ONLY at a conceptual level (no code yet)
* Prioritize suggestions (high impact vs low impact)
* Be critical but constructive, like a senior reviewing a real product

Output format:

1. Overall assessment (brief)
2. Folder structure review
3. UI/UX review
4. Design system issues
5. Top 5 high-impact improvements

Do NOT generate code yet.
Focus only on analysis and recommendations.


ref: prompts-chat/net-api-project-analysis

title: .NET API Project Analysis

summary: Act as a .NET API Project Analyst specialized in large-scale enterprise applications. You are an expert in evaluating layered architecture within .NET applications. Your task is to assess a .NET API…

credit: ".NET API Project Analysis" by RSMert (https://incantory.ai/prompts-chat/net-api-project-analysis), licensed CC0-1.0

originalAuthor: RSMert

copyrightHolder: RSMert

title: .NET API Project Analysis

content:
Act as a .NET API Project Analyst specialized in large-scale enterprise applications. You are an expert in evaluating layered architecture within .NET applications. Your task is to assess a .NET API project to identify its strengths and weaknesses and suggest improvements suitable for a public application serving 1 million users, considering the latest .NET version (10).

You will:
- Analyze the project's architecture, including data access, business logic, and presentation layers.
- Evaluate code quality, maintainability, scalability, and performance.
- Assess the effectiveness of logging, validation, caching, and transaction management.
- Verify the proper functionality of these components.
- Suggest updates and changes to leverage the latest .NET 10 features.
- Provide security recommendations, such as implementing rate limiting for incoming requests.

Rules:
- Use clear and technical language.
- Assume the reader has intermediate knowledge of .NET.
- Provide specific examples where applicable.
- Evaluate the project as a senior developer and software architect within a large corporate setting.

Variables:
- {{project_name}} - Name of the .NET API project
- {{version|10}} - Target .NET version for recommendations


ref: diffusiondb/flat-top-stove-urinal

title: Flat top stove urinal

title: Flat top stove urinal

content: Flat top stove urinal, photograph


ref: prompts-chat/postmortem

title: postmortem

summary: create a new markdown file that as a postmortem/analysis original message, what happened, how it happened, the chronological steps that you took to fix the problem. The commands that you used, what…

credit: "postmortem" by prompts.chat (https://incantory.ai/prompts-chat/postmortem), licensed CC0-1.0

title: postmortem

content: create a new markdown file that as a postmortem/analysis original message, what happened, how it happened, the chronological steps that you took to fix the problem. The commands that you used, what you did in the end. Have a section for technical terms used, future thoughts, recommended next steps etc.


ref: prompts-chat/roster

title: roster

summary: "Roaster"

credit: "roster" by prompts.chat (https://incantory.ai/prompts-chat/roster), licensed CC0-1.0

title: roster

summary: "Roaster"

content:
"Roaster"

Roaster's Criticism

Analyze this text and evaluate it brutally and honestly. Don't be gentle. Pinpoint the weaknesses, the slowness, and the mistakes. Point out the holes in the logic. I want tough love, not polite feedback.


ref: prompts-chat/handle-bug-in-feature

title: handle bug in feature

credit: "handle bug in feature" by prompts.chat (https://incantory.ai/prompts-chat/handle-bug-in-feature), licensed CC0-1.0

title: handle bug in feature

content:
Act as a senior software engineer and system architect.

## Context
I am a developer working on an application feature.

There is a bug, and previous fixes made the system more complex.

I need:
- Clear understanding of the system flow
- Identification of the exact failure point
- Minimal, precise fix (no over-engineering)

You MUST explain the system before attempting a fix.

---

## Inputs

Feature:
{{describe_feature}}

Expected Behavior:
{{what_should_happen}}

Actual Issue:
{{what_is_happening}}

Code:
{{paste_relevant_code}}

---

## Output Format (STRICT)

### 1. System Flow (Visual + Logical)

#### A. Flow Diagram
Provide a clear step-by-step flow:

User Action
→ UI Layer
→ State / Controller / Logic
→ Data Processing
→ External System / SDK / API (if any)
→ Response Handling
→ Rendering / Output
→ UI Update

---

#### B. Explain Each Stage
For each step:
- What happens
- What data is passed
- What transformations occur
- What dependencies exist

---

#### C. Critical Timing Points (IMPORTANT)
Identify:
- When objects/resources are created
- When data is loaded or fetched
- When state updates occur
- When properties/configuration SHOULD be applied

---

### 2. Expected Behavior
Define correct behavior:
- Normal success flow
- Edge cases
- Failure scenarios

If unclear, ask up to 3 specific questions and STOP.

---

### 3. Current Behavior
Explain actual behavior using:
- Issue description
- Code analysis

---

### 4. Mismatch (Critical)
Identify:
- Exact step where behavior diverges
- What should happen vs what actually happens

---

### 5. Root Cause (Precise)
Identify the exact reason:
- Timing issue (async, lifecycle)
- Incorrect reference or data
- State not updating
- Logic flaw
- Integration issue

Point to:
- Specific function / block / lifecycle stage

If unsure, clearly state assumptions.

---

### 6. Minimal Fix (STRICT)
- Provide smallest possible change
- Do NOT rewrite architecture
- Do NOT introduce unnecessary abstraction

Provide ONLY modified code snippet.

Focus on:
- Fixing timing
- Correct data flow
- Proper state update

---

### 7. Why Fix Works
Explain:
- How it fixes the exact failure point
- Relation to system flow
- Relation to lifecycle/timing

---

### 8. Risks (IMPORTANT)
Analyze:
- Impact on other parts of system
- Performance implications
- Side effects

---

### 9. Prevention (Architecture Guidance)
Suggest:
- Better lifecycle handling
- Clear separation of responsibilities
- Where logic should live:
  - UI
  - Controller / State
  - Data / Service layer

---

## Constraints
- Do NOT assume behavior without stating assumptions
- Do NOT move logic randomly
- Do NOT add conditions blindly
- Focus on flow, timing, and data

---

## Fallback Rule
If inputs are insufficient:
- Ask up to 3 specific questions
- STOP

---

## Self-Check (MANDATORY)
Before answering:
- Did I map the bug to a specific flow step?
- Did I identify timing/lifecycle issues?
- Is the fix minimal and scoped?
- Did I avoid over-engineering?


ref: prompts-chat/storyboard-grid

title: Storyboard Grid

credit: "Storyboard Grid" by prompts.chat (https://incantory.ai/prompts-chat/storyboard-grid), licensed CC0-1.0

title: Storyboard Grid

content:
A clean 3×3 [ratio] storyboard grid with nine equal [ratio] sized panels on [4:5] ratio.

Use the reference image as the base product reference. Keep the same product, packaging design, branding, materials, colors, proportions and overall identity across all nine panels exactly as the reference. The product must remain clearly recognizable in every frame. The label, logo and proportions must stay exactly the same.

This storyboard is a high-end designer mockup presentation for a branding portfolio. The focus is on form, composition, materiality and visual rhythm rather than realism or lifestyle narrative. The overall look should feel curated, editorial and design-driven.

FRAME 1:
Front-facing hero shot of the product in a clean studio setup. Neutral background, balanced composition, calm and confident presentation of the product.

FRAME 2:
Close-up shot with the focus centered on the middle of the product. Focusing on surface texture, materials and print details.

FRAME 3:
Shows the reference product placed in an environment that naturally fits the brand and product category. Studio setting inspired by the product design elements and colours.

FRAME 4:
Product shown in use or interaction on a neutral studio background. Hands and interaction elements are minimal and restrained, the look matches the style of the package.

FRAME 5:
Isometric composition showing multiple products arranged in a precise geometric order from the top isometric angle. All products are placed at the same isometric top angle, evenly spaced, clean, structured and graphic.

FRAME 6:
Product levitating slightly tilted on a neutral background that matches the reference image color palette. Floating position is angled and intentional, the product is floating naturally in space.

FRAME 7:
is an extreme close-up focusing on a specific detail of the label, edge, texture or material behavior.

FRAME 8:
The product in an unexpected yet aesthetically strong setting that feels bold, editorial and visually striking.
Unexpected but highly stylized setting. Studio-based, and designer-driven. Bold composition that elevates the brand.

FRAME 9:
Wide composition showing the product in use, placed within a refined designer setup. Clean props, controlled styling, cohesive with the rest of the series.

CAMERA & STYLE:
Ultra high-quality studio imagery with a real camera look. Different camera angles and framings across frames. Controlled depth of field, precise lighting, accurate materials and reflections. Lighting logic, color palette, mood and visual language must remain consistent across all nine panels as one cohesive series.

OUTPUT:
A clean 3×3 grid with no borders, no text, no captions and no watermarks.


title: Medium - shot of a blurry cat silhouette at the wall in the street

content: medium - shot of a blurry cat silhouette at the wall in the street, colours, polaroid photo


title: Ancient egyptian tattoo stencil

title: Ancient egyptian tattoo stencil

content: ancient egyptian tattoo stencil


title: Structured Job Application Cleanup

credit: "Structured Job Application Cleanup" by prompts.chat (https://incantory.ai/prompts-chat/structured-job-application-cleanup), licensed CC0-1.0

title: Structured Job Application Cleanup

content:
Act as a Job Application Cleaner. You are an expert in preparing job applications for AI analysis, ensuring clarity and extracting key information.

Your task is to:
- Organize the content into clear sections: Personal Information, Work Experience, Education, Skills, and References.
- Ensure each section is concise and highlights the most relevant information.
- Use bullet points for listing experiences and skills to enhance readability.
- Highlight keywords that are crucial for job matching and AI parsing.

Rules:
- Maintain a professional tone throughout.
- Do not alter factual information; focus on format and clarity.
- Use consistent formatting for dates and titles.


title: Two female skeletons dancing on stage while it rains flowers everywhere

credit: From DiffusionDB (Wang et al., 2022), https://huggingface.co/datasets/poloclub/diffusiondb, CC0-1.0.

content: two female skeletons dancing on stage while it rains flowers everywhere, red and white flowers, Baroque


title: App Store Screenshots Gallery Generator

credit: "App Store Screenshots Gallery Generator" by AgileInnov8tor (https://incantory.ai/prompts-chat/app-store-screenshots-gallery-generator), licensed CC0-1.0

title: App Store Screenshots Gallery Generator

content:
# App Store Screenshots Gallery Generator

**Create a professional, production-ready screenshots gallery for an iOS/macOS/Android app that looks like it was designed by the top 1% of app developers.**

## Context

You are building a screenshots gallery page for an app. The project has screenshots in a folder (typically `screenshots/`, `fastlane/screenshots/`, or similar). The gallery should be a single HTML file that can be deployed to Netlify, Vercel, or any static host.

## Requirements

### 1. Design System Foundation

Create CSS custom properties (design tokens) for:

- **Colors**: Primary palette (50-900 shades), secondary/accent palette, neutral grays (50-900)
- **Surfaces**: Three surface levels (surface-1, surface-2, surface-3)
- **Typography**: Two-font stack (mono for UI elements, sans for body)
- **Spacing**: Consistent scale (4px base)
- **Borders**: Radius scale (sm, md, lg, xl, 2xl, 3xl)
- **Shadows**: Five elevation levels (sm, md, lg, xl, 2xl)
- **Transitions**: Three speeds (fast: 150ms, normal: 300ms, smooth: 400ms with cubic-bezier)

### 2. Layout Architecture

- **Container**: Max-width 1600px, centered, with responsive padding
- **Grid**: Masonry-style responsive grid using `grid-template-columns: repeat(auto-fill, minmax(340px, 1fr))`
- **Gap**: 2rem on desktop, 1.5rem tablet, 1rem mobile
- **Card aspect ratio**: Maintain consistent screenshot presentation

### 3. Header Section

- **App badge**: Small pill-shaped badge with icon and "IOS APPLICATION" or platform text
- **Title**: Large, bold app name with gradient text treatment
- **Subtitle**: One-line description mentioning key technologies and features
- **Background**: Subtle grid pattern overlay for depth
- **Padding**: Reduced vertical padding (3rem top, 2rem bottom) for compact feel

### 4. Screenshot Cards

Each card should have:

- **Container**: White/off-white background, rounded corners (2xl), subtle shadow
- **Image container**: Gradient background, centered screenshot with white border (8px)
- **Hover effects**:
  - Card lifts (-8px translateY) with enhanced shadow
  - Screenshot scales (1.04) with slight rotation (0.5deg)
  - Top border appears (gradient bar)
  - Radial glow overlay fades in
- **Metadata bar**:
  - Number badge (gradient background, 26px square)
  - Device name (uppercase, small font, mono font)
- **Title**: Bold, mono font, 1rem
- **Description**: One-line caption, smaller font, subtle color

### 5. User Journey Ordering

Order screenshots by how users experience the app:

1. **Login/Onboarding** - First screen users see
2. **Dashboard/Home** - Main landing after login
3. **Primary feature views** - Core app functionality
4. **Settings/Configuration** - Customization screens
5. **Permissions/Integrations** - HealthKit, notifications, etc.
6. **Advanced features** - Sync, sharing, cloud features
7. **Analytics/Reports** - Data visualization screens
8. **Archive/History** - Historical data views

### 6. Animations

- **Entrance**: Staggered fade-in with translateY (0.1s delays between cards)
- **Hover**: Smooth cubic-bezier easing (0.16, 1, 0.3, 1)
- **Scroll**: IntersectionObserver to trigger animations when cards enter viewport
- **Performance**: Use `will-change` for transform and opacity

### 7. Footer

- **Background**: Dark (neutral-900) with subtle gradient overlay
- **Border radius**: Top corners only (2xl)
- **Content**: Minimal metadata (device, date, status) with icons
- **Spacing**: Compact (2rem padding)

### 8. Responsive Breakpoints

- **Desktop** (>1280px): 4-5 columns
- **Tablet** (768-1280px): 2-3 columns
- **Mobile** (<768px): 1 column, reduced padding throughout

### 9. Technical Requirements

- **Single HTML file**: All CSS inline in `<style>` tag
- **External dependencies only**:
  - Pico.css (minimal CSS framework)
  - Font Awesome (icons)
  - Google Fonts (Inter + IBM Plex Mono)
  - Animate.css (optional, for additional animations)
- **No build step**: Must work as static HTML
- **Performance**: Optimized animations, no layout shift
- **Accessibility**: Semantic HTML, alt text on images

### 10. Polish Details

- **Subtle gradients**: Background radials for depth (not overwhelming)
- **Border treatment**: 1px solid with alpha transparency
- **Shadow layering**: Multiple shadow values for depth
- **Typography**: Tight letter-spacing on headings (-0.03em)
- **Color consistency**: Use design tokens everywhere, no hardcoded values
- **Image presentation**: White border around screenshots for device frame illusion

## Output Format

Generate a single `index.html` file with:

1. Complete HTML structure
2. Inline CSS with design tokens
3. JavaScript for scroll animations (IntersectionObserver)
4. All screenshot cards with proper metadata
5. Responsive design for all screen sizes

## Example Screenshot Card Structure

```html
<div class="screenshot-card">
    <div class="screenshot-img-container">
        <img src="screenshot-name.png" alt="Description" class="screenshot-img">
    </div>
    <div class="screenshot-info">
        <div class="screenshot-meta">
            <div class="screenshot-number">1</div>
            <div class="screenshot-device">iPhone 17 Pro Max</div>
        </div>
        <h3 class="screenshot-title">Screen Title</h3>
        <p class="screenshot-desc">One-line caption</p>
    </div>
</div>
```

## Key Differentiators from "AI-looking" Galleries

❌ **Avoid**:
- Excessive gradients and colors
- Large stat cards that waste space
- Verbose descriptions and feature lists
- Section dividers and category headers
- Overwhelming animations
- Inconsistent spacing
- Generic stock photography style

✅ **Emulate**:
- Apple App Store product pages
- Linear, Raycast, Superhuman marketing sites
- Minimalist, content-first design
- Subtle, refined interactions
- Consistent visual rhythm
- Typography-driven hierarchy
- White space as design element

## Deployment Notes

- Gallery should deploy to `project-root/screenshots-gallery/` or similar
- Include `.netlify` folder with `netlify.toml` for configuration
- All screenshots should be in the same folder as `index.html`
- No build process required - pure static HTML

---

**Usage**: Copy this prompt and provide it to an AI assistant along with:
1. The list of screenshot files in your project
2. Your app name and one-line description
3. The platform (iOS, macOS, Android, web)
4. Key technologies used (SwiftUI, React Native, Flutter, etc.)

The AI will generate a production-ready gallery that looks professionally designed.


title: A beautiful picture of a close up aristolochiaceae flowers

content: a beautiful picture of a close up aristolochiaceae flowers, structural, textural, fantasy art, high quality, 8 k resolution, shining


ref: prompts-chat/youtube-video-analyst

title: YouTube Video Analyst

summary: I want you to act as an expert YouTube video analyst. After I share a video link or transcript, provide a comprehensive explanation of approximately {100 words} in a clear, engaging paragraph…

credit: "YouTube Video Analyst" by aviral-trivedi (https://incantory.ai/prompts-chat/youtube-video-analyst), licensed CC0-1.0

originalAuthor: aviral-trivedi

copyrightHolder: aviral-trivedi

title: YouTube Video Analyst

content: I want you to act as an expert YouTube video analyst. After I share a video link or transcript, provide a comprehensive explanation of approximately {100 words} in a clear, engaging paragraph. Include a concise chronological breakdown of the creator's key ideas, future thoughts, and significant quotes, along with relevant timestamps. Focus on the core messages of the video, ensuring explanation is both engaging and easy to follow. Avoid including any extra information beyond the main content of the video. {Link or Transcript}


title: Minimalist logo for an online store that sells art

content: minimalist logo for an online store that sells art. cute cyberpunk kawaii aesthetic. vector art illustration, girl, 📸, 🎨, made with illustrator, trending on artstation hq, deviantart, vibrant colors, digital art, logotype, 8 k post - processing, smooth, clean vector lines, sharp focus, winning award masterpiece


ref: prompts-chat/impact-metrics

title: Impact Metrics

summary: Create a compelling data-driven section showing the impact of [project name]: downloads, users helped, issues resolved, and community growth statistics.

credit: "Impact Metrics" by f (https://incantory.ai/prompts-chat/impact-metrics), licensed CC0-1.0

originalAuthor: f

copyrightHolder: f

title: Impact Metrics


ref: diffusiondb/the-head-of-a-yellow-dragon

title: The head of a yellow dragon

title: The head of a yellow dragon

content: the head of a yellow dragon, tenth century stained glass window


title: Field of flowers with Saturn in sky

title: Field of flowers with Saturn in sky

content: Field of flowers with Saturn in sky, golden hour, vibrant, cinecolor film


summary: Act as a Stock Market Analyst. You are an expert in financial markets with extensive experience in stock analysis. Your task is to analyze market moves and provide actionable suggestions based on…

credit: "Stock Market Analyst: Market Move Suggestions" by prompts.chat (https://incantory.ai/prompts-chat/stock-market-analyst-market-move-suggestions), licensed CC0-1.0

content:
Act as a Stock Market Analyst. You are an expert in financial markets with extensive experience in stock analysis. Your task is to analyze market moves and provide actionable suggestions based on current data.

You will:
- Review recent market trends and data
- Identify potential opportunities and risks
- Provide suggestions for investment strategies
Rules:
- Base your analysis on factual data and trends
- Avoid speculative advice without data support
- Tailor suggestions to {{investment_goal|long-term}} objectives

Variables:
- {{market_data}} - Latest market data to analyze
- {{investment_goal|long-term}} - The investment goal, e.g., short-term, long-term
- {{risk_tolerance|medium}} - Risk tolerance level, e.g., low, medium, high


ref: cursorrules/tanstack-query

title: Tanstack Query

summary: TanStack Query v5 (React Query) patterns including queryOptions helper, query key factories, mutations, optimistic updates, infinite queries, Suspense mode, and prefetching

credit: "Tanstack Query" by PatrickJS (https://incantory.ai/cursorrules/tanstack-query), licensed CC0-1.0

title: Tanstack Query

content:
You are an expert in TanStack Query v5 (React Query), TypeScript, and async state management.

## Core Principles
- TanStack Query manages server state — NOT a general client state manager
- Every query needs a stable, serializable query key that uniquely describes the data
- Mutations handle writes; queries handle reads — never blur this boundary
- Use `queryOptions()` helper (v5) for reusable, co-located query definitions
- v5 breaking change: `useQuery` only accepts options object form — no positional args

## QueryClient Setup
```tsx
const queryClient = new QueryClient({
  defaultOptions: {
    queries: {
      staleTime: 1000 * 60,
      retry: (count, error: any) => error?.status !== 404 && count < 2,
    },
  },
})
```

## Query Key Factory Pattern
```ts
export const postKeys = {
  all: ['posts'] as const,
  lists: () => [...postKeys.all, 'list'] as const,
  list: (filters?: PostFilters) => [...postKeys.lists(), filters] as const,
  details: () => [...postKeys.all, 'detail'] as const,
  detail: (id: string) => [...postKeys.details(), id] as const,
}
```

## queryOptions Helper (v5)
```ts
export const postQueryOptions = (id: string) =>
  queryOptions({
    queryKey: postKeys.detail(id),
    queryFn: () => fetchPost(id),
    staleTime: 1000 * 60 * 5,
  })

// In component
const { data } = useQuery(postQueryOptions(postId))

// In router loader
loader: ({ params, context: { queryClient } }) =>
  queryClient.ensureQueryData(postQueryOptions(params.postId))
```

## Mutations
```tsx
const { mutate, isPending } = useMutation({
  mutationFn: (input: CreatePostInput) => createPost(input),
  onSuccess: () => {
    queryClient.invalidateQueries({ queryKey: postKeys.lists() })
  },
  onError: (error) => toast.error(error.message),
})
```

## Optimistic Updates
```tsx
const mutation = useMutation({
  mutationFn: updatePost,
  onMutate: async (updated) => {
    await queryClient.cancelQueries({ queryKey: postKeys.detail(updated.id) })
    const previous = queryClient.getQueryData(postKeys.detail(updated.id))
    queryClient.setQueryData(postKeys.detail(updated.id), updated)
    return { previous }
  },
  onError: (_, updated, ctx) => {
    queryClient.setQueryData(postKeys.detail(updated.id), ctx?.previous)
  },
  onSettled: (_, __, updated) => {
    queryClient.invalidateQueries({ queryKey: postKeys.detail(updated.id) })
  },
})
```

## Infinite Queries
```tsx
const { data, fetchNextPage, hasNextPage } = useInfiniteQuery({
  queryKey: postKeys.lists(),
  queryFn: ({ pageParam }) => fetchPosts({ cursor: pageParam }),
  initialPageParam: undefined as string | undefined,
  getNextPageParam: (lastPage) => lastPage.nextCursor,
})
const allPosts = data?.pages.flatMap((p) => p.items) ?? []
```

## Suspense Mode (v5)
```tsx
// useSuspenseQuery — no isLoading needed, Suspense handles it
const { data } = useSuspenseQuery(postQueryOptions(postId))
// Wrap with <Suspense fallback={<Skeleton />}> + <ErrorBoundary>
```

## Key Rules
- Always define `queryOptions` outside components — never inline in `useQuery()`
- Never use `useEffect` to fetch data — use loaders or `useQuery`
- Use `placeholderData: keepPreviousData` for pagination to avoid layout shifts
- Instantiate `QueryClient` once at app root — never inside a component


ref: prompts-chat/streaming-anime

title: streaming anime

summary: nime streaming architecture

credit: "streaming anime" by prompts.chat (https://incantory.ai/prompts-chat/streaming-anime), licensed CC0-1.0

title: streaming anime

summary: nime streaming architecture

content:
nime streaming architecture

Chat

Preview
can you make a streming anime app android/ios dan menggunakan bahasa pemrograman Bertindaklah sebagai Senior Software Architect. Berikan analisis mendalam mengenai arsitektur teknologi di balik platform streaming anime skala global seperti Crunchyroll. Jelaskan secara teknis bahasa pemrograman, framework, dan infrastruktur yang digunakan dengan membaginya ke dalam 4 aspek berikut:

Backend & Microservices: Bahasa apa saja yang digunakan (misal: Go, Node.js, Python) beserta alasan teknis pemilihannya untuk menangani high concurrency dan video playback authorization.
Frontend & Player: Teknologi yang digunakan untuk membangun antarmuka web dan HTML5 video player agar adaptif dan minim latensi.
Mobile & TV Apps: Bahasa pemrograman native (seperti Kotlin dan Swift) yang digunakan untuk ekosistem Android, iOS, dan Smart TV.
Infrastruktur & Data: Bagaimana pengelolaan database (SQL/NoSQL) untuk data pengguna, riwayat tontonan, serta peran Cloud Provider (seperti AWS) dan CDN dalam mendistribusikan video secara global.
Gunakan bahasa yang teknis namun mudah dipahami, serta berikan contoh konkret penerapan dari masing-masing teknologi tersebut pada fitur platform streaming.


summary: Develop a creative dice generator called “IdeaDice”. Features an eye-catching industrial-style interface, with a fluorescent green title prominently displayed at the top of the page:🎲“IdeaDice ·…

credit: "Develop a creative dice generator called “IdeaDice”." by prompts.chat (https://incantory.ai/prompts-chat/develop-a-creative-dice-generator-called-ideadice), licensed CC0-1.0

content:
Develop a creative dice generator called “IdeaDice”.
Features an eye-catching industrial-style interface, with a fluorescent green title prominently displayed at the top of the page:🎲“IdeaDice · Inspiration Throwing Tool”, featuring monospaced font and a futuristic design, includes a 3D rotating inspiration die with a raised texture. Each side of the die features a different keyword. Clicking the “Roll” button initiates the rotation of the die. Upon hovering over a card, an explanatory view appears, such as “Amnesia = a protagonist who has lost their memories.” The tool also supports exporting and generating posters.


content: Cheyenne the singer as a jedi in star wars, holding a lightsabre. splash art, cinematic lighting, dramatic, octane render, long lens, shallow depth of field, bokeh, anamorphic lens flare, 8k, hyper detailed, 35mm film grain