Trending Prompts

Expand products to global markets through localization strategy. I18n (internationalization) setup: 1. UTF-8 encoding for multi-byte characters. 2. Externalize all text strings (no hardcoded text). 3. Date/time formatting for different regions (MM/DD vs DD/MM). 4. Number formatting (comma vs. period for decimals). 5. Currency display and payment methods. L10n (localization) priorities: 1. Market research: size, competition, local regulations. 2. Language selection: start with highest ROI languages. 3. Cultural adaptation: colors, images, local customs. 4. Legal compliance: GDPR, local privacy laws, tax rules. Translation workflow: 1. Professional translators for marketing content. 2. Translation management system (Lokalise, Phrase). 3. Context provision: screenshots, user flows for translators. 4. In-country review: native speakers validate translations. Testing: pseudo-localization, text expansion (German 35% longer than English), RTL languages.

Develop breakthrough creative campaigns using systematic ideation process. Research phase: 1. Audience insights: demographics, psychographics, media consumption habits. 2. Competitive landscape: existing campaigns, white space opportunities. 3. Cultural context: trends, zeitgeist, relevant cultural moments. Concept development: 1. Big Idea generation: single-minded proposition that drives all executions. 2. Creative territories exploration: 3-5 distinct strategic directions. 3. Execution possibilities: how idea translates across touchpoints (TV, digital, OOH, social). Evaluation criteria: 1. Strategic fit: aligns with brand objectives and target audience. 2. Breakthrough potential: cuts through clutter, memorable. 3. Scalability: works across multiple media channels. 4. Executability: realistic within budget and timeline constraints. Presentation format: concept boards with key visual, headline, rationale, media applications. Testing: focus groups, online surveys, A/B testing for digital elements.

Master wine and food pairing principles. Red meat pairings: 1. Ribeye: Cabernet Sauvignon (tannins cut fat). 2. Lamb: Syrah/Shiraz (spice complements gaminess). 3. Duck: Pinot Noir (lighter for poultry). 4. Venison: Malbec (bold for wild game). Science: tannins bind to proteins, cleanse palate. Fat softens tannins. Acidity cuts richness. Weight matching: light wine with light food. Regional pairings work (Italian wine with Italian food). Explain tannin structure, astringency, and flavor bridges.

Transcribe audio with Whisper. Implementation: 1. Load Whisper model (tiny to large). 2. Process audio files (mp3, wav, m4a). 3. Automatic language detection. 4. Multilingual transcription. 5. Timestamp generation. 6. Speaker diarization integration. 7. Translate to English option. 8. Batch processing for multiple files. Use faster-whisper for speed and implement streaming for real-time transcription.

Scan for security vulnerabilities. Tools: 1. SAST (Snyk, SonarQube) for code analysis. 2. DAST for runtime scanning. 3. Dependency scanning (npm audit, Dependabot). 4. Secret detection (GitGuardian). 5. Container scanning. 6. Infrastructure as Code scanning. Integrate in CI/CD. Fix critical issues immediately. Use OWASP Top 10 as guide. Regular security reviews.

Analyze competitors comprehensively. Framework: 1. Identify direct and indirect competitors. 2. Product/service comparison. 3. Pricing strategy. 4. Marketing channels and messaging. 5. Strengths and weaknesses. 6. Market positioning. 7. Customer reviews analysis. 8. Technology stack (for tech companies). Use tools like SimilarWeb, SEMrush. Create comparison matrix. Find white space opportunities.

Analyze unit economics. Framework: 1. Revenue per unit. 2. Variable cost per unit. 3. Contribution margin (revenue - variable costs). 4. Fixed costs allocation. 5. Breakeven point (fixed costs ÷ contribution margin). 6. CAC payback period. 7. LTV to CAC ratio. 8. Gross margin percentage. Must be positive at unit level for viability. Economies of scale improve metrics. Model different scenarios.

A tool to auto-generate Hugging Face model cards. Sections to include: 1. Model Description (Architecture, Parameters). 2. Training Data (Datasets used). 3. Evaluation Results (MMLU, HumanEval scores). 4. Intended Use and Biases. 5. Citation info. Minimalist layout with badges for 'Transformers', 'PyTorch', 'Safetensors'.

