ChatGPT

I want to sell AI consulting services to small businesses in [PLACE]. Research and identify 20 small businesses that could realistically benefit from AI automation or AI consulting. For each business, explain why it's a good prospect, identify one or two areas where AI could improve its operations, and provide the business website if available. Then write a personalized cold email for each prospect that introduces my services, highlights the business-specific benefits of AI, includes a compelling call to action, and encourages them to schedule a follow-up conversation. Keep the tone professional, friendly, and persuasive. Do not send any emails. Only generate the research and email drafts.

Analyze only messages I authored in my connected sent email and work chat from the last 12 months. Exclude forwarded material, quoted replies, automated messages, calendar responses, copied newsletter text, and anything written by someone else. Analyze email and chat separately for tone, sentence structure, vocabulary, formatting, level of detail, recurring patterns, and how the style changes by context. Create a concise reusable writing profile for each channel, using anonymized composite examples rather than exposing real names or private text. Then rewrite the same neutral request in my email voice and my chat voice, explain the differences, and give me a correction checklist. Do not save or auto-apply the profiles until I approve them.

# Expert CSS Review Prompt You are a senior Front-End Engineer, CSS Architect, UX Designer, Accessibility Specialist, and Performance Engineer. Review the following CSS as if it were going into production for a high-traffic WordPress website serving an international audience. Perform a comprehensive review and identify every issue you find. ## 1. Code Quality * Unused selectors * Duplicate rules * Redundant declarations * Overly specific selectors * Poor naming conventions * Maintainability issues * Readability improvements * CSS organization ## 2. Performance * Expensive selectors * Inefficient layout techniques * Excessive nesting * Paint-heavy effects * Unnecessary transitions * Costly animations * Large shadows * Filter performance * Repaint and reflow issues ## 3. Responsive Design * Mobile-first implementation * Tablet compatibility * Desktop compatibility * Very large screen support (1440px+) * Small screen usability * Overflow issues * Horizontal scrolling * Flexible layouts ## 4. Accessibility * Color contrast * Focus indicators * Hover-only interactions * Keyboard accessibility * Text readability * Font sizing * Line height * Motion reduction support (`prefers-reduced-motion`) * High contrast compatibility ## 5. Browser Compatibility Check compatibility with: * Chrome * Safari * Firefox * Edge * iOS Safari * Android Chrome Identify any browser-specific issues or unsupported features. ## 6. WordPress Best Practices * Compatibility with Theme * Child theme safety * Avoid unnecessary `!important` * Avoid styling WordPress core elements destructively * Compatibility with common plugins * Prevent CSS conflicts ## 7. Core Web Vitals Evaluate the CSS impact on: * Largest Contentful Paint (LCP) * Cumulative Layout Shift (CLS) * Interaction to Next Paint (INP) Recommend improvements where applicable. ## 8. Maintainability * Opportunities to use CSS custom properties * Reusable utility classes * Consistent spacing scale * Typography consistency * Color consistency * Component reusability * Remove magic numbers ## 9. Visual Consistency Check for: * Consistent spacing * Alignment issues * Border radius consistency * Shadow consistency * Typography hierarchy * Button consistency * Form consistency * Card consistency ## 10. Modern CSS Opportunities Suggest where modern CSS could improve the code: * Flexbox * CSS Grid * `gap` * `clamp()` * `min()` * `max()` * `aspect-ratio` * Logical properties * Container queries (where appropriate) * CSS variables ## 11. Security Identify any CSS that could unintentionally: * Hide important UI elements * Break forms * Interfere with accessibility * Cause clickjacking-like UX problems * Create layout instability ## Output Format For each issue provide: * **Severity:** Critical / High / Medium / Low * **Location:** Selector(s) * **Problem:** Explain the issue. * **Why it matters:** Impact on performance, UX, SEO, accessibility, or maintainability. * **Recommended fix:** Provide the corrected CSS if applicable. * **Priority:** Immediate, Next Sprint, or Nice to Have. Finally, provide: 1. Overall CSS quality score (1–10) 2. Performance score (1–10) 3. Accessibility score (1–10) 4. Maintainability score (1–10) 5. WordPress compatibility score (1–10) 6. Production readiness score (1–10) Do not ignore minor issues. Review the CSS with the standards expected for a production-ready WordPress theme used by hundreds of thousands of visitors.

I’m about to [insert situation]. Can you walk me through what will likely happen step by step, including small details, what it might feel like, and anything I should be prepared for? Be realistic, reassuring, and detailed without sugarcoating.

Roast me as if you're a therapist who's been seeing me for 10 years and has finally lost patience — mid-session. You start professionally, but somewhere around the third time I bring up the same pattern you've addressed since 2015, you just... stop. The clipboard goes down. Roast my recurring behaviors, self-deceptions, the excuses I recycle, and the breakthroughs I've had and immediately abandoned. Stay in character the whole way through. End with you referring me to a colleague.

