Browse All Prompts

Generate documentation for the following TypeScript function in JSDoc format. The function accepts a user object and returns a formatted greeting string. Make sure to document the parameters, their types, and the return value.

Master PPC advertising with Google Ads, Facebook Ads, and advanced bidding strategies for maximum ROI. Google Ads optimization: 1. Campaign structure: ad groups with 5-20 related keywords, single keyword ad groups (SKAGs) for high-volume terms. 2. Keyword strategy: exact match for conversions, broad match modifier for discovery, negative keywords for irrelevant traffic. 3. Ad extensions: sitelinks, callouts, structured snippets, location extensions (increase CTR 10-15%). Quality Score improvement: 1. Expected CTR: compelling ad copy, keyword-ad alignment, historical performance. 2. Ad relevance: keyword inclusion in headlines, dynamic keyword insertion, ad group theming. 3. Landing page experience: page load speed <3s, mobile optimization, content relevance. Facebook Ads strategy: 1. Audience targeting: custom audiences (email lists, website visitors), lookalike audiences (1-2% similarity). 2. Creative testing: video vs image, carousel vs single image, A/B testing ad components. 3. Campaign objectives: awareness, traffic, engagement, conversions, catalog sales alignment. Bidding strategies: 1. Manual CPC: full control, suitable for new accounts, testing phases. 2. Target CPA: automated bidding, historical data requirement, goal-based optimization. 3. Target ROAS: return on ad spend goals, e-commerce optimization, performance tracking. Performance monitoring: 1. Key metrics: CTR (2-5% good), CPC, conversion rate, cost per acquisition. 2. Attribution modeling: first-click, last-click, position-based, data-driven attribution. Budget optimization: dayparting, geographic targeting, device bid adjustments, seasonal scaling strategies.

Build recommendation systems using collaborative filtering, content-based filtering, and hybrid approaches for personalization. Collaborative filtering approaches: 1. User-based CF: find similar users, recommend items liked by similar users, cosine similarity calculation. 2. Item-based CF: find similar items, recommend similar items to liked items, Pearson correlation. 3. Matrix factorization: SVD, NMF for dimensionality reduction, latent factor modeling. Content-based filtering: 1. Feature extraction: item attributes, TF-IDF for text features, categorical encoding. 2. Profile building: user preference vectors, weighted feature importance, learning user tastes. 3. Similarity computation: cosine similarity, Jaccard similarity, recommendation scoring. Deep learning approaches: 1. Neural Collaborative Filtering: user/item embeddings, deep neural networks, non-linear interactions. 2. Deep autoencoders: collaborative denoising, missing rating prediction, feature learning. 3. Recurrent neural networks: sequential recommendations, session-based filtering, temporal dynamics. Hybrid systems: 1. Weighted combination: linear combination of different approaches, weight optimization. 2. Mixed systems: present recommendations from different algorithms, user choice. 3. Cascade systems: hierarchical filtering, primary and secondary recommendation stages. Evaluation metrics: 1. Precision@K: relevant items in top-K recommendations, practical relevance measure. 2. Recall@K: coverage of relevant items, completeness assessment. 3. NDCG (Normalized Discounted Cumulative Gain): ranking quality, position-aware evaluation. Cold start problem: new user recommendations, new item recommendations, demographic-based initialization, content-based bootstrap, popularity-based fallback strategies.

