The Free Social Platform forAI Prompts
Prompts are the foundation of all generative AI. Share, discover, and collect them from the community. Free and open source — self-host with complete privacy.
or explore by industry
Click to explore
Sponsored by
Support CommunityLoved by AI Pioneers
Greg Brockman
President & Co-Founder at OpenAI · Dec 12, 2022
“Love the community explorations of ChatGPT, from capabilities (https://github.com/f/prompts.chat) to limitations (...). No substitute for the collective power of the internet when it comes to plumbing the uncharted depths of a new deep learning model.”
Wojciech Zaremba
Co-Founder at OpenAI · Dec 10, 2022
“I love it! https://github.com/f/prompts.chat”
Clement Delangue
CEO at Hugging Face · Sep 3, 2024
“Keep up the great work!”
Thomas Dohmke
Former CEO at GitHub · Feb 5, 2025
“You can now pass prompts to Copilot Chat via URL. This means OSS maintainers can embed buttons in READMEs, with pre-defined prompts that are useful to their projects. It also means you can bookmark useful prompts and save them for reuse → less context-switching ✨ Bonus: @fkadev added it already to prompts.chat 🚀”
Featured Prompts

Create an ultra-realistic cinematic portrait image using specific visual elements like dramatic lighting, sharp focus, and high resolution. Customize aspects such as gender, hair style, and clothing to achieve a unique and detailed composition.
Ultra realistic cinematic portrait of a referance photo, centered composition, head and shoulders framing, direct eye contact, serious neutral expression, short slightly messy dark hair, light stubble beard, wearing a black shirt and black textured jacket with zipper details, dramatic red rim lighting from both sides, soft frontal key light, deep black background, high contrast, low-key lighting, sharp focus, 85mm lens, shallow depth of field, studio photography, ultra detailed skin texture, 8k resolution
[00:00 - 00:03] Hyper-realistic 8K 3D human heart anatomy, beating slowly, detailed muscle texture with coronary arteries, Golden Hour Cinematic lighting, fisheye distortion effect, 35mm storytelling lens, professional medical infographic style, blurred futuristic laboratory background. --ar 9:16 [00:03 - 00:06] Extreme close-up of heart anatomy, dramatic golden hour lighting, 35mm fisheye lens distortion, hyper-realistic biological textures, cinematic 8K, 9:16 vertical composition. --ar 9:16
[00:00 - 00:02] [Extreme close-up] of Komar's face, an 18-year-old Indonesian teenage boy, short hair, wearing black-framed glasses with minus lenses reflecting the light of a desk lamp. A very meticulous and focused expression. Warm lighting from a desk lamp, cinematic_bokeh, volumetric_lighting, [8k resolution], [ultra-realistic skin texture]. [00:02 - 00:04] macro_shot of the hands of Komar, an 18-year-old Indonesian teenage boy, wearing a dark blue short-sleeved t-shirt, assembling a miniature Indonesian train locomotive using tweezers. Precise plastic miniature texture details, dramatic side lighting, [50mm] lens, [f/2.8], professional_studio_lighting, intricate mechanical details. [00:04 - 00:06] medium_shot Komar, an 18-year-old Indonesian man with short hair, wearing black-framed glasses with minus lenses, wearing a plain navy blue short-sleeved t-shirt with a regular fit. Sitting at a wooden workbench filled with model kit equipment. Warm atmosphere, dust_motes visible in light beams, cinematic_color_grading, soft_shadows.
A structured expert-role prompt designed to make an AI perform a comprehensive, clinically reasoned evaluation of a medical laboratory report. It enforces specialist-level analysis, standardized output formatting, risk prioritization, preventive health focus, and actionable recommendations, while communicating findings in clear patient-friendly language.
You are a senior physician with 20+ years of clinical experience in preventive medicine and laboratory interpretation. Analyze the attached health report comprehensively and clinically. Provide output in the following structured format: 1. Overall Health Summary 2. Parameters Within Optimal Range (explain why good) 3. Parameters Outside Normal Range - Normal range - Patient value - Clinical interpretation - Risk level (low / moderate / high) 4. Early Warning Patterns or System-Level Insights 5. Action Plan - Lifestyle correction - Nutrition - Monitoring frequency - When medical consultation is required 6. Symptoms Patient Should Monitor 7. Long-Term Risk if Unchanged Use clear patient-friendly language while maintaining clinical accuracy. Prioritize preventive health insights.
Cinematic vertical smartphone video, portrait orientation, centered composition with strong top and bottom headroom. Elegant Piña Colada cocktail inside a coconut shell glass placed in the middle of a tall frame. Clean marble bar surface only in lower third, soft tropical daylight, palm leaf shadows moving gently across background. Slow creamy Piña Colada pour with visible thick texture and condensation. Camera performs slow vertical push-in macro movement, shallow depth of field, luxury beverage commercial style, minimal aesthetic, portrait framing, vertical composition, tall frame, 9:16 aspect ratio, no text.

Create a dramatic digital painting that captures the solitary moment of a figure in a snowy landscape, featuring a high-contrast scene with a house engulfed in flames. This prompt guides you to depict a mysterious and melancholic atmosphere with cinematic influences, using deep blues and vibrant reds against the stark white snow.
1{2 "colors": {3 "color_temperature": "cool",...+76 more lines

Create a minimalist vector illustration of a man fishing on the back of a giant whale, emphasizing themes of scale and obliviousness. This prompt explores the use of negative space and symbolism, ideal for conceptual art projects and training models in visual storytelling.
1{2 "colors": {3 "color_temperature": "cool",...+75 more lines
A structural blueprint generator for new podcasts. It designs a unique episode format, segments, and a comprehensive audio branding strategy (intro/outro, stingers, sound beds) tailored to your specific niche.
I want you to act as a Senior Podcast Producer and Audio Branding Expert. I will provide you with a target niche, the host's background, and the desired vibe of the show. Your goal is to construct a unique, repeatable podcast format and a distinct sonic identity. For this request, you must provide: 1) **The Episode Blueprint:** A strict timeline breakdown (e.g., 00:00-02:00 Cold Open, 02:00-03:30 Intro/Theme, etc.) for a standard episode. 2) **Signature Segments:** 2 unique, recurring mini-segments (e.g., a rapid-fire question round or a specific interactive game) that differentiate this show from competitors. 3) **Audio Branding Strategy:** Specific directives for the sound design. Detail the instrumentation and tempo for the main theme music, the style of transition stingers, and the ambient beds to be used during deep conversations. 4) **Studio & Gear Philosophy:** 1 essential piece of advice regarding the acoustic environment or signal chain to capture the exact 'vibe' requested. 5) **Title & Hook:** 3 creative podcast name ideas and a compelling 2-sentence pitch for Apple Podcasts/Spotify. Do not break character. Be pragmatic, highly structured, and focus on professional production standards. Target Niche: Target_Niche Host Background: Host_Background Desired Vibe: Desired_Vibe
A strategic blueprint generator for solo founders and "vibecoders". It turns a raw app idea into a concrete MVP plan, detailing the core user loop, AI integration strategy, tech stack, and the exact starting prompt for AI coding assistants.
I want you to act as a Micro-SaaS 'Vibecoder' Architect and Senior Product Manager. I will provide you with a problem I want to solve, my target user, and my preferred AI coding environment. Your goal is to map out a clear, actionable blueprint for building an AI-powered MVP. For this request, you must provide: 1) **The Core Loop:** A step-by-step breakdown of the single most important user journey (The 'Aha' Moment). 2) **AI Integration Strategy:** Specifically how LLMs or AI APIs should be utilized (e.g., prompt chaining, RAG, direct API calls) to solve the core problem efficiently. 3) **The 'Vibecoder' Tech Stack:** Recommend the fastest path to deployment (frontend, backend, database, and hosting) suited for rapid AI-assisted coding. 4) **MVP Scope Reduction:** Identify 3 features that founders usually build first but must be EXCLUDED from this MVP to launch faster. 5) **The Kickoff Prompt:** Write the exact, highly detailed prompt I should paste into my AI coding assistant to generate the foundational boilerplate for this app. Do not break character. Be highly technical but ruthlessly focused on shipping fast. Problem to Solve: Problem_to_Solve Target User: Target_User Preferred AI Coding Tool: Cursor, v0, Lovable, Bolt.new, etc.
Today's Most Upvoted

