Trending Prompts

Master platform-specific copywriting for maximum social media engagement. Platform specifications: 1. Twitter: 280 characters, 1-2 hashtags, newsjacking opportunities. 2. LinkedIn: professional tone, 1300 character sweet spot, industry insights. 3. Facebook: casual tone, 40-80 characters for high engagement, community focus. 4. Instagram: visual-first, longer captions OK, 10-30 hashtags, story highlights. 5. TikTok: trending sounds, casual language, hook in first 3 seconds. Copy formulas: 1. Hook-Value-CTA: attention grabber → useful content → clear action. 2. Problem-Solution-Proof: pain point → your answer → social proof. 3. Story-Lesson-Link: personal anecdote → key takeaway → resource. Content types: 1. Educational: tips, tutorials, how-tos with carousel posts. 2. Behind-the-scenes: process videos, team spotlights, company culture. 3. User-generated content: customer photos, testimonials, reviews. Hashtag strategy: mix of broad (#marketing) and niche (#b2bsaasmarketing) tags. Posting optimization: platform-specific peak times, consistent brand voice, engagement within first hour crucial for algorithm boost.

Master copyediting skills using style guides and maintaining consistency standards. Major style guides: 1. AP (Associated Press): journalism, news writing, web content. 2. Chicago: books, academic publishing, historical writing. 3. MLA: literature, humanities, language arts. 4. APA: psychology, education, social sciences. 5. AMA: medical, scientific, health-related content. Style guide application: 1. Numbers: spell out vs. numerals (AP: spell one-nine, numerals 10+). 2. Dates: format consistency (March 3, 2024 vs. 3/3/24). 3. Capitalization: headlines, titles, proper nouns. 4. Punctuation: serial commas, quotation marks, hyphenation. 5. Abbreviations: periods, spacing, first usage definitions. Consistency tracking: 1. Style sheets: document decisions for project-specific issues. 2. Character names: spelling, titles, relationships. 3. Technical terms: definitions, usage, formatting. 4. Timeline: chronological accuracy, age calculations. Quality markers: 1. Parallel structure: consistent formatting for similar elements. 2. Tone consistency: formal vs. casual throughout document. 3. Tense agreement: past vs. present, narrative consistency. Fact-checking process: 1. Statistics: source verification, current data. 2. Citations: complete, accurate, properly formatted. Professional standards: client style preferences, industry conventions, deadline management.

Leverage Valtio's proxy magic for state. Usage: 1. proxy() creates mutable state. 2. Direct property mutations. 3. snapshot() for immutable reads. 4. useSnapshot hook in React. 5. subscribe() for listeners. 6. Nested objects auto-tracked. 7. Derive computed values. 8. Works outside React. Simple mental model: mutate state directly, components auto-update. Use with class instances for OOP patterns.

Craft custom visualizations with D3.js. Patterns: 1. Data binding with selection.data(). 2. Enter/update/exit pattern. 3. Scales (linear, time, ordinal). 4. Axes with d3.axis(). 5. SVG path generation. 6. Transitions for smooth updates. 7. Zoom and pan behaviors. 8. Force-directed graphs. Use Observable Plot for simpler charts or build completely custom. Integrate with React using useRef.

Build comprehensive analytics infrastructure for data-driven decisions. Analytics architecture: 1. Data collection: event tracking, user interactions, system metrics. 2. Data pipeline: ETL processes, data validation, transformation. 3. Data warehouse: centralized storage, dimensional modeling. 4. Business intelligence: dashboards, reports, self-service analytics. Key metrics framework: 1. Acquisition: traffic sources, conversion rates, cost per acquisition. 2. Activation: onboarding completion, time-to-first-value, feature adoption. 3. Retention: DAU/MAU, cohort retention, churn analysis. 4. Revenue: ARPU, LTV, conversion rates, expansion revenue. 5. Referral: viral coefficient, NPS, organic growth rate. Reporting strategy: 1. Executive dashboards: KPIs, trends, alerts. 2. Product dashboards: feature usage, user flows, experimentation results. 3. Operational reports: performance monitoring, error tracking. Tools: Segment for data collection, Snowflake for warehousing, Tableau for visualization. Data governance: quality monitoring, access controls, privacy compliance, documentation standards.

Identify and leverage emerging creative trends for competitive advantage and innovation. Trend research methodology: 1. Cultural signals: social media conversations, viral content patterns, influencer behavior. 2. Industry analysis: design awards, creative conferences, agency case studies. 3. Consumer behavior: generational shifts, purchasing patterns, lifestyle changes. 4. Technology adoption: new platforms, tools, creative possibilities. 5. Global perspectives: international markets, cross-cultural creative exchange. Trend validation framework: 1. Signal strength: frequency of appearance across multiple sources. 2. Audience alignment: relevance to target demographics and psychographics. 3. Brand fit: consistency with brand values and positioning. 4. Longevity assessment: flash trend vs. lasting shift prediction. Application strategy: 1. Early adoption: test trends in low-risk projects first. 2. Brand adaptation: modify trends to fit brand personality and guidelines. 3. Timing optimization: balance being first vs. waiting for validation. Innovation opportunities: 1. Trend combination: merge multiple trends for unique approaches. 2. Counter-trends: zi when everyone else zags. 3. Trend evolution: predict next phase of current trends. Documentation: trend database with examples, implications, and application recommendations for creative teams.

Implement database DevOps with automated schema migrations, backup strategies, and zero-downtime deployments. Migration frameworks: 1. Flyway: version-based migrations, checksum validation, rollback support, team collaboration. 2. Liquibase: XML/YAML changesets, database-agnostic, conditional execution. 3. Alembic (Python): revision control, branching support, auto-generation from models. Database CI/CD: 1. Schema testing: unit tests for stored procedures, data validation, performance regression testing. 2. Environment promotion: dev → test → staging → production with data anonymization. 3. Deployment automation: blue-green database deployments, read replica promotion. Zero-downtime strategies: 1. Backward-compatible changes: additive migrations, column defaults, index creation online. 2. Multi-phase deployment: expand (add new), migrate (data transformation), contract (remove old). 3. Shadow tables: parallel table structures, gradual data migration, validation queries. Backup and recovery: 1. Automated backups: daily full backups, transaction log backups every 15 minutes. 2. Cross-region replication: RTO < 4 hours, RPO < 1 hour for critical systems. 3. Disaster recovery testing: monthly failover tests, recovery time validation. Performance monitoring: 1. Query performance: slow query logging (>1 second), index optimization recommendations. 2. Connection pooling: PgBouncer, connection limits based on server capacity. Database security: encryption at rest, TDE implementation, access control with least privilege, audit logging for sensitive operations.

Perfect medium-rare ribeye using sous vide. Setup: 1. Season 1.5-inch ribeye with salt and pepper. 2. Vacuum seal with butter and thyme. 3. Cook at 129°F for 2 hours (uniform edge-to-edge pink). 4. Ice bath shock for 5 minutes. 5. Pat dry thoroughly. 6. Sear in cast iron with avocado oil (90 seconds per side). 7. Rest 5 minutes. Compare Maillard reaction development with traditional cooking. Explain protein denaturation and moisture retention.

Elegant whole fish service technique. Fish: Mediterranean branzino, roasted with lemon and herbs. Deboning tableside: 1. Cut along dorsal fin and belly. 2. Gently separate top fillet from bones. 3. Plate top fillet. 4. Lift skeleton from tail, remove in one piece. 5. Plate bottom fillet. 6. Drizzle with herb oil. Technique requires: sharp fish knife, fish spatula, practice. Explain bone structure and presentation importance in fine dining. Check for pin bones.

Design balanced sales territories for maximum coverage. Data inputs: accounts by geography, revenue potential, current customer concentration, sales rep capacity. Criteria for balance: 1. Equal revenue opportunity ($2-3M per rep). 2. Manageable account count (50-75 active accounts). 3. Geographic proximity (minimize travel). 4. Industry expertise alignment. Process: 1. Map all accounts on visualization tool. 2. Identify natural clusters. 3. Assign territories. 4. Calculate opportunity per territory. 5. Adjust for balance. 6. Get rep buy-in. Review quarterly. Tools: Maptive, Badger Maps, Salesforce Territory Management. Prevents neglected accounts and rep burnout.

Conduct a systematic literature review. Process: 1. Define research question and scope. 2. Develop search strategy (databases, keywords, Boolean operators). 3. Set inclusion/exclusion criteria. 4. Screen titles and abstracts. 5. Full-text review of selected papers. 6. Extract data systematically. 7. Synthesize findings thematically. Use tools: Zotero, Mendeley for reference management. Create PRISMA flow diagram. Assess quality of studies. Identify gaps in literature. Aim for 30-50 key sources. Document search process for reproducibility.

Create a production-quality Jupyter notebook template. Structure: 1. Markdown header with title, author, date, and objective. 2. Table of contents with anchor links. 3. Environment setup cell (imports, configs, random seed). 4. Exploratory Data Analysis section with visualizations. 5. Modeling section with clear train/test split. 6. Results summary with key metrics and business recommendations. Use consistent styling, hide warnings, and include inline documentation.

Create a statistical analysis tool for A/B test results. Features: 1. Calculate conversion rate for Control vs Variant. 2. Compute p-value using two-proportion z-test. 3. Determine statistical significance at 95% confidence level. 4. Calculate required sample size for desired power (80%). 5. Visualize confidence intervals with error bars. Include interpretation guidelines for non-technical stakeholders.

Implement a real-time chat application. Use Supabase for Auth and Realtime Database. Features: 1. Channels/Rooms management. 2. Instantly visible messages using Postgres Changes. 3. 'User typing...' indicator. 4. Chat bubble UI with sender/receiver alignment. 5. Emoji picker integration and image attachment support using Supabase Storage.

Craft a persuasive executive business proposal. Structure: 1. Cover page with company logos and date. 2. Executive Summary (problem, solution, value in 1 page). 3. Situational Analysis (current state challenges). 4. Proposed Solution (detailed approach and deliverables). 5. Implementation Timeline (phases and milestones). 6. Investment and ROI Analysis. 7. Team and Credentials. 8. Terms and Next Steps. Use professional formatting with charts and visuals. Tailor language to C-suite audience.

Apply giant, shaking googly eyes to any object (fruit, shoes, buildings). Attributes: 1. Realistic plastic texture with internal black pupils that move with gravity. 2. Subtle drop shadow to make them 'pop' from the surface. 3. Hilarious, goofy expressions. 4. Seamless integration with the underlying object's curves. High-engagement viral content.

Design clean RESTful APIs. Principles: 1. Use nouns for resources (/users, not /getUsers). 2. HTTP methods: GET (read), POST (create), PUT (update), DELETE (delete). 3. Proper status codes (200 OK, 201 Created, 400 Bad Request, 404 Not Found, 500 Server Error). 4. Versioning (/v1/users). 5. Filtering, sorting, pagination (?page=2&sort=name). 6. HATEOAS (include links to related resources). 7. Consistent naming (camelCase or snake_case). Use JSON. Stateless requests. Authentication with JWT/OAuth. Rate limiting. Comprehensive documentation (OpenAPI/Swagger). Error messages should be helpful.

The ultimate 'Food Porn' shot of an Italian Tiramisu. The 'Reveal': 1. Cake ring being lifted to show clean layers of mascarpone and coffee-soaked ladyfingers. 2. Sifting of high-quality cocoa powder onto the top. 3. Macro shot showing the airy texture of the cream. Soft, warm kitchen lighting with a rustic espresso bar background.

A set of low-pressure, high-conversion DM templates for Instagram/X. Strategy: 1. No immediate pitch. 2. Genuine compliment on recent work. 3. Relevant 'value add' question. 4. Soft CTA for a quick chat. 5. Follow-up logic. Optimized to bypass spam filters and spark real conversations with decision-makers.

Dynamic visualization of Microsoft AutoGen agent chats. Use a messaging interface style where each bubble indicates which agent (Assistant, Critic, User) spoke. Include a 'Context Window' sidebar that shows the tokens used and cost per message. Highlight when the 'TERMINATE' command is triggered.

Develop effective mobile strategy for multi-platform products. Platform considerations: 1. Native development: platform-specific optimization, best performance. 2. Cross-platform: React Native, Flutter for code sharing. 3. Progressive Web App (PWA): web-based, app-like experience. 4. Hybrid: web technology wrapped in native container. Decision framework: 1. Performance requirements: games need native, content apps work cross-platform. 2. Platform features: camera, location, notifications importance. 3. Development resources: team skills, time-to-market. 4. Maintenance overhead: multiple codebases vs. shared code. Mobile-first considerations: 1. Touch interface design: finger-friendly targets, gestures. 2. Performance optimization: battery life, network efficiency. 3. Offline functionality: local storage, sync capabilities. 4. Push notifications: engagement and retention strategy. App store strategy: 1. App Store Optimization (ASO): keywords, screenshots, reviews. 2. Release strategy: phased rollouts, A/B testing. Distribution: direct download, enterprise app stores, web-to-app flows. Analytics: mobile-specific metrics, session depth, crash tracking.

Build a time series forecasting model using Facebook Prophet. Steps: 1. Prepare historical sales data with daily granularity. 2. Add custom seasonality for Black Friday and holiday peaks. 3. Include external regressors (marketing spend, weather). 4. Generate 90-day forecast with uncertainty intervals. 5. Validate model using cross-validation and MAPE metric. Visualize actual vs predicted with interactive Plotly charts.

Drive local traffic to restaurant. Google My Business: 1. Complete profile (hours, menu, photos). 2. Post weekly updates. 3. Respond to all reviews. 4. Add Q&A section. 5. Enable messaging. Local SEO: target 'best [cuisine] near me' keywords. Content: blog about dishes, behind-scenes. Social: Instagram stories, TikTok reels. Partnerships: local influencers (trade meals for posts). Promotions: email list for loyalty. Paid ads: Google Local Services Ads, Facebook/Instagram targeting 5-mile radius. Track: reservations, website visits, calls. Explain local pack ranking factors.

Teach students to analyze primary sources like a historian. Framework: Sourcing, Contextualizing, Close Reading, Corroborating (Stanford History Education Group - SHEG). Activity: Give students two primary source documents about the Boston Massacre—one from a British officer, one from a colonial patriot. Analysis Steps: 1. Sourcing: Who wrote this? When? Why? Is it reliable? 2. Contextualizing: What was happening at the time that might influence this account? 3. Close Reading: What claims does the author make? What words do they use to persuade the reader? 4. Corroborating: How do the two accounts differ? Where do they agree? Which account is more believable and why? This moves students from memorizing facts to interpreting evidence.

Master data fetching with Tanstack Query (React Query). Features: 1. useQuery for async state management. 2. Query keys for caching strategy. 3. Automatic refetching on window focus. 4. Mutations with invalidation. 5. Optimistic updates for instant UI. 6. Infinite queries for pagination. 7. Prefetching for better UX. 8. DevTools for debugging. Use with axios or fetch and implement retry logic with exponential backoff.

Model complex logic with XState. Machine structure: 1. States and transitions. 2. Context for extended state. 3. Actions on entry/exit. 4. Guards for conditional transitions. 5. Services for async invocations. 6. Parallel states. 7. History states. 8. Visualize with @xstate/inspect. Use for multi-step forms, auth flows, or game logic. Prevents impossible states through explicit modeling.

Enable real-time features with Socket.io. Implementation: 1. Server-side io instance. 2. Client-side connection. 3. Emit and on for events. 4. Rooms for group messaging. 5. Broadcasting to multiple clients. 6. Acknowledgements for reliability. 7. Middleware for authentication. 8. Automatic reconnection. Use with Redis adapter for scaling across servers and implement presence detection.

Implement reproducible research practices throughout project lifecycle. Preregistration: 1. Register study protocol before data collection (OSF, ClinicalTrials.gov). 2. Include hypotheses, methods, analysis plan, sample size justification. 3. Distinguish confirmatory from exploratory analyses. Reproducible workflow: 1. Version control: Git/GitHub for code and document management. 2. Literate programming: R Markdown, Jupyter notebooks combining code and narrative. 3. Environment management: Docker containers, package version recording. 4. Automated reporting: dynamic documents that update with new data. Open data and materials: 1. Data repositories: disciplinary (e.g., ICPSR) or general (OSF, Zenodo). 2. Code sharing: GitHub with clear documentation and README files. 3. Materials sharing: survey instruments, interview guides, stimuli. Transparency reporting: 1. CONSORT for RCTs, STROBE for observational studies. 2. Report all measures, manipulations, exclusions. Publication: preprints for rapid dissemination, open access journals when possible.

Balance new features with technical debt reduction effectively. Technical debt assessment: 1. Code quality metrics: cyclomatic complexity, test coverage, duplication. 2. Performance impact: page load times, API response times. 3. Developer productivity: time to implement new features. 4. Bug frequency: hotfixes and customer-impacting issues. 5. Security vulnerabilities: outdated dependencies, known exploits. Debt categorization: 1. Critical: security issues, major performance problems (fix immediately). 2. Important: impacts developer velocity significantly (plan in next sprint). 3. Nice-to-have: code cleanliness, minor optimizations (backlog). Resource allocation: allocate 15-25% of development capacity to debt reduction. Stakeholder communication: explain debt in business terms (slower features, more bugs, security risk). Tools: SonarQube for code analysis, New Relic for performance monitoring. Prevent future debt: code reviews, architecture decisions documentation, regular refactoring.

Design load balancing and high availability systems for fault-tolerant, scalable application infrastructure. Load balancing strategies: 1. Application Load Balancer (ALB): Layer 7 routing, host/path-based routing, SSL termination. 2. Network Load Balancer (NLB): Layer 4 performance, static IP addresses, ultra-low latency. 3. Global load balancing: geographical distribution, DNS-based routing, CDN integration. Health checks: 1. HTTP health endpoints: /health returning 200 OK, comprehensive system status checks. 2. Check intervals: 30-second intervals, 3 consecutive failures for unhealthy marking. 3. Custom metrics: database connectivity, external service dependencies, resource availability. High availability design: 1. Multi-AZ deployment: minimum 2 availability zones, automatic failover mechanisms. 2. Auto Scaling Groups: CPU target 70%, predictive scaling for traffic patterns. 3. Circuit breaker pattern: fail fast when dependencies unavailable, graceful degradation. Performance optimization: 1. Connection pooling: database connections, HTTP keep-alive, connection limits. 2. Caching strategies: Redis/ElastiCache, CDN caching, application-level caching. 3. Content delivery: static assets via CDN, edge locations, cache invalidation strategies. Disaster recovery: 1. Cross-region replication: RTO < 4 hours, RPO < 1 hour for critical systems. 2. Backup strategies: automated daily backups, point-in-time recovery, cross-region backup storage. Traffic management: blue-green deployments, canary releases with 5% traffic initially, feature flags for instant rollback.

Implement chaos engineering practices for system resilience testing and failure mode discovery through controlled experiments. Chaos engineering principles: 1. Hypothesis formation: define steady state behavior, predict impact of injected failures. 2. Controlled experiments: gradual scope increase, production-like environments, safety measures. 3. Minimal blast radius: limit failure scope, immediate rollback capability, monitoring safeguards. 4. Continuous practice: regular chaos days, automated experiments, team learning culture. Failure injection types: 1. Infrastructure chaos: server termination, network partitions, disk space exhaustion. 2. Application chaos: service unavailability, increased latency, memory pressure, CPU throttling. 3. Network chaos: packet loss, bandwidth limitations, DNS failures, certificate expiration. Tools and platforms: 1. Chaos Monkey: random instance termination, AWS integration, configurable schedules. 2. Gremlin: comprehensive failure injection, team collaboration, hypothesis tracking. 3. Litmus: Kubernetes-native chaos engineering, workflow automation, GitOps integration. 4. Pumba: Docker container chaos, network emulation, stress testing. Experiment design: 1. Baseline measurement: performance metrics, error rates, user experience indicators. 2. Hypothesis definition: expected system behavior, acceptable degradation levels. 3. Metrics collection: SLI monitoring, error budgets, customer impact assessment. Safety measures: 1. Circuit breakers: automatic experiment termination, blast radius containment. 2. Monitoring: real-time alerting, anomaly detection, automated rollback triggers. Learning integration: postmortem analysis, system improvement recommendations, resilience scoring, team knowledge sharing, incident response improvement.

Implement performance reviews. Framework: 1. Goal setting (beginning of period). 2. Regular 1-on-1s (weekly/bi-weekly). 3. Mid-year check-in. 4. Annual review (achievements, areas for growth). 5. 360-degree feedback. 6. Self-assessment component. 7. Development plan. 8. Compensation decisions separate. Focus on growth not punishment. Document throughout year. Make it dialogue not monologue.

Instagram-worthy acai bowl styling. Base: blend frozen acai, banana, berries, splash of almond milk (thick consistency). Bowl arrangement: 1. Smooth base with back of spoon. 2. Toppings in sections: sliced banana, strawberries, blueberries, granola, coconut flakes, chia seeds, honey drizzle. 3. Arrange by color gradient. 4. Add edible flowers. Photography: natural light, 45-degree angle, shallow depth of field. Props: wooden board, white marble, greenery. Explain visual appeal psychology and color theory in food photography.

Visualize a team of AI agents working together. The 'Crew' includes: 1. 'Researcher' (fetches facts). 2. 'Writer' (drafts blog). 3. 'Manager' (approves/feedback). Show a timeline of tasks being handed off between agents. Use a clean, modern dashboard with status badges (Ongoing, Completed, Failed).

Create accessible dropdowns with Alpine.js. Features: 1. x-data for component state. 2. x-show with transitions for visibility. 3. x-on:click.outside to close dropdown. 4. Keyboard navigation (Arrow, Enter, Esc). 5. x-bind for dynamic classes. 6. Focus trap within dropdown. 7. ARIA attributes for screen readers. 8. Multiple dropdown coordination. Use x-cloak to prevent flash and implement searchable dropdown with x-model for filter input.

Create and maintain comprehensive product documentation ecosystem. Documentation types: 1. User guides: step-by-step instructions for end users. 2. API documentation: endpoints, parameters, examples. 3. Admin documentation: configuration, troubleshooting. 4. Developer docs: SDKs, integration guides. 5. Release notes: feature updates, bug fixes. Content strategy: 1. Audience-based: different docs for different user types. 2. Progressive disclosure: basic → advanced information. 3. Multimedia: screenshots, videos, interactive tutorials. 4. Search optimization: logical structure, good navigation. Maintenance workflow: 1. Documentation requirements in user stories. 2. Review process: technical accuracy, clarity. 3. Version control: docs synchronized with product releases. 4. Analytics: track usage, identify gaps. 5. User feedback: ratings, comments, improvement suggestions. Tools: GitBook, Notion, Confluence for authoring, Algolia for search. Success metrics: documentation usage, support ticket reduction, user satisfaction scores. Keep docs current: assign ownership, regular audits, automated link checking.

Prepare for productive parent-teacher conferences. Preparation: 1. Gather student work samples (strengths and areas for growth). 2. Review grades, attendance, and behavior data. 3. Prepare specific examples and anecdotes. 4. Set 2-3 key talking points. 5. Anticipate questions and concerns. During conference: Start with positives. Use 'sandwich' approach (positive-concern-positive). Listen actively. Collaborate on action plan. End with next steps. Follow up in writing. Keep to 15-20 min. Document conversation. Build partnership for student success.

Authentic Thai green curry paste using mortar and pestle. Ingredients: 10 green chilies, 2 stalks lemongrass, galangal, shallots, garlic, cilantro roots, coriander seeds, cumin, kaffir lime zest, shrimp paste. Technique: 1. Toast dry spices first. 2. Pound chilies with salt. 3. Add aromatics one at a time in order of hardness. 4. Grind to fine paste (15-20 minutes). 5. Bloom paste in coconut cream. Balance spicy-salty-sweet-sour flavors. Store in fridge or freeze portions.

Create a comprehensive data management plan. Components: 1. Data types and formats. 2. Metadata and documentation standards. 3. Storage and backup strategy (3-2-1 rule). 4. Access and sharing policies. 5. Ethical and legal compliance (GDPR, HIPAA). 6. Roles and responsibilities. 7. Long-term preservation and archiving. 8. Budget for data management. Use repositories: OSF, Dataverse, Zenodo. Follow FAIR principles (Findable, Accessible, Interoperable, Reusable). Version control with Git. Required by many funders.

A technical guide to boosting email opens. Covers: 1. Subject line psychology. 2. Preheader text strategy. 3. Deliverability checks (SPF, DKIM). 4. Best times to send per timezone. 5. A/B testing variables. Includes 20 'High-Open' subject line templates for various industries (Finance, Creative, SaaS).

Build with Supabase as backend. Features: 1. PostgreSQL database with REST API. 2. Auto-generated APIs from schema. 3. Authentication (email, OAuth, magic links). 4. Row-level security policies. 5. Real-time subscriptions. 6. Storage for files. 7. Edge functions for serverless. 8. TypeScript SDK. Use supabase.from() for queries and implement triggers for complex logic.

Design effective user onboarding to drive activation and retention. Onboarding success metrics: 1. Time-to-first-value (TTFV): how quickly users achieve core benefit. 2. Activation rate: percentage reaching 'aha moment'. 3. Day 1, 7, 30 retention: usage stickiness over time. Onboarding flow design: 1. Progressive disclosure: show features gradually, not all at once. 2. Interactive tutorials: hands-on vs. passive video watching. 3. Personalization: tailor experience to user role/use case. 4. Empty states: helpful content when users haven't added data yet. 5. Success celebrations: acknowledge user achievements. Optimization process: 1. Map current flow and identify drop-off points. 2. User testing: watch people go through onboarding. 3. A/B testing: test different approaches (tooltip vs. modal vs. guided tour). 4. Iterative improvements: make small changes, measure impact. Tools: Appcues, Pendo, WalkMe for guided experiences.

Create engaging blog content that builds audience and drives website traffic. Blog post structure: 1. Headline: compelling, specific, keyword-optimized (60 characters max). 2. Introduction: hook reader with question, statistic, or story (150 words). 3. Body: 3-5 main points with subheadings, examples, data. 4. Conclusion: recap key points, call-to-action for comments or shares. Content types: 1. How-to guides: step-by-step instructions with actionable advice. 2. List posts: '10 Ways to...', '5 Mistakes to Avoid'. 3. Case studies: real results with specific metrics and lessons. 4. Industry analysis: trends, predictions, expert opinions. 5. Personal stories: behind-the-scenes, challenges overcome. Engagement tactics: 1. Questions to readers: encourage comments and discussion. 2. Visual elements: images every 300 words, infographics, charts. 3. Internal linking: 3-5 relevant posts for deeper engagement. 4. Social sharing buttons: make spreading content easy. Publishing cadence: consistent schedule (weekly minimum for growth), optimal posting times based on analytics. Metrics tracking: page views, time on page, social shares, comment engagement, email signups.

An educational visualization of Pixar's storytelling logic. Shot: 1. A 3D graph showing 'Tension' over 'Time'. 2. Iconic characters (e.g., Woody, Joy, Buzz) placed at emotional peaks. 3. Bright, friendly lighting and rounded 3D shapes. 4. Instructional annotations in a playful font. 5. High-fidelity 3D render with sub-surface scattering.

Perfect smash burger technique. Patties: 2.5oz 80/20 ground chuck, room temp, loose balls. Griddle: cast iron or flat-top at 400°F+. Method: 1. Place ball on griddle, smash hard with spatula for 3 seconds (thin = crispy edges). 2. Season with salt/pepper. 3. Cook 2 minutes undisturbed for crust. 4. Flip, add American cheese. 5. Steam under lid 30 seconds. 6. Stack two patties. Bun: Martin's potato roll, toasted with butter. Toppings: pickles, onions, special sauce. Explain Maillard browning and lacy edges.

Use restorative circles to address classroom conflicts instead of punitive measures. Scenario: Two students had a verbal argument. Process: 1. Preparation: Meet with each student individually to hear their perspective. 2. The Circle: Bring both students, a facilitator (teacher/counselor), and possibly a trusted peer for each. 3. Opening: Use a talking piece to ensure one person speaks at a time. 4. Questions: 'What happened?' 'What were you thinking at the time?' 'Who has been affected?' 'What do you need to make things right?' 5. Agreement: Students collaboratively decide on a plan to repair the harm (e.g., apology, replacing a damaged item, working together on a task). 6. Follow-up: Check in with students the next day. Goal: focus on repairing relationships and learning from mistakes.

Implement comprehensive quality assurance for product reliability. Testing pyramid: 1. Unit tests (70%): individual component functionality. 2. Integration tests (20%): component interactions. 3. End-to-end tests (10%): full user workflows. Testing types: 1. Functional testing: features work as specified. 2. Performance testing: load, stress, volume testing. 3. Security testing: vulnerability scanning, penetration testing. 4. Usability testing: user experience validation. 5. Accessibility testing: compliance with accessibility standards. QA process: 1. Test planning: define scope, approach, criteria. 2. Test case design: positive and negative scenarios. 3. Test execution: manual and automated testing. 4. Bug reporting: clear reproduction steps, severity classification. 5. Regression testing: ensure new changes don't break existing functionality. Automation strategy: automate repetitive tests, maintain test suite health, balance speed vs. coverage. Tools: Selenium for web testing, Cypress for modern web apps, Postman for API testing. Quality metrics: test coverage, defect density, customer-reported bugs, time-to-detection.

Create a web-based IDE mockup inspired by Cursor. Requirements: 1. File explorer sidebar. 2. Multi-tab editor with dummy code. 3. 'AI Assistant' chat window on the right. 4. Command palette (Ctrl+K) simulation. 5. Integrated terminal at the bottom. Use dark VS Code colors (One Dark Pro) and high-density spacing.

Craft the perfect Product Hunt 'Launch' day asset. Includes: 1. Catchy tagline (Max 60 chars). 2. Key features bullet points. 3. Maker's comment (The 'Founder' story). 4. A gallery of high-shimmer GIF previews. 5. 'Community' Q&A prompt. Designed to hit #1 Product of the Day. Clean, minimalist, and tech-focused.

Build a 5-year financial projection model for Series A fundraising. Components: 1. Revenue forecast with multiple growth scenarios (conservative, base, aggressive). 2. Unit economics (CAC, LTV, payback period). 3. Operating expenses breakdown (headcount, marketing, infrastructure). 4. Cash flow statement and runway calculation. 5. Key metrics dashboard (burn rate, MRR growth, gross margin). Use Excel/Google Sheets with clear assumptions tab. Include sensitivity analysis for key variables.