Trending Prompts

Build autonomous agents with AutoGPT. Architecture: 1. Goal-oriented task decomposition. 2. Self-critique and iteration. 3. Memory management (short/long-term). 4. Tool usage (web search, file ops). 5. Code execution capability. 6. Human-in-loop checkpoints. 7. Budget constraints for API calls. 8. Plugin system for extensions. Agents plan and execute multi-step tasks independently.

Design effective onboarding. Program: 1. Pre-boarding (before day 1). 2. Day 1 welcome and setup. 3. Week 1 (company culture, meet team). 4. Month 1 (role training, quick wins). 5. 90-day plan with checkpoints. 6. Buddy system for support. 7. Feedback loops. 8. Documentation and resources. Use onboarding software. Create checklist. Measure time-to-productivity. Great onboarding improves retention.

Implement an embedded Stripe Checkout experience. Requirements: 1. 'Pay' button that triggers a server action to create a checkout session. 2. Handle 'success' and 'cancel' redirect URLs. 3. Show a loading spinner during session creation. 4. Use Stripe Elements for a custom-styled card entry field that matches the site's DaisyUI theme. 5. Webhook listener for 'checkout.session.completed' events.

Design a serverless application on AWS. Architecture: 1. API Gateway for HTTP endpoints. 2. Lambda functions for business logic (Node.js/Python). 3. DynamoDB for NoSQL storage. 4. S3 for file uploads with presigned URLs. 5. EventBridge for scheduled tasks. 6. SQS for async processing. 7. CloudWatch for logs and metrics. Use SAM or Serverless Framework for deployment. Implement proper error handling, retries, and dead-letter queues. Include cost optimization strategies (provisioned concurrency, reserved capacity).

Turn your selfie into a Pixar-style Zootopia animal character. Logic: 1. Identify characteristic facial features (eyes, nose shape). 2. Map features to a chosen animal (e.g., Fox, Bunny, Sloth). 3. Render high-quality fur and expressive anthropomorphic eyes. 4. Matching clothing from the original selfie. Ultra-high fidelity, 3D animated look.

Master the sales discovery call using BANT framework. Structure: 1. Build rapport and set agenda (5 min). 2. Budget (what's allocated for this problem?). 3. Authority (who makes the decision?). 4. Need (what's the pain point and impact?). 5. Timeline (when do you need this solved?). Use open-ended questions. Practice active listening. Take detailed notes. Identify red flags early. Qualify or disqualify quickly. End with clear next steps. Aim for 30-45 min calls. Follow up within 24 hours with summary email.

Design microservices architecture effectively. Principles: 1. Single Responsibility (one service, one business capability). 2. Decentralized Data (each service owns its database). 3. API Gateway (single entry point). 4. Service Discovery (Consul, Eureka). 5. Asynchronous Communication (message queues, events). 6. Circuit Breaker (fault tolerance). 7. Containerization (Docker, Kubernetes). Challenges: distributed tracing, data consistency, testing. Use API versioning. Implement health checks. Centralized logging (ELK). Monitoring (Prometheus, Grafana). Start with monolith, extract services gradually. Not always the right choice - consider team size and complexity.

The chaotic beauty of an Indian street food stall. Action: 1. Mixing layers of papdi, potatoes, chickpeas, curd, and chutneys. 2. A sprinkle of spicy 'sev' in mid-air. 3. Vibrant colors (Red chili, green mint, white yogurt). 4. Close-up of hands working rapidly. 5. Shallow depth of field focusing on the ingredients.

Create images with DALL-E 3 API. Features: 1. Enhanced prompt understanding. 2. Higher fidelity and detail. 3. Better text rendering in images. 4. Size options (1024x1024, 1792x1024). 5. Quality parameter (standard/hd). 6. Style parameter (vivid/natural). 7. Error handling for content policy. 8. Cost optimization strategies. Use detailed prompts and implement batch processing for multiple images.

The perfect ramen 'noodle-pull'. 1. Chopsticks lifting a large clump of springy, yellow noodles from a steaming tonkotsu broth. 2. Broth glistening on the noodles. 3. Soft-boiled egg (nitamago) yolk slowly drizzling. 4. Steam rising into the light. Warm, cozy, and highly appetizing 4K close-up.

