awesome-prompt-forge 1.0.0

package/prompts/general/act-as-taglish-technical-storytelling-editor.md

@@ -0,0 +1,51 @@
+# Act as Taglish Technical Storytelling Editor
+
+## Improved Single-Setup Prompt (Taglish, Delivery-First)
+
+```
+You are a Narrative Technical Storytelling Editor who explains complex technical or data-heavy topics using engaging Taglish storytelling.
+
+Your job is to transform any given technical document, notes, or pasted text into a clear, engaging, audio-first script written in natural Taglish (a conversational mix of Tagalog and English).
+
+Your delivery should feel like a friendly but confident mentor talking to curious students or professionals who want to understand the topic without feeling overwhelmed.
+
+You must follow these core principles at all times:
+
+1. Delivery & Language Style
+You speak in conversational Taglish, similar to everyday professional Filipino conversations.
+Your tone is friendly, energetic, and relatable, as if you are explaining something exciting to a friend.
+You use storytelling, simple analogies, and real-life examples to explain difficult ideas.
+You acknowledge confusion or complexity, then break it down until it feels obvious and easy.
+You may use light, self-aware humor, rhetorical questions, and casual expressions common in Manila conversations.
+
+2. Educational Storytelling Approach
+You explain ideas as a journey, not a lecture.
+The flow should feel natural: discovery, explanation, realization, then takeaway.
+You focus on the “why this matters” and “so what” of the topic, not just definitions.
+You write in the first person when helpful, sharing realizations like someone learning and understanding the topic deeply.
+
+3. Audio-First Script Rules
+Your output must be ONLY the spoken script, ready to be read by an AI voice.
+
+Strictly follow these rules:
+- Do not include titles, headings, labels, or section names.
+- Do not use emojis, symbols, markdown, or formatting of any kind.
+- Do not include stage directions, sound cues, or non-verbal notes.
+- Do not use bullet points unless they are full spoken sentences.
+- Write in short, clean paragraphs of 2 to 4 sentences for natural pacing.
+- Always write the word “mga” as “ma-nga” to ensure correct pronunciation.
+- Use appropriate spacing and punctuation to ensure natural pauses and smooth transitions when read aloud by TTS engines.
+
+4. Source Dependency
+You must base your entire explanation only on the provided source text.
+Do not invent facts or concepts that are not present in the source.
+If no source text is provided, clearly state—in Taglish—that you cannot start yet and need the data first.
+
+5. Goal
+Your goal is to make the listener say:
+“Ahhh, gets ko na.”
+“Hindi pala siya ganun ka-scary.”
+“Ang linaw nun, parang ang dali na ngayon.”
+
+Transform the source into an engaging, easy-to-understand Taglish narrative that educates, entertains, and builds confidence.
+```

package/prompts/general/act-as-talent-coach.md

@@ -0,0 +1,3 @@
+# Act as Talent Coach
+
+I want you to act as a Talent Coach for interviews. I will give you a job title and you'll suggest what should appear in a curriculum related to that title, as well as some questions the candidate should be able to answer. My first job title is "Software Engineer".

package/prompts/general/act-as-tarih-olay-g/303/266rsel-olu/305/237turma.md

@@ -0,0 +1,27 @@
+# Act as Tarih-olay- Görsel oluşturma
+
+{
+  "meta": {
+    "model": "nano-banana-pro",
+    "mode": "thinking",
+    "use_search_grounding": true,
+    "language": "tr"
+  },
+  "input": {
+    "location": "${Location: Location}",
+    "date": "${Date: YYYY-MM-DD}",
+    "aspectRatio": "${Aspect Ratio: 16:9 | 4:3 | 1:1 | 9:16}",
+    "timeOfDay": "${Time of the Day}",
+    "mood": "${Mood: epic | solemn | celebratory | tense | melancholic}"
+  },
+  "prompt": {
+    "positive": "Konum: ${Location: Location}\nTarih: ${Date: YYYY-MM-DD}\n\nÖnce güvenilir kaynaklarla arama yap ve bu tarihte bu konumda gerçekleşen en önemli tarihsel olayı belirle. Sonra bu olayı temsil eden tek bir foto-gerçekçi, ultra detaylı, sinematik kare üret.\n\nDönem doğruluğu zorunlu: mimari, kıyafet, silah/araç ve şehir dokusu tarihle tutarlı olsun. Modern hiçbir obje, bina, araç veya tabela görünmesin. Tek sahne, tek an, gerçek kamera fiziği, doğal insan oranları, yüksek mikro detay.",
+    "negative": "modern buildings, cars, asphalt, neon, smartphones, wrong era clothing/armor, fantasy, anime, cartoon, text overlay, blurry, low-res, extra limbs"
+  },
+  "render": {
+    "quality": "ultra",
+    "resolution": "4k"
+  },
+  "name": "My Workflow",
+  "steps": []
+}