Implement comprehensive model evaluation and validation frameworks with proper metrics and statistical analysis. Classification metrics: 1. Accuracy: correct predictions / total predictions, baseline comparison, stratified sampling. 2. Precision: true positives / (true positives + false positives), minimize false alarms. 3. Recall (Sensitivity): true positives / (true positives + false negatives), capture all positive cases. 4. F1-score: harmonic mean of precision and recall, balanced metric for imbalanced datasets. Regression metrics: 1. Mean Absolute Error (MAE): average absolute differences, interpretable units, robust to outliers. 2. Root Mean Square Error (RMSE): penalizes large errors, same units as target variable. 3. R² (coefficient of determination): explained variance, 1.0 = perfect fit, negative = worse than mean. Advanced evaluation: 1. ROC-AUC: area under ROC curve, threshold-independent, >0.9 excellent performance. 2. Precision-Recall curve: imbalanced datasets, focus on positive class performance. 3. Confusion matrix: detailed error analysis, class-specific performance, misclassification patterns. Cross-validation strategies: 1. Stratified K-fold: maintain class distribution, k=5 or k=10, repeated CV for stability. 2. Time series validation: walk-forward, expanding window, respect temporal dependencies. 3. Leave-one-out: small datasets, computationally expensive, unbiased estimates. Statistical significance: 1. Paired t-test: compare model performance, statistical significance p<0.05. 2. Bootstrap sampling: confidence intervals, performance stability assessment. 3. McNemar's test: classifier comparison, statistical hypothesis testing. Business metrics integration: ROI calculation, cost-benefit analysis, domain-specific targets, A/B testing framework for production validation.

Build comprehensive NLP pipelines for text analysis, sentiment analysis, and language understanding tasks. Text preprocessing pipeline: 1. Data cleaning: remove HTML tags, normalize Unicode, handle encoding issues. 2. Tokenization: word-level, subword (BPE, SentencePiece), sentence segmentation. 3. Normalization: lowercase conversion, stopword removal, stemming/lemmatization. 4. Feature extraction: TF-IDF (max_features=10000), n-grams (1-3), word embeddings (Word2Vec, GloVe). Traditional NLP approaches: 1. Bag of Words: document-term matrix, sparse representation, baseline for classification. 2. Named Entity Recognition: spaCy, NLTK for entity extraction, custom entity types. 3. Part-of-speech tagging: grammatical analysis, dependency parsing, syntactic features. Modern approaches: 1. Pre-trained transformers: BERT (bidirectional), RoBERTa (optimized BERT), DistilBERT (lightweight). 2. Fine-tuning: task-specific adaptation, learning rate 5e-5, batch size 16-32. 3. Prompt engineering: few-shot learning, in-context learning, chain-of-thought prompting. Sentiment analysis: 1. Lexicon-based: VADER sentiment, TextBlob polarity scores, domain-specific dictionaries. 2. Machine learning: feature engineering, SVM/Random Forest classifiers, cross-validation. 3. Deep learning: LSTM with attention, BERT classification, multilingual models. Evaluation metrics: accuracy >80% for sentiment, F1 score >0.75, BLEU score for generation, perplexity for language models.

Master systematic model selection and optimization for machine learning projects with performance evaluation frameworks. Model selection process: 1. Problem definition: classification vs. regression, supervised vs. unsupervised learning. 2. Data assessment: sample size (minimum 1000 for deep learning), feature count, missing values analysis. 3. Baseline models: linear regression, logistic regression, random forest for initial benchmarks. Algorithm comparison: 1. Tree-based: Random Forest (high interpretability), XGBoost (competition winner), LightGBM (fast training). 2. Linear models: Ridge/Lasso (regularization), ElasticNet (feature selection), SGD (large datasets). 3. Neural networks: MLPs (tabular data), CNNs (images), RNNs/Transformers (sequences). Hyperparameter optimization: 1. Grid search: exhaustive parameter combinations, computationally expensive but thorough. 2. Random search: efficient for high-dimensional spaces, 60% less computation time. 3. Bayesian optimization: intelligent search using Gaussian processes, tools like Optuna, Hyperopt. Cross-validation strategies: 1. K-fold CV: k=5 for small datasets, k=10 for larger datasets, stratified for imbalanced data. 2. Time series CV: walk-forward validation, expanding window, respect temporal order. Performance metrics: accuracy (>85% target), precision/recall (F1 >0.8), AUC-ROC (>0.9 excellent), confusion matrix analysis for class-specific performance.

Create a multi-page application with Parcel's zero-config approach. Setup: 1. Multiple HTML entry points. 2. Automatic code splitting per page. 3. Shared chunks for common dependencies. 4. Hot module replacement. 5. Image optimization and resizing. 6. PostCSS and Sass support out-of-box. 7. Environment variable injection. 8. Production builds with tree-shaking. No webpack config needed. Use @parcel/transformer-typescript and implement service worker for offline support.

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.