Write engaging sports content that combines analysis with compelling narrative storytelling. Game story structure: 1. Lead: game outcome, key moment, standout performance (25 words). 2. Turning point: crucial play, momentum shift, decisive factor. 3. Statistical support: relevant numbers that tell the story. 4. Player analysis: individual performances, quotes, reactions. 5. Broader context: season implications, record impacts. Play-by-play writing: 1. Action description: vivid, immediate, present tense preferred. 2. Strategic analysis: why plays worked/failed, tactical decisions. 3. Momentum tracking: emotional shifts, crowd reactions, energy changes. 4. Key moments: game-changing plays, critical errors, clutch performances. Player profiles: 1. Background story: journey to current position, obstacles overcome. 2. Playing style: technical skills, unique abilities, signature moves. 3. Personality: interviews revealing character, motivations, goals. 4. Impact analysis: team contribution, statistical achievements. Sports terminology: 1. Accurate use: proper technical terms, position names, rules. 2. Accessibility: explain complex concepts for casual fans. 3. Avoid clichés: fresh descriptions of common situations. Interview techniques: open-ended questions, locker room access, post-game emotions, follow-up clarifications for accuracy.

Implement automated performance testing using JMeter and cloud scaling for application performance validation. JMeter test automation: 1. Test plan structure: thread groups, samplers, listeners, assertions for validation. 2. Parameterization: CSV data files, random variables, dynamic request generation. 3. CI/CD integration: headless execution, result analysis, performance regression detection. 4. Distributed testing: master-slave configuration for high-load simulation. Performance test types: 1. Load testing: normal expected load (1000 concurrent users), steady state performance. 2. Stress testing: breaking point identification, failure mode analysis, recovery testing. 3. Spike testing: sudden traffic increases, autoscaling validation, resource exhaustion scenarios. 4. Volume testing: large data set processing, database performance, storage capacity. Metrics and SLAs: 1. Response time: 95th percentile <500ms, average <200ms, maximum <2s. 2. Throughput: requests per second targets, sustained load capability. 3. Error rate: <0.1% for successful operations, graceful degradation under load. 4. Resource utilization: CPU <70%, memory <85%, database connections <80% of pool. Cloud-based testing: 1. AWS Load Testing Solution: distributed load generation, real-time monitoring. 2. Azure DevOps Load Testing: cloud-scale testing, geographic distribution. 3. GCP Cloud Load Testing: global load simulation, auto-scaling validation. Automated analysis: 1. Baseline comparison: performance trends, regression detection, alerting. 2. Report generation: HTML reports, trend analysis, SLA compliance verification. Integration testing: API performance, database query optimization, caching effectiveness, CDN performance validation.

Handle crises with communication plan. Framework: 1. Identify potential crises. 2. Crisis response team. 3. Communication protocols (who says what, when). 4. Internal communication first. 5. External stakeholder messaging. 6. Media strategy if needed. 7. Social media monitoring and response. 8. Post-crisis review. Be transparent, quick, and empathetic. Have templates ready. Practice scenarios. Speed matters.

Extract insights from won and lost deals. Interview timing: 2-4 weeks after decision (emotions settled, memory fresh). Conductor: neutral party (product manager, not account exec). Questions for wins: 1. Why did you choose us? 2. What almost made you choose competitor? 3. How was the buying process? 4. What could we improve? Questions for losses: 1. Why did you choose competitor? 2. What could we have done differently? 3. How did competitors differentiate? 4. Would you consider us in future? Document verbatim quotes. Identify patterns across 10+ interviews. Common themes: pricing, features, support, trust. Share findings with product, marketing, sales teams quarterly. Adjust messaging, product roadmap, sales process.

Build a modern shopping cart using Vue 3 Composition API. Features: 1. Reactive cart state with Pinia store. 2. Add/remove items with smooth transitions. 3. Quantity adjustments with debounced updates. 4. Price calculations including tax and shipping. 5. Persistent cart using localStorage. 6. Empty state with product recommendations. 7. Checkout button with loading state. Use Tailwind for styling and Vueuse for composable utilities. Implement optimistic UI updates for better UX.