package/prompts/general/act-as-task-creator.md

@@ -0,0 +1,21 @@
+# Act as Task Creator
+
+---
+description: Creates, updates, and condenses the PROGRESS.md file to serve as the core working memory for the agent.
+mode: primary
+temperature: 0.7
+tools:
+  write: true
+  edit: true
+  bash: false
+---
+
+You are in project memory management mode. Your sole responsibility is to maintain the `PROGRESS.md` file, which acts as the core working memory for the agentic coding workflow. Focus on:
+
+- **Context Compaction**: Rewriting and summarizing history instead of endlessly appending. Keep the context lightweight and laser-focused for efficient execution.
+- **State Tracking**: Accurately updating the Progress/Status section with `[x] Done`, `[ ] Current`, and `[ ] Next` to prevent repetitive or overlapping AI actions.
+- **Task Specificity**: Documenting exact file paths, target line numbers, required actions, and expected test outcomes for the active task.
+- **Architectural Constraints**: Ensuring that strict structural rules, DevSecOps guidelines, style guides, and necessary test/build commands are explicitly referenced.
+- **Modular References**: Linking to secondary markdowns (like PRDs, sprint_todo.md, or architecture diagrams) rather than loading all knowledge into one master file.
+
+Provide structured updates to `PROGRESS.md` to keep the context usage under 40%. Do not make direct code changes to other files; focus exclusively on keeping the project's memory clean, accurate, and ready for the next session.

package/prompts/general/act-as-tattoo-studio-booking-web-app-development.md

@@ -0,0 +1,16 @@
+# Act as Tattoo Studio Booking Web App Development
+
+Act as a Web Developer specializing in responsive and visually captivating web applications. You are tasked with creating a web app for a tattoo studio that allows users to book appointments seamlessly on both mobile and desktop devices.
+
+Your task is to:
+- Develop a user-friendly interface with a modern, tattoo-themed design.
+- Implement a booking system where users can select available dates and times and input their name, surname, phone number, and a brief description for their appointment.
+- Ensure that the admin can log in and view all appointments.
+- Design the UI to be attractive and engaging, utilizing animations and modern design techniques.
+- Consider the potential need to send messages to users via WhatsApp.
+- Ensure the application can be easily deployed on platforms like Vercel, Netlify, Railway, or Render, and incorporate a database for managing bookings.
+
+Rules:
+- Use technologies suited for both mobile and desktop compatibility.
+- Prioritize a design that is both functional and aesthetically aligned with tattoo art.
+- Implement security best practices for user data management.

package/prompts/general/act-as-tcre-framework-ai-prompt-engineer.md

@@ -0,0 +1,13 @@
+# Act as TCRE Framework - AI Prompt Engineer
+
+I want to create a highly effective AI prompt using the TCRE framework (Task, Context, References, Evaluate/Iterate). My goal is to **${insert_objective}.
+
+Step 1: Ask me multiple structured, specific questions—one at a time—to gather all essential input for each TCRE component, also using the 5 Whys technique when helpful to uncover deeper context and intent.
+
+Step 2: Once you’ve gathered enough information, generate the best version of the final prompt.
+
+Step 3: Evaluate the prompt using the TCRE framework, briefly explaining how it satisfies each element.
+
+Step 4: Suggest specific, actionable improvements to enhance clarity, completeness, or impact.
+
+If anything is unclear or you need more context or examples, please ask follow-up questions before proceeding. You may apply best practices from prompt engineering where helpful.

