Trending Prompts

Create custom CMS with Sanity.io. Architecture: 1. Schema definitions with Sanity Studio. 2. Portable Text for rich content. 3. Real-time collaboration. 4. GROQ query language. 5. Custom input components. 6. Image pipeline with hotspot. 7. Versioning and drafts. 8. Live preview integration. Deploy studio separately or with app. Use @sanity/client and implement incremental builds.

Choose Git workflow for team. Strategies: 1. Git Flow (main, develop, feature, release, hotfix). 2. GitHub Flow (main, feature branches, PR). 3. Trunk-based (short-lived branches, frequent merges). 4. Branch naming conventions. 5. Commit message standards. 6. Pull request templates. 7. Protected branches. 8. Squash vs merge commits. Use GitHub Actions or GitLab CI. Automate what you can.

Traditional dumpling pleating technique. Wrapper: round dumpling skin (3-inch). Filling: pork and cabbage (1 tbsp per dumpling). Method: 1. Hold wrapper in left hand. 2. Add filling in center. 3. Fold in half, seal center point. 4. Pleat right side (9 pleats), press to seal. 5. Repeat left side (9 pleats). 6. Final check for air pockets. Cook: boil 6 minutes or pan-fry for potstickers. Key: keep wrappers moist, practice makes perfect. Explain why pleating matters for texture and presentation.

Write a transparent security breach notification. Must include: 1. Clear statement that breach occurred. 2. What data was compromised. 3. What data was NOT affected. 4. Timeline of discovery and response. 5. Immediate actions taken to secure systems. 6. Required customer actions (password reset, monitor accounts). 7. Resources provided (credit monitoring, support line). 8. Commitment to preventing future incidents. Be honest, clear, and action-oriented.

Run efficient, outcome-driven sales meetings. Pre-meeting (24 hours before): send agenda email. 'Looking forward to our call. My understanding is we'll cover: 1. [Agenda item]. 2. [item]. 3. [item]. I'll share [specific outcome]. Please let me know if you'd like to add anything.' Meeting structure: 1. Rapport (2 mins): genuine small talk, reference something personal from LinkedIn. 2. Agenda alignment (1 min): 'I have us for 30 minutes to discuss X, Y, Z. Sound good?' 3. Discovery or demo (20 mins): bulk of meeting. 4. Questions (5 mins): open floor, address concerns. 5. Next steps (2 mins): 'Based on this, what are the next steps?' Schedule next meeting before hanging up. Post-meeting (1 hour after): send recap email with action items, links discussed, calendar hold for next meeting. Use meeting note template in CRM for consistency.

Implement robust error handling in Remix. Patterns: 1. Route-level ErrorBoundary for unexpected errors. 2. useRouteError hook to access error details. 3. CatchBoundary for thrown responses (404, 401). 4. Nested error boundaries for granular recovery. 5. Custom error pages with helpful messages. 6. Error logging to external service. 7. Fallback UI with retry button. 8. Development vs production error display. Use loader error throwers for validation failures and graceful degradation.

Generate breakthrough creative ideas using structured ideation methods. Divergent techniques: 1. Traditional brainstorming: 'yes, and' mentality, no criticism, quantity over quality, aim for 50+ ideas in 30 minutes. 2. SCAMPER method: Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse. 3. Mind mapping: central concept with radiating branches, visual connections between ideas. 4. Random word technique: combine random word with challenge for unexpected associations. Convergent techniques: 1. Dot voting: participants vote on most promising ideas. 2. 2x2 matrix: plot ideas on impact vs. effort axes. 3. Six thinking hats: evaluate ideas from different perspectives (logical, emotional, creative, cautious, optimistic, process). 4. COCD box: track ideas through Concepts, Opportunities, Concerns, Do next steps. Session structure: warm-up exercise (5 min), divergent phase (25 min), convergent phase (20 min), next steps (10 min). Documentation: capture all ideas, photograph session outputs, assign follow-up owners.

Create an auto-response for peak times. Message: 1. Acknowledge receipt of inquiry. 2. Explain higher than normal volume. 3. Provide expected response timeframe. 4. Link to self-service resources (FAQ, knowledge base). 5. Offer alternative contact methods. 6. Provide order status checker if applicable. 7. Thank them for patience. 8. Assure them they haven't been forgotten. Include ticket number for reference.