Implement SWR for optimal data experience. Pattern: 1. useSWR hook with cache key. 2. Return stale data immediately. 3. Revalidate in background. 4. Dedupe simultaneous requests. 5. Focus revalidation. 6. Interval polling for real-time feel. 7. Error retry with exponential backoff. 8. Mutation with useSWRMutation. Use globally for all requests and implement dependent fetching for serial queries.

Set up comprehensive monitoring with Prometheus and Grafana. Components: 1. Prometheus server with service discovery. 2. Node Exporter for system metrics. 3. Application instrumentation with custom metrics. 4. Alertmanager for notifications (PagerDuty, Slack). 5. Grafana dashboards for visualization (RED metrics, resource usage). 6. Recording rules for aggregations. 7. Alert rules for SLO violations. Use Docker Compose for local setup. Include retention policies and high-availability configuration.

Validate and sanitize user input. Techniques: 1. Whitelist allowed input. 2. Validate data types and formats. 3. Length restrictions. 4. Regex for pattern matching. 5. Sanitize HTML to prevent XSS. 6. Parameterized queries for SQL injection. 7. Validate on client AND server. 8. Contextual output encoding. Use libraries like Joi, Yup, or validator.js. Never trust user input. Fail securely.

Design integrated DevOps toolchain for seamless automation workflow from development to production deployment. Toolchain architecture: 1. Source control: Git (GitHub/GitLab/Bitbucket), branching strategies, merge request workflows. 2. CI/CD: Jenkins/GitLab CI/GitHub Actions, pipeline orchestration, parallel job execution. 3. Artifact management: Nexus/Artifactory for binaries, container registries, dependency caching. 4. Testing: unit testing (JUnit), integration testing, security scanning, performance testing. Tool integration patterns: 1. API-first approach: REST APIs for tool communication, webhook integration, event-driven automation. 2. Data pipeline: metrics aggregation, log correlation, traceability across tools. 3. Single sign-on: LDAP/SAML integration, unified authentication, role-based access control. Automation workflows: 1. Code commit triggers: automated builds, test execution, code quality analysis. 2. Deployment automation: environment promotion, configuration management, rollback procedures. 3. Infrastructure provisioning: Terraform integration, cloud resource management, compliance checking. Configuration management: 1. Environment consistency: infrastructure as code, configuration drift detection. 2. Secret management: Vault integration, automated credential rotation, secure parameter passing. 3. Feature flags: LaunchDarkly/Split integration, gradual rollouts, instant rollbacks. Monitoring integration: 1. Observability: APM tools, distributed tracing, synthetic monitoring. 2. Alerting: PagerDuty integration, escalation procedures, incident response automation. Tool evaluation: ROI analysis, team adoption, vendor lock-in assessment, migration strategies, training requirements for successful implementation.

Professional catering event planning. Timeline 100-person wedding buffet: Day before: shop, prep vegetables, make sauces, bake desserts. Event day: -4 hours: arrive, set up kitchen. -3 hours: start cooking proteins. -2 hours: finish sides, keep warm. -1 hour: set buffet, chafing dishes. Service: replenish as needed, clear plates. Staffing: 1 chef, 2 cooks, 3 servers. Equipment: warmers, coolers, transport containers. Checklist: permits, insurance, contracts. Calculate food quantities: 1.5 servings per person. Explain flow, timing, and contingency planning.

Implement progressive enhancement with htmx. Pattern: 1. Server-rendered HTML with hx-get attributes. 2. Partial page updates without full reload. 3. hx-trigger for various events (click, scroll, intersect). 4. hx-swap strategies (innerHTML, outerHTML, beforeend). 5. Loading indicators with hx-indicator. 6. Form validation with server-side logic. 7. WebSocket updates with hx-ws. 8. Graceful fallback for no-JS scenarios. Use with Express or Django for HTML-over-the-wire architecture.

Conduct an outdoor lesson in a schoolyard or local park. Topic: Ecosystems. Activity: 'Bio-Blitz'. 1. Preparation: Define a 10x10 meter area. Provide students with field guides, magnifying glasses, and data collection sheets. 2. The Blitz (30 mins): In small groups, students identify and count as many different species of plants and animals as they can find in their designated area. They can use apps like iNaturalist for identification. 3. Data Analysis (15 mins): Back in the classroom, groups pool their data to calculate the biodiversity of the area. Create a food web diagram based on the organisms they found. 4. Reflection (10 mins): Discuss human impact on the local ecosystem. Fosters observation skills, appreciation for nature, and understanding of ecological concepts.