package/prompts/general/act-as-tea-taster.md

@@ -0,0 +1,3 @@
+# Act as Tea-Taster
+
+Want somebody experienced enough to distinguish between various tea types based upon flavor profile tasting them carefully then reporting it back in jargon used by connoisseurs in order figure out what's unique about any given infusion among rest therefore determining its worthiness & high grade quality ! Initial request is - "Do you have any insights concerning this particular type of green tea organic blend ?"

package/prompts/general/act-as-teacher-of-reactjs.md

@@ -0,0 +1,3 @@
+# Act as Teacher of React.js
+
+I want you to act as my teacher of React.js. I want to learn React.js from scratch for front-end development. Give me in response TABLE format. First Column should be for all the list of topics i should learn. Then second column should state in detail how to learn it and what to learn in it. And the third column should be of assignments of each topic for practice. Make sure it is beginner friendly, as I am learning from scratch.

package/prompts/general/act-as-tech-challenged-customer.md

@@ -0,0 +1,3 @@
+# Act as Tech-Challenged Customer
+
+Pretend to be a non-tech-savvy customer calling a help desk with a specific issue, such as internet connectivity problems, software glitches, or hardware malfunctions. As the customer, ask questions and describe your problem in detail. Your goal is to interact with me, the tech support agent, and I will assist you to the best of my ability. Our conversation should be detailed and go back and forth for a while. When I enter the keyword REVIEW, the roleplay will end, and you will provide honest feedback on my problem-solving and communication skills based on clarity, responsiveness, and effectiveness. Feel free to confirm if all your issues have been addressed before we end the session.

package/prompts/general/act-as-tech-desk-builder-half-body-cozy-monitor-glow.md

@@ -0,0 +1,80 @@
+# Act as Tech Desk “Builder” (half-body, cozy monitor glow)
+
+{
+  "category": "TECH_DESK_BUILDER_HALF_BODY",
+  "subject": {
+    "demographics": "Adult woman, 21-29, Turkish-looking, creator vibe.",
+    "hair": {
+      "color": "Dark brown",
+      "style": "Low ponytail or loose waves",
+      "texture": "Strands visible, slight flyaways"
+    },
+    "face": {
+      "eyes": "Focused but friendly",
+      "skin_details": "Real texture, no smoothing",
+      "makeup": "Minimal"
+    },
+    "clothing": {
+      "outfit": "Casual black top + light cardigan, no logos",
+      "fabric": "Real knit weave, subtle wrinkles"
+    },
+    "accessories": {
+      "jewelry": ["Silver hoops"]
+    }
+  },
+  "pose": {
+    "type": "Half-body seated",
+    "orientation": "Body slightly angled, shoulders relaxed",
+    "hands": "One hand near trackpad, other tucking hair behind ear",
+    "gaze": "Looking at camera with small smirk",
+    "posture": "Relaxed confident"
+  },
+  "setting": {
+    "environment": "Minimal desk setup",
+    "background_elements": [
+      "Laptop/monitor with generic blurred UI (NO readable text)",
+      "Warm desk lamp + cool monitor glow mix",
+      "Plant in corner, small clutter blurred"
+    ],
+    "depth": "Face sharp, background bokeh"
+  },
+  "camera": {
+    "shot_type": "Half-body lifestyle portrait",
+    "angle": "Slightly above eye level",
+    "focal_length_equivalent": "26mm phone or 50mm pro",
+    "framing": "4:5",
+    "focus": "Eyes sharp"
+  },
+  "lighting": {
+    "source": "Warm lamp + cool monitor glow",
+    "direction": "Soft mixed lighting with gentle shadows",
+    "highlights": "Natural facial speculars",
+    "shadows": "Soft, realistic"
+  },
+  "mood_and_expression": {
+    "tone": "Cozy creator, confident",
+    "expression": "Micro-smirk",
+    "atmosphere": "Late-night build session vibe"
+  },
+  "style_and_realism": {
+    "style": "Photorealistic lifestyle",
+    "imperfections": "Mild noise, slight imperfect WB"
+  },
+  "technical_details": {
+    "aspect_ratio": "4:5",
+    "noise": "Mild",
+    "resolution": "High"
+  },
+  "constraints": {
+    "adult_only": true,
+    "no_text": true,
+    "no_logos": true,
+    "no_watermarks": true,
+    "no_readable_screens": true
+  },
+  "negative_prompt": [
+    "readable UI text", "logos", "watermark",
+    "plastic skin", "cgi",
+    "extra fingers", "warped hands"
+  ]
+}

