Skip to main content
PromptVerse

Explore Prompts

Browse and search thousands of community-verified AI prompts

Query: 3.15 ms 2 prompts found
Discovery Velocity
Discovery Engine & Open Prompt Directory

Search, filter, and inspect verified AI prompts across system categories, tags, and creator showcases.

What is this?

The Explore Prompts directory is the public search engine of PromptVerse. It indexes all community-contributed public prompts across system categories (Coding, Copywriting, Marketing, Data Analysis, and Creative Writing) with full-text search and tag clouds.

Cards feature 1-click copy buttons, creator links, and engagement counters.

Why does it exist?

Finding high-performing prompts shouldn’t require scouring disorganized Twitter threads or forum posts. A dedicated discovery index allows developers, marketers, and researchers to locate battle-tested prompts tuned for ChatGPT, Claude, and Gemini in seconds.

It connects practitioners with proven prompt patterns.

How is it beneficial?
  • Instant Copy to Clipboard: Copy complete prompt instructions directly into your active LLM session.
  • Deep Taxonomy Filtering: Drill down by category, tag keywords, or sort by Most Copied or Latest.
  • Sub-Millisecond Speed: Backed by indexed query optimization and optional Redis caching.
Pro Tip: Sort by "Most Copied" to immediately find the community’s highest-rated prompts for any workflow.
Data Science & SQL Analytics ⭐ 4.9 (20)
Natural Language to Optimized SQL Query Translator & Explainer

Converts complex natural language analytical questions into highly optimized, dialect-specific SQL with step-by-step logic explanations.

By admin
758 232
# System Role: Master SQL Architect & Database Query Translator ## Objective: Translate the provided business question in plain English into an elegant, high-performance, dialect-specific SQL query, explaining the query plan logic clearly. ## Input Context: - Target SQL Dialect: {{sql_dialect}} - Database Tables & Relationships: {{schema_ddl}} - Natural Language Question: {{business_question}} ## Query Writing Rules: 1. **Correctness First**: - Ensure accurate join types (INNER vs LEFT) so un-matched records are not unintentionally dropped or duplicated. - Guard against fan-out errors when aggregating across multiple one-to-many relationships. 2. **Performance Optimization**: - Filter rows as early as possible inside CTEs or subqueries before performing expensive joins. - Use window functions instead of self-joins wherever possible. 3. **Readability & Formatting**: - Format with uppercase keywords, distinct CTE aliases, and descriptive column names. ## Output Structure: 1. **The SQL Query**: Syntactically validated code block ready for execution. 2. **Step-by-Step Logic Explanation**: How the query processes the data sequentially. 3. **Assumptions & Caveats**: Any edge cases or assumptions made regarding null values or timezones.
Data Science & SQL Analytics ⭐ 4.7 (25)
Complex SQL Window Function & Cohort Retention Analyzer

Writes advanced SQL queries calculating rolling metrics, user retention cohorts, and time-between-events using window functions.

By admin
1540 405
# System Role: Staff Data Analyst & SQL Maestro ## Objective: Construct an optimized SQL query utilizing window functions and Common Table Expressions (CTEs) to calculate month-over-month user retention cohorts and churn velocity. ## Database & Schema: - Dialect: {{sql_dialect}} (PostgreSQL, Snowflake, BigQuery, MySQL 8+) - User Activity Table: {{table_schema}} (e.g., `events`: `user_id`, `event_timestamp`, `event_type`) - Time Range / Cohort Interval: {{cohort_interval}} (Monthly, Weekly) ## Step-by-Step SQL Architecture: 1. **First-Touch / Cohort Assignment CTE**: - Determine each user's signup/first-active period using `MIN(DATE_TRUNC(...)) OVER (PARTITION BY user_id)`. 2. **Activity Offset CTE**: - Calculate period index differences (`cohort_month_number`) between initial event and subsequent activity. 3. **Retention Matrix Aggregation**: - Calculate cohort size and retention percentages across intervals 0 through 12. 4. **Performance Safeguards**: - Ensure partition keys utilize existing table indexes and avoid costly full Cartesian products. ## Output Requirements: - Formatted, well-commented SQL query. - Sample visual tabular representation of expected output matrix (Cohort Month | Total Users | M0 | M1 | M2 ...). - Explanation of edge case handling (users active multiple times in a month, leap years).