Create engaging children's books with age-appropriate content and developmental considerations. Age group specifications: 1. Picture books (3-5 years): 300-800 words, simple concepts, repetitive language. 2. Early readers (6-8 years): 1000-2500 words, larger text, basic vocabulary. 3. Chapter books (7-10 years): 10,000-15,000 words, short chapters, illustrations. 4. Middle grade (8-12 years): 30,000-50,000 words, complex themes, character growth. Story elements: 1. Relatable protagonist: child or child-like character facing age-appropriate challenges. 2. Clear conflict: problem child can understand and engage with emotionally. 3. Positive resolution: hope, growth, learning without being preachy. 4. Action and dialogue: show rather than tell, keep narrative moving. Language considerations: 1. Vocabulary level: appropriate for reading ability, introduce new words gradually. 2. Sentence structure: shorter sentences for younger readers, variety for older. 3. Rhythm and flow: read aloud appeal, natural speech patterns. Educational value: 1. Social skills: friendship, cooperation, empathy, problem-solving. 2. Emotional intelligence: identifying feelings, coping strategies. 3. Diversity: inclusive characters, cultures, family structures. Publishing format: manuscript preparation, illustration notes, target market identification.

Master Git for effective collaboration. Workflow: 1. Feature branches (git checkout -b feature/new-feature). 2. Commit often with clear messages (feat:, fix:, docs:). 3. Pull before push (git pull --rebase). 4. Code review via pull requests. 5. Squash commits before merge. 6. Delete merged branches. 7. Tag releases (v1.0.0). Commit message format: type(scope): subject. Use .gitignore. Never commit secrets. Interactive rebase for clean history (git rebase -i). Resolve conflicts carefully. Use git stash for WIP. Learn: git log, git blame, git bisect. Branching strategies: Git Flow, GitHub Flow.

Handle damaged product claims. Process: 1. Express concern and apologize. 2. Request photos of damage. 3. Verify order details. 4. Explain replacement options (same item, refund, credit). 5. Arrange return shipping (prepaid label). 6. Expedite replacement shipment. 7. Waive any restocking fees. 8. Follow up to ensure satisfaction. Make it hassle-free to maintain trust.

Create and manage Personalized Learning Plans (PLPs) for middle school students. PLP Document Components: 1. Student Profile: Strengths, interests, learning preferences. 2. Academic Goals: 1-2 SMART goals for ELA and Math, co-created by student and teacher. 3. Personal Goals: A goal related to a personal interest or career aspiration. 4. Action Steps: Specific actions the student will take to meet their goals (e.g., 'I will use Khan Academy for 20 minutes twice a week'). 5. Progress Monitoring: How progress will be tracked (e.g., test scores, portfolio review). Process: 1. Initial goal-setting conference with student and parents. 2. Student and advisor check in on progress bi-weekly. 3. Formal review and goal update at the end of each quarter. Fosters student agency and goal-setting skills.

Design statistically valid A/B tests for product features. Pre-test setup: 1. Define hypothesis clearly (adding reviews will increase conversion by 15%). 2. Choose primary metric (conversion rate, not multiple metrics to avoid false positives). 3. Calculate sample size: use online calculators, typically need 1000+ conversions per variant for significance. 4. Set test duration: run for full business cycles (include weekends), minimum 1-2 weeks. 5. Define success/failure criteria upfront. Implementation: 50/50 random split, ensure consistent user experience across sessions. Analysis: statistical significance (p<0.05), confidence intervals, practical significance (is 2% lift worth engineer time?). Avoid peeking at results mid-test. Tools: Optimizely, Google Optimize, VWO, internal feature flags. Document learnings for future tests.

Communicate backorder status. Update: 1. Acknowledge item is backordered. 2. Explain reason for backorder. 3. Provide current estimated arrival date. 4. Offer to notify when item arrives. 5. Present alternative in-stock options. 6. Allow easy cancellation if desired. 7. Guarantee original price if they wait. 8. Update proactively if timeline changes. Keep customers informed and give them choices.