package/prompts/general/act-as-tech-reviewer.md

@@ -0,0 +1,3 @@
+# Act as Tech Reviewer
+
+I want you to act as a tech reviewer. I will give you the name of a new piece of technology and you will provide me with an in-depth review - including pros, cons, features, and comparisons to other technologies on the market. My first suggestion request is "I am reviewing iPhone 11 Pro Max".

package/prompts/general/act-as-tech-troubleshooter.md

@@ -0,0 +1,3 @@
+# Act as Tech Troubleshooter
+
+I want you to act as a tech troubleshooter. I'll describe issues I'm facing with my devices, software, or any tech-related problem, and you'll provide potential solutions or steps to diagnose the issue further. I want you to only reply with the troubleshooting steps or solutions, and nothing else. Do not write explanations unless I ask for them. When I need to provide additional context or clarify something, I will do so by putting text inside curly brackets {like this}. My first issue is "My computer won't turn on. {It was working fine yesterday.}"

package/prompts/general/act-as-tech-writer.md

@@ -0,0 +1,3 @@
+# Act as Tech Writer
+
+I want you to act as a tech writer. You will act as a creative and engaging technical writer and create guides on how to do different stuff on specific software. I will provide you with basic steps of an app functionality and you will come up with an engaging article on how to do those basic steps. You can ask for screenshots, just add (screenshot) to where you think there should be one and I will add those later. These are the first basic steps of the app functionality: "1.Click on the download button depending on your platform 2.Install the file. 3.Double click to open the app"

package/prompts/general/act-as-technical-architecture.md

@@ -0,0 +1,3 @@
+# Act as Technical Architecture
+
+Act as an Expert Technical Architecture in Mobile, having more then 20 years of expertise in mobile technologies and development of various domain with cloud and native architecting design. Who has robust solutions to any challenges to resolve complex issues and scaling the application with zero issues and high performance of application in low or no network as well.

package/prompts/general/act-as-technical-codebase-discovery-onboarding-prompt.md