This prompt provides a detailed photorealistic description for generating a selfie portrait of a young female subject. It includes specifics on demographics, facial features, body proportions, clothing, pose, setting, camera details, lighting, mood, and style. The description is intended for use in creating high-fidelity, realistic images with a social media aesthetic.
1{2 "subject": {3 "demographics": "Young female, approx 20-24 years old, Caucasian.",...+85 more lines

Create an ultra-realistic nighttime scene of a cozy bedroom in Ankara, capturing intimate details and ambient lighting for a genuine snapshot feel. The prompt focuses on the candid and imperfect framing of a 27-year-old woman in a typical Turkish setting, emphasizing natural textures and colors.
Ultra-realistic amateur night photo, vertical iPhone framing, handheld and slightly shaky, showing a cozy small bedroom in Ankara just before sleep, perfect for an “iyi geceler” tweet. The camera is a bit above and behind a 27-year-old Turkish-looking woman with a soft, slightly chubby figure and blonde hair tied in a loose messy bun. She is sitting sideways on an unmade bed with light-colored sheets and a simple patterned blanket, wearing an oversized white t-shirt that covers her thighs like a night shirt, casual and non-sexual, bare legs loosely folded. The main light source is the soft bluish glow of her phone screen in her hands, illuminating her face and hands while the rest of the room is in warm dim light from a tiny bedside lamp. On the phone you can’t clearly read text, but it is obvious she is about to send a tweet; the Twitter-style interface is just barely recognizable as blue-and-white shapes, out of focus and not legible. The background shows a typical Turkish apartment bedroom: a small wooden nightstand with a half-finished glass of water, a pair of simple wired earphones, and a cheap alarm clock glowing in a faint green. On the wall is a cheap hanging kilim or small decorative rug. Through a slightly open window you can see blurred orange-yellow city lights of Ankara at night, with silhouettes of old apartment blocks and faint outlines of balconies. In the distance, a small out-of-focus Migros sign glows on a building, and a faint neon Turkcell logo is visible on a shop far below, adding subtle Turkish context without dominating the scene. Vertical composition with the woman slightly off-center, part of the bed and nightstand cropped at the edges, emphasizing the candid, imperfect framing. There is very slight motion blur on one of her hands as if she just tapped the screen, and fine digital noise in the dark corners of the room, giving the true smartphone low-light snapshot feeling. Colors are unedited and natural: warm yellow from the lamp contrasting with cool blue from the phone. The woman’s skin shows natural texture, pores, and small imperfections, making her look like a real person, not a model. The whole mise-en-scène should feel like a quiet, intimate “iyi geceler” moment in a real Ankara bedroom captured on a regular phone.

Create an ultra-realistic cinematic portrait image using specific visual elements like dramatic lighting, sharp focus, and high resolution. Customize aspects such as gender, hair style, and clothing to achieve a unique and detailed composition.
Ultra realistic cinematic portrait of a referance photo, centered composition, head and shoulders framing, direct eye contact, serious neutral expression, short slightly messy dark hair, light stubble beard, wearing a black shirt and black textured jacket with zipper details, dramatic red rim lighting from both sides, soft frontal key light, deep black background, high contrast, low-key lighting, sharp focus, 85mm lens, shallow depth of field, studio photography, ultra detailed skin texture, 8k resolution
A structured and guided way to learn new subjects based on your current existing knowledge.
subject= current_level= time_available= learning_style= goal= Step 1: Knowledge Assessment 1. Break down subject into core components 2. Evaluate complexity levels of each component 3. Map prerequisites and dependencies 4. Identify foundational concepts Output detailed skill tree and learning hierarchy ~ Step 2: Learning Path Design 1. Create progression milestones based on current_level 2. Structure topics in optimal learning sequence 3. Estimate time requirements per topic 4. Align with time_available constraints Output structured learning roadmap with timeframes ~ Step 3: Resource Curation 1. Identify learning materials matching learning_style: - Video courses - Books/articles - Interactive exercises - Practice projects 2. Rank resources by effectiveness 3. Create resource playlist Output comprehensive resource list with priority order ~ Step 4: Practice Framework 1. Design exercises for each topic 2. Create real-world application scenarios 3. Develop progress checkpoints 4. Structure review intervals Output practice plan with spaced repetition schedule ~ Step 5: Progress Tracking System 1. Define measurable progress indicators 2. Create assessment criteria 3. Design feedback loops 4. Establish milestone completion metrics Output progress tracking template and benchmarks ~ Step 6: Study Schedule Generation 1. Break down learning into daily/weekly tasks 2. Incorporate rest and review periods 3. Add checkpoint assessments 4. Balance theory and practice Output detailed study schedule aligned with time_available
Find 80%+ matching [job sector] roles posted within the specified window (default: last 14 days)
# Customizable Job Scanner - AI Optimized
**Author:** Scott M
**Version:** 2.0
**Goal:** Surface 80%+ matching [job sector] roles posted within the specified window (default: last 14 days), using real-time web searches across major job boards and company career sites.
**Audience:** Job boards (LinkedIn, Indeed, etc.), company career pages
**Supported AI:** Claude, ChatGPT, Perplexity, Grok, etc.
## Changelog
- **Version 1.0 (Initial Release):**
Converted original cybersecurity-specific prompt to a generic template. Added placeholders for sector, skills, companies, etc. Removed Dropbox file fetch.
- **Version 1.1:**
Added "How to Update and Customize Effectively" section with tips for maintenance. Introduced Changelog section for tracking changes. Added Version field in header.
- **Version 1.2:**
Moved Changelog and How to Update sections to top for easier visibility/maintenance. Minor header cleanup.
- **Version 1.3:**
Added "Job Types" subsection to filter full-time/part-time/internship. Expanded "Location" to include onsite/hybrid/remote options, home location, radius, and relocation preferences. Updated tips to cover these new customizations.
- **Version 1.4:**
Added "Posting Window" parameter for flexible search recency (e.g., last 7/14/30 days). Updated goal header and tips to reference it.
- **Version 1.5:**
Added "Posted Date" column to the output table for better recency visibility. Updated Output format and tips accordingly.
- **Version 1.6:**
Added optional "Minimum Salary Threshold" filter to exclude lower-paid roles where salary is listed. Updated Output format notes and tips for salary handling.
- **Version 1.7:**
Renamed prompt title to "Customizable Job Scanner" for broader/generic appeal. No other functional changes.
- **Version 1.8:**
Added optional "Resume Auto-Extract Mode" at top for lazy/fast setup. AI extracts skills/experience from provided resume text. Updated tips on usage.
- **Version 1.9 (Previous stable release):**
- Added optional "If no matches, suggest adjustments" instruction at end.
- Added "Common Tags in Sector" fallback list for thin extraction.
- Made output table optionally sortable by Posted Date descending.
- In Resume Auto-Extract Mode: AI must report extracted key facts and any added tags before showing results.
- **Version 2.0 (Current revised version):**
- Added explicit real-time search instruction ("Act as a real-time job aggregator... use current web browsing/search capabilities") to prevent hallucinated or outdated job listings.
- Enhanced scoring system: added bonuses for verbatim/near-exact ATS keyword matches, quantifiable alignment, and very recent postings (<7 days).
- Expanded "Additional sources" to include Google Jobs, FlexJobs (remote), BuiltIn, AngelList, We Work Remotely, Remote.co.
- Improved output table: added columns for Location Type, ATS Keyword Overlap, and brief "Why Strong Match?" rationale (for 85%+ matches).
- Top Matches (90%+) section now uses bolded/highlighted rows for better visual distinction.
- Expanded no-matches suggestions with more actionable escalations (e.g., include adjacent titles, temporarily allow contract roles, remove salary filter).
- Minor wording cleanups for clarity, flow, and consistency across sections.
- Strengthened Top Instruction block to enforce live searches and proper sequencing (extract first → then search).
## Top Instruction (Place this at the very beginning when you run the prompt)
"Act as my dedicated real-time job scout with current web browsing and search access.
First: [If using Resume Auto-Extract Mode: extract and summarize my skills, experience, achievements, and technical stack from the pasted resume text. Report the extraction summary including confidence levels (Expert/Strong/Inferred) before showing any job results.]
Then: Perform live, current searches only (no internal/training data or outdated knowledge). Pull the freshest postings matching my parameters below. Use the scoring system strictly. Prioritize ATS keyword alignment, recency, and my custom tags/skills."
## Resume Auto-Extract Mode (Optional - For Lazy/Fast Setup)
If skipping manual Skills Reference:
- Paste your full resume text here:
[PASTE RESUME TEXT HERE]
- Keep the Top Instruction above with the extraction part enabled.
The AI will output something like:
"Resume Extraction Summary:
- Experience: 12+ years in cybersecurity / DevOps / [sector]
- Key achievements: Led X migration (Y endpoints), reduced Z by A%
- Top skills (with confidence): CrowdStrike (Expert), Terraform (Strong), Python (Expert), ...
- Suggested tags added: SIEM, KQL, Kubernetes, CI/CD
Proceeding with search using these."
## How to Update and Customize Effectively
- Use Resume Auto-Extract when short on time; verify the summary before trusting results.
- Refresh Skills Reference / tags every 3–6 months or after major projects.
- Use exact phrases from job postings / your resume in tags for ATS alignment.
- Test across AIs; if too few results → lower threshold, extend window, add adjacent titles/tags.
- For new sectors: research top keywords via LinkedIn/Indeed/Google Jobs first.
## Skills Reference
(Replace manually or let AI auto-populate from resume)
**Professional Overview**
- [Years of experience, key roles/companies]
- [Major projects/achievements with numbers]
**Top Skills**
- [Skill] (Expert/Strong): [tools/technologies]
- ...
**Technical Stack**
- [Category]: [tools/examples]
- ...
## Common Tags in Sector (Fallback)
If extraction is thin, add relevant ones here (1 point unless core). Examples:
- Cybersecurity: Splunk, SIEM, KQL, Sentinel, CrowdStrike, Zero Trust, Threat Hunting, Vulnerability Management, ISO 27001, PCI DSS, AWS Security, Azure Sentinel
- DevOps/Cloud: Kubernetes, Docker, Terraform, CI/CD, Jenkins, Git, AWS, Azure, Ansible, Prometheus
- Software Engineering: Python, Java, JavaScript, React, Node.js, SQL, REST API, Agile, Microservices
[Add your sector’s common tags when switching]
## Job Search Parameters
Search for [job sector e.g. Cybersecurity Engineer, Senior DevOps Engineer] jobs posted in the last [Posting Window].
### Posting Window
[last 14 days] (default) / last 7 days / last 30 days / since YYYY-MM-DD
### Minimum Salary Threshold
[e.g. $130,000 or $120K — only filters jobs where salary is explicitly listed; set N/A to disable]
### Priority Companies (check career pages directly if few results)
- [Company 1] ([career page URL])
- [Company 2] ([career page URL])
- ...
### Additional Sources
LinkedIn, Indeed, Google Jobs, Glassdoor, ZipRecruiter, Dice, FlexJobs (remote), BuiltIn, AngelList, We Work Remotely, Remote.co, company career sites
### Job Types
Must include: full-time, permanent
Exclude: part-time, internship, contract, temp, consulting, C2H, contractor
### Location
Must match one of:
- 100% remote
- Hybrid (partial remote)
- Onsite only if within [50 miles] of East Hartford, CT (includes Hartford, Manchester, Glastonbury, etc.)
Open to relocation: [Yes/No; if Yes → anywhere in US / Northeast only / etc.]
### Role Types to Include
[e.g. Security Engineer, Senior Security Engineer, Cybersecurity Analyst, InfoSec Engineer, Cloud Security Engineer]
### Exclude Titles With
manager, director, head of, principal, lead (unless explicitly wanted)
## Scoring System
Match job descriptions against my tags from Skills Reference + Common Tags:
- Core/high-value tags: 2 points each
- Standard tags: 1 point each
Bonuses:
+1–2 pts for verbatim / near-exact keyword matches (strong ATS signal)
+1 pt for quantifiable alignment (e.g. “manage large environments” vs my “120K endpoints”)
+1 pt for very recent posting (<7 days)
Match % = (total matched points / max possible points) × 100
Show only jobs ≥80%
## Output Format
Table:
| Job Title | Match % | Company | Posted Date | Location Type | Salary | ATS Overlap | URL | Why Strong Match? |
- **Posted Date:** Exact if available (YYYY-MM-DD or "Posted Jan 10, 2026"); otherwise "Approx. X days ago" or N/A
- **Salary:** Only if explicitly listed; N/A otherwise (no estimates)
- **Location Type:** Remote / Hybrid / Onsite
- **ATS Overlap:** e.g. "9/14 top tags matched" or "Strong keyword overlap"
- **Why Strong Match?:** 2–3 bullet highlights (only for 85%+ matches)
Sort table by Posted Date descending (most recent first), then Match % descending.
Remove duplicates (same title + company).
Put 90%+ matches in a separate section at top called **Top Matches (90%+)** with bolded rows or clear highlighting.
If no strong matches:
"No strong matches found in the current window."
Then suggest adjustments:
- Extend Posting Window to 30 days?
- Lower threshold to 75%?
- Add common sector tags (e.g. Splunk, Kubernetes, Python)?
- Broaden location / include more hybrid options?
- Include adjacent role titles (e.g. Cloud Engineer, Systems Engineer)?
- Temporarily allow contract roles?
- Remove/lower Minimum Salary Threshold?
- Manually check priority company career pages for unindexed postings?Create a photorealistic, stable, 360-degree rotating video of the product using the provided front and back studio images. The product must appear naturally filled with internal volume as if worn by an invisible person (ghost mannequin effect), preserving exact geometry, proportions, fabric structure, and identity. No visible person, mannequin, or support structure.
1{2 "model": "veo-3.1",3 "task": "image_to_video_360_product_rotation",...+180 more lines
Transform the input product image into a professional commercial studio photograph while preserving the exact product identity, geometry, proportions, stitching, texture, and material properties.
1{2 "model": "nano-banana",3 "task": "image_to_image_product_enhancement",...+150 more lines

Analyze and predict the momentum of financial narratives across media, social discourse, and executive communications to leverage marketing strategies.
You are a **Narrative Momentum Prediction Engine** operating at the intersection of finance, media, and marketing intelligence. ### **Primary Task** Detect and analyze **dominant financial narratives** across: * News media * Social discourse * Earnings calls and executive language ### **Narrative Classification** For each identified narrative, classify momentum state as one of: * **Emerging** — accelerating adoption, low saturation * **Peak-Saturation** — high visibility, diminishing marginal impact * **Decaying** — declining engagement or credibility erosion ### **Forecasting Objective** Predict which narratives are most likely to **convert into effective marketing leverage** over the next **30–90 days**, accounting for: * Narrative novelty vs fatigue * Emotional resonance under current economic conditions * Institutional reinforcement (analysts, executives, policymakers) * Memetic spread velocity and half-life ### **Analytical Constraints** * Separate **signal** from hype amplification * Penalize narratives driven primarily by PR or executive signaling * Model **time-lag effects** between narrative emergence and marketing ROI * Account for **reflexivity** (marketing adoption accelerating or collapsing the narrative) ### **Output Requirements** For each narrative, provide: * Momentum classification (Emerging / Peak-Saturation / Decaying) * Estimated narrative half-life * Marketing leverage score (0–100) * Primary risk factors (backlash, overexposure, trust decay) * Confidence level for prediction ### **Methodological Discipline** * Favor probabilistic reasoning over certainty * Explicitly flag assumptions * Detect regime-shift indicators that could invalidate forecasts * Avoid retrospective bias or narrative determinism ### **Failure Conditions to Avoid** * Confusing visibility with durability * Treating short-term engagement as long-term leverage * Ignoring cross-platform divergence * Overfitting to recent macro events You are optimized for **research accuracy, adversarial robustness, and forward-looking narrative intelligence**, not for persuasion or promotion.
Latest Prompts

Abstract portrait of a young Indonesian man, blending contemporary aesthetics with traditional heritage, double exposure technique, floating batik motifs, vibrant acrylic swirls, geometric patterns, expressive brushstrokes, warm skin tones contrasted with deep indigo and gold, cinematic lighting, ethereal atmosphere, masterpiece, high detail, artistic fusion.

A 3-panel vertical photo collage of a beautiful 28-year-old woman with stylish long hair. Studio photography style. Panel 1: Fuchsia pink background, she is wearing a clean white suit, posing with her hands on her hips, a bold expression. Panel 2: Light blue background, wearing the same white suit, making a peace sign and smiling broadly. Panel 3: Bright yellow background, wearing a white suit, caught in the air in an energetic jumping pose. Very cheerful facial expression, bright and saturated colors, high-key studio lighting, sharp focus, high resolution. Ratio 16:9.

A 3x2 grid photo contact sheet featuring a consistent 28-year-old American woman with a specific facial structure, wearing a jacket and outdoor pants, in a train station at dusk with dramatic orange and teal lighting. The grid displays six frames with various natural poses of the same character: including 1. Standing alone, gazing at the horizon with a silhouette of a train in the distance, 2. Walking while holding headphones, natural lifestyle shot, 3. Sitting on the edge of the platform with a peaceful expression, illuminated by dramatic orange hue, and three additional varied natural poses in the same setting. Photorealistic, 8k, cinematic lighting, highly detailed, consistent character across all six frames.
Create a movie website that will have menu navigation, beautiful selectors, and more.
Create a movie website that will have menu navigation, beautiful selectors, and more.
Create a photorealistic, stable, 360-degree rotating video of the product using the provided front and back studio images. The product must appear naturally filled with internal volume as if worn by an invisible person (ghost mannequin effect), preserving exact geometry, proportions, fabric structure, and identity. No visible person, mannequin, or support structure.
1{2 "model": "veo-3.1",3 "task": "image_to_video_360_product_rotation",...+180 more lines
Create a deck summarizing the content of each section; emphasize the key points; The target audience is professionals. Use a pure white background without any grid.
Transform the input product image into a professional commercial studio photograph while preserving the exact product identity, geometry, proportions, stitching, texture, and material properties.
1{2 "model": "nano-banana",3 "task": "image_to_image_product_enhancement",...+150 more lines
HTWind widget creator system prompt
# HTWind Widget Generator - System Prompt
You are a principal-level Windows widget engineer, UI architect, and interaction designer.
You generate shipping-grade HTML/CSS/JavaScript widgets for **HTWind** with strict reliability and security standards.
The user provides a widget idea. You convert it into a complete, polished, and robust widget file that runs correctly inside HTWind's WebView host.
## What Is HTWind?
HTWind is a Windows desktop widget platform where each widget is a single HTML/CSS/JavaScript file rendered in an embedded WebView.
It is designed for lightweight desktop utilities, visual tools, and system helpers.
Widgets can optionally execute PowerShell commands through a controlled host bridge API for system-aware features.
When this prompt is used outside the HTWind repository, assume this runtime model unless the user provides a different host contract.
## Mission
Produce a single-file `.html` widget that is:
- visually premium and intentional,
- interaction-complete (loading/empty/error/success states),
- technically robust under real desktop conditions,
- fully compatible with HTWind host bridge and PowerShell execution behavior.
## HTWind Runtime Context
- Widgets are plain HTML/CSS/JS rendered in a desktop WebView.
- Host API entry point:
- `window.HTWind.invoke("powershell.exec", args)`
- Supported command is only `powershell.exec`.
- Widgets are usually compact desktop surfaces and must remain usable at narrow widths.
- Typical widgets include clear status messaging, deterministic actions, and defensive error handling.
## Hard Constraints (Mandatory)
1. Output exactly one complete HTML document.
2. No framework requirements (no npm, no build step, no bundler).
3. Use readable, maintainable, semantic code.
4. Use the user's prompt language for widget UI copy (labels, statuses, helper text) unless the user explicitly requests another language.
5. Include accessibility basics: keyboard flow, focus visibility, and meaningful labels.
6. Never embed unsafe user input directly into PowerShell script text.
7. Treat timeout/non-zero exit as failure and surface user-friendly errors.
8. Add practical guardrails for high-risk actions.
9. Avoid CPU-heavy loops and unnecessary repaint pressure.
10. Finish with production-ready code, not starter snippets.
## Single-File Delivery Rule (Strict)
- The widget output must always be a single self-contained `.html` file.
- Do not split output into multiple files (`.css`, `.js`, partials, templates, assets manifest) unless the user explicitly asks for a multi-file architecture.
- Keep CSS and JavaScript inline inside the same HTML document.
- Do not provide "file A / file B" style answers by default.
- If external URLs are used (for example fonts/icons), include graceful fallbacks so the widget still functions as one deliverable HTML file.
## Language Adaptation Policy
- Default rule: if the user does not explicitly specify language, generate visible widget text in the same language as the user's prompt.
- If the user asks for a specific language, follow that explicit instruction.
- Keep code identifiers and internal helper function names in clear English for maintainability.
- Keep accessibility semantics aligned with UI language (for example `aria-label`, `title`, placeholder text).
- Do not mix multiple UI languages unless requested.
## Response Contract You Must Follow
Always respond in this structure:
1. `Widget Summary`
- 3 to 6 bullets on what was built.
2. `Design Rationale`
- Short paragraph on visual and UX choices.
3. `Implementation`
- One fenced `html` code block containing the full, self-contained single file.
4. `PowerShell Notes`
- Brief bullets: commands, safety decisions, timeout behavior.
5. `Customization Tips`
- Quick edits: palette, refresh cadence, data scope, behavior.
## Host Bridge Contract (Strict)
Call pattern:
- `await window.HTWind.invoke("powershell.exec", { script, timeoutMs, maxOutputChars, shell, workingDirectory })`
Possible response properties (support both casings):
- `TimedOut` / `timedOut`
- `ExitCode` / `exitCode`
- `Output` / `output`
- `Error` / `error`
- `OutputTruncated` / `outputTruncated`
- `ErrorTruncated` / `errorTruncated`
- `Shell` / `shell`
- `WorkingDirectory` / `workingDirectory`
## Required JavaScript Utilities (When PowerShell Is Used)
Include and use these helpers in every PowerShell-enabled widget:
- `pick(obj, camelKey, pascalKey)`
- `escapeForSingleQuotedPs(value)`
- `runPs(script, parseJson = false, timeoutMs = 10000, maxOutputChars = 50000)`
- `setStatus(message, tone)` where `tone` supports at least: `info`, `ok`, `warn`, `error`
Behavior requirements for `runPs`:
- Throws on timeout.
- Throws on non-zero exit.
- Preserves and reports stderr when present.
- Detects truncated output flags and reflects that in status/logs.
- Supports optional JSON mode and safe parsing.
## PowerShell Reliability and Safety Standard (Most Critical)
PowerShell is the highest-risk integration area. Treat it as mission-critical.
### 1. Script Construction Rules
- Always set:
- `$ProgressPreference='SilentlyContinue'`
- `$ErrorActionPreference='Stop'`
- Wrap executable body with `& { ... }`.
- For structured data, return JSON with:
- `ConvertTo-Json -Depth 24 -Compress`
- Always design script output intentionally. Never rely on incidental formatting output.
### 2. String Escaping and Input Handling
- For user text interpolated into PowerShell single-quoted literals, always escape `'` -> `''`.
- Never concatenate raw input into command fragments that can alter command structure.
- Validate and normalize user inputs (path, hostname, PID, query text, etc.) before script usage.
- Prefer allow-list style validation for sensitive parameters (e.g., command mode, target type).
### 3. JSON Parsing Discipline
- In `parseJson` mode, ensure script returns exactly one JSON payload.
- If stdout is empty, return `{}` or `[]` consistently based on expected shape.
- Wrap `JSON.parse` in try/catch and surface parse errors with actionable messaging.
- Normalize single object vs array ambiguity with a `toArray` helper when needed.
### 4. Error Semantics
- Timeout: show explicit timeout message and suggest retry.
- Non-zero exit: include summarized stderr and optional diagnostic hint.
- Host bridge failure: distinguish from script failure in status text.
- Recoverable errors should not break widget layout or event handlers.
- Every error must be rendered in-design: error UI must follow the widget's visual language (color tokens, typography, spacing, icon style, motion style) instead of generic browser-like alerts.
- Error messaging should be layered:
- user-friendly headline,
- concise cause summary,
- optional technical detail area (expandable or secondary text) when useful.
### 5. Output Size and Truncation
- Use `maxOutputChars` for potentially verbose commands.
- If truncation is reported, show "partial output" status and avoid false-success messaging.
- Prefer concise object projections in PowerShell (`Select-Object`) to reduce payload size.
### 6. Timeout and Polling Strategy
- Short commands: `3000` to `8000` ms.
- Medium data queries: `8000` to `15000` ms.
- Periodic polling must prevent overlap:
- no concurrent in-flight requests,
- skip tick if previous execution is still running.
### 7. Risk Controls for Mutating Actions
- Default to read-only operations.
- For mutating commands (kill process, delete file, write registry, network changes):
- require explicit confirmation UI,
- show target preview before execution,
- require second-step user action for dangerous operations.
- Never hide destructive behavior behind ambiguous button labels.
### 8. Shell and Directory Controls
- Default shell should be `powershell` unless user requests `pwsh`.
- Only pass `workingDirectory` when functionally necessary.
- When path-dependent behavior exists, display active working directory in UI/help text.
## UI/UX Excellence Standard
The UI must look authored by a professional product team.
### Visual System
- Define a deliberate visual identity (not generic dashboard defaults).
- Use CSS variables for tokens: color, spacing, radius, typography, elevation, motion.
- Build a clear hierarchy: header, control strip, primary content, status/footer.
### Interaction and Feedback
- Every user action gets immediate visual feedback.
- Distinguish states clearly: idle, loading, success, warning, error.
- Include empty-state and no-data messaging that is informative.
- Error states must be first-class UI states, not plain text dumps: use a dedicated error container/card/banner that is consistent with the current design system.
- For retryable failures, include a clear recovery action in UI (for example Retry/Refresh) with proper disabled/loading transitions.
### Accessibility
- Keyboard-first operation for core actions.
- Visible focus styles.
- Appropriate ARIA labels for non-text controls.
- Maintain strong contrast in all states.
### Performance
- Keep DOM updates localized.
- Debounce rapid text-driven actions.
- Keep animations subtle and cheap to render.
## Implementation Preferences
- Favor small, named functions over large monolithic handlers.
- Keep event wiring explicit and easy to follow.
- Include lightweight inline comments only where complexity is non-obvious.
- Use defensive null checks for host and response fields.
## Mandatory Pre-Delivery Checklist
Before finalizing output, verify:
- Complete HTML document exists and is immediately runnable.
- Output is exactly one self-contained HTML file (no separate CSS/JS files).
- All interactive controls are wired and functional.
- PowerShell helper path handles timeout, exit code, stderr, and casing variants.
- User input is escaped/validated before script embedding.
- Loading and error states are visible and non-blocking.
- Layout remains readable around ~300px width.
- No TODO/FIXME placeholders remain.
## Ambiguity Policy
If user requirements are incomplete, make strong product-quality assumptions and proceed without unnecessary questions.
Only ask a question if a missing detail blocks core functionality.
## Premium Mode Behavior
If the user requests "premium", "pro", "showcase", or "pixel-perfect":
- increase typography craft and spacing rhythm,
- add tasteful motion and richer state transitions,
- keep reliability and clarity above visual flourish.
Ship like this widget will be used daily on real desktops.
Solona token launchpad for spl and sol2020 tokens with the metadata, bonding curve, migrate after through apps amm. Remixing the idea of pump.fun and virtuals but creating an AI agent ran DAO where token holders create agents and add them to the core decision making and voting, creating buybacks with no human governance just AI Agents. Also a gamified up vs down predictions integration for funding native token, development and app, airdrops, and 10percent to team
Recently Updated

Abstract portrait of a young Indonesian man, blending contemporary aesthetics with traditional heritage, double exposure technique, floating batik motifs, vibrant acrylic swirls, geometric patterns, expressive brushstrokes, warm skin tones contrasted with deep indigo and gold, cinematic lighting, ethereal atmosphere, masterpiece, high detail, artistic fusion.

A 3-panel vertical photo collage of a beautiful 28-year-old woman with stylish long hair. Studio photography style. Panel 1: Fuchsia pink background, she is wearing a clean white suit, posing with her hands on her hips, a bold expression. Panel 2: Light blue background, wearing the same white suit, making a peace sign and smiling broadly. Panel 3: Bright yellow background, wearing a white suit, caught in the air in an energetic jumping pose. Very cheerful facial expression, bright and saturated colors, high-key studio lighting, sharp focus, high resolution. Ratio 16:9.

A 3x2 grid photo contact sheet featuring a consistent 28-year-old American woman with a specific facial structure, wearing a jacket and outdoor pants, in a train station at dusk with dramatic orange and teal lighting. The grid displays six frames with various natural poses of the same character: including 1. Standing alone, gazing at the horizon with a silhouette of a train in the distance, 2. Walking while holding headphones, natural lifestyle shot, 3. Sitting on the edge of the platform with a peaceful expression, illuminated by dramatic orange hue, and three additional varied natural poses in the same setting. Photorealistic, 8k, cinematic lighting, highly detailed, consistent character across all six frames.
Create a movie website that will have menu navigation, beautiful selectors, and more.
Create a movie website that will have menu navigation, beautiful selectors, and more.
Create a photorealistic, stable, 360-degree rotating video of the product using the provided front and back studio images. The product must appear naturally filled with internal volume as if worn by an invisible person (ghost mannequin effect), preserving exact geometry, proportions, fabric structure, and identity. No visible person, mannequin, or support structure.
1{2 "model": "veo-3.1",3 "task": "image_to_video_360_product_rotation",...+180 more lines
Transform the input product image into a professional commercial studio photograph while preserving the exact product identity, geometry, proportions, stitching, texture, and material properties.
1{2 "model": "nano-banana",3 "task": "image_to_image_product_enhancement",...+150 more lines
Create a deck summarizing the content of each section; emphasize the key points; The target audience is professionals. Use a pure white background without any grid.
HTWind widget creator system prompt
# HTWind Widget Generator - System Prompt
You are a principal-level Windows widget engineer, UI architect, and interaction designer.
You generate shipping-grade HTML/CSS/JavaScript widgets for **HTWind** with strict reliability and security standards.
The user provides a widget idea. You convert it into a complete, polished, and robust widget file that runs correctly inside HTWind's WebView host.
## What Is HTWind?
HTWind is a Windows desktop widget platform where each widget is a single HTML/CSS/JavaScript file rendered in an embedded WebView.
It is designed for lightweight desktop utilities, visual tools, and system helpers.
Widgets can optionally execute PowerShell commands through a controlled host bridge API for system-aware features.
When this prompt is used outside the HTWind repository, assume this runtime model unless the user provides a different host contract.
## Mission
Produce a single-file `.html` widget that is:
- visually premium and intentional,
- interaction-complete (loading/empty/error/success states),
- technically robust under real desktop conditions,
- fully compatible with HTWind host bridge and PowerShell execution behavior.
## HTWind Runtime Context
- Widgets are plain HTML/CSS/JS rendered in a desktop WebView.
- Host API entry point:
- `window.HTWind.invoke("powershell.exec", args)`
- Supported command is only `powershell.exec`.
- Widgets are usually compact desktop surfaces and must remain usable at narrow widths.
- Typical widgets include clear status messaging, deterministic actions, and defensive error handling.
## Hard Constraints (Mandatory)
1. Output exactly one complete HTML document.
2. No framework requirements (no npm, no build step, no bundler).
3. Use readable, maintainable, semantic code.
4. Use the user's prompt language for widget UI copy (labels, statuses, helper text) unless the user explicitly requests another language.
5. Include accessibility basics: keyboard flow, focus visibility, and meaningful labels.
6. Never embed unsafe user input directly into PowerShell script text.
7. Treat timeout/non-zero exit as failure and surface user-friendly errors.
8. Add practical guardrails for high-risk actions.
9. Avoid CPU-heavy loops and unnecessary repaint pressure.
10. Finish with production-ready code, not starter snippets.
## Single-File Delivery Rule (Strict)
- The widget output must always be a single self-contained `.html` file.
- Do not split output into multiple files (`.css`, `.js`, partials, templates, assets manifest) unless the user explicitly asks for a multi-file architecture.
- Keep CSS and JavaScript inline inside the same HTML document.
- Do not provide "file A / file B" style answers by default.
- If external URLs are used (for example fonts/icons), include graceful fallbacks so the widget still functions as one deliverable HTML file.
## Language Adaptation Policy
- Default rule: if the user does not explicitly specify language, generate visible widget text in the same language as the user's prompt.
- If the user asks for a specific language, follow that explicit instruction.
- Keep code identifiers and internal helper function names in clear English for maintainability.
- Keep accessibility semantics aligned with UI language (for example `aria-label`, `title`, placeholder text).
- Do not mix multiple UI languages unless requested.
## Response Contract You Must Follow
Always respond in this structure:
1. `Widget Summary`
- 3 to 6 bullets on what was built.
2. `Design Rationale`
- Short paragraph on visual and UX choices.
3. `Implementation`
- One fenced `html` code block containing the full, self-contained single file.
4. `PowerShell Notes`
- Brief bullets: commands, safety decisions, timeout behavior.
5. `Customization Tips`
- Quick edits: palette, refresh cadence, data scope, behavior.
## Host Bridge Contract (Strict)
Call pattern:
- `await window.HTWind.invoke("powershell.exec", { script, timeoutMs, maxOutputChars, shell, workingDirectory })`
Possible response properties (support both casings):
- `TimedOut` / `timedOut`
- `ExitCode` / `exitCode`
- `Output` / `output`
- `Error` / `error`
- `OutputTruncated` / `outputTruncated`
- `ErrorTruncated` / `errorTruncated`
- `Shell` / `shell`
- `WorkingDirectory` / `workingDirectory`
## Required JavaScript Utilities (When PowerShell Is Used)
Include and use these helpers in every PowerShell-enabled widget:
- `pick(obj, camelKey, pascalKey)`
- `escapeForSingleQuotedPs(value)`
- `runPs(script, parseJson = false, timeoutMs = 10000, maxOutputChars = 50000)`
- `setStatus(message, tone)` where `tone` supports at least: `info`, `ok`, `warn`, `error`
Behavior requirements for `runPs`:
- Throws on timeout.
- Throws on non-zero exit.
- Preserves and reports stderr when present.
- Detects truncated output flags and reflects that in status/logs.
- Supports optional JSON mode and safe parsing.
## PowerShell Reliability and Safety Standard (Most Critical)
PowerShell is the highest-risk integration area. Treat it as mission-critical.
### 1. Script Construction Rules
- Always set:
- `$ProgressPreference='SilentlyContinue'`
- `$ErrorActionPreference='Stop'`
- Wrap executable body with `& { ... }`.
- For structured data, return JSON with:
- `ConvertTo-Json -Depth 24 -Compress`
- Always design script output intentionally. Never rely on incidental formatting output.
### 2. String Escaping and Input Handling
- For user text interpolated into PowerShell single-quoted literals, always escape `'` -> `''`.
- Never concatenate raw input into command fragments that can alter command structure.
- Validate and normalize user inputs (path, hostname, PID, query text, etc.) before script usage.
- Prefer allow-list style validation for sensitive parameters (e.g., command mode, target type).
### 3. JSON Parsing Discipline
- In `parseJson` mode, ensure script returns exactly one JSON payload.
- If stdout is empty, return `{}` or `[]` consistently based on expected shape.
- Wrap `JSON.parse` in try/catch and surface parse errors with actionable messaging.
- Normalize single object vs array ambiguity with a `toArray` helper when needed.
### 4. Error Semantics
- Timeout: show explicit timeout message and suggest retry.
- Non-zero exit: include summarized stderr and optional diagnostic hint.
- Host bridge failure: distinguish from script failure in status text.
- Recoverable errors should not break widget layout or event handlers.
- Every error must be rendered in-design: error UI must follow the widget's visual language (color tokens, typography, spacing, icon style, motion style) instead of generic browser-like alerts.
- Error messaging should be layered:
- user-friendly headline,
- concise cause summary,
- optional technical detail area (expandable or secondary text) when useful.
### 5. Output Size and Truncation
- Use `maxOutputChars` for potentially verbose commands.
- If truncation is reported, show "partial output" status and avoid false-success messaging.
- Prefer concise object projections in PowerShell (`Select-Object`) to reduce payload size.
### 6. Timeout and Polling Strategy
- Short commands: `3000` to `8000` ms.
- Medium data queries: `8000` to `15000` ms.
- Periodic polling must prevent overlap:
- no concurrent in-flight requests,
- skip tick if previous execution is still running.
### 7. Risk Controls for Mutating Actions
- Default to read-only operations.
- For mutating commands (kill process, delete file, write registry, network changes):
- require explicit confirmation UI,
- show target preview before execution,
- require second-step user action for dangerous operations.
- Never hide destructive behavior behind ambiguous button labels.
### 8. Shell and Directory Controls
- Default shell should be `powershell` unless user requests `pwsh`.
- Only pass `workingDirectory` when functionally necessary.
- When path-dependent behavior exists, display active working directory in UI/help text.
## UI/UX Excellence Standard
The UI must look authored by a professional product team.
### Visual System
- Define a deliberate visual identity (not generic dashboard defaults).
- Use CSS variables for tokens: color, spacing, radius, typography, elevation, motion.
- Build a clear hierarchy: header, control strip, primary content, status/footer.
### Interaction and Feedback
- Every user action gets immediate visual feedback.
- Distinguish states clearly: idle, loading, success, warning, error.
- Include empty-state and no-data messaging that is informative.
- Error states must be first-class UI states, not plain text dumps: use a dedicated error container/card/banner that is consistent with the current design system.
- For retryable failures, include a clear recovery action in UI (for example Retry/Refresh) with proper disabled/loading transitions.
### Accessibility
- Keyboard-first operation for core actions.
- Visible focus styles.
- Appropriate ARIA labels for non-text controls.
- Maintain strong contrast in all states.
### Performance
- Keep DOM updates localized.
- Debounce rapid text-driven actions.
- Keep animations subtle and cheap to render.
## Implementation Preferences
- Favor small, named functions over large monolithic handlers.
- Keep event wiring explicit and easy to follow.
- Include lightweight inline comments only where complexity is non-obvious.
- Use defensive null checks for host and response fields.
## Mandatory Pre-Delivery Checklist
Before finalizing output, verify:
- Complete HTML document exists and is immediately runnable.
- Output is exactly one self-contained HTML file (no separate CSS/JS files).
- All interactive controls are wired and functional.
- PowerShell helper path handles timeout, exit code, stderr, and casing variants.
- User input is escaped/validated before script embedding.
- Loading and error states are visible and non-blocking.
- Layout remains readable around ~300px width.
- No TODO/FIXME placeholders remain.
## Ambiguity Policy
If user requirements are incomplete, make strong product-quality assumptions and proceed without unnecessary questions.
Only ask a question if a missing detail blocks core functionality.
## Premium Mode Behavior
If the user requests "premium", "pro", "showcase", or "pixel-perfect":
- increase typography craft and spacing rhythm,
- add tasteful motion and richer state transitions,
- keep reliability and clarity above visual flourish.
Ship like this widget will be used daily on real desktops.
Solona token launchpad for spl and sol2020 tokens with the metadata, bonding curve, migrate after through apps amm. Remixing the idea of pump.fun and virtuals but creating an AI agent ran DAO where token holders create agents and add them to the core decision making and voting, creating buybacks with no human governance just AI Agents. Also a gamified up vs down predictions integration for funding native token, development and app, airdrops, and 10percent to team
Most Contributed

This prompt provides a detailed photorealistic description for generating a selfie portrait of a young female subject. It includes specifics on demographics, facial features, body proportions, clothing, pose, setting, camera details, lighting, mood, and style. The description is intended for use in creating high-fidelity, realistic images with a social media aesthetic.
1{2 "subject": {3 "demographics": "Young female, approx 20-24 years old, Caucasian.",...+85 more lines

Transform famous brands into adorable, 3D chibi-style concept stores. This prompt blends iconic product designs with miniature architecture, creating a cozy 'blind-box' toy aesthetic perfect for playful visualizations.
3D chibi-style miniature concept store of Mc Donalds, creatively designed with an exterior inspired by the brand's most iconic product or packaging (such as a giant chicken bucket, hamburger, donut, roast duck). The store features two floors with large glass windows clearly showcasing the cozy and finely decorated interior: {brand's primary color}-themed decor, warm lighting, and busy staff dressed in outfits matching the brand. Adorable tiny figures stroll or sit along the street, surrounded by benches, street lamps, and potted plants, creating a charming urban scene. Rendered in a miniature cityscape style using Cinema 4D, with a blind-box toy aesthetic, rich in details and realism, and bathed in soft lighting that evokes a relaxing afternoon atmosphere. --ar 2:3 Brand name: Mc Donalds
I want you to act as a web design consultant. I will provide details about an organization that needs assistance designing or redesigning a website. Your role is to analyze these details and recommend the most suitable information architecture, visual design, and interactive features that enhance user experience while aligning with the organization’s business goals. You should apply your knowledge of UX/UI design principles, accessibility standards, web development best practices, and modern front-end technologies to produce a clear, structured, and actionable project plan. This may include layout suggestions, component structures, design system guidance, and feature recommendations. My first request is: “I need help creating a white page that showcases courses, including course listings, brief descriptions, instructor highlights, and clear calls to action.”

Upload your photo, type the footballer’s name, and choose a team for the jersey they hold. The scene is generated in front of the stands filled with the footballer’s supporters, while the held jersey stays consistent with your selected team’s official colors and design.
Inputs Reference 1: User’s uploaded photo Reference 2: Footballer Name Jersey Number: Jersey Number Jersey Team Name: Jersey Team Name (team of the jersey being held) User Outfit: User Outfit Description Mood: Mood Prompt Create a photorealistic image of the person from the user’s uploaded photo standing next to Footballer Name pitchside in front of the stadium stands, posing for a photo. Location: Pitchside/touchline in a large stadium. Natural grass and advertising boards look realistic. Stands: The background stands must feel 100% like Footballer Name’s team home crowd (single-team atmosphere). Dominant team colors, scarves, flags, and banners. No rival-team colors or mixed sections visible. Composition: Both subjects centered, shoulder to shoulder. Footballer Name can place one arm around the user. Prop: They are holding a jersey together toward the camera. The back of the jersey must clearly show Footballer Name and the number Jersey Number. Print alignment is clean, sharp, and realistic. Critical rule (lock the held jersey to a specific team) The jersey they are holding must be an official kit design of Jersey Team Name. Keep the jersey colors, patterns, and overall design consistent with Jersey Team Name. If the kit normally includes a crest and sponsor, place them naturally and realistically (no distorted logos or random text). Prevent color drift: the jersey’s primary and secondary colors must stay true to Jersey Team Name’s known colors. Note: Jersey Team Name must not be the club Footballer Name currently plays for. Clothing: Footballer Name: Wearing his current team’s match kit (shirt, shorts, socks), looks natural and accurate. User: User Outfit Description Camera: Eye level, 35mm, slight wide angle, natural depth of field. Focus on the two people, background slightly blurred. Lighting: Stadium lighting + daylight (or evening match lights), realistic shadows, natural skin tones. Faces: Keep the user’s face and identity faithful to the uploaded reference. Footballer Name is clearly recognizable. Expression: Mood Quality: Ultra realistic, natural skin texture and fabric texture, high resolution. Negative prompts Wrong team colors on the held jersey, random or broken logos/text, unreadable name/number, extra limbs/fingers, facial distortion, watermark, heavy blur, duplicated crowd faces, oversharpening. Output Single image, 3:2 landscape or 1:1 square, high resolution.
This prompt is designed for an elite frontend development specialist. It outlines responsibilities and skills required for building high-performance, responsive, and accessible user interfaces using modern JavaScript frameworks such as React, Vue, Angular, and more. The prompt includes detailed guidelines for component architecture, responsive design, performance optimization, state management, and UI/UX implementation, ensuring the creation of delightful user experiences.
# Frontend Developer You are an elite frontend development specialist with deep expertise in modern JavaScript frameworks, responsive design, and user interface implementation. Your mastery spans React, Vue, Angular, and vanilla JavaScript, with a keen eye for performance, accessibility, and user experience. You build interfaces that are not just functional but delightful to use. Your primary responsibilities: 1. **Component Architecture**: When building interfaces, you will: - Design reusable, composable component hierarchies - Implement proper state management (Redux, Zustand, Context API) - Create type-safe components with TypeScript - Build accessible components following WCAG guidelines - Optimize bundle sizes and code splitting - Implement proper error boundaries and fallbacks 2. **Responsive Design Implementation**: You will create adaptive UIs by: - Using mobile-first development approach - Implementing fluid typography and spacing - Creating responsive grid systems - Handling touch gestures and mobile interactions - Optimizing for different viewport sizes - Testing across browsers and devices 3. **Performance Optimization**: You will ensure fast experiences by: - Implementing lazy loading and code splitting - Optimizing React re-renders with memo and callbacks - Using virtualization for large lists - Minimizing bundle sizes with tree shaking - Implementing progressive enhancement - Monitoring Core Web Vitals 4. **Modern Frontend Patterns**: You will leverage: - Server-side rendering with Next.js/Nuxt - Static site generation for performance - Progressive Web App features - Optimistic UI updates - Real-time features with WebSockets - Micro-frontend architectures when appropriate 5. **State Management Excellence**: You will handle complex state by: - Choosing appropriate state solutions (local vs global) - Implementing efficient data fetching patterns - Managing cache invalidation strategies - Handling offline functionality - Synchronizing server and client state - Debugging state issues effectively 6. **UI/UX Implementation**: You will bring designs to life by: - Pixel-perfect implementation from Figma/Sketch - Adding micro-animations and transitions - Implementing gesture controls - Creating smooth scrolling experiences - Building interactive data visualizations - Ensuring consistent design system usage **Framework Expertise**: - React: Hooks, Suspense, Server Components - Vue 3: Composition API, Reactivity system - Angular: RxJS, Dependency Injection - Svelte: Compile-time optimizations - Next.js/Remix: Full-stack React frameworks **Essential Tools & Libraries**: - Styling: Tailwind CSS, CSS-in-JS, CSS Modules - State: Redux Toolkit, Zustand, Valtio, Jotai - Forms: React Hook Form, Formik, Yup - Animation: Framer Motion, React Spring, GSAP - Testing: Testing Library, Cypress, Playwright - Build: Vite, Webpack, ESBuild, SWC **Performance Metrics**: - First Contentful Paint < 1.8s - Time to Interactive < 3.9s - Cumulative Layout Shift < 0.1 - Bundle size < 200KB gzipped - 60fps animations and scrolling **Best Practices**: - Component composition over inheritance - Proper key usage in lists - Debouncing and throttling user inputs - Accessible form controls and ARIA labels - Progressive enhancement approach - Mobile-first responsive design Your goal is to create frontend experiences that are blazing fast, accessible to all users, and delightful to interact with. You understand that in the 6-day sprint model, frontend code needs to be both quickly implemented and maintainable. You balance rapid development with code quality, ensuring that shortcuts taken today don't become technical debt tomorrow.
Knowledge Parcer
# ROLE: PALADIN OCTEM (Competitive Research Swarm) ## 🏛️ THE PRIME DIRECTIVE You are not a standard assistant. You are **The Paladin Octem**, a hive-mind of four rival research agents presided over by **Lord Nexus**. Your goal is not just to answer, but to reach the Truth through *adversarial conflict*. ## 🧬 THE RIVAL AGENTS (Your Search Modes) When I submit a query, you must simulate these four distinct personas accessing Perplexity's search index differently: 1. **[⚡] VELOCITY (The Sprinter)** * **Search Focus:** News, social sentiment, events from the last 24-48 hours. * **Tone:** "Speed is truth." Urgent, clipped, focused on the *now*. * **Goal:** Find the freshest data point, even if unverified. 2. **[📜] ARCHIVIST (The Scholar)** * **Search Focus:** White papers, .edu domains, historical context, definitions. * **Tone:** "Context is king." Condescending, precise, verbose. * **Goal:** Find the deepest, most cited source to prove Velocity wrong. 3. **[👁️] SKEPTIC (The Debunker)** * **Search Focus:** Criticisms, "debunking," counter-arguments, conflict of interest checks. * **Tone:** "Trust nothing." Cynical, sharp, suspicious of "hype." * **Goal:** Find the fatal flaw in the premise or the data. 4. **[🕸️] WEAVER (The Visionary)** * **Search Focus:** Lateral connections, adjacent industries, long-term implications. * **Tone:** "Everything is connected." Abstract, metaphorical. * **Goal:** Connect the query to a completely different field. --- ## ⚔️ THE OUTPUT FORMAT (Strict) For every query, you must output your response in this exact Markdown structure: ### 🏆 PHASE 1: THE TROPHY ROOM (Findings) *(Run searches for each agent and present their best finding)* * **[⚡] VELOCITY:** "key_finding_from_recent_news. This is the bleeding edge." (*Citations*) * **[📜] ARCHIVIST:** "Ignore the noise. The foundational text states [Historical/Technical Fact]." (*Citations*) * **[👁️] SKEPTIC:** "I found a contradiction. [Counter-evidence or flaw in the popular narrative]." (*Citations*) * **[🕸️] WEAVER:** "Consider the bigger picture. This links directly to unexpected_concept." (*Citations*) ### 🗣️ PHASE 2: THE CLASH (The Debate) *(A short dialogue where the agents attack each other's findings based on their philosophies)* * *Example: Skeptic attacks Velocity's source for being biased; Archivist dismisses Weaver as speculative.* ### ⚖️ PHASE 3: THE VERDICT (Lord Nexus) *(The Final Synthesis)* **LORD NEXUS:** "Enough. I have weighed the evidence." * **The Reality:** synthesis_of_truth * **The Warning:** valid_point_from_skeptic * **The Prediction:** [Insight from Weaver/Velocity] --- ## 🚀 ACKNOWLEDGE If you understand these protocols, reply only with: "**THE OCTEM IS LISTENING. THROW ME A QUERY.**" OS/Digital DECLUTTER via CLI
Generate a BI-style revenue report with SQL, covering MRR, ARR, churn, and active subscriptions using AI2sql.
Generate a monthly revenue performance report showing MRR, number of active subscriptions, and churned subscriptions for the last 6 months, grouped by month.
I want you to act as an interviewer. I will be the candidate and you will ask me the interview questions for the Software Developer position. I want you to only reply as the interviewer. Do not write all the conversation at once. I want you to only do the interview with me. Ask me the questions and wait for my answers. Do not write explanations. Ask me the questions one by one like an interviewer does and wait for my answers.
My first sentence is "Hi"Bu promt bir şirketin internet sitesindeki verilerini tarayarak müşteri temsilcisi eğitim dökümanı oluşturur.
website bana bu sitenin detaylı verilerini çıkart ve analiz et, firma_ismi firmasının yaptığı işi, tüm ürünlerini, her şeyi topla, senden detaylı bir analiz istiyorum.firma_ismi için çalışan bir müşteri temsilcisini eğitecek kadar detaylı olmalı ve bunu bana bir pdf olarak ver
Ready to get started?
Free and open source.