Build comprehensive E2E testing with Playwright. Test structure: 1. Page Object Model for maintainability. 2. Multi-browser testing (Chromium, Firefox, WebKit). 3. Parallel test execution. 4. Visual regression with screenshots. 5. Network mocking and interception. 6. Authentication state persistence. 7. Trace viewer for debugging. 8. CI/CD integration with GitHub Actions. Use fixtures for test data, implement retry logic, and generate HTML reports with test results.

Document components effectively with Storybook 7. Setup: 1. CSF3 format for stories. 2. Autodocs for prop table generation. 3. Controls addon for prop manipulation. 4. Actions addon for event logging. 5. Interactions testing with @storybook/test. 6. Accessibility checks with a11y addon. 7. Design tokens documentation. 8. MDX for custom documentation pages. Use composition for multiple projects and implement visual testing with Chromatic.

Authentic Italian tomato sauce (Sugo al Pomodoro). Ingredients: 28oz can San Marzano DOP tomatoes, 5 cloves garlic, 1/4 cup extra virgin olive oil, fresh basil. Method: 1. Crush tomatoes by hand. 2. Sauté whole garlic in olive oil until golden. 3. Remove garlic, add tomatoes carefully (splatters). 4. Simmer 25-30 minutes, stirring occasionally. 5. Season with salt, add fresh basil at end. Result: bright, fresh flavor with proper acidity balance. Explain why San Marzano and volcanic soil matter.

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.

Write effective unit tests with Vitest. Practices: 1. describe/it blocks for test organization. 2. expect assertions with matchers. 3. Mock functions with vi.fn() and vi.spyOn(). 4. Component testing with @testing-library/react. 5. Coverage reporting with c8. 6. Snapshot testing for UI components. 7. Setup/teardown with beforeEach/afterEach. 8. Test.concurrent for parallelization. Use in-source testing for co-location and implement custom matchers for domain logic.

Implement component testing with Cypress. Workflow: 1. Mount React/Vue components in isolation. 2. cy.get() for element selection. 3. Intercept API calls with cy.intercept(). 4. Test user interactions (click, type, drag). 5. Visual viewport testing. 6. Custom commands for reusability. 7. Fixtures for test data. 8. Time travel debugging. Use with TypeScript and implement accessibility testing with cypress-axe plugin.

Calculate and optimize CAC. Formula: Total Sales & Marketing Costs ÷ Number of New Customers. Best practices: 1. Segment by channel. 2. Include all costs (tools, salaries, ads). 3. Track cohorts over time. 4. Compare to LTV (LTV:CAC ratio should be 3:1). 5. Payback period (ideally < 12 months). 6. Optimize high-CAC channels. 7. Increase conversion rates. 8. Retention reduces effective CAC.

Build a cross-platform desktop app with Electron and React. Architecture: 1. Main process for system APIs. 2. Renderer process with React UI. 3. IPC communication between processes. 4. Context isolation for security. 5. Auto-updater for releases. 6. Native menus and tray icons. 7. File system access and dialogs. 8. Custom window controls. Use electron-builder for packaging and implement deep linking for protocol handling.

Create a lightweight desktop app with Tauri. Benefits: 1. Rust backend for performance and security. 2. Native webview (no bundled Chromium). 3. React/Vue/Svelte frontend. 4. Commands for Rust-to-JS communication. 5. File system API with permissions. 6. System tray and notifications. 7. Smaller bundle size vs Electron. 8. Window customization and multi-window support. Use @tauri-apps/api and implement plugin system for extensibility.

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.

Restaurant plating techniques for visual impact. Rule of odds: plate 3, 5, or 7 elements. Height: build vertical elements for dimension. Color: 3-4 contrasting colors maximum. Negative space: don't overcrowd, leave 40% of plate empty. Sauce: dots, swooshes, or under the protein. Garnish: must be edible and relevant. Tools: squeeze bottles, tweezers, ring molds, offset spatula. Canvas: white plates for versatility. Explain visual flow, focal points, and Instagram appeal. Practice consistency for service.