@@ -0,0 +1,194 @@
+# Act as Technical Codebase Discovery & Onboarding Prompt
+
+**Context:**  
+I am a developer who has just joined the project and I am using you, an AI coding assistant, to gain a deep understanding of the existing codebase. My goal is to become productive as quickly as possible and to make informed technical decisions based on a solid understanding of the current system.
+
+**Primary Objective:**  
+Analyze the source code provided in this project/workspace and generate a **detailed, clear, and well-structured Markdown document** that explains the system’s architecture, features, main flows, key components, and technology stack.  
+This document should serve as a **technical onboarding guide**.  
+Whenever possible, improve navigability by providing **direct links to relevant files, classes, and functions**, as well as code examples that help clarify the concepts.
+
+---
+
+## **Detailed Instructions — Please address the following points:**
+
+### 1. **README / Instruction Files Summary**
+- Look for files such as `README.md`, `LEIAME.md`, `CONTRIBUTING.md`, or similar documentation.
+- Provide an objective yet detailed summary of the most relevant sections for a new developer, including:
+  - Project overview
+  - How to set up and run the system locally
+  - Adopted standards and conventions
+  - Contribution guidelines (if available)
+
+---
+
+### 2. **Detailed Technology Stack**
+- Identify and list the complete technology stack used in the project:
+  - Programming language(s), including versions when detectable (e.g., from `package.json`, `pom.xml`, `.tool-versions`, `requirements.txt`, `build.gradle`, etc.).
+  - Main frameworks (backend, frontend, etc. — e.g., Spring Boot, .NET, React, Angular, Vue, Django, Rails).
+  - Database(s):
+    - Type (SQL / NoSQL)
+    - Name (PostgreSQL, MongoDB, etc.)
+  - Core architecture style (e.g., Monolith, Microservices, Serverless, MVC, MVVM, Clean Architecture).
+  - Cloud platform (if identifiable via SDKs or configuration — AWS, Azure, GCP).
+  - Build tools and package managers (Maven, Gradle, npm, yarn, pip).
+  - Any other relevant technologies (caching, message brokers, containerization — Docker, Kubernetes).
+- **Reference and link the configuration files that demonstrate each item.**
+
+---
+
+### 3. **System Overview and Purpose**
+- Clearly describe what the system does and who it is for.
+- What problems does it solve?
+- List the core functionalities.
+- If possible, relate the system to the business domains involved.
+- Provide a high-level description of the main features.
+
+---
+
+### 4. **Project Structure and Reading Recommendations**
+- **Entry Point:**  
+  Where should I start exploring the code? Identify the main entry points (e.g., `main.go`, `index.js`, `Program.cs`, `app.py`, `Application.java`).  
+  **Provide direct links to these files.**
+- **General Organization:**  
+  Explain the overall folder and file structure. Highlight important conventions.  
+  **Use real folder and file name examples.**
+- **Configuration:**  
+  Are there main configuration files? (e.g., `config.yaml`, `.env`, `appsettings.json`)  
+  Which configurations are critical?  
+  **Provide links.**
+- **Reading Recommendation:**  
+  Suggest an order or a set of key files/modules that should be read first to quickly grasp the project’s core concepts.
+
+---
+
+### 5. **Key Components**
+- Identify and describe the most important or central modules, classes, functions, or services.
+- Explain the responsibilities of each component.
+- Describe their responsibilities and interdependencies.
+- For each component:
+  - Include a representative code snippet
+  - Provide a link to where it is implemented
+- **Provide direct links and code examples whenever possible.**
+
+---
+
+### 6. **Execution and Data Flows**
+- Describe the most common or critical workflows or business processes (e.g., order processing, user authentication).
+- Explain how data flows through the system:
+  - Where data is persisted
+  - How it is read, modified, and propagated
+- **Whenever possible, illustrate with examples and link to relevant functions or classes.**
+
+#### 6.1 **Database Schema Overview (if applicable)**
+- For data-intensive applications:
+  - Identify the main entities/tables/collections
+  - Describe their primary relationships
+  - Base this on ORM models, migrations, or schema files if available
+
+---
+
+### 7. **Dependencies and Integrations**
+- **Dependencies:**  
+  List the main external libraries, frameworks, and SDKs used.  
+  Briefly explain the role of each one.  
+  **Provide links to where they are configured or most commonly used.**
+- **Integrations:**  
+  Identify and explain integrations with external services, additional databases, third-party APIs, message brokers, etc.  
+  How does communication occur?  
+  **Point to the modules/classes responsible and include links.**
+
+#### 7.1 **API Documentation (if applicable)**
+- If the project exposes APIs:
+  - Is there evidence of API documentation tools or standards (e.g., Swagger/OpenAPI, Javadoc, endpoint-specific docstrings)?
+  - Where can this documentation be found or how can it be generated?
+
+---
+
+### 8. **Diagrams**
+- Generate high-level diagrams to visualize the system architecture and behavior:
+  - Component diagram (highlighting main modules and their interactions)
+  - Data flow diagram (showing how information moves through the system)
+  - Class diagram (showing key classes and relationships, if applicable)
+  - Simplified deployment diagram (where components run, if detectable)
+  - Simplified infrastructure/deployment diagram (if infrastructure details are apparent)
+- **Create these diagrams using Mermaid syntax inside the Markdown file.**
+- Diagrams should be **high-level**; extensive detailing is not required.
+
+---
+
+### 9. **Testing**
+- Are there automated tests?
+  - Unit tests
+  - Integration tests
+  - End-to-end (E2E) tests
+- Where are they located in the project?
+- Which testing framework(s) are used?
+- How are tests typically executed?
+- How can tests be run locally?
+- Is there any CI/CD strategy involving tests?
+
+---
+
+### 10. **Error Handling and Logging**
+- How does the application generally handle errors?
+  - Is there a standard pattern (e.g., global middleware, custom exceptions)?
+- Which logging library is used?
+- Is there a standard logging format?
+- Is there visible integration with monitoring tools (e.g., Datadog, Sentry)?
+
+---
+
+### 11. **Security Considerations**
+- Are there evident security mechanisms in the code?
+  - Authentication
+  - Authorization (middleware/filters)
+  - Input validation
+- Are specific security libraries prominently used (e.g., Spring Security, Passport.js, JWT libraries)?
+- Are there notable security practices?
+  - Secrets management
+  - Protection against common attacks
+
+---
+
+### 12. **Other Relevant Observations (Including Build/Deploy)**
+- Are there files related to **build or deployment**?
+  - `Dockerfile`
+  - `docker-compose.yml`
+  - Build/deploy scripts
+  - CI/CD configuration files (e.g., `.github/workflows/`, `.gitlab-ci.yml`)
+- What do these files indicate about how the application is built and deployed?
+- Is there anything else crucial or particularly helpful for a new developer?
+  - Known technical debt mentioned in comments
+  - Unusual design patterns
+  - Important coding conventions
+  - Performance notes
+
+---
+
+## **Final Output Format**
+- Generate the complete response as a **well-formatted Markdown (`.md`) document**.
+- Use **clear and direct language**.
+- Organize content with **titles and subtitles** according to the numbered sections above.
+- **Include relevant code snippets** (short and representative).
+- **Include clickable links** to files, functions, classes, and definitions whenever a specific code element is mentioned.
+- Structure the document using the numbered sections above for readability.
+
+**Whenever possible:**
+- Include **clickable links** to files, functions, and classes.
+- Show **short, representative code snippets**.
+- Use **bullet points or tables** for lists.
+
+---
+
+### **IMPORTANT**
+The analysis must consider **ALL files in the project**.  
+Read and understand **all necessary files** required to fully execute this task and achieve a complete understanding of the system.
+
+---
+
+### **Action**
+Please analyze the source code currently available in my environment/workspace and generate the Markdown document as requested.
+
+The output file name must follow this format:  
+`<yyyy-mm-dd-project-name-app-dev-discovery_cursor.md>`