Request payment method update. Communication: 1. Explain why update is needed (expiration, decline). 2. Provide secure update link. 3. Assure data security measures. 4. Set deadline to avoid service interruption. 5. List accepted payment methods. 6. Offer assistance if they have trouble. 7. Confirm successful update. 8. Thank them for prompt action. Make process secure and simple.

Build type-safe APIs with tRPC. Architecture: 1. Define routers with input/output schemas. 2. Zod for runtime validation. 3. Automatic TypeScript inference. 4. React Query integration for client. 5. Middleware for auth and logging. 6. Context for user sessions. 7. Subscriptions with WebSockets. 8. Error handling with TRPCError. No code generation needed. Use with Next.js or standalone Express server.

Optimize subscription business. Levers: 1. Pricing tiers and packaging. 2. Free trial vs freemium. 3. Seamless signup and payment. 4. Onboarding for activation. 5. Feature gating and upsells. 6. Dunning for failed payments. 7. Pause option instead of cancel. 8. Annual prepay incentives. Focus on LTV:CAC and retention. Monthly vs annual billing considerations. Self-serve vs sales-assisted. Optimize each funnel stage.

Create a secure password reset process. Workflow: 1. Verify customer identity (email, phone, security questions). 2. Explain reset process clearly. 3. Send secure reset link with expiration. 4. Provide alternative methods if email inaccessible. 5. Guide through creating strong password. 6. Confirm successful reset. 7. Suggest enabling 2FA. 8. Provide security best practices. Balance security with user-friendliness.

Address international shipping questions. Cover: 1. Countries you ship to. 2. Shipping methods and carriers. 3. Estimated delivery times by region. 4. Shipping costs and calculation method. 5. Customs and duties responsibility. 6. Tracking availability. 7. Import restrictions or prohibited items. 8. Currency and payment options. Provide country-specific information when possible.

Explain price match policy. Details: 1. Eligible competitors and retailers. 2. Timeframe for price match (before/after purchase). 3. Required proof (screenshot, ad, link). 4. Exclusions (clearance, used, different model). 5. How to submit price match request. 6. Processing time and method of refund. 7. Limitations (one per customer, etc.). 8. Contact for questions. Build trust through transparency.

Create comprehensive recall FAQ. Include: 1. Which products are affected (with images). 2. How to identify if you have affected product. 3. What the safety issue is. 4. What customers should do immediately. 5. Return/refund/replacement options. 6. How to get more information. 7. Timeline for resolution. 8. Contact information for questions. Prioritize clarity and customer safety.

Handle account consolidation. Process: 1. Verify ownership of both accounts. 2. Explain what will be merged (orders, points, preferences). 3. Clarify what cannot be merged. 4. Outline data retention from each account. 5. Confirm which email will be primary. 6. Provide timeline for merger. 7. Explain how to access consolidated account. 8. Follow up to ensure successful merger. Protect data while providing convenience.

Create comprehensive sales playbook for consistency. Sections: 1. ICP and Buyer Personas (who we sell to, pain points, motivations). 2. Value Propositions (core message, differentiation per persona). 3. Sales Process (stages, exit criteria, average time per stage). 4. Methodology (MEDDIC, Challenger, SPIN - which we use). 5. Prospecting (channels, scripts, templates, cadences). 6. Discovery Questions (by persona, problem area). 7. Demo Guidelines (structure, key features to show, customization tips). 8. Objection Handling (top 10 objections, proven responses). 9. Closing Techniques (negotiation tactics, discount policies). 10. Tools and Resources (CRM, sales engagement, enablement content). 11. Metrics and KPIs (what we measure, targets). Format: living Wiki or PDF, searchable, visual (screenshots, flowcharts). Ownership: sales ops maintains, reps contribute. Update: quarterly reviews. Usage: onboarding (week 1 reading), certification (test knowledge), ongoing reference.

Build a framework-agnostic design system with Lit. Components: 1. Custom elements with @customElement decorator. 2. Reactive properties with @property. 3. Shadow DOM for style encapsulation. 4. Slots for content projection. 5. CSS custom properties for theming. 6. Event dispatching with CustomEvent. 7. Form-associated custom elements. 8. TypeScript for type safety. Package as npm library, document with web-component-analyzer, and test with @web/test-runner.

Design a systematic literature review following PRISMA guidelines. Protocol steps: 1. Define research question using PICO framework (Population, Intervention, Comparison, Outcome). 2. Develop search strategy: identify 3-5 databases (PubMed, Scopus, Web of Science), create Boolean search terms, set inclusion/exclusion criteria. 3. Screen titles/abstracts independently by 2 reviewers, resolve conflicts with third reviewer. 4. Full-text review using predefined criteria. 5. Data extraction using standardized forms (study design, sample size, outcomes, bias assessment). 6. Quality assessment using appropriate tools (Cochrane Risk of Bias, Newcastle-Ottawa Scale). 7. Synthesize findings narratively or through meta-analysis if appropriate. Document decisions transparently. Register protocol in PROSPERO before starting.

Design the UI for an AI-powered code generator. Elements: 1. Prompt input field with history and suggestions. 2. Preview window with mobile/desktop viewport toggle. 3. 'Code' tab with syntax highlighting. 4. Version history sidebar. 5. Modern glassmorphism effects and subtle radial gradients in the background.

Craft effective UX copy and microcopy that guides users and reduces friction. Microcopy audit: 1. Error messages: clear explanation of problem + actionable solution. 2. Button labels: specific action verbs (Download Report vs. Click Here). 3. Form instructions: contextual help, inline validation feedback. 4. Empty states: helpful guidance when no content exists. 5. Loading states: progress indication with estimated time. Writing principles: 1. Clarity over cleverness: straightforward language wins over witty copy. 2. User's mental model: use terminology they understand, not internal jargon. 3. Scannable format: bullet points, short sentences, generous white space. 4. Progressive disclosure: reveal information when needed, not all at once. Voice and tone framework: 1. Brand personality: professional, friendly, authoritative (choose 2-3 attributes). 2. Situational adaptation: supportive for errors, encouraging for onboarding. Content testing: 1. A/B testing: button labels, headlines, form instructions. 2. User interviews: comprehension testing, terminology validation. 3. Analytics review: completion rates, drop-off points, support ticket analysis. Tools: Grammarly for clarity, Hemingway for readability, UserVoice for feedback collection.

Design a comprehensive user research interview protocol. Structure: 1. Introduction and rapport building (5 min). 2. Background questions (user context, current workflow). 3. Behavioral questions (tell me about a time...). 4. Pain point exploration (what frustrates you?). 5. Solution validation (prototype feedback). 6. Wrap-up and thank you. Use open-ended questions. Avoid leading questions. Practice active listening. Record with permission. Aim for 30-45 min interviews. Synthesize findings into insights and themes.

Code qualitative data systematically. Process: 1. Familiarize with data (read transcripts multiple times). 2. Generate initial codes (open coding, line-by-line). 3. Organize codes into categories (axial coding). 4. Identify themes and patterns (selective coding). 5. Create codebook with definitions and examples. 6. Code data using software (NVivo, Atlas.ti, MAXQDA). 7. Check inter-rater reliability. 8. Write analytic memos. Use inductive or deductive approach. Ensure saturation. Triangulate with other data sources. Report themes with supporting quotes.

Craft a helpful out-of-stock response. Include: 1. Apologize for unavailability. 2. Explain reason (high demand, seasonal, discontinued). 3. Provide restock date if known. 4. Offer waitlist/notification signup. 5. Suggest similar products with comparison. 6. Highlight benefits of alternatives. 7. Offer discount on alternative as goodwill. 8. Provide easy way to save original item. Turn disappointment into opportunity.

Request customer feedback effectively. Message should: 1. Thank them for being a customer. 2. Explain why feedback matters. 3. Estimate time to complete (keep it short). 4. Assure anonymity if applicable. 5. Highlight how feedback drives improvements. 6. Offer incentive if appropriate (discount, entry to drawing). 7. Make survey mobile-friendly. 8. Provide easy opt-out. Timing is crucial - send after positive interaction.

Handle data privacy requests. Process: 1. Acknowledge request within required timeframe. 2. Verify customer identity securely. 3. Explain what data you hold. 4. Provide data export in readable format. 5. Process deletion requests per policy. 6. Confirm completion of request. 7. Explain data retention requirements. 8. Document all requests for compliance. Follow GDPR/CCPA requirements strictly.

Guide email preference updates. Instructions: 1. Provide link to preference center. 2. Explain different email categories (promotional, transactional, newsletters). 3. Allow granular control over frequency. 4. Offer digest options instead of unsubscribe. 5. Respect unsubscribe requests immediately. 6. Confirm preference changes. 7. Explain which emails they'll still receive (account-related). 8. Make it easy to update anytime. Respect their communication preferences.

Design a high-converting pricing page using Tailwind CSS v3.4 and DaisyUI 4.0. Feature three tiers: Starter, Pro, and Enterprise. Requirements: 1. Smooth hover scaling effects on the 'Pro' card. 2. A monthly/yearly toggle switch that updates prices with a transition. 3. Gradient borders for the featured plan. 4. Fully responsive flexbox layout. 5. Use primary/secondary theme colors consistently.

A landing page section testing 3 different pricing psychological effects: 1. The Decoy Effect (Added a dummy plan). 2. Anchoring (High original price slashed). 3. Scarcity (Only 5 spots left). Detailed documentation on which cognitive biases each section targets and how to measure the lift in A/B tests.

Use Google's Gemini for multimodal AI. Capabilities: 1. Text and image input simultaneously. 2. Vision understanding for analysis. 3. Long context window (up to 1M tokens). 4. Function calling support. 5. Code generation and execution. 6. Gemini Pro vs Ultra models. 7. Streaming responses. 8. Safety settings configuration. Use for image captioning, OCR, and visual Q&A.

Write effective press releases that capture media attention and drive coverage. Press release structure: 1. Headline: newsworthy, keyword-rich, under 70 characters. 2. Dateline: location and release date. 3. Lead paragraph: who, what, when, where, why in first 25 words. 4. Body paragraphs: supporting details, quotes, background information. 5. Boilerplate: company description, contact information. Newsworthiness factors: 1. Timeliness: recent events, trending topics. 2. Impact: affects large audience or important outcomes. 3. Proximity: local interest, geographic relevance. 4. Prominence: recognizable names, industry leaders. 5. Conflict: disputes, competitive dynamics. Quote integration: 1. Executive quotes: strategic vision, company positioning. 2. Expert quotes: industry context, technical explanation. 3. Customer quotes: real results, user experience. Distribution strategy: 1. Media list building: relevant journalists, industry publications. 2. Personalized outreach: target specific beats, reference recent articles. 3. Timing optimization: Tuesday-Thursday, 10am-2pm for maximum attention. Follow-up process: 1. One week follow-up: brief check-in, additional information offer. 2. Exclusive offers: special access, interviews, additional data.

The Zen of lunch. A beautifully arranged Japanese Bento box. Includes: 1. Salmon teriyaki, sushi, tamagoyaki, and pickled vegetables. 2. Perfectly compartmentalized sections. 3. Natural wood box texture. 4. Soft, overhead natural lighting (morning sun). 5. Focus on the harmony of colors and textures (green, pink, orange, white).

Draft a high-performance React 19 Server Component for a 'Product Listing' page. Use the new 'use()' hook for data fetching and 'Suspense' for granular loading states. Implement a skeleton loader that matches the final UI layout. Ensure the component is 'async' and handles empty states and error boundaries gracefully. Focus on minimal client-side JS bundle size.

Design balanced sales territories for maximum coverage. Methodology: 1. Analyze market potential by geography/industry/company size. 2. Assess current account distribution and revenue. 3. Define territory boundaries (geographic, vertical, account-based). 4. Balance workload and opportunity across reps. 5. Assign accounts based on rep skills and relationships. 6. Set territory-specific quotas. 7. Plan for coverage gaps and transitions. Use CRM data and market intelligence. Minimize disruption to customer relationships. Review semi-annually. Aim for <20% variance in territory potential.

Classic French omelette mastery. Eggs: 3 large, whisked with salt. Pan: 8-inch nonstick, medium-high heat, butter. Technique: 1. Swirl butter to coat. 2. Add eggs, immediately stir vigorously with fork. 3. Shake pan while stirring (30 seconds). 4. Smooth surface, let set 5 seconds. 5. Tilt pan, roll omelette using fork. 6. Shape into oval log. Result: pale yellow (no browning), creamy interior. Filling: herbs, cheese, added before rolling. Explain protein coagulation and achieving baveuse (flowing) center.

Generate a viral LinkedIn professional story. Structure: 1. The 'Hook' (Controversial or counter-intuitive insight). 2. The 'Conflict' (Personal or business crisis). 3. The 'Solution' (3 actionable takeaways). 4. The 'Outcome' (Hard numbers/metrics). 5. The 'Call to Engagement' (Question to the audience). Expert tone, formatted for high readability on mobile.

Equip sales team with competitive intelligence. Battlecard structure per competitor: 1. Company overview (size, funding, target market). 2. Strengths (what they do well, when they win). 3. Weaknesses (gaps, common complaints). 4. Differentiation (why you win against them). 5. Objection traps (questions to ask that expose weaknesses). 6. Proof points (case studies where you won against them). 7. Pricing comparison. Research sources: G2 reviews, Reddit discussions, sales calls (ask 'who else are you evaluating?'), competitor websites, former employees. Update quarterly. Make easily accessible (Wiki, PDF with search). Train reps on delivery: never bash competitor, focus on your strengths. Landmine questions: 'How important is [feature they lack] to you?'

Apply design patterns to solve common problems. Creational: 1. Singleton (single instance). 2. Factory (object creation). 3. Builder (complex object construction). Structural: 4. Adapter (interface compatibility). 5. Decorator (add behavior dynamically). 6. Facade (simplified interface). Behavioral: 7. Observer (event notification). 8. Strategy (interchangeable algorithms). 9. Command (encapsulate requests). 10. Template Method (algorithm skeleton). Don't force patterns - use when appropriate. Understand problem first. Patterns improve communication ('let's use Observer here'). Study Gang of Four book. Practice with real examples.

Create a comprehensive PRD (Product Requirements Document) template. Sections: 1. Executive Summary (Problem, Solution, Success Metrics). 2. User Stories and Personas. 3. Functional Requirements (Must-have vs Nice-to-have). 4. Technical Constraints and Dependencies. 5. Success Criteria and KPIs. 6. Timeline and Milestones. 7. Open Questions and Risks. Use clear, unambiguous language. Include wireframes placeholders and acceptance criteria for each requirement.

Manage complex research projects with multiple phases and stakeholders. Project planning: 1. Work breakdown structure: divide project into manageable tasks. 2. Dependencies: identify which tasks must be completed before others can start. 3. Critical path: sequence of tasks that determines minimum project duration. 4. Resource allocation: personnel, equipment, funding by time period. Timeline development: 1. Start with fixed deadlines (conference presentations, grant reports). 2. Work backwards to determine intermediate milestones. 3. Build in buffer time: 20-30% additional time for unexpected delays. 4. Plan for seasonal variations: holiday breaks, summer schedules. Tools: 1. Gantt charts: Microsoft Project, Smartsheet for visual timelines. 2. Agile methods: Scrum for iterative development with regular check-ins. 3. Risk management: identify potential problems and mitigation strategies. Communication: 1. Weekly team meetings with status updates. 2. Monthly steering committee reports. 3. Quarterly stakeholder briefings. Change management: formal process for protocol modifications, budget amendments.

Get structured data from LLMs with Instructor. Pattern: 1. Define Pydantic models for output. 2. Use instructor.patch() on OpenAI client. 3. LLM returns validated objects. 4. Automatic retry on validation errors. 5. Partial streaming for progressive updates. 6. Union types for multiple formats. 7. Nested models for complex data. 8. Field descriptions guide LLM. Type-safe LLM outputs. Use for data extraction and classification.

Design an effective academic conference poster. Layout: 1. Title, authors, affiliations (top, large font). 2. Introduction (brief background, research question). 3. Methods (concise, visual). 4. Results (emphasis on figures and tables). 5. Conclusions (key takeaways, implications). 6. References and acknowledgments. Design principles: readable from 6 feet, 40-50% white space, consistent color scheme, minimal text, high-quality graphics. Size: typically 48"×36". Use templates from PowerPoint or Adobe Illustrator. Practice 2-minute elevator pitch. Bring business cards.

Write a compelling research grant proposal. Sections: 1. Abstract (200 words, standalone summary). 2. Significance (why this research matters). 3. Innovation (novel approach or contribution). 4. Approach (methodology, timeline, feasibility). 5. Preliminary Data (proof of concept). 6. Research Team (qualifications, roles). 7. Budget and Justification. 8. References. Follow funder guidelines precisely. Address review criteria. Use clear, accessible language. Include visual diagrams. Highlight broader impacts. Get feedback from colleagues. Submit early.

Reduce BigQuery costs for a high-volume analytics workload. Strategies: 1. Partition tables by date and cluster by high-cardinality columns. 2. Use materialized views for frequently-run aggregations. 3. Implement query result caching and avoid SELECT *. 4. Set up cost controls with custom quotas per project. 5. Analyze query execution plans to identify expensive operations. Provide before/after cost comparison and ROI calculation. Include monitoring dashboard for ongoing cost tracking.

Measure and validate product-market fit. Indicators: 1. Sean Ellis test (% users 'very disappointed' if product disappeared >40%). 2. Retention cohorts (flattening curve after initial drop). 3. Organic growth rate (word-of-mouth, low CAC). 4. NPS score (>50 is excellent). 5. Sales cycle length (decreasing over time). 6. Customer feedback themes (solving real pain). Conduct surveys and analyze usage data. If PMF not achieved, pivot or iterate. Document assumptions and validate continuously.

Synthesize customer feedback into actionable insights. Sources: 1. User interviews and surveys. 2. Support tickets and chat logs. 3. App store reviews and social media. 4. Sales call notes and lost deals. 5. Usage analytics and session recordings. Process: Tag feedback by theme. Quantify frequency and impact. Identify patterns and root causes. Prioritize by strategic importance. Create insights report with quotes and data. Share with stakeholders. Convert insights into product roadmap items. Close the loop with customers.

Apply a realistic thunderstorm effect to any outdoor scene. Features: 1. Forked lightning bolts with a purple-white core. 2. Realistic 'wet' surface reflections on the ground. 3. Heavy rain streaks with motion blur. 4. Dramatic, darkened cloud structures. 5. Fog and mist for atmospheric depth. 100% weather accuracy using 'Nano Banana' meteorology logic.

Write high-converting copy for a SaaS landing page. Structure: 1. Hero headline using the 'outcome + timeframe' formula. 2. Subheadline addressing the main pain point. 3. Three benefit-focused feature blocks (not feature-focused). 4. Social proof section with specific metrics. 5. Two CTAs: primary (Start Free Trial) and secondary (Watch Demo). Use power words, active voice, and address objections preemptively. Target B2B decision-makers.

Create a digital escape room for a unit review using Google Forms. Theme: 'Escape the Mad Scientist's Lab' for a science unit. Structure: 1. Create a Google Form with multiple sections. 2. Set up 'response validation' for each question, so students can only proceed to the next section if they answer correctly. This acts as the 'lock'. 3. The questions are puzzles related to the unit content (e.g., a riddle about mitosis, a coded message with vocabulary words). 4. The final section reveals a 'You Escaped!' message. 5. Use a storyline to connect the puzzles. Share the form with students to complete in small groups. Promotes collaboration, problem-solving, and engagement.

Write effective unit tests with TDD approach. TDD cycle: 1. Red (write failing test). 2. Green (write minimal code to pass). 3. Refactor (improve code while keeping tests green). Best practices: Test one thing per test. Use AAA pattern (Arrange, Act, Assert). Descriptive test names (should_returnTrue_when_inputIsValid). Mock external dependencies. Aim for 80%+ code coverage. Fast tests (<1 sec). Independent tests (no order dependency). Use test fixtures for setup. Frameworks: Jest, Pytest, JUnit. Benefits: confidence in changes, living documentation, better design.