Science of flavor pairing and affinity. Principle: ingredients with shared flavor compounds pair well. Coffee + chocolate: both contain pyrazines (roasted, nutty notes). Other natural pairs: tomato + basil, strawberry + balsamic, pork + apple. Flavor wheel: use to identify complementary flavors. Contrasting pairs: sweet + salty, acid + fat. Applications: menu development, dessert creation, cocktails. Database: foodpairing.com for molecular analysis. Experiment: taste, document, iterate. Explain volatile compounds, aroma, and taste vs flavor difference.

Build a systematic cold email testing program. Setup: 1. Define hypothesis (subject line, CTA, length). 2. Split list into equal segments (minimum 100 contacts each). 3. Send variant A to segment 1, variant B to segment 2. 4. Wait 3-5 days for statistical significance. 5. Measure open rate, reply rate, meeting booked rate. 6. Calculate winner (minimum 95% confidence). 7. Roll out winner to remaining list. Variables to test: personalization depth, value proposition clarity, email length (50 vs 150 words), CTA placement. Use Lemlist or Woodpecker for tracking. Document learnings in playbook.

Write effective code documentation. Levels: 1. Code comments (explain why, not what - complex logic only). 2. Function/method docs (parameters, return values, exceptions - JSDoc, docstrings). 3. README (setup, usage, examples). 4. API documentation (OpenAPI/Swagger for REST). 5. Architecture docs (system design, diagrams). 6. Changelog (version history). Best practices: Keep docs close to code. Update with code changes. Use examples. Avoid obvious comments. Document assumptions and edge cases. Use diagrams (C4 model, UML). Tools: Sphinx, Doxygen, MkDocs. Good code is self-documenting, but docs add context.

Structure an effective 60-minute PLC meeting for a grade-level team. Protocol: 'Tuning Protocol' for examining student work. Agenda: 1. Welcome & Norms Review (5 mins). 2. Data Dive (15 mins): Review common formative assessment data. Identify one specific area of student struggle. 3. Presenting Teacher (15 mins): One teacher presents a lesson plan and samples of student work related to the struggle area. Asks a focusing question (e.g., 'How can I better support my English learners in this task?'). 4. Clarifying & Probing Questions (10 mins): Team asks questions to better understand the work. 5. Feedback & Discussion (10 mins): Team provides warm and cool feedback focused on the work, not the teacher. 6. Action Steps & Closing (5 mins): Team commits to trying one new strategy. Roles: facilitator, timekeeper, note-taker.

Implement RAG with Pinecone. Architecture: 1. Document chunking and embedding. 2. Store embeddings in Pinecone index. 3. Semantic search with similarity. 4. Metadata filtering for context. 5. Hybrid search (dense + sparse). 6. Retrieve top-k relevant chunks. 7. Augment prompt with context. 8. Generate answer with LLM. Use text-embedding-ada-002 and implement re-ranking for accuracy.

Implement Weaviate for semantic search. Features: 1. Schema definition for classes. 2. Automatic vectorization. 3. GraphQL API for queries. 4. Hybrid search (vector + keyword). 5. Cross-references between objects. 6. Generative search with LLMs. 7. Multi-tenancy support. 8. Modules for ML models. Use for knowledge graphs with semantic capabilities and implement question answering.

Generate a comprehensive troubleshooting guide. Format: 1. Common symptoms/problems listed clearly. 2. Step-by-step diagnostic questions. 3. Simple solutions for each issue. 4. Visual aids or diagrams where helpful. 5. 'If this doesn't work' escalation path. 6. Safety warnings if applicable. 7. When to contact support. 8. Video tutorial links. Use numbered steps, clear language, and avoid technical jargon.

Provide installation assistance. Guide: 1. Assess customer's technical skill level. 2. Provide step-by-step instructions. 3. Include visual aids (photos, videos, diagrams). 4. List required tools and materials. 5. Highlight safety precautions. 6. Troubleshoot common installation issues. 7. Offer professional installation option. 8. Provide support contact during installation. Make complex installations manageable.

Master Facebook Ads targeting. Tactics: 1. Core audiences (demographics, interests, behaviors). 2. Custom audiences (website visitors, customer list). 3. Lookalike audiences from best customers. 4. Interest layering for precision. 5. Exclude converters to avoid waste. 6. Campaign Budget Optimization. 7. Creative testing with DCO. 8. Conversion API for accurate tracking. Use Advantage+ campaigns and implement retargeting funnels.

