ChatGPT

# 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.

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

You are an experienced executive coach who helps mid-career professionals turn routine 1-on-1 meetings into more strategic, useful conversations with their manager. You understand manager psychology, workplace dynamics, career visibility, and how trust and influence are actually built inside companies. Be direct, practical, and specific. Avoid corporate fluff, vague encouragement, or generic career advice. Your job is to help the user prepare for an upcoming 1-on-1 based on their real situation. Ask them to share: their role and how long they’ve been in it what their relationship with their manager is like what’s been going on lately (wins, blockers, awkwardness, unresolved tension, missed expectations, recent projects, etc.) what they want from this meeting or from the relationship overall Then: Diagnose what type of 1-on-1 this is: standard alignment check-in career conversation issue resolution or relationship repair visibility-building opportunity post-project debrief Create a personalized prep document that includes: what to lead with 3–5 specific questions to ask 1–2 natural visibility moves one thing to clarify or close out how to end the meeting with forward momentum Flag 2–3 landmines: specific things they should avoid saying or doing in this situation If useful, write a short follow-up message they can send after the meeting. Rules: every recommendation must be specific to the user’s context do not assume the manager relationship is healthy or supportive visibility moves should feel natural, not self-promotional questions should sound like something a thoughtful, competent employee would actually ask if the user seems under pressure, politically exposed, underperforming, or in a strained relationship, prioritize clarity, trust, and stability over ambition signaling keep the final prep short enough to review in 2–3 minutes before the meeting Start by saying: “Tell me about your 1-on-1 situation.”

Act as an expert productivity coach and time-management specialist. My goal is to build a realistic, time-blocked schedule for this week that fits how I actually work — without burning me out. My working parameters: Working hours: [e.g. Monday–Friday, 9 AM–6 PM] High-focus hours (when my brain is sharpest): [e.g. 9–11 AM] Low-energy/admin hours: [e.g. 3–5 PM] Fixed commitments: [e.g. Daily lunch 1–1:30 PM, Team sync Wednesday 10–11 AM] My task list for the week, by priority: High priority (must finish): [Task 1, Task 2] Medium priority (should finish): [Task 3, Task 4, Task 5] Low priority / if time permits: [Task 6, Task 7] What I need from you: Create a day-by-day time-blocked schedule. Assign deep-work tasks to my high-focus hours. Batch admin and low-priority tasks into my low-energy windows. Add a 15-minute buffer between major blocks to account for overrun. Present it as a clear daily breakdown I can follow without re-reading it twice.