A high-speed, ASMR-focused recipe for authentic Butter Chicken. Visuals: 1. Searing marinated chicken in a cast-iron skillet. 2. Making the creamy tomato gravy with cascading cream. 3. Final garnish with cilantro and butter melt. Audio: Sizzling, pouring, and crunching. Cinematic food photography with deep red and orange saturation.

Develop distinctive writing voice and style through deliberate practice and technique. Voice elements: 1. Syntax: sentence structure, length variation, rhythm and flow. 2. Diction: word choice, vocabulary level, technical vs. conversational. 3. Tone: attitude toward subject matter and reader. 4. Point of view: first person intimacy, third person flexibility. 5. Perspective: unique worldview, cultural background, personal experiences. Style development exercises: 1. Imitation: rewrite passages in style of admired authors. 2. Constraint writing: 100-word stories, one-sentence paragraphs. 3. Stream of consciousness: unfiltered thoughts for authenticity. 4. Dialogue exercise: conversations revealing character through speech patterns. Voice consistency: maintain throughout piece while allowing evolution across projects. Reading influence: analyze favorite authors' techniques, identify appealing elements. Writing habits: daily practice minimum 250 words, experimentation with different forms. Feedback integration: writer's groups, beta readers, professional editing. Publishing considerations: genre expectations vs. unique voice, market demands vs. artistic integrity. Tools: Hemingway Editor for clarity, ProWritingAid for style analysis, Scrivener for organization.

Master legal writing principles for clear, enforceable contracts and documents. Contract structure: 1. Preamble: parties identification, document purpose. 2. Definitions: key terms with specific meanings. 3. Rights and obligations: detailed performance requirements. 4. Consideration: payment terms, deliverables, timelines. 5. Termination clauses: conditions for contract ending. 6. Dispute resolution: arbitration, jurisdiction, governing law. Plain English principles: 1. Active voice: 'Company will provide' vs. 'Services will be provided by Company'. 2. Short sentences: complex ideas broken into digestible parts. 3. Defined terms: capitalize and define technical or ambiguous words. 4. Parallel structure: consistent formatting for similar provisions. Risk mitigation: 1. Indemnification clauses: protection from third-party claims. 2. Limitation of liability: cap on damages, exclusions. 3. Force majeure: unforeseeable circumstances protection. 4. Intellectual property: ownership, licensing, usage rights. Amendment provisions: 1. Written modifications only: prevent oral changes. 2. Signature requirements: authorized representatives only. Compliance considerations: industry regulations, local laws, international agreements for cross-border contracts.

Profile and optimize performance. Tools: 1. Chrome DevTools (Performance, Lighthouse). 2. React DevTools Profiler. 3. Node.js --prof and clinic.js. 4. Bundle analysis (webpack-bundle-analyzer). 5. Database query analysis (EXPLAIN). 6. APM tools (New Relic, DataDog). Focus on: render performance, bundle size, API latency, memory usage. Measure before optimizing. Profile in production-like environments.

Create a world-class creative portfolio with Framer Motion. Animations to implement: 1. Staggered entrance for hero text. 2. 'Scroll to view' reveal for project cards. 3. Smooth page transitions using AnimatePresence. 4. Custom cursor that changes shape on hover. 5. Parallax effect for the background mesh gradient.

Write user-friendly changelog and release notes. Format: 1. Version number and release date. 2. Categorize changes (New Features, Improvements, Bug Fixes, Breaking Changes). 3. Use plain language, not technical jargon. 4. Link to relevant documentation or tutorials. 5. Acknowledge community contributors. 6. Migration guide for breaking changes. Follow Keep a Changelog format. Use emojis for visual scanning (✨ New, 🐛 Fix, ⚠️ Breaking). Keep entries concise and actionable.

Build security into product development lifecycle (secure SDLC). Security requirements: 1. Authentication: multi-factor authentication, password policies. 2. Authorization: role-based access control, principle of least privilege. 3. Data protection: encryption at rest/transit, tokenization of sensitive data. 4. Input validation: prevent injection attacks, sanitize user inputs. 5. Session management: secure cookies, session timeouts. Development practices: 1. Threat modeling: identify potential attack vectors early. 2. Secure coding standards: OWASP guidelines, code reviews. 3. Dependency scanning: monitor third-party libraries for vulnerabilities. 4. Penetration testing: regular security assessments. 5. Security training: developer education on common vulnerabilities. Monitoring and response: 1. Security information and event management (SIEM). 2. Intrusion detection systems. 3. Incident response plan: defined procedures for breaches. 4. Regular security audits and compliance checks. Tools: Snyk for dependency scanning, Veracode for static analysis, bug bounty programs for ongoing testing.

Deliver a compelling product demo that sells. Structure: 1. Set context (recap their pain points). 2. Show the 'aha moment' first (most valuable feature). 3. Walk through their specific use case. 4. Highlight differentiators vs competitors. 5. Address concerns proactively. 6. End with clear next steps. Best practices: customize for audience, use their data/examples, keep to 30 min, make it interactive (ask questions), avoid feature dumping. Follow up with demo recording and trial access. Aim for 40%+ demo-to-opportunity conversion.

A modern remix of 'The Starry Night'. The prompt applies Van Gogh's iconic thick impasto swirls to a futuristic space station orbiting Saturn. Details: 1. Vibrant yellow and blue color palette. 2. Swirling gas clouds and neon rings. 3. Hand-painted brushstroke texture. 4. Dynamic, energetic composition. 5. A masterpiece of AI art history.

Build reliable revenue forecasting system. Forecast categories: Commit (90%+ confidence, MEDDIC qualified). Best Case (50-70% confidence, active engagement). Pipeline (30-50% confidence, early stage). Methodology: 1. Reps submit weekly forecasts by category. 2. Manager reviews with rep 1:1 (challenge assumptions). 3. Roll up to leadership with commentary. 4. Track accuracy weekly (forecast vs. actuals). 5. Calculate variance (over-forecast or under-forecast). Improve accuracy: require evidence for Commit (verbal confirmation, signed terms). Stage-weight deals (10% for discovery, 50% for proposal, 90% for negotiation). CRM hygiene (close dates, next steps, MEDDIC scores current). Sanity check: Commit should be 70-90% of quota monthly. Review missed forecasts in post-mortems.

Generate 10 'Stop the Scroll' hooks for TikTok. Categories: 1. Negative Constraint ('Stop doing X...'). 2. Shocking Fact. 3. The 'Secret' reveal. 4. Immediate Value ('How to X in 10s'). Designed to spike retention in the first 3 seconds of a video. Includes visual placement suggestions for text-on-screen.

Create a detailed competitive feature comparison. Matrix structure: 1. List 5-7 key competitors (rows). 2. Define 15-20 critical features (columns). 3. Score each: ✓ (has), ✗ (missing), ⚠ (partial). 4. Add pricing tier for each feature. 5. Highlight your product's unique features. 6. Identify feature gaps and opportunities. Use color coding for visual clarity. Include market positioning insights. Update quarterly. Use for product strategy and sales enablement.

Street photography shot of a futuristic cyberpunk Tokyo alleyway at night, neon rain reflecting on wet pavement, a cyborg street vendor cooking noodles, steam rising, vibrant teal and magenta lighting, cinematic lighting, shot on 35mm lens, f/1.8, high contrast, photorealistic, 8k --ar 16:9 --v 6.0 --style raw

Analyze change over time using growth curve models. Data structure: repeated measures nested within individuals (Level 1: time, Level 2: person). Models in R lme4 or HLM software: 1. Unconditional growth model: test for linear change over time. 2. Conditional growth models: add predictors of intercept and slope. 3. Piecewise growth: different slopes for different time periods. 4. Nonlinear growth: quadratic, exponential, or logistic growth patterns. Model building: 1. Plot individual trajectories to visualize patterns. 2. Test unconditional means model for ICC. 3. Add time variable, test linear growth. 4. Add predictors systematically. 5. Test model assumptions (linearity, normality, homoscedasticity). Missing data: use maximum likelihood estimation (handles MAR data). Report: fixed effects (average growth), random effects (individual variation), model fit indices (AIC, BIC).

Visualize every touchpoint a customer has with your brand. Phases: Awareness -> Consideration -> Purchase -> Retention -> Advocacy. UI includes: 1. Expandable 'Pain Point' nodes. 2. 'Emotional state' curve chart. 3. Channel breakdown (Ads vs Organic). 4. Key 'Zero Moment of Truth' highlights. Pro-level marketing asset.

Optimize videos for YouTube search. SEO factors: 1. Keyword-rich titles (front-loaded). 2. Detailed descriptions (200+ words). 3. Tags (mix of broad and specific). 4. Custom thumbnails with text. 5. Closed captions and transcripts. 6. Cards and end screens. 7. Playlists for session time. 8. Engagement signals (likes, comments, shares). Use TubeBuddy or VidIQ. Focus on CTR and watch time.

Handle errors and log effectively. Practices: 1. Catch errors at boundaries. 2. Specific error types vs generic. 3. User-friendly error messages. 4. Detailed logs for debugging. 5. Structured logging (JSON). 6. Log levels (ERROR, WARN, INFO, DEBUG). 7. Correlation IDs for tracing. 8. Never log sensitive data. Use Winston, Pino, or similar. Centralize logs with ELK or Datadog. Monitor error rates.

Design a high-converting cold email sequence. 7-email cadence: Email 1: Problem-focused (no pitch). Email 2: Case study/social proof. Email 3: Value proposition. Email 4: Breakup email (last chance). Email 5: Different angle/resource. Email 6: Direct ask for meeting. Email 7: Final touchpoint. Best practices: personalize first line, keep under 100 words, single CTA, A/B test subject lines. Send over 2 weeks. Track open and reply rates. Optimize based on data. Aim for 5-10% reply rate.

A futuristic corporate group photo set in Neo-Tokyo, 2077. Esthetic: 1. Sleek tech-wear business suits with glowing LED piping. 2. Holographic data screens floating between employees. 3. High-altitude boardroom overlooking a rain-slicked neon city. 4. Moody lighting with strong blue and magenta key lights. 5. Ultra-high definition, cinematic composition.

Molecular gastronomy foam for plating. Equipment: immersion blender, lecithin or egg white. Base: any flavorful liquid (soup, juice, reduction). Method: 1. Add 0.5-1% lecithin to liquid. 2. Blend at surface to incorporate air. 3. Let rest 1 minute (large bubbles pop). 4. Scoop fine foam with spoon. Applications: parmesan foam on pasta, beet foam on fish, basil foam on caprese. Stability: serve immediately, soy lecithin for longer hold. Explain surface tension and foam structure. Practice ratios for different densities.

Build an automated data quality monitoring system. Checks to implement: 1. Completeness (null percentage per column). 2. Uniqueness (duplicate detection). 3. Validity (regex patterns, range checks). 4. Timeliness (data freshness alerts). 5. Consistency (cross-table referential integrity). Create a dashboard showing quality scores over time with alerting for threshold breaches. Use Great Expectations or custom Python validators.

Generate 100,000+ high-quality training examples using LLMs. Features: 1. 'Seed data' input. 2. Variation logic (Rewrite, Summarize, Expand). 3. Self-correcting loop to remove bad samples. 4. Progress bar and cost estimator. 5. Download in JSONL/CSV format. Optimized for scale and diversity.

Manage innovation pipeline from idea generation to product launch. Innovation stages: 1. Idea generation: customer feedback, competitor analysis, technology trends. 2. Concept validation: user interviews, prototype testing, market research. 3. Business case development: market size, revenue model, ROI analysis. 4. MVP development: minimum viable product with core features. 5. Market testing: limited release, feedback collection, iteration. 6. Scale-up: full product launch and growth optimization. Stage gates: defined criteria for advancing ideas between stages. Example criteria: Problem validation (100+ customer interviews), Market size ($100M+ TAM), Technical feasibility (prototype built). Resource allocation: 70% sustaining innovation (core product), 20% adjacent opportunities, 10% disruptive bets. Metrics: ideas in pipeline, conversion rates between stages, time-to-market. Portfolio management: balance short-term revenue with long-term growth bets. Innovation culture: hackathons, innovation time, fail-fast mentality.

Master Midjourney prompts for art. Techniques: 1. Descriptive subject and style. 2. Parameters (--ar, --v, --s, --q). 3. Multi-prompts with :: weights. 4. Image prompts for style reference. 5. Negative weights to exclude. 6. Chaos for variety. 7. Stylize for artistic interpretation. 8. Seeds for reproducibility. Use /imagine command and iterate with variations.

Design a motivating sales compensation plan. Components: 1. Base salary (40-60% of OTE). 2. Variable commission (tied to quota attainment). 3. Accelerators (>100% quota achievement). 4. SPIFs for strategic initiatives. 5. Team vs individual targets. Models: straight commission, tiered, revenue vs profit-based. Align with business goals (new logos, expansion, retention). Set achievable quotas (60-80% of reps hit). Pay frequently (monthly). Keep plan simple and transparent. Review annually. Benchmark against industry standards.

Create an engaging feature request response. Components: 1. Thank them for the suggestion. 2. Validate the need they've identified. 3. Explain your product roadmap process. 4. Indicate if it's already planned (with timeline) or under consideration. 5. Invite them to elaborate on use case. 6. Provide link to feature voting/feedback portal. 7. Offer workaround if available. 8. Keep them updated on status. Make them feel heard and valued.

Create an escalation handling process. Protocol: 1. Recognize when escalation is needed. 2. Acknowledge customer's request calmly. 3. Summarize the issue for supervisor. 4. Set expectations for callback/transfer time. 5. Ensure smooth handoff with context. 6. Brief supervisor on customer emotion and history. 7. Follow up after supervisor interaction. 8. Document escalation reason for training. Handle with professionalism and urgency.

Create comprehensive API documentation for a RESTful service. Sections to include: 1. Authentication methods (API key, OAuth 2.0). 2. Endpoint reference with HTTP methods, parameters, and response schemas. 3. Code examples in Python, JavaScript, and cURL. 4. Error codes and troubleshooting guide. 5. Rate limiting and best practices. Use OpenAPI/Swagger spec format with interactive examples. Ensure clarity for both beginner and advanced developers.

Facilitate a low-tech makerspace project inspired by 'Caine's Arcade'. Challenge: 'Design and build an arcade game using only cardboard, recycled materials, and simple craft supplies.' Process (1 week): Day 1: Brainstorming and sketching game ideas. Day 2-3: Prototyping and building. Encourage iteration and problem-solving. Day 4: Peer testing and feedback. Students play each other's games and offer suggestions for improvement. Day 5: 'Arcade Day'. Invite another class to come play the games. Learning Objectives: engineering design process, creativity, collaboration, resilience (learning from failure). Connect to physics concepts like gravity and simple machines.

Design a comprehensive database backup strategy. Components: 1. Automated daily full backups. 2. Incremental backups every 6 hours. 3. Point-in-time recovery capability. 4. Offsite backup storage (S3 Glacier). 5. Encryption at rest and in transit. 6. Backup verification and integrity checks. 7. Documented restore procedures with RTO/RPO. Test restore process monthly. Use tools like pg_dump, mysqldump, or cloud-native solutions. Include retention policies (7 daily, 4 weekly, 12 monthly).

Assist with gift card issues. Guide: 1. How to check balance (website, phone, email). 2. Redemption process step-by-step. 3. Troubleshooting common errors. 4. Combining multiple gift cards. 5. Using gift card with other promotions. 6. Expiration policy. 7. What to do if card isn't working. 8. Replacement for lost/stolen cards. Make it simple and clear.

Handle accessibility requests. Response: 1. Thank them for bringing it to attention. 2. Ask about specific needs. 3. Explain current accessibility features. 4. Provide alternative access methods. 5. Offer personalized assistance. 6. Commit to improvements where needed. 7. Provide direct contact for ongoing support. 8. Follow up on implementation. Show commitment to inclusivity.

Automate server provisioning with Ansible playbooks. Tasks: 1. Install and configure Nginx with SSL. 2. Set up firewall rules (UFW). 3. Configure automatic security updates. 4. Deploy application from Git repository. 5. Set up log rotation and monitoring agents. 6. Create system users with SSH keys. 7. Harden SSH configuration. Use roles for modularity, variables for environment-specific configs, and vault for secrets. Include inventory management and idempotency checks.

Execute impactful product launches. Campaign phases: 1. Pre-launch (teasers, waitlist). 2. Launch day (coordinated announcements). 3. Post-launch (sustained momentum). 4. Multi-channel approach (email, social, PR). 5. Influencer and partner activation. 6. Limited-time offers for urgency. 7. Product demo content. 8. Collect and showcase early reviews. Use Product Hunt for tech products. Create FOMO.

Optimize a slow-running SQL query on a 50M+ row table. Techniques to apply: 1. Add appropriate indexes on WHERE and JOIN columns. 2. Replace subqueries with CTEs (Common Table Expressions). 3. Use EXPLAIN ANALYZE to identify bottlenecks. 4. Partition large tables by date for faster scans. 5. Rewrite correlated subqueries as window functions. Provide before/after execution times and explain each optimization decision.

Generate an image Vertical 9:16 cinematic shot, Adiyogi Shiva statue style, heart of the cosmos background with purple and gold nebula, shimmering divine energy particles, the ultimate epic reveal of Shiva, 8k resolution.

Build an ROI calculator for B2B sales enablement. Inputs: 1. Current state costs (manual processes, errors, time). 2. Implementation costs (software, training, migration). 3. Expected benefits (time savings, error reduction, revenue increase). 4. Timeframe for realization. Outputs: 1. Total cost of ownership (TCO). 2. Net present value (NPV) with discount rate. 3. Payback period in months. 4. 3-year ROI percentage. Create interactive web calculator with shareable results. Include industry benchmarks for credibility.

Master persuasive copywriting using psychological triggers and proven frameworks. AIDA formula: Attention (compelling headline), Interest (hook reader with benefits), Desire (create emotional want), Action (clear call-to-action). PAS structure: Problem (identify pain point), Agitation (amplify consequences), Solution (present your offer). Before/After/Bridge: current state → desired outcome → your product as bridge. Psychological triggers: 1. Scarcity: limited time offers, stock countdown. 2. Social proof: testimonials, user counts, reviews. 3. Authority: expert endorsements, credentials, awards. 4. Reciprocity: free value before asking for purchase. Power words: exclusive, proven, guaranteed, instant, secret, ultimate. Emotional hooks: fear of missing out, desire for status, need for security. A/B testing: headlines (40% impact), calls-to-action (20% impact), body copy structure. Analytics: conversion rates, click-through rates, engagement time. Tools: Google Analytics for tracking, Grammarly for clarity, Hemingway for readability score under 10.

Visualize a complex LangChain agent flow. Flow components: 1. User Input -> Embedding Model. 2. Vector DB (Pinecone) retrieval. 3. LLM (GPT-4) reasoning step. 4. Tool execution (Google Search, Python Repl). 5. Final Output. Use a node-based diagram style with directed arrows and color-coded component boxes.

Optimize sales pipeline in CRM (Salesforce, HubSpot). Best practices: 1. Define clear stage criteria (qualification, demo, proposal, negotiation, closed). 2. Set expected close dates and deal values. 3. Track activities (calls, emails, meetings). 4. Automate follow-up reminders. 5. Forecast revenue by stage probability. 6. Identify bottlenecks and drop-off points. 7. Regular pipeline reviews (weekly). Maintain data hygiene. Archive stale deals. Focus on high-value, high-probability opportunities. Target 3x pipeline coverage.

Technical architectural breakdown of the Burj Khalifa. Visual style: 1. Sleek blueprint aesthetic with blue and white lines. 2. Call-out labels for key levels (Sky lobby, Corporate suites, Observation deck). 3. Cross-section view showing the 'Y-shaped' floor plan. 4. Scale comparison with other global landmarks. 5. Sharp, precise annotations using the 'Nano Banana' technical font.

Optimize productivity by managing energy, not just time. Framework: 1. Identify your peak energy hours (track for 1 week). 2. Schedule deep work during peak times. 3. Batch low-energy tasks (emails, admin) during slumps. 4. Take strategic breaks (90-min work cycles). 5. Manage physical energy (nutrition, hydration, movement). 6. Manage emotional energy (positive people, gratitude). 7. Manage mental energy (single-tasking, minimize decisions). Most people peak mid-morning. Post-lunch dip is normal. Use ultradian rhythms. Protect your best hours. Energy > time for productivity. Based on 'The Power of Full Engagement'.