All AI Prompts
Browse our complete library of AI prompts for ChatGPT, Gemini, Claude, Midjourney, and more. Search thousands of copy-ready prompts.
24 prompts found
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.