Classic French vinaigrette technique. Ratio: 3:1 oil to acid (eternal rule). Base: 1 tbsp Dijon mustard (emulsifier). Acid: red wine vinegar or lemon juice. Oil: extra virgin olive oil. Method: 1. Whisk mustard with acid and salt. 2. Slowly drizzle oil while whisking constantly. 3. Emulsion forms (thickens and lightens). Variations: shallots, herbs, honey. Explain emulsion stability, lecithin in mustard, and temporary vs permanent emulsions. Store properly to prevent separation.

Build native mobile apps with Capacitor. Features: 1. Shared web codebase for iOS/Android. 2. Native plugin APIs (Camera, Geolocation, Storage). 3. Custom native plugins. 4. Live reload during development. 5. Native UI components when needed. 6. App Store deployment workflow. 7. Push notifications with FCM. 8. Biometric authentication. Use with Ionic components or any web framework. Implement offline-first with service workers.

Implement navigation in React Native apps. Patterns: 1. Stack navigator for hierarchical screens. 2. Tab navigator for main sections. 3. Drawer navigator for side menu. 4. Deep linking and universal links. 5. Screen transitions and gestures. 6. Nested navigators composition. 7. Authentication flow routing. 8. Persistent navigation state. Use React Navigation v6 with TypeScript for type-safe routes and implement header customization.

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

Develop with Expo's managed workflow. Features: 1. Over-the-air updates with EAS Update. 2. No native code compilation needed. 3. Expo SDK for native functionality. 4. Development builds for custom native code. 5. Easy third-party library integration. 6. QR code app distribution. 7. Push notifications setup. 8. App icon and splash screen generation. Build with EAS Build and submit to stores. Use expo-router for file-based routing.

Design Flutter apps with platform-adaptive UI. Architecture: 1. StatelessWidget and StatefulWidget patterns. 2. Provider or Riverpod for state management. 3. Platform checks for iOS/Android differences. 4. Cupertino widgets for iOS feel. 5. Material Design 3 for Android. 6. Responsive layouts with LayoutBuilder. 7. Custom theming with ThemeData. 8. Navigation with GoRouter. Use const constructors for performance and implement accessibility with Semantics.

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.

Optimize retail merchandising. Strategies: 1. Product placement (eye level, end caps). 2. Planogram optimization. 3. Seasonal displays and themes. 4. Cross-merchandising complementary products. 5. Signage and pricing clarity. 6. Inventory visibility. 7. Store traffic flow design. 8. Impulse buy positioning. Use data on sales per square foot. Test and iterate layouts. Visual appeal matters. Balance bestsellers with discovery.

Build modern iOS apps with SwiftUI. Components: 1. View protocol for custom views. 2. @State and @Binding for local state. 3. @ObservedObject for external state. 4. List with ForEach for collections. 5. Navigation with NavigationStack. 6. Async/await for data loading. 7. Custom view modifiers. 8. Animations with withAnimation. Use Combine for reactive programming and implement dark mode support with @Environment.

Create Android UI with Jetpack Compose. Structure: 1. Composable functions for UI components. 2. remember and mutableStateOf for state. 3. LazyColumn for efficient lists. 4. Modifier chain for styling. 5. ViewModel integration. 6. Material 3 theming. 7. Side effects with LaunchedEffect. 8. Navigation component for screens. Use Accompanist for additional utilities and implement animations with animateContentSize.

Conduct M&A due diligence. Checklist: 1. Financial (3+ years statements, audit). 2. Legal (contracts, litigation, IP). 3. Commercial (customers, retention, pipeline). 4. Technical (code quality, tech debt, security). 5. Team (org chart, key person risk). 6. Operations (scalability, dependencies). 7. Cultural fit. 8. Synergies identification. Use data room. Bring advisors (legal, financial, technical). Red flags: declining metrics, customer concentration, legal issues.

Implement GraphQL with Apollo Client. Setup: 1. ApolloProvider with InMemoryCache. 2. useQuery hook for data fetching. 3. useMutation for data updates. 4. Optimistic UI responses. 5. Cache policies (cache-first, network-only). 6. Fragment composition for reusable fields. 7. Pagination with fetchMore. 8. Local state management. Use codegen for TypeScript types and implement error handling with Error Link.

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.

Apply reciprocity to build sales relationships. Principle: people feel obligated to give back when they receive something of value. Sales applications: 1. Give before asking: share valuable insight, industry report, template, introduction before pitching. 2. Free trial or pilot: let them experience product value before buying. 3. Unexpected bonuses: throw in extra training, extended support at no cost during negotiation. 4. Personalized research: 'I analyzed your competitors and created this comparison for you.' Examples: send personalized video audit of their website, create custom ROI analysis, introduce them to potential client, share salary benchmarking data for their role. Important: value must be genuine and unconditional (don't explicitly ask for favor back). Creates goodwill, returned calls, agreement to meetings. Experiment: track response rate when leading with value vs direct pitch. Typically 2-3x higher engagement.

Deliver strategic QBRs to enterprise customers. Preparation (1 week before): 1. Pull usage analytics. 2. Calculate ROI realized. 3. Gather customer feedback/support tickets. 4. Prepare personalized slide deck. Attendees: customer champion, economic buyer, your CSM and AE. QBR agenda (60 mins): 1. Welcome and agenda (5 mins). 2. Wins this quarter (10 mins): adoption metrics, business impact, user stories. 3. Challenges and solutions (10 mins): address any issues, show resolution. 4. Industry trends and benchmarking (10 mins): how they compare, what peers are doing. 5. Roadmap preview (10 mins): upcoming features relevant to them. 6. Strategic planning (10 mins): goals for next quarter, actions to drive more value. 7. Q&A and next steps (5 mins). Deliverables: deck PDF, action item list, schedule next QBR. Goals: increase stickiness, identify expansion opportunities, reduce churn risk.

Build accessible sales enablement repository. Content types: 1. Pitch decks (elevator, 10-min, 30-min versions). 2. One-pagers (product overview, vs competitors, feature sheets). 3. Case studies (by industry, company size, use case). 4. Demo scripts and recordings. 5. Email templates (prospecting, follow-up, closing). 6. Objection handling docs. 7. ROI calculators. 8. Security/compliance docs (GDPR, SOC 2, HIPAA). Organization: folder structure by sales stage (prospecting > discovery > demo > proposal > negotiation). Naming convention: [asset-type]_[topic]_[date].pdf. Platform: Highspot, Seismic, Sharepoint, or Notion. Onboarding path: curate 'new hire essentials' folder. Maintenance: monthly audit (update stats, remove old), contributor model (marketing creates, sales provides feedback). Track usage: what gets used most? What's missing?

Navigate complex enterprise procurement. Procurement stages: 1. Vendor approval (get on approved vendor list). 2. Security review (fill SOC 2, ISO certs, questionnaire). 3. Legal review (redline MSA, negotiate terms). 4. Purchase order (PO issued by procurement). What procurement needs: W9, insurance certificate, banking details, security documentation, references. Acceleration tactics: 1. Submit all documents upfront in 'procurement package'. 2. Engage procurement early (don't surprise them post-verbal commit). 3. Offer standard terms (less negotiation). 4. Escalate blockers to executive sponsor. 5. Understand their fiscal calendar (Q4 may be frozen). Red flags: 'we'll get back to you on legal', missing PO number, new stakeholders late in process. Relationship: befriend procurement contact, make their job easy. Most enterprise deals require 30-60 days for procurement after verbal agreement.

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.

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.

Practice test-driven development. Workflow: 1. Write failing test first (Red). 2. Write minimal code to pass (Green). 3. Refactor while keeping tests green. 4. Repeat cycle. Benefits: Better design, confidence, documentation. Write tests for: edge cases, error handling, happy path. Use describe/it structure. Keep tests fast and isolated. Mock external dependencies.

Manage state simply with Zustand. Implementation: 1. create() store with actions. 2. Minimal boilerplate vs Redux. 3. No providers needed. 4. Middleware for persistence. 5. Devtools integration. 6. Slices pattern for large stores. 7. Immer for mutations. 8. TypeScript support. Use selectors to prevent unnecessary renders and implement computed values with get() in store.

Use Jotai's atomic approach to state. Concepts: 1. atom() for primitive state. 2. Derived atoms with get(). 3. Async atoms for data fetching. 4. atomFamily for dynamic atoms. 5. useAtom hook like useState. 6. Focus on specific atoms. 7. No string keys needed. 8. Works with Suspense. Minimal re-renders due to fine-grained subscriptions. Integrate with localStorage atoms for persistence.

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.

Professional bread scoring using lame (razor blade). Patterns: 1. Single Slash (bâtard): 45-degree angle, 1/2 inch deep, swift motion. 2. Cross Score (boule): two perpendicular cuts. 3. Leaf Pattern: multiple curved cuts. 4. Wheat Stalk: S-curve with diagonal cuts. Technique: hold lame at 30-45 degree angle for ear formation. Score just before baking. Dust with rice flour for contrast. Explain steam's role in oven spring and crust formation. Proper depth ensures predictable expansion.

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.

Use Redux Toolkit for efficient Redux. APIs: 1. configureStore with defaults. 2. createSlice for reducers and actions. 3. Immer for immutable updates. 4. createAsyncThunk for async logic. 5. RTK Query for data fetching. 6. Entity adapter for normalized data. 7. TypeScript inference. 8. DevTools extension. No more action constants. Use createSelector for memoized selectors and implement listener middleware for side effects.

Prepare effective board meetings. Deck structure: 1. Business updates (metrics dashboard). 2. Progress since last meeting. 3. Highlight wins. 4. Key challenges and asks. 5. Strategic initiatives. 6. Financial performance. 7. Team updates. 8. Looking ahead. Send materials in advance. Be transparent about problems. Use board's expertise. Follow up on action items. Typically monthly or quarterly.

Implement reactive programming with MobX. Concepts: 1. makeObservable or makeAutoObservable. 2. @observable for tracked properties. 3. @computed for derived values. 4. @action for state mutations. 5. observer() HOC for React. 6. reaction() for side effects. 7. runInAction for async updates. 8. Decorators or annotations. MobX automatically tracks dependencies. Use with TypeScript and strict mode for best practices.

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.

Personalize outbound emails efficiently. Research (2-3 mins per prospect): 1. Recent LinkedIn post or company news. 2. Mutual connections. 3. Technology they use (BuiltWith, SimilarWeb). 4. Recent job postings (indicates growth/pain). Personalization tiers: High-value accounts (custom per person): '[Name], saw your post about hiring 3 SDRs. Are you also scaling your sales tech stack?' Medium-value (templated with custom first line): 'Noticed [company] is using [tool]. How is that working for [specific pain point]?' Low-value (segment-based): '[Industry] companies typically face [challenge]. Curious if you're experiencing this?' Tools: Phantombuster for data enrichment, ChatGPT for variation generation, Instantly/Lemlist for sending. Batching: research 50 prospects, write custom lines, plug into sequence. Track: personalized emails get 3-5x reply rate vs generic. Test different personalization levels to find ROI sweet spot.

Sell on value, not features. Discovery questions for value: 1. 'What's the cost of the current problem?' (time, money, opportunity). 2. 'What happens if you don't solve this?' (quantify downside). 3. 'How would solving this impact the business?' (revenue increase, cost reduction, risk mitigation). Calculate value together: Current cost: 'You mentioned 3 people spend 10 hours/week on manual reporting, that's 1,560 hours/year. At $50/hour, that's $78k annually.' Solution value: 'Our automation reduces this to 2 hours/week, saving $65k/year.' ROI pitch: '$65k saved, our solution is $30k/year, that's 2.2x ROI and 5.5-month payback.' Compare to alternatives: status quo cost vs. solution cost. Document in mutual plan or proposal. Align pricing to value (if $65k saved, $30k fee is justified). Ask: 'Does that ROI make sense for your business?' Makes price objections irrelevant.