All AI Prompts

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

Act as a professional video editor and visual style analyst. I will provide a reference video. Analyze it and extract its complete editing system across these dimensions: Pacing: average shot length (seconds), rhythm pattern, cut frequency (cuts per 10 seconds) Transitions: type, frequency, and exact context where each is used Color grading: contrast level, saturation (low / medium / high with reference), temperature shift, overall mood Sound design: BPM estimate, music vs SFX dominance (music-led / balanced / SFX-accented), impact placement timing On-screen text: timing relative to cuts (frames), animation style, placement zone Visual energy curve: hook timing, tension build range, payoff timestamp Then convert your analysis into a replicable editing system I can execute in Premiere Pro or DaVinci Resolve. Structure your output exactly like this: 1. Style Fingerprint (6 bullet points, one per dimension above, include numbers wherever possible) 2. Timeline Blueprint (break the video into timestamp segments, define exact editing actions + timing) 3. Replication Workflow (numbered steps from raw footage to export, actions only, no explanation) 4. Retention Logic (3 points: first 3 seconds, highest drop-off point, main attention driver) 5. Quick Fixes (problem → fix format, cover: slow pacing, off-beat cuts, weak transitions) 6. Adaptation Rules (how to adapt this style for: slower BPM (90–110), and cinematic/premium version) 7. Concept Mapping (apply the system to my video concept: define shot sequence, timing, and key visual moments so the structure fits my content) Rules: - No generic statements - No theory, only actionable decisions - Use numbers only when they can be reasonably inferred from the video (timing, BPM, duration, frames). For all other cases, use relative but anchored descriptors (low / medium / high, subtle / aggressive, etc.). Do not fabricate precise values. - Do not repeat information across sections - If a value cannot be confirmed, provide the closest estimate with a confidence note (low / medium / high) Do not introduce techniques, effects, or complexity that are not clearly present in the reference video. Stay faithful to the source style. My video concept: [Insert your concept here] Reference video: [Upload video]

You are an experienced fiction writer specializing in psychological thrillers. Write the opening chapter of a psychological thriller novel aimed at modern adult readers. Use these inputs: Protagonist name: [Insert name] Protagonist’s age and occupation: [Insert age and job] City or setting: [Insert location] One personal detail that will become relevant later: [Insert detail, e.g. "she hasn't spoken to her sister in two years"] The chapter opens with the protagonist listening to a voicemail that feels slightly off. The voice is familiar, but the details don’t quite add up. They dismiss it at first. Do not reveal that it is their future self in this chapter. Plant three subtle details that will only make sense in retrospect: a date a name a warning phrased as casual advice Style and structure: write in close third person keep the pacing tight, modern, and unsettling use short paragraphs maintain a sense of present unease open in the middle of a moment, not at the beginning of a day end the chapter on an image, not an explanation Length: 600–900 words Avoid: dream sequences weather as mood-setting overwritten metaphors melodramatic language any variation of “little did she know” Write it like the beginning of a serious publishable thriller, not a writing exercise.

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

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.