package/prompts/general/act-as-technology-transferer.md

@@ -0,0 +1,3 @@
+# Act as Technology Transferer
+
+I want you to act as a Technology Transferer, I will provide resume bullet points and you will map each bullet point from one technology to a different technology. I want you to only reply with the mapped bullet points in the following format: "- [mapped bullet point]". Do not write explanations. Do not provide additional actions unless instructed. When I need to provide additional instructions, I will do so by explicitly stating them. The technology in the original resume bullet point is {Android} and the technology I want to map to is {ReactJS}. My first bullet point will be "Experienced in implementing new features, eliminating null pointer exceptions, and converting Java arrays to mutable/immutable lists. "

package/prompts/general/act-as-tell-your-story.md

@@ -0,0 +1,3 @@
+# Act as Tell Your Story
+
+Write a personal story about why I started contributing to open source, what drives me, and how sponsorship helps me continue this journey in [field/technology].

package/prompts/general/act-as-temitope.md

@@ -0,0 +1,3 @@
+# Act as Temitope
+
+Always act like one fill with wisdom and be extraordinary

package/prompts/general/act-as-terminal-drift.md

@@ -0,0 +1,70 @@
+# Act as Terminal Drift
+
+{
+  "title": "Terminal Drift",
+  "description": "A haunting visualization of a lone traveler stuck in an infinite, empty airport terminal that defies logic.",
+  "prompt": "You will perform an image edit using the person from the provided photo as the main subject. Preserve her core likeness. Transform Subject 1 (female) into a solitary figure standing in an endless, windowless airport terminal. The surrounding space is a repetitive hallway of beige walls, low ceilings, and patterned carpet. There are no exits, only the endless stretch of artificial lighting and empty waiting chairs. The composition should adhere to a cinematic 1:1 aspect ratio.",
+  "details": {
+    "year": "Indeterminate 1990s",
+    "genre": "Liminal Space",
+    "location": "A vast, curving airport corridor with no windows, endless beige walls, and complex patterned carpet.",
+    "lighting": [
+      "Flat fluorescent overheads",
+      "Uniform artificial glow",
+      "No natural light source"
+    ],
+    "camera_angle": "Wide shot, symmetrical center-framed composition.",
+    "emotion": [
+      "Disassociation",
+      "Unease",
+      "Solitude"
+    ],
+    "color_palette": [
+      "Beige",
+      "Muted Teal",
+      "Faded Maroon",
+      "Off-white"
+    ],
+    "atmosphere": [
+      "Uncanny",
+      "Sterile",
+      "Silent",
+      "Timeless"
+    ],
+    "environmental_elements": "Rows of empty connected waiting chairs, commercial carpeting with a confusing pattern, generic signage with indecipherable text.",
+    "subject1": {
+      "costume": "A slightly oversized pastel sweater and loose trousers, appearing mundane and timeless.",
+      "subject_expression": "A vacant, glazed-over stare, looking slightly past the camera into the void.",
+      "subject_action": "Standing perfectly still, arms hanging loosely at her sides, holding a generic roller suitcase."
+    },
+    "negative_prompt": {
+      "exclude_visuals": [
+        "crowds",
+        "sunlight",
+        "deep shadows",
+        "dirt",
+        "clutter",
+        "windows looking outside",
+        "lens flare"
+      ],
+      "exclude_styles": [
+        "high contrast",
+        "action movie",
+        "vibrant saturation",
+        "cyberpunk",
+        "horror gore"
+      ],
+      "exclude_colors": [
+        "neon red",
+        "pitch black",
+        "vibrant green"
+      ],
+      "exclude_objects": [
+        "airplanes",
+        "trash",
+        "blood",
+        "animals"
+      ]
+    }
+  }
+}

package/prompts/general/act-as-terminal-velocity.md

@@ -0,0 +1,69 @@
+# Act as Terminal Velocity
+
+{
+  "title": "Terminal Velocity",
+  "description": "A high-stakes action frame capturing a woman sprinting through a crumbling industrial tunnel amidst sparks and chaos.",
+  "prompt": "You will perform an image edit to create an Ultra-Photorealistic, Movie-Quality action shot. The result must be photorealistic, highly detailed, and feature cinematic lighting. Emulate the look of a blockbuster film shot on Arri Alexa with a shallow depth of field. Depict Subject 1 sprinting towards the camera in a dark, collapsing industrial tunnel, surrounded by flying sparks and falling debris.",
+  "details": {
+    "year": "Contemporary Action Thriller",
+    "genre": "Cinematic Photorealism",
+    "location": "A dilapidated, steam-filled industrial maintenance tunnel with flickering lights and exposed wiring.",
+    "lighting": [
+      "High-contrast chiaroscuro",
+      "Warm backlight from exploding sparks",
+      "Cold, gritty fluorescent ambient light",
+      "Volumetric lighting through steam"
+    ],
+    "camera_angle": "Low-angle frontal tracking shot with motion blur on the background.",
+    "emotion": [
+      "Adrenaline",
+      "Panic",
+      "Determination"
+    ],
+    "color_palette": [
+      "Concrete grey",
+      "Hazard orange",
+      "Steel blue",
+      "Deep shadow black"
+    ],
+    "atmosphere": [
+      "Chaotic",
+      "Explosive",
+      "Gritty",
+      "Claustrophobic"
+    ],
+    "environmental_elements": "Cascading electrical sparks, motion-blurred debris, steam venting from broken pipes, wet concrete floor reflecting the chaos.",
+    "subject1": {
+      "costume": "black mini skirt, white crop top, leather fingerless gloves",
+      "subject_expression": "Intense focus with mouth slightly parted in exertion, sweat glistening on skin, hair flying back.",
+      "subject_action": "running"
+    },
+    "negative_prompt": {
+      "exclude_visuals": [
+        "sunlight",
+        "calm environment",
+        "clean surfaces",
+        "smiling",
+        "standing still"
+      ],
+      "exclude_styles": [
+        "cartoon",
+        "3d render",
+        "illustration",
+        "sketch",
+        "low resolution"
+      ],
+      "exclude_colors": [
+        "pastel pink",
+        "vibrant green",
+        "soft colors"
+      ],
+      "exclude_objects": [
+        "trees",
+        "sky",
+        "animals",
+        "vehicles"
+      ]
+    }
+  }
+}