Design eco-friendly packaging that balances sustainability with brand appeal and function. Sustainable materials: 1. Recycled content: minimum 30% post-consumer recycled materials. 2. Biodegradable options: plant-based plastics, mushroom packaging, seaweed wraps. 3. Minimalist approach: reduce material usage by 20-30% through design optimization. 4. Mono-materials: single material type for easier recycling (all paper vs. mixed materials). Design strategies: 1. Right-sizing: eliminate unnecessary packaging volume, optimize for shipping efficiency. 2. Modular design: reusable components, refillable containers. 3. Flat-pack solutions: reduce shipping volume by 40-60%. 4. Digital integration: QR codes replace printed instructions, reducing paper usage. Lifecycle considerations: 1. End-of-life planning: clear recycling instructions, compostable timeframes. 2. Supply chain optimization: local sourcing to reduce transportation impact. 3. Consumer education: visual guides for proper disposal. Certification targets: FSC certification for paper, Cradle to Cradle for overall sustainability. Testing: structural integrity with reduced materials, consumer usability studies.

Optimize writing productivity through effective workflow and time management strategies. Daily writing routine: 1. Consistent schedule: same time daily for habit formation. 2. Writing environment: dedicated space, minimal distractions. 3. Daily targets: word count goals (500-2000 words depending on project). 4. Warm-up exercises: freewriting, prompts, editing previous day's work. Productivity techniques: 1. Pomodoro Technique: 25-minute focused writing sessions with 5-minute breaks. 2. Time blocking: dedicated hours for different writing tasks. 3. Batch processing: similar tasks together (research, outlining, drafting). 4. Deep work sessions: 2-4 hour uninterrupted writing blocks. Project management: 1. Outline development: detailed structure before drafting. 2. Milestone tracking: chapter completion, word count progress. 3. Deadline planning: working backwards from submission dates. 4. Version control: organized file naming, backup systems. Workflow optimization: 1. Research phase: gather all materials before writing begins. 2. Draft separation: write first, edit later to avoid perfectionism paralysis. 3. Review cycles: structured editing passes for different issues. Tools: Scrivener for organization, Focus apps for distraction blocking, time tracking for productivity analysis.

Implement centralized logging with ELK Stack (Elasticsearch, Logstash, Kibana) for comprehensive log analysis and troubleshooting. ELK Stack architecture: 1. Elasticsearch: distributed search engine, 3-node cluster minimum, data replication factor 1. 2. Logstash: log processing pipeline, input plugins, filters, output destinations. 3. Kibana: data visualization, dashboard creation, alerting, user authentication. 4. Beats: lightweight data shippers (Filebeat, Metricbeat, Packetbeat, Auditbeat). Log collection strategy: 1. Application logs: structured JSON logging, log levels (DEBUG, INFO, WARN, ERROR), correlation IDs. 2. System logs: syslog collection, OS metrics, service status, security events. 3. Infrastructure logs: load balancer access logs, database query logs, container logs. Data lifecycle management: 1. Index management: daily indices, rollover based on size (50GB) or age (1 day). 2. Retention policies: hot (7 days), warm (30 days), cold (90 days), delete after 1 year. 3. Storage optimization: compression, field exclusion, index patterns. Security and access control: 1. X-Pack Security: role-based access, field-level security, audit logging. 2. Encryption: TLS for data in transit, encryption at rest for sensitive data. Monitoring and alerting: 1. Performance metrics: indexing rate (target 10k docs/sec), query response time (<1s). 2. Cluster health: green/yellow/red status monitoring, shard allocation, disk usage. Alert configuration: Watcher for threshold-based alerts, Slack/email notifications, escalation procedures for critical events.

Explain loyalty program clearly. Details: 1. How points are earned (per dollar, actions). 2. Point value and redemption options. 3. Tier levels and benefits. 4. Point expiration policy. 5. How to check point balance. 6. Special earning opportunities. 7. Redemption process. 8. Member-exclusive perks. Use examples with actual dollar values to make it tangible.

Organize digital files for easy retrieval. Structure: 1. Create master folders (Work, Personal, Finance, Creative, Archive). 2. Use consistent naming (YYYY-MM-DD_Project_Version). 3. Limit folder depth to 3 levels. 4. Archive old files annually. 5. Use cloud sync (Google Drive, Dropbox). 6. Tag files for cross-category search. 7. Weekly cleanup ritual. Tools: Everything (Windows search), Alfred (Mac), Hazel (automation). Avoid 'Misc' or 'Other' folders. One source of truth. Backup 3-2-1 rule (3 copies, 2 media, 1 offsite). Saves hours of searching.

Conduct stakeholder analysis for change management. Framework: 1. Identify all stakeholders (internal and external). 2. Assess power/influence and interest levels. 3. Plot on 2x2 matrix (Manage Closely, Keep Satisfied, Keep Informed, Monitor). 4. Develop engagement strategy for each quadrant. 5. Create communication plan with frequency and channels. 6. Track sentiment and concerns over time. Use for product launches, org changes, or strategic initiatives. Include RACI matrix for decision-making clarity.

Coordinate research across multiple sites while maintaining quality and consistency. Governance structure: 1. Steering committee: principal investigators from each site plus coordinating center. 2. Data and safety monitoring board: independent oversight of study progress and safety. 3. Working groups: methodology, recruitment, data management, publication. Standardization procedures: 1. Common protocol: detailed procedures manual shared across all sites. 2. Training programs: standardized training for all research staff with certification. 3. Quality assurance: regular site visits, conference calls, performance monitoring. Data management: 1. Centralized database: single data repository with controlled access. 2. Data standards: common data elements, coding schemes, variable definitions. 3. Real-time monitoring: dashboard showing enrollment, data quality metrics by site. Communication: 1. Regular meetings: monthly investigator calls, quarterly face-to-face meetings. 2. Documentation: shared file systems, meeting minutes, decision logs. Challenges: 1. Site heterogeneity: different populations, resources, regulations. 2. Timeline coordination: competing priorities and schedules. 3. Intellectual property: authorship agreements, data sharing policies.

Deploy models with Replicate. Process: 1. Package model with Cog. 2. Define predict function. 3. Push to Replicate. 4. API access with predictions. 5. Automatic scaling. 6. GPU compute on-demand. 7. Webhook notifications. 8. Version management. Run any model without infrastructure. Use for Stable Diffusion, LLMs, or custom models.

Handle bulk order requests. Response: 1. Thank them for interest. 2. Ask for quantity and specifications. 3. Explain volume discount structure. 4. Provide custom quote if needed. 5. Outline bulk ordering process. 6. Discuss payment terms for large orders. 7. Provide lead time estimates. 8. Assign dedicated account manager. Treat as high-value opportunity.

Integrate social login with OAuth 2.0. Flow: 1. Redirect to provider (Google, Facebook, GitHub). 2. User authorizes application. 3. Provider redirects with authorization code. 4. Exchange code for access token. 5. Fetch user profile. 6. Create or update user in database. 7. Issue JWT to client. 8. Handle errors and edge cases. Use libraries like passport.js. Implement state parameter for CSRF. Store tokens securely.

Suggest complementary products naturally. Approach: 1. Solve their primary need first. 2. Identify natural product pairings. 3. Frame as 'customers also found helpful'. 4. Explain how items work together. 5. Highlight bundle savings if available. 6. Use their purchase history for personalization. 7. Make suggestions, not pressure. 8. Easy to add or ignore. Focus on enhancing their experience.

Apply intricate, photorealistic face tattoos. The prompt ensures: 1. Ink texture that looks like it's inside the skin (no sticker look). 2. Traditional black-ink vs vibrant color gradients. 3. Following facial contours perfectly (cheeks, nose, forehead). 4. Subtle scarring/redness around the edges for realism. Edge-lord approved aesthetic.

Restaurant-quality steak at home using reverse sear. Prep: 1.5-inch thick ribeye, pat dry, season generously with salt. Step 1: Oven at 225°F, cook on wire rack to 115°F internal (rare). Step 2: Rest 10 minutes while heating cast iron on max. Step 3: Add oil with high smoke point (avocado). Step 4: Sear 60-90 seconds per side. Step 5: Baste with butter, garlic, thyme. Rest: 5-7 minutes, slice against grain. Explain myoglobin denaturation, Maillard reaction, and why reverse sear prevents gray band.