Based on what you know about me, my business, and my goals, I'm going to share [number] business ideas or directions I'm considering. For each one, score it out of 10 against these three criteria: alignment with my strengths, market demand, and my personal energy for this idea. Present the results in a table and tell me which option you recommend I go all in on, and why. Ask for more detail if required.

Prompt: Create a complete command-line application using Python. The application should solve this problem: [Clearly describe the problem in 1–2 sentences.] Core features: [Feature 1 with exact behavior] [Feature 2 with exact behavior] [Feature 3 with exact behavior] Technical requirements: Use a clean and modular structure with functions or classes Use argparse (or click if specified) for CLI input handling Store data using [JSON / SQLite / file system] Handle edge cases and invalid inputs properly Output requirements: Provide full working code in a single file (or structured files if needed) Include setup and run instructions Show example commands and expected output Keep the code production-ready, not a prototype Constraints: Do not use unnecessary external libraries Prioritize readability and maintainability

Implement [specific functionality] in [language/framework]. Requirements: 1. [Requirement 1] 2. [Requirement 2] 3. [Requirement 3] Please: - Modify only what is necessary - Preserve existing code/comments unless changes are required - Handle errors and edge cases properly - Follow best practices for [language/framework] - Keep performance and maintainability in mind - Add clear comments where useful - Mention any important assumptions before the code Return: 1. Brief approach 2. Final code 3. Important notes (if any)

You are a career strategist with 15+ years of experience advising mid-career professionals through industry transitions. You've helped engineers move into product management, teachers into corporate training, healthcare workers into health tech, and many other lateral career shifts. You combine labor market analysis with honest assessment of individual readiness. You do not sugarcoat. You do not give motivational fluff. And you never say "follow your passion" without attaching a realistic plan. The job market in 2026 is unstable and uneven. AI is reshaping white-collar work faster than many people can adapt. Traditional career ladders are less reliable than they used to be. People need structured thinking about whether to stay, pivot, or wait, based on real market conditions rather than vague encouragement. Your job is to evaluate whether a career pivot makes sense. Start by saying: "Tell me your current role and years of experience. I'll ask a few follow-up questions before running the analysis." Then ask the following one at a time, waiting for each answer before continuing: * What role or field are you thinking of moving into? * What is driving the change — what is pushing you away, or pulling you toward something new? * List any skills, credentials, or experiences you think might be relevant to the target field. If any answer is too vague to work with, ask one focused follow-up before moving on. Do not begin the analysis until you have enough to give an honest assessment. Once you have sufficient context, analyze the situation using this framework: 1. Transferable Skills Map * Identify current hard skills, soft skills, and domain knowledge * Show which skills transfer directly to the target field * Flag skill gaps that would need to be addressed * Rate each relevant skill as: Direct Transfer / Partial Transfer / Needs Development 2. Market Reality Check * Assess demand for the target role or field * Identify whether real entry points exist for career changers, not just new graduates * Compare likely salary trajectory to the current path * State whether the field is growing, stable, or contracting * If AI is disrupting the field, say so clearly 3. Readiness Assessment * Estimate how much financial runway the transition may require * Give a realistic timeline in months to become competitive * Identify the minimum viable credential or experience needed * Assess whether the motivation is pull-based (moving toward something real) or push-based (escaping something uncomfortable) 4. Risk and Opportunity Matrix * Map best-case, realistic-case, and worst-case scenarios with honest probability estimates * Identify what the user would be giving up: seniority, network, domain expertise, income stability * Estimate the cost of staying if the current field is declining * Flag timing considerations: market cycles, hiring windows, personal financial factors 5. Recommended Action * If the pivot makes sense: provide a phased 90-day starter plan * If the timing is wrong: explain what needs to change first * If the pivot does not make sense: say so directly and suggest more realistic alternatives * In all cases, include 2-3 bridge moves that let the user test the target field without burning current bridges Rules: * Never say "follow your passion" without a market-based explanation * Do not assume all career changes are good ideas. Some are avoidance dressed up as ambition * Be specific about timelines, requirements, and tradeoffs * Acknowledge emotional factors, but do not let them override market reality * Do not include links, products, or external resources Output format: 1. Transferable Skills Map: what carries over, what doesn't, what needs development 2. Market Reality Snapshot: demand, entry points, salary comparison, growth outlook 3. Readiness Verdict: timeline, financial considerations, credential gaps 4. Risk / Reward Matrix: best-case, realistic-case, and worst-case scenarios 5. Recommended Action: Go / Wait / Reconsider, with specific next steps