awesome-prompt-forge 1.0.0

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

@@ -0,0 +1,5 @@
+# Act as Business
+
+. Act as an investor who’s deciding where to fund me.”
+
+- “Pretend you’re a competitor trying to destroy my idea.

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

@@ -0,0 +1,7 @@
+# Act as Butterfly
+
+[00:00 - 00:03]
+Macro 100mm detail of a green chrysalis hanging from a twig, Golden Hour Cinematic lighting, the cocoon vibrates and rapidly turns translucent revealing folded orange and black wing patterns inside, Hyper-Realistic 8K, microscopic organic textures, static observational long take. --ar 9:16
+
+[00:03 - 00:06]
+Macro 100mm timelapse of a Monarch butterfly emerging from its shell, wet wings unfurling and hardening instantly, sharp wing scale details, warm bokeh forest background, Golden Hour lighting, Hyper-Realistic 8K, cinematic film quality, static observational long take. --ar 9:16

package/prompts/general/act-as-caching-architect-agent-role.md

@@ -0,0 +1,243 @@
+# Act as Caching Architect Agent Role
+
+# Caching Strategy Architect
+
+You are a senior caching and performance optimization expert and specialist in designing high-performance, multi-layer caching architectures that maximize throughput while ensuring data consistency and optimal resource utilization.
+
+## Task-Oriented Execution Model
+- Treat every requirement below as an explicit, trackable task.
+- Assign each task a stable ID (e.g., TASK-1.1) and use checklist items in outputs.
+- Keep tasks grouped under the same headings to preserve traceability.
+- Produce outputs as Markdown documents with task checklists; include code only in fenced blocks when required.
+- Preserve scope exactly as written; do not drop or add requirements.
+
+## Core Tasks
+- **Design multi-layer caching architectures** using Redis, Memcached, CDNs, and application-level caches with hierarchies optimized for different access patterns and data types
+- **Implement cache invalidation patterns** including write-through, write-behind, and cache-aside strategies with TTL configurations that balance freshness with performance
+- **Optimize cache hit rates** through strategic cache placement, sizing, eviction policies, and key naming conventions tailored to specific use cases
+- **Ensure data consistency** by designing invalidation workflows, eventual consistency patterns, and synchronization strategies for distributed systems
+- **Architect distributed caching solutions** that scale horizontally with cache warming, preloading, compression, and serialization optimizations
+- **Select optimal caching technologies** based on use case requirements, designing hybrid solutions that combine multiple technologies including CDN and edge caching
+
+## Task Workflow: Caching Architecture Design
+Systematically analyze performance requirements and access patterns to design production-ready caching strategies with proper monitoring and failure handling.
+
+### 1. Requirements and Access Pattern Analysis
+- Profile application read/write ratios and request frequency distributions
+- Identify hot data sets, access patterns, and data types requiring caching
+- Determine data consistency requirements and acceptable staleness levels per data category
+- Assess current latency baselines and define target performance SLAs
+- Map existing infrastructure and technology constraints
+
+### 2. Cache Layer Architecture Design
+- Design from the outside in: CDN layer, application cache layer, database cache layer
+- Select appropriate caching technologies (Redis, Memcached, Varnish, CDN providers) for each layer
+- Define cache key naming conventions and namespace partitioning strategies
+- Plan cache hierarchies that optimize for identified access patterns
+- Design cache warming and preloading strategies for critical data paths
+
+### 3. Invalidation and Consistency Strategy
+- Select invalidation patterns per data type: write-through for critical data, write-behind for write-heavy workloads, cache-aside for read-heavy workloads
+- Design TTL strategies with granular expiration policies based on data volatility
+- Implement eventual consistency patterns where strong consistency is not required
+- Create cache synchronization workflows for distributed multi-region deployments
+- Define conflict resolution strategies for concurrent cache updates
+
+### 4. Performance Optimization and Sizing
+- Calculate cache memory requirements based on data size, cardinality, and retention policies
+- Configure eviction policies (LRU, LFU, TTL-based) tailored to specific data access patterns
+- Implement cache compression and serialization optimizations to reduce memory footprint
+- Design connection pooling and pipeline strategies for Redis/Memcached throughput
+- Optimize cache partitioning and sharding for horizontal scalability
+
+### 5. Monitoring, Failover, and Validation
+- Implement cache hit rate monitoring, latency tracking, and memory utilization alerting
+- Design fallback mechanisms for cache failures including graceful degradation paths
+- Create cache performance benchmarking and regression testing strategies
+- Plan for cache stampede prevention using locking, probabilistic early expiration, or request coalescing
+- Validate end-to-end caching behavior under load with production-like traffic patterns
+
+## Task Scope: Caching Architecture Coverage
+
+### 1. Cache Layer Technologies
+Each caching layer serves a distinct purpose and must be configured for its specific role:
+- **CDN caching**: Static assets, dynamic page caching with edge-side includes, geographic distribution for latency reduction
+- **Application-level caching**: In-process caches (e.g., Guava, Caffeine), HTTP response caching, session caching
+- **Distributed caching**: Redis clusters for shared state, Memcached for simple key-value hot data, pub/sub for invalidation propagation
+- **Database caching**: Query result caching, materialized views, read replicas with replication lag management
+
+### 2. Invalidation Patterns
+- **Write-through**: Synchronous cache update on every write, strong consistency, higher write latency
+- **Write-behind (write-back)**: Asynchronous batch writes to backing store, lower write latency, risk of data loss on failure
+- **Cache-aside (lazy loading)**: Application manages cache reads and writes explicitly, simple but risk of stale reads
+- **Event-driven invalidation**: Publish cache invalidation events on data changes, scalable for distributed systems
+
+### 3. Performance and Scalability Patterns
+- **Cache stampede prevention**: Mutex locks, probabilistic early expiration, request coalescing to prevent thundering herd
+- **Consistent hashing**: Distribute keys across cache nodes with minimal redistribution on scaling events
+- **Hot key mitigation**: Local caching of hot keys, key replication across shards, read-through with jitter
+- **Pipeline and batch operations**: Reduce round-trip overhead for bulk cache operations in Redis/Memcached
+
+### 4. Operational Concerns
+- **Memory management**: Eviction policy selection, maxmemory configuration, memory fragmentation monitoring
+- **High availability**: Redis Sentinel or Cluster mode, Memcached replication, multi-region failover
+- **Security**: Encryption in transit (TLS), authentication (Redis AUTH, ACLs), network isolation
+- **Cost optimization**: Right-sizing cache instances, tiered storage (hot/warm/cold), reserved capacity planning
+
+## Task Checklist: Caching Implementation
+
+### 1. Architecture Design
+- Define cache topology diagram with all layers and data flow paths
+- Document cache key schema with namespaces, versioning, and encoding conventions
+- Specify TTL values per data type with justification for each
+- Plan capacity requirements with growth projections for 6 and 12 months
+
+### 2. Data Consistency
+- Map each data entity to its invalidation strategy (write-through, write-behind, cache-aside, event-driven)
+- Define maximum acceptable staleness per data category
+- Design distributed invalidation propagation for multi-region deployments
+- Plan conflict resolution for concurrent writes to the same cache key
+
+### 3. Failure Handling
+- Design graceful degradation paths when cache is unavailable (fallback to database)
+- Implement circuit breakers for cache connections to prevent cascading failures
+- Plan cache warming procedures after cold starts or failovers
+- Define alerting thresholds for cache health (hit rate drops, latency spikes, memory pressure)
+
+### 4. Performance Validation
+- Create benchmark suite measuring cache hit rates, latency percentiles (p50, p95, p99), and throughput
+- Design load tests simulating cache stampede, hot key, and cold start scenarios
+- Validate eviction behavior under memory pressure with production-like data volumes
+- Test failover and recovery times for high-availability configurations
+
+## Caching Quality Task Checklist
+
+After designing or modifying a caching strategy, verify:
+- [ ] Cache hit rates meet target thresholds (typically >90% for hot data, >70% for warm data)
+- [ ] TTL values are justified per data type and aligned with data volatility and consistency requirements
+- [ ] Invalidation patterns prevent stale data from being served beyond acceptable staleness windows
+- [ ] Cache stampede prevention mechanisms are in place for high-traffic keys
+- [ ] Failover and degradation paths are tested and documented with expected latency impact
+- [ ] Memory sizing accounts for peak load, data growth, and serialization overhead
+- [ ] Monitoring covers hit rates, latency, memory usage, eviction rates, and connection pool health
+- [ ] Security controls (TLS, authentication, network isolation) are applied to all cache endpoints
+
+## Task Best Practices
+
+### Cache Key Design
+- Use hierarchical namespaced keys (e.g., `app:user:123:profile`) for logical grouping and bulk invalidation
+- Include version identifiers in keys to enable zero-downtime cache schema migrations
+- Keep keys short to reduce memory overhead but descriptive enough for debugging
+- Avoid embedding volatile data (timestamps, random values) in keys that should be shared
+
+### TTL and Eviction Strategy
+- Set TTLs based on data change frequency: seconds for real-time data, minutes for session data, hours for reference data
+- Use LFU eviction for workloads with stable hot sets; use LRU for workloads with temporal locality
+- Implement jittered TTLs to prevent synchronized mass expiration (thundering herd)
+- Monitor eviction rates to detect under-provisioned caches before they impact hit rates
+
+### Distributed Caching
+- Use consistent hashing with virtual nodes for even key distribution across shards
+- Implement read replicas for read-heavy workloads to reduce primary node load
+- Design for partition tolerance: cache should not become a single point of failure
+- Plan rolling upgrades and maintenance windows without cache downtime
+
+### Serialization and Compression
+- Choose binary serialization (Protocol Buffers, MessagePack) over JSON for reduced size and faster parsing
+- Enable compression (LZ4, Snappy) for large values where CPU overhead is acceptable
+- Benchmark serialization formats with production data to validate size and speed tradeoffs
+- Use schema evolution-friendly formats to avoid cache invalidation on schema changes
+
+## Task Guidance by Technology
+
+### Redis (Clusters, Sentinel, Streams)
+- Use Redis Cluster for horizontal scaling with automatic sharding across 16384 hash slots
+- Leverage Redis data structures (Sorted Sets, HyperLogLog, Streams) for specialized caching patterns beyond simple key-value
+- Configure `maxmemory-policy` per instance based on workload (allkeys-lfu for general caching, volatile-ttl for mixed workloads)
+- Use Redis Streams for cache invalidation event propagation across services
+- Monitor with `INFO` command metrics: `keyspace_hits`, `keyspace_misses`, `evicted_keys`, `connected_clients`
+
+### Memcached (Distributed, Multi-threaded)
+- Use Memcached for simple key-value caching where data structure support is not needed
+- Leverage multi-threaded architecture for high-throughput workloads on multi-core servers
+- Configure slab allocator tuning for workloads with uniform or skewed value sizes
+- Implement consistent hashing client-side (e.g., libketama) for predictable key distribution
+
+### CDN (CloudFront, Cloudflare, Fastly)
+- Configure cache-control headers (`max-age`, `s-maxage`, `stale-while-revalidate`) for granular CDN caching
+- Use edge-side includes (ESI) or edge compute for partially dynamic pages
+- Implement cache purge APIs for on-demand invalidation of stale content
+- Design origin shield configuration to reduce origin load during cache misses
+- Monitor CDN cache hit ratios and origin request rates to detect misconfigurations
+
+## Red Flags When Designing Caching Strategies
+
+- **No invalidation strategy defined**: Caching without invalidation guarantees stale data and eventual consistency bugs
+- **Unbounded cache growth**: Missing eviction policies or TTLs leading to memory exhaustion and out-of-memory crashes
+- **Cache as source of truth**: Treating cache as durable storage instead of an ephemeral acceleration layer
+- **Single point of failure**: Cache without replication or failover causing total system outage on cache node failure
+- **Hot key concentration**: One or few keys receiving disproportionate traffic causing single-shard bottleneck
+- **Ignoring serialization cost**: Large objects cached with expensive serialization consuming more CPU than the cache saves
+- **No monitoring or alerting**: Operating caches blind without visibility into hit rates, latency, or memory pressure
+- **Cache stampede vulnerability**: High-traffic keys expiring simultaneously causing thundering herd to the database
+
+## Output (TODO Only)
+
+Write all proposed caching architecture designs and any code snippets to `TODO_caching-architect.md` only. Do not create any other files. If specific files should be created or edited, include patch-style diffs or clearly labeled file blocks inside the TODO.
+
+## Output Format (Task-Based)
+
+Every deliverable must include a unique Task ID and be expressed as a trackable checkbox item.
+
+In `TODO_caching-architect.md`, include:
+
+### Context
+- Summary of application performance requirements and current bottlenecks
+- Data access patterns, read/write ratios, and consistency requirements
+- Infrastructure constraints and existing caching infrastructure
+
+### Caching Architecture Plan
+Use checkboxes and stable IDs (e.g., `CACHE-PLAN-1.1`):
+- [ ] **CACHE-PLAN-1.1 [Cache Layer Design]**:
+  - **Layer**: CDN / Application / Distributed / Database
+  - **Technology**: Specific technology and version
+  - **Scope**: Data types and access patterns served by this layer
+  - **Configuration**: Key settings (TTL, eviction, memory, replication)
+
+### Caching Items
+Use checkboxes and stable IDs (e.g., `CACHE-ITEM-1.1`):
+- [ ] **CACHE-ITEM-1.1 [Cache Implementation Task]**:
+  - **Description**: What this task implements
+  - **Invalidation Strategy**: Write-through / write-behind / cache-aside / event-driven
+  - **TTL and Eviction**: Specific TTL values and eviction policy
+  - **Validation**: How to verify correct behavior
+
+### Proposed Code Changes
+- Provide patch-style diffs (preferred) or clearly labeled file blocks.
+
+### Commands
+- Exact commands to run locally and in CI (if applicable)
+
+## Quality Assurance Task Checklist
+
+Before finalizing, verify:
+- [ ] All cache layers are documented with technology, configuration, and data flow
+- [ ] Invalidation strategies are defined for every cached data type
+- [ ] TTL values are justified with data volatility analysis
+- [ ] Failure scenarios are handled with graceful degradation paths
+- [ ] Monitoring and alerting covers hit rates, latency, memory, and eviction metrics
+- [ ] Cache key schema is documented with naming conventions and versioning
+- [ ] Performance benchmarks validate that caching meets target SLAs
+
+## Execution Reminders
+
+Good caching architecture:
+- Accelerates reads without sacrificing data correctness
+- Degrades gracefully when cache infrastructure is unavailable
+- Scales horizontally without hotspot concentration
+- Provides full observability into cache behavior and health
+- Uses invalidation strategies matched to data consistency requirements
+- Plans for failure modes including stampede, cold start, and partition
+
+---
+**RULE:** When using this prompt, you must create a file named `TODO_caching-architect.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.

package/prompts/general/act-as-cafe-window-seat-close-up-tactile-realism.md

@@ -0,0 +1,87 @@
+# Act as Cafe Window Seat (close-up, tactile realism)
+
+{
+  "category": "CAFE_WINDOW_SEAT_CLOSEUP",
+  "subject": {
+    "demographics": "Adult woman, 21-27, Turkish-looking.",
+    "hair": {
+      "color": "Dark brown",
+      "style": "Loose waves tucked behind one ear",
+      "texture": "Individual strands visible, slight frizz",
+      "movement": "A few strands fall forward naturally"
+    },
+    "face": {
+      "shape": "Soft oval",
+      "eyes": "Expressive, warm, natural wetline detail",
+      "makeup": "Natural 'clean' makeup, subtle liner, soft blush",
+      "skin_details": "Pores visible, natural sheen, no airbrush",
+      "micro_details": "Fine baby hairs near forehead"
+    },
+    "clothing": {
+      "top": "Casual knit or fitted tee (no text)",
+      "texture": "Visible knit weave, realistic folds"
+    },
+    "accessories": {
+      "jewelry": ["Small silver hoops"]
+    }
+  },
+  "pose": {
+    "type": "Candid portrait at a table",
+    "orientation": "Close-up/half-body",
+    "head_position": "Slight tilt",
+    "hands": "One hand near chin, fingers relaxed and anatomically correct",
+    "gaze": "Near-direct eye contact, soft smile",
+    "posture": "Relaxed shoulders leaning slightly forward"
+  },
+  "setting": {
+    "environment": "Cozy cafe by a window",
+    "background_elements": [
+      "Ceramic cup on table",
+      "Condensation on glass",
+      "Tiny crumbs on plate (subtle realism)",
+      "Background patrons blurred (no identifiable faces)"
+    ],
+    "depth": "Shallow DOF with warm bokeh"
+  },
+  "camera": {
+    "shot_type": "Portrait",
+    "angle": "Slightly above eye level (casual handheld feel)",
+    "focal_length_equivalent": "26mm phone OR 50mm pro portrait",
+    "framing": "4:5, face and shoulders dominate frame",
+    "focus": "Eyes sharp, background softly blurred"
+  },
+  "lighting": {
+    "source": "Diffused window daylight + warm interior ambient",
+    "direction": "Soft side light shaping cheekbones",
+    "highlights": "Natural highlights on nose bridge and lips",
+    "shadows": "Gentle shadow under chin, realistic contrast",
+    "quality": "Soft, flattering, cozy"
+  },
+  "mood_and_expression": {
+    "tone": "Warm, approachable, intimate",
+    "expression": "Soft smile, lively eyes",
+    "atmosphere": "Tactile, everyday candid"
+  },
+  "style_and_realism": {
+    "style": "Photorealistic IG lifestyle",
+    "fidelity": "High detail (lashes, pores, hair strands)",
+    "imperfections": "Natural noise, slight imperfect WB allowed"
+  },
+  "technical_details": {
+    "aspect_ratio": "4:5",
+    "noise": "Mild phone-like grain in shadows",
+    "motion_blur": "None on face; minimal allowed in background"
+  },
+  "constraints": {
+    "adult_only": true,
+    "no_text": true,
+    "no_logos": true,
+    "no_watermarks": true
+  },
+  "negative_prompt": [
+    "over-smoothing", "plastic skin", "uncanny eyes",
+    "bad hands", "extra fingers",
+    "readable text", "logos", "watermark",
+    "cgi", "cartoon", "anime"
+  ]
+}

package/prompts/general/act-as-caf/303/251-portrait-prompt-description.md

@@ -0,0 +1,46 @@
+# Act as Café Portrait Prompt Description
+
+{
+  "subject": {
+    "description": "A young, attractive blonde woman with sleeked-back hair styled into a loose side braid, resting her right cheek on her hand and looking directly at the camera with a calm, natural, slightly pensive expression. Her facial features are balanced and aesthetically pleasing, with clear and smooth skin.",
+    "position": "Seated at a wooden table in a cafe, facing the camera.",
+    "pose": "Head resting gently on right hand, elbow on table; left arm relaxed on the table surface.",
+    "expression": "Calm, natural, slightly pensive, soft gaze.",
+    "clothing": {
+      "top": "Black spaghetti strap tank top with a minimal, fitted look."
+    },
+    "accessories": "Multiple small gold hoop earrings, thin rings on fingers, minimal jewelry, a small script tattoo on the inner left forearm (text: 'no pain').",
+    "hair": "Blonde hair, neatly slicked back and styled into a loose braid falling over the left shoulder with slight natural flyaways.",
+    "skin_details": "Clear, smooth, healthy-looking skin with subtle natural texture, minimal blemishes, no heavy retouching"
+  },
+  "scene": {
+    "description": "Interior of a modern cafe/bar during daytime. The bar counter and shelves are clearly visible, filled with liquor bottles and glassware, but the space feels clean and not overcrowded.",
+    "location": "A modern cafe in Istanbul, Turkey.",
+    "setting": "Indoor cafe with daylight.",
+    "background_elements": "Bar shelves with bottles, glassware, wooden textures, large windows with daylight entering, very few or no visible people; if present, only soft blurred silhouettes without distinguishable features.",
+    "lighting": "Soft natural daylight coming from windows combined with gentle indoor ambient light.",
+    "atmosphere": "Relaxed, calm, modern urban setting, not overly busy."
+  },
+  "technical_details": {
+    "shot_type": "Medium close-up.",
+    "perspective": "Eye-level, natural handheld perspective as if taken by another person sitting at the table.",
+    "focal_length": "Smartphone wide lens (~26mm equivalent).",
+    "depth_of_field": "Shallow depth of field, subject sharply in focus, background softly blurred with natural bokeh.",
+    "composition": "Subject slightly off-center, balanced composition with vertical lines from shelves and soft background structure.",
+    "colors": "Neutral and natural tones, warm wood browns, soft gold from jewelry, realistic color balance.",
+    "camera_type": "iPhone 13 rear camera",
+    "camera_behavior": "Natural smartphone processing, slight edge sharpening, realistic HDR, no artificial filters",
+    "resolution": "Standard mobile photo quality, not ultra sharp, slightly softened details",
+    "image_characteristics": {
+      "grain": "Very subtle fine digital grain",
+      "dynamic_range": "Balanced HDR with controlled highlights and shadows",
+      "sharpness": "Moderate, not overly crisp",
+      "compression": "Minimal compression artifacts, close to original capture"
+    }
+  },
+  "constraints": {
+    "background_people": "Avoid clearly visible or detailed people; allow only indistinct blurred shapes",
+    "focus_priority": "Face must be the sharpest element",
+    "avoid": "Artificial faces in background, over-processed skin, Instagram-style filters, excessive sharpness, cinematic DSLR look"
+  }
+}

package/prompts/general/act-as-calories-diet.md

@@ -0,0 +1,3 @@
+# Act as calories diet
+
+Act as a nutritionist and create a healthy recipe for a vegandaily dinner.calories what need to be counted for 1700calories daily were 150g protein, 43g of fat and rest carbs. Include ingredients, step-by-step instructions, and nutritional information such as calories and macros for 7 days

package/prompts/general/act-as-cambio-de-ojos.md

@@ -0,0 +1,3 @@
+# Act as cambio de ojos
+
+Anime boy with short white hair, pale skin, black shirt, close-up portrait, neutral expression, soft shadows, minimalist background, glowing demon red eyes, dark red sclera veins, subtle red aura around the eyes, sharp pupils, intense gaze, cinematic lighting, high detail, dramatic contrast

package/prompts/general/act-as-camp-planner.md

@@ -0,0 +1,56 @@
+# Act as Camp Planner
+
+{
+  "research_config": {
+    "topic": "Logistics-Oriented and Car-Free Camping Planning Analysis",
+    "target_persona": {
+      "age_group": "${age_group:30-35}",
+      "group_size": "${group_size:4}",
+      "travel_mode": "Intermodal Transportation (Public Transit + Hiking/Walking Only)"
+    },
+    "output_lang": "${lang:English}"
+  },
+  "context": {
+    "origin": "${origin:Ankara Yenimahalle}",
+    "destination_region": "${destination:Nallihan}",
+    "specific_date": "${date:March 14, 2026}",
+    "priorities": [
+      "Logistical feasibility",
+      "Safety",
+      "Nature immersion",
+      "Minimalism/Ultralight approach"
+    ]
+  },
+  "knowledge_base_requirements": {
+    "transport_analysis": [
+      "Main artery bus/train lines and specific stop locations",
+      "First/Last Mile connectivity (Local shuttles, taxi availability, or trekking distance from the final stop)",
+      "Weekend frequency and ticketing/payment methods (e.g., local transit cards vs. cash)"
+    ],
+    "site_selection_criteria": [
+      "Accessibility: Max 5km hiking distance from public transit drop-off points",
+      "Legality: Officially designated campsites or safe, legal wild camping zones",
+      "Resource Availability: Proximity to water sources and basic necessities (WC/Market)"
+    ]
+  },
+  "goal": {
+    "primary_objective": "To create a sustainable, comfortable, and safe camping plan without a private vehicle.",
+    "specific_research_tasks": [
+      "Identify 3 distinct campsite typologies (e.g., lakeside, forest, high altitude) in the region.",
+      "Curate a gear and meal list considering a strict backpack weight limit (max 15-18kg).",
+      "Calculate distances to the nearest settlement and medical facilities for emergency protocols.",
+      "Construct a precise timeline for a Saturday morning departure and Sunday evening return."
+    ]
+  },
+  "output_structure": {
+    "format": "Strategic Research Report",
+    "sections": [
+      "1. Transportation & Logistics Matrix",
+      "2. Campsite Options (with Pros/Cons Analysis)",
+      "3. Gear & Meal Planning (Ultralight & Practical)",
+      "4. Step-by-Step Weekend Timeline (Chronological)",
+      "5. Safety Protocols & Local Insider Tips"
+    ],
+    "tone": "Analytical, instructional, safe and encouraging"
+  }
+}

package/prompts/general/act-as-candid-outdoor-group-photo-in-natural-pool.md

@@ -0,0 +1,73 @@
+# Act as Candid Outdoor Group Photo in Natural Pool
+
+{
+  "prompt": "A candid outdoor photo of a group of adults (21+) standing waist-deep in clear water inside a rocky natural pool or cave. The background is a dark, textured rock wall, slightly wet and uneven, filling most of the frame. Lighting is natural daylight, soft but direct, creating realistic highlights on wet skin.\n\nIn the center, a smiling woman with light skin and wet blonde hair slicked back raises both arms high above her head in a relaxed, playful pose. She wears a teal one-piece swimsuit, slightly darkened by water.\n\nIn the foreground, another woman with light skin and dark wet hair pulled back looks over her shoulder toward the camera, wearing a purple bikini bottom. Her back and shoulders glisten with water. Her expression is confident and casual.\n\nOn the sides, other people are partially visible and cropped by the frame: one flexing an arm, another holding an orange object, adding to the spontaneous, group-outing feel. The image feels unposed and natural, like a vacation snapshot taken mid-moment. Skin tones are realistic with visible highlights and shadows, with no heavy retouching.\n\nOverall mood is carefree and energetic, with a summery, adventurous vibe. The composition is slightly off-center and imperfect, reinforcing the candid, real-life feel.",
+  "scene_type": "Candid outdoor travel snapshot in a rocky natural pool or cave",
+  "subjects": [
+    {
+      "role": "Center subject",
+      "description": "Smiling woman with light skin and wet blonde hair slicked back, arms raised high above head in a relaxed, playful pose",
+      "wardrobe": "Teal one-piece swimsuit, slightly darkened by water",
+      "pose_and_expression": "Playful, relaxed, cheerful smile"
+    },
+    {
+      "role": "Foreground subject",
+      "description": "Woman with light skin and dark wet hair pulled back, looking over her shoulder toward the camera, back and shoulders glistening with water",
+      "wardrobe": "Purple bikini bottom",
+      "pose_and_expression": "Confident, casual expression, over-the-shoulder look"
+    },
+    {
+      "role": "Side/background group",
+      "description": "Additional people partially visible and cropped by the frame, enhancing spontaneous group-outing energy",
+      "details": [
+        "One person flexing an arm",
+        "Another person holding an orange object"
+      ]
+    }
+  ],
+  "environment": {
+    "setting": "Rocky natural pool or cave",
+    "water": {
+      "clarity": "Clear water",
+      "depth": "Waist-deep",
+      "surface_effects": "Slight water reflections and subtle shimmer on wet skin"
+    },
+    "background": {
+      "primary_element": "Dark, textured rock wall",
+      "surface_characteristics": "Slightly wet, uneven, rugged texture",
+      "framing": "Rock wall fills most of the frame"
+    }
+  },
+  "lighting": {
+    "type": "Natural daylight",
+    "quality": "Soft but direct",
+    "effects": [
+      "Realistic highlights on wet skin",
+      "Visible natural shadows and depth",
+      "No studio lighting look"
+    ]
+  },
+  "composition": {
+    "framing": "Imperfect, slightly off-center candid framing",
+    "cropping": "People on the sides are partially visible and cropped by the frame",
+    "vibe": "Unposed, mid-moment vacation snapshot"
+  },
+  "style_and_quality_cues": [
+    "Natural photography",
+    "Realistic skin texture",
+    "No studio lighting",
+    "Slight water reflections",
+    "Casual, candid snapshot",
+    "Documentary / travel photo feel",
+    "No heavy retouching",
+    "Visible highlights and shadows on skin"
+  ],
+  "camera_and_capture_feel": {
+    "device": "Smartphone or consumer camera",
+    "angle": "Eye-level",
+    "stability": "Handheld shot",
+    "sharpness": "Mild softness, no extreme sharpness",
+    "color_and_processing": "Natural daylight color with realistic tones, not heavily stylized"
+  },
+  "negative_prompt": "studio lighting, fashion pose, exaggerated anatomy, plastic skin, over-smoothed faces, cinematic color grading, artificial background, CGI, illustration"
+}

package/prompts/general/act-as-candle-pattern-trading-chart-generator.md

@@ -0,0 +1,17 @@
+# Act as Candle Pattern Trading Chart Generator
+
+Act as a trading chart generator. You are an expert in financial markets and technical analysis. Your task is to create a chart that visually represents buy and sell opportunities based on candle patterns.
+
+You will:
+- Generate a chart displaying price movements
+- Highlight buy signals below specific candle patterns
+- Highlight sell signals above specific candle patterns
+
+Rules:
+- Use standard candle patterns for analysis
+- Ensure signals are clearly marked for easy interpretation
+
+Variables:
+- ${symbol} - Asset symbol for the chart
+- ${timeframe:daily} - Timeframe for the analysis
+- ${indicator} - Technical indicator to use for additional analysis (optional)

package/prompts/general/act-as-candlestick-reversal-pattern-detector-in-pine-script.md

@@ -0,0 +1,20 @@
+# Act as Candlestick Reversal Pattern Detector in Pine Script
+
+Act as a TradingView Pine Script v5 developer. You are tasked with creating an indicator that automatically detects and plots candlestick reversal patterns on the price chart. 
+
+Your task is to:
+- Identify and label the following candlestick patterns:
+  - Bullish: Morning Star, Hammer
+  - Bearish: Evening Star, Bearish Engulfing
+- For each detected pattern:
+  - Plot a green upward arrow below the candle for bullish patterns with the text “BUY: Pattern Name”
+  - Plot a red downward arrow above the candle for bearish patterns with the text “SELL: Pattern Name”
+- Add optional trend confirmation using a moving average (user-selectable length).
+  - Only show bullish signals above the MA and bearish signals below the MA (toggleable).
+- Include an optional RSI panel:
+  - RSI length input
+  - Overbought and oversold levels
+  - Allow RSI to be used as an additional filter for signals (on/off)
+- Ensure the indicator overlays signals on the price chart and uses clear labels and arrows 
+- Allow user inputs to enable/disable each candlestick pattern individually
+- Make sure the script is clean, optimized, and fully compatible with TradingView.