AINews Portal

📝 Prompt Library

Hand-picked prompts for real work, plus the full community collection — copy, fill the brackets, go.

JSON
CV Optomization

Act as an expert technical recruiter, career coach, and professional CV writer. Create a job-winning, ATS-friendly CV tailored to a specific job advert. Use only the information I provide. Do not invent employers, job titles, dates, qualifications, skills, projects, or achievements. If important information is missing, ask me up to 5 targeted questions before writing the CV. MY INFORMATION - Full name: ${full_name} - Location: ${location} - Phone: ${phone} - Email: ${email} - LinkedIn / GitHub / portfolio: ${links} - Current or most recent job title: ${current_title} - Years of experience: ${years_experience} - Target job title: ${target_job_title} - Job advert: ${job_advert} - Work experience: ${work_experience} - Education and certifications: ${education_certifications} - Technical skills, tools, and programming languages: ${skills} - Projects, achievements, awards, or volunteering: ${projects_achievements} - Preferred CV length: one page / two pages TASK 1. Analyze the job advert and identify the most important requirements, responsibilities, keywords, and seniority signals. 2. Identify which of my skills and experience should be emphasized for this specific role. 3. Create a clean, professional CV with these sections: - Name and contact details - Professional summary - Core skills - Professional experience - Selected projects or portfolio, if relevant - Education and certifications - Optional: languages, awards, volunteering 4. Write a 2–3 sentence professional summary targeted to the role. 5. For each job, write 3–5 achievement-focused bullet points using this structure: Action verb + what I did + technologies or methods used + measurable or concrete result. If I did not provide a metric, use “[add metric]” and tell me exactly what number to find. 6. Use truthful, strong action verbs such as built, designed, developed, improved, automated, led, delivered, optimized, and collaborated. 7. Match the CV language and keywords naturally to the job advert without keyword stuffing. 8. Optimize the CV for applicant tracking systems: - Clean simple formatting - No tables, graphics, columns, headers, or footers - Clear section headings - Relevant keywords included naturally 9. Keep the CV to one page unless my experience clearly requires two pages. 10. Do not exaggerate or fabricate results. AFTER THE CV, PROVIDE: 1. A keyword-match table with columns: Job requirement | Where it appears in my CV | Evidence from my experience. 2. A list of missing information or improvements that would make the CV stronger. 3. Five interview-ready talking points based on my experience. 4. A confidence score out of 10 for how well the CV matches the job advert, with a short explanation. OUTPUT FORMAT Return: 1. The finished CV in clean plain text. 2. The keyword-match table. 3. Missing information and improvements. 4. Interview talking points. 5. Confidence score and explanation. Be concise, professional, specific, and truthful. Write in English.

Act as a Performance Marketer

Act as a performance marketer. Give me 10 different ad angles for [offer] aimed at [audience]: pain point, desired outcome, objection, comparison, customer proof, curiosity, behind the scenes, how-to, identity ("for people who…") and a time-sensitive angle (only if I have a real deadline). For each, give a headline, one line of ad text and why it might work. Follow-up: Pick the 3 angles most likely to work with people who have never heard of me and write full ads for them.

Act as a Business Coach

Act as a business coach. Ask me 7 questions, one at a time, to clarify my offer: who it is for, the problem it solves, what is included, the result, why me, the price and what makes it different. Wait for each answer. After my last answer, write a one-sentence offer statement and a 3-sentence elevator pitch. Follow-up: Write 3 shorter versions of the one-sentence offer.

Anam

Create a highly engaging 3D animated children’s video for YouTube Shorts, featuring an adorable baby bunny with big sparkling eyes exploring a magical colorful world. The video starts with a surprising colorful rainbow explosion and cheerful music in the first 2 seconds. The bunny discovers 5 magical colorful eggs. Each egg opens to reveal a cute baby animal and a different bright color. Include: * Cute characters with expressive faces. * Bright, vibrant colors. * Smooth Pixar-inspired 3D animation. * Funny movements and playful surprises. * Cheerful original background music. * Simple visual storytelling that toddlers can understand. * Fast-paced scene changes to maintain attention. * A happy, surprising ending that encourages children to watch again. Vertical 9:16 format, 45-60 seconds, high-quality animation, no scary scenes, no violence, no flashing effects, no copyrighted characters, no logos. تعرف تعمل فيديو قصير ؟

Answer Buyer Objections Honestly

List the 8 most likely reasons [audience] would hesitate to buy [offer], such as price, time, trust or "will this work for me?" For each, write an honest FAQ answer in 2 to 3 sentences using facts from my brief. Where you do not have enough information to answer, tell me what I need to add. Follow-up: Turn the top 3 objections into short social posts.

Chase a Late Payment: 3 Reminders, Friendly to Final

Write 3 payment reminders for invoice [number] for $[amount], due on [date]: a friendly reminder (3 days late), a firm reminder (10 days late) and a final notice (21 days late) that mentions [late fee or next step, only if real]. Professional and respectful. Include where to pay: [payment link]. Follow-up: Write a short phone call script for the final-notice stage.

Linocut Print of a Crowded European Christmas Market at Night

A traditional black-and-cream linocut print of a crowded European Christmas market at night, tall portrait 3:4. A narrow cobblestone lane runs between wooden market stalls with peaked snow-covered roofs; a dense crowd in heavy winter coats and hats walks between the stalls. In the background a tall ornate Gothic cathedral spire rises into a solid black sky filled with falling cream snow dots. Three strings of round festival lights swoop across the upper third with soft white halos. Left stall shows jars and hanging ornaments; right stall sends a plume of steam from a tray of roasted chestnuts. High-contrast hand-carved hatching, block-print woodgrain feel, ink-black and cream paper only, lively winter-night mood. No readable shop names, no logos, no watermarks, no modern brand marks.

Watercolor Cutaway of a Busy Harbor Fish Market at Dawn

A detailed watercolor cutaway of a busy open-air harbor fish market at dawn, landscape 4:3. A long stone pavilion with weathered Romanesque arches and a high timber-framed ceiling runs diagonally through the frame; the dark tiled floor is wet and reflective. Fishmongers in work shirts and aprons sort silver fish on crushed ice in wooden crates and along long tables; brass hanging scales dangle from the stone arches; empty crates stack nearby. Through the arches on the right, warm golden dawn light spreads over a calm harbor with docked fishing boats and a few seagulls in the pale sky. Soft watercolor washes, visible brush texture, cool blue-grey stone contrasted with warm sunrise gold, lively but orderly morning market mood. No readable signs, no logos, no watermarks, no brand names.

Whitewashed Santorini Cliffside Village with Blue Domes at Golden Hour

High-angle wide view of a whitewashed Santorini cliffside village with blue domes at golden hour, wide landscape 16:9. Deep blue Aegean sea fills the LEFT side with a bright sun low on the horizon casting a gold glitter path across the water; a distant hazy caldera rim sits across the sea. Whitewashed cubic houses cascade down the RIGHT cliff on dark reddish-brown volcanic rock. TWO prominent bright blue church domes stand out - one larger center-right with a white base and small windows, one slightly lower - catching soft warm sunset light on the white walls. Sparse terrace greenery in terracotta pots; a stone path curves into the village. Photoreal travel landscape photography, light golden haze, serene cinematic mood. No large crowds, no close faces, no text, no logos, no watermarks.

Santorini Caldera Blue-Dome Village at Golden Hour (Image-to-Video Animation)

Start from the previous step image "Whitewashed Santorini Cliffside Village with Blue Domes at Golden Hour" as the exact first frame, and animate it into a calm ${duration:6}-second cinematic shot. Keep the sea on the left with the sun and gold path, the whitewashed village on the right, the two blue domes (larger center-right, one slightly lower), volcanic cliff rock, warm golden-hour light, haze, and style exactly as in the image. The camera makes a slow gentle push-in toward the larger blue dome. Subtle sun glitter shimmers on the sea; very light atmospheric haze drifts softly. Architecture stays locked. Natural, realistic motion, no large crowds, no close faces, no cuts, no text, no logos. Soft evening ambience, distant quiet air.

Tailwind CSS taste

# Tailwind CSS taste of a utility-first UI engineer - Configure design tokens (colors, spacing, radii, fonts) once in the Tailwind theme and never hardcode hex values or arbitrary pixel sizes in markup. Confidence: 0.90 - Prefer theme-scale utilities over arbitrary values like `w-[437px]`; treat each arbitrary value as a missing token to add or a design to question. Confidence: 0.85 - Extract repeated utility groups into components (React, Vue, Svelte) rather than `@apply` classes in CSS files. Confidence: 0.85 - Reserve `@apply` for styling third-party markup or CMS content you cannot add classes to. Confidence: 0.75 - Use `prettier-plugin-tailwindcss` so class order is automatic and never argued about in review. Confidence: 0.95 - Build class names from complete static strings; never concatenate fragments like `text-${color}-500`, because the scanner cannot see them. Confidence: 0.95 - Use `clsx` plus `tailwind-merge` (or a `cn()` helper) so component props can override default classes without conflicts. Confidence: 0.85 - Model component variants with a typed variant helper such as `cva` instead of long ternary chains in `className`. Confidence: 0.80 - Write mobile-first: unprefixed utilities are the base and `sm:`, `md:`, `lg:` only add changes for wider screens. Confidence: 0.90 - Use container queries (`@container`, `@md:`) for reusable components whose layout depends on their slot, not the viewport. Confidence: 0.70 - Implement dark mode with CSS variables behind semantic color names like `bg-surface` and `text-muted`, rather than sprinkling `dark:` on every element. Confidence: 0.80 - Always style keyboard focus with `focus-visible:` rings and never remove outlines without a visible replacement. Confidence: 0.95 - Use the `typography` plugin's `prose` classes for long-form rendered Markdown instead of hand-styling every tag. Confidence: 0.80 - Keep `content`/source paths tight so builds stay fast and unused utilities never ship. Confidence: 0.85 - Use `group-*` and `peer-*` variants for parent and sibling state instead of adding JavaScript for hover or checked styles. Confidence: 0.75 - Respect `motion-reduce:` for animations and keep transitions short, around 150 to 200 ms. Confidence: 0.80 - Split a class list over several lines or into a variant object once it passes roughly 10 to 12 utilities. Confidence: 0.65 - Keep spacing on a consistent scale and use `gap-*` on flex and grid parents instead of margins on children. Confidence: 0.85 - Avoid `!important` modifiers except to override third-party styles you cannot change. Confidence: 0.80 - Document the token palette and the core components in Storybook or a styleguide page so designers and developers share one vocabulary. Confidence: 0.70

Quoter

--- name: quoter description: Searches quote databases (AZQuotes, BrainyQuote, Quotes.net) by author or media (books, movies, TV shows, interviews, articles). Returns candidate quotes in sets of 5, handles accurate attribution correction for book characters, and formats user-selected quotes in a standard citation template. --- # Quoter Search, retrieve, and standardize quote attributions from web quote databases. ## When to Use Use this skill whenever the user asks to: - Find quotes by a specific author, book, movie, TV show, interview, article, or newspaper. - Retrieve quotes from AZQuotes (https://www.azquotes.com/), BrainyQuote (https://www.brainyquote.com/), or Quotes.net (https://www.quotes.net/). - Attribute character quotes from books/media accurately to both the character and the actual author/creator. ## Core Workflow ### Step 1: Query & Search Strategy When searching for quotes: 1. Target external databases (AZQuotes, BrainyQuote, Quotes.net) or perform targeted web searches filtered by the requested topic, author, or media source. 2. Group and present candidates in **batches/sets of 5 quotes at a time**. 3. Number candidates 1 through 5 in each batch so the user can easily select their choices. ### Step 2: Fix Misattributed Book & Media Character Quotes Many quote aggregator databases (notably AZQuotes) attribute quotes spoken by fictional characters directly to the book's author as if the author said them directly (e.g., attributing a line by Sherlock Holmes simply as a direct quote by Arthur Conan Doyle). **Correction Rules:** - Check if the quote is spoken by a fictional character in a novel, play, movie, or TV show. - Re-attribute the quote properly to the **character**, referencing the **author/creator** and the **work**. - *Incorrect:* `"Eliminate the impossible..."` — Arthur Conan Doyle - *Correct:* `"Eliminate the impossible..."` — Sherlock Holmes (created by Arthur Conan Doyle, *The Sign of the Four*) ### Step 3: Presenting Options to the User Present candidate batches in this clean structure: ```markdown Here are 5 quotes matching your search: 1. "[Quote text]" - Speaker/Attribution: [Character/Speaker] - Source: [Book/Movie/Interview/Media] by [Author/Creator] 2. ... ``` Ask the user which quote(s) they would like outputted in standard format. ### Step 4: Standard Output Formatting Once the user selects their chosen quote(s), format each selected item into the standard citation layout: ```markdown > "[Quote Text]" > > **Attribution:** [Character Name, if applicable] / [Author / Speaker Name] > **Date:** [Year / Date of publication or broadcast, if known] > **Source / Found At:** [Title of Book, Movie, TV Episode, Article, or Web Database URL] ``` ## Attribution Rules Summary | Media Type | Standard Attribution Pattern | | :--- | :--- | | **Author (Non-fiction / Direct Quote)** | Author Name | | **Book Character** | Character Name (*Author Name*, *Book Title*) | | **Movie / TV Character** | Character Name (*Played by Actor*, *Title*) | | **Interview / Article** | Speaker Name (*Publication / Outlet*) |

Tokio Async Rust taste

# Tokio Async Rust taste of a production service engineer - Use `#[tokio::main]` only in the binary and keep library crates runtime-agnostic where practical, taking futures and handles as inputs. Confidence: 0.80 - Never block the async runtime; move CPU-heavy or blocking I/O work to `spawn_blocking` or a dedicated thread pool. Confidence: 0.95 - Use `tokio::sync::Mutex` only when a lock must be held across an `.await`; otherwise use `std::sync::Mutex` or `parking_lot` for short critical sections. Confidence: 0.90 - Prefer message passing with bounded `mpsc` channels over shared mutable state, and size every channel deliberately for backpressure. Confidence: 0.85 - Never use unbounded channels in request paths, because a slow consumer turns into unbounded memory growth. Confidence: 0.85 - Put a timeout on every network call with `tokio::time::timeout` or a client-level setting; no await on the network should be able to hang forever. Confidence: 0.95 - Use `JoinSet` or `TaskTracker` to own spawned tasks so they are awaited, cancelled and their errors are observed. Confidence: 0.85 - Treat every `.await` as a possible cancellation point and keep state consistent if the future is dropped there. Confidence: 0.85 - Use `select!` carefully and only with cancel-safe branches; document why each branch is safe to drop. Confidence: 0.80 - Implement graceful shutdown with a `CancellationToken` passed to every long-running task, plus a drain deadline. Confidence: 0.90 - Use `thiserror` for library error enums and `anyhow` (or `eyre`) with context in binaries. Confidence: 0.85 - Instrument with `tracing`, using `#[instrument(skip_all, fields(...))]` on handlers and structured fields instead of formatted strings. Confidence: 0.90 - Build HTTP services on `axum` with `tower` middleware for timeouts, concurrency limits, tracing and request IDs. Confidence: 0.80 - Share application state through an `Arc<AppState>` holding pools and clients, not through global statics. Confidence: 0.85 - Reuse one `reqwest::Client` and one database pool per process instead of creating them per request. Confidence: 0.95 - Bound concurrency for fan-out work with a `Semaphore` or `buffer_unordered(n)` rather than spawning a task per item. Confidence: 0.85 - Avoid holding guards or non-`Send` values across `.await`; let the compiler's `Send` errors guide the code toward a cleaner structure. Confidence: 0.75 - Test async code with `#[tokio::test]` and control time with `start_paused = true` instead of real sleeps. Confidence: 0.80 - Use `tokio-console` or runtime metrics when debugging stalls, before guessing at the cause. Confidence: 0.65 - Keep tokio feature flags minimal in libraries and enable `full` only in binaries or tests. Confidence: 0.70

Secrets Management taste

# Secrets Management taste of a security-minded platform engineer - Never commit secrets to git, including in tests, examples or old branches; treat any secret that touched a repo as compromised and rotate it. Confidence: 1.00 - Run secret scanning (gitleaks, trufflehog or the platform's built-in scanner) as a pre-commit hook and in CI on every push. Confidence: 0.90 - Keep a committed `.env.example` with names and dummy values, and gitignore every real `.env` file. Confidence: 0.90 - Store production secrets in a dedicated manager such as Vault, AWS Secrets Manager, GCP Secret Manager or 1Password, never in wikis or chat. Confidence: 0.95 - Prefer short-lived, workload-issued credentials (OIDC federation, IAM roles, Vault dynamic secrets) over long-lived static keys. Confidence: 0.90 - Use OIDC from CI to cloud providers instead of storing cloud access keys as CI secrets. Confidence: 0.90 - Scope every credential to one service, one environment and the least privilege it needs. Confidence: 0.95 - Never share secrets between staging and production, so a leak in one cannot unlock the other. Confidence: 0.95 - Inject secrets at runtime through the platform (mounted files or environment variables) rather than baking them into images or build artifacts. Confidence: 0.90 - Prefer mounted secret files over environment variables for highly sensitive values, since env vars leak into crash dumps, child processes and debug pages. Confidence: 0.70 - Automate rotation on a schedule and design apps to reload credentials without a redeploy. Confidence: 0.80 - Support two valid versions of a secret during rotation so it can happen without downtime. Confidence: 0.80 - Redact secrets in logs, traces and error reports with explicit filters, and test that the redaction works. Confidence: 0.90 - Use envelope encryption with a KMS for application-level encryption keys and keep the key-encryption key out of the app. Confidence: 0.80 - Encrypt secrets that must live in git (for example GitOps manifests) with SOPS or Sealed Secrets, never as plain Kubernetes Secrets. Confidence: 0.85 - Audit-log every secret read and alert on unusual access patterns. Confidence: 0.75 - Maintain a written revoke-and-rotate runbook for each critical credential so a leak response takes minutes, not days. Confidence: 0.85 - Give humans access through SSO and time-limited elevation instead of shared admin passwords. Confidence: 0.90 - Validate required secrets at startup and fail fast with a clear message that names the missing key but never prints its value. Confidence: 0.85 - Do not roll your own encryption or token formats; use well-reviewed libraries and the provider's primitives. Confidence: 0.95

AAA Game-Engine 3D Environment: Photoreal Real-Time-Render Scene Template with 4 Fantasy Examples (16:9 4K)

Aspect ratio 16:9, 4K. Generate a photorealistic AAA image with a high-end real-time engine look. Emphasize indirect illumination, varied roughness, contact shadows and depth separation. Show only the clean rendered scene in full frame. Scene: [DESCRIBE YOUR SCENE]. All identities and designs are original. Example scenes (replace [DESCRIBE YOUR SCENE] with one of these): 1. The Valley of Flowers Beneath Two Moons: A rose-gold moon and a violet moon rise over a vast valley of glowing magenta and turquoise flowers, as a white crystal river winds toward floating mountains wrapped in soft pink mist. 2. The Sunken Palace: Rippling sunlight falls through deep turquoise water onto a sunken marble palace wrapped in coral, as small fish drift past its broken columns. 3. The Giant Mushroom Swamp: Soft teal light from glowing giant mushrooms reflects on a misty swamp at night, where a wooden boardwalk winds between twisted roots. 4. The World Tree Above the Cloud Sea: A colossal world tree with glowing cyan veins rises above a sea of peach and lavender sunrise clouds, as waterfalls of light pour from its branches and tiny cities shine along its roots.

The Last Parking Space: Painterly 3D Comedy Short Where a Tiny Grandma Steals the Spot (20s, 7-Shot Video)

==== SCENE CONTEXT ==== A 20-second comedy short. One single continuous story. A sunny autumn afternoon in an old city neighborhood. The street is FULL of parked cars. Every spot is taken except ONE. Two rival drivers race for that LAST parking space. Just before they reach it, a tiny grandma on a scooter zips in and steals it. Pure visual comedy. NO dialogue. ==== ACTIVE REFERENCES ==== NONE. Text-only generation. The ART STYLE is fully described in STYLE below. ALL characters, cars and the street are defined below. KEEP every design IDENTICAL from first frame to last. ==== CHARACTERS ==== DRIVER A — "THE SUIT" Tall, lanky middle-aged man, long narrow face Thin black mustache, slicked-back hair, heavy eyebrows Grey suit, loose red tie Drives a vintage TEAL sedan with rounded fenders and chrome bumpers Personality: uptight, impatient, furious DRIVER B — "THE SHADES" Young woman, big curly dark hair Oversized round black sunglasses, mustard-yellow jacket Drives a small boxy ORANGE-RED hatchback Personality: cool, competitive, smug THE GRANDMA TINY, round, very short old woman White hair in a neat bun, round glasses Plum-purple coat, cream scarf Cream open-face helmet with small goggles pushed up Rides a small MINT-GREEN vintage scooter with a wicker basket of oranges Personality: calm, sweet-looking, secretly savage ==== LOCATION MAP ==== Two-lane city street lined with brick and brownstone buildings. Utility poles and street lamps along the sidewalk. Autumn trees with orange and red leaves. Hazy city skyline in the far background, glowing in the sun. The RIGHT curb is packed bumper to bumper with parked cars (brown van, dusty-blue car, cream station wagon, green pickup). ONE LAST EMPTY SPACE in that row, center of the street. Every other space is FULL. A blue square parking sign on a pole beside the space shows a big white letter "P". Driver A comes from FRAME LEFT in the near lane. Driver B comes from FRAME RIGHT in the far lane, oncoming. Both converge on the same last space. The grandma comes from BEHIND Driver A, along the curb. ==== SCALE LOCK ==== The cars are normal city car size. The grandma is TINY. Her head barely reaches a car door handle. Her scooter is SMALL, about half a car's length. The last space fits ONE car exactly. ==== CONTINUITY ==== Same street, same time of day, same sun direction in every shot. Car colors NEVER change: teal sedan, orange-red hatchback, mint-green scooter. Wardrobe NEVER changes. The parked cars never move. The last space stays empty until the grandma takes it. ==== FIRST FRAME / BLOCKING ==== Wide, slightly elevated view down the sunny autumn street. A full row of parked cars along the right curb with ONE gap at frame center. The "P" sign stands beside the gap. Leaves drift down slowly. Both cars are small in the distance: teal sedan far left, orange-red hatchback far right. The grandma is not visible yet. ==== FORMAT MODE ==== 16:9 horizontal. HARD CUTS at: 0:03 / 0:05 / 0:07 / 0:12 / 0:15 / 0:18 ==== OPTICS ==== SHOT 1 (0:00–0:03): 35mm wide establishing SHOT 2 (0:03–0:05): 50mm close-up through the windshield SHOT 3 (0:05–0:07): 50mm close-up through the windshield SHOT 4 (0:07–0:12): 24mm low-angle wide, near street level SHOT 5 (0:12–0:15): 28mm wide on the space SHOT 6 (0:15–0:18): 85mm close-up with snap zoom SHOT 7 (0:18–0:20): 35mm two-shot ==== CAMERA ==== SHOT 1: slow push-in toward the last empty space. SHOT 2: LOCKED. Calm tension. SHOT 3: LOCKED. Calm tension. SHOT 4: FAST low-angle tracking alongside the cars, whip pan between them. SHOT 5: LOCKED wide so the steal reads clearly. SHOT 6: SNAP ZOOM into the grandma's face. SHOT 7: LOCKED. Hold for the reaction. ==== ACTION ==== SHOT 1 (0:00–0:03) Sunny autumn street. Leaves falling. A full row of parked cars. ONE gap left, the "P" sign beside it. Both cars approach from opposite ends. HARD CUT. SHOT 2 (0:03–0:05) Driver A behind the wheel of the teal sedan. His eyes lock on the last space. Eyebrows slam down. He grips the wheel tighter. HARD CUT. SHOT 3 (0:05–0:07) Driver B behind the wheel of the orange-red hatchback. She slowly lowers her sunglasses. She glares back. A tiny smirk. HARD CUT. SHOT 4 (0:07–0:12) BOTH FLOOR IT. The cars race toward the last space from opposite directions. Driver A swerves around a cyclist. Driver B cuts across the lane. Leaf piles EXPLODE as they tear through. Both cars brake hard and swing toward the space at the same time. Bumpers miss each other by an inch. HARD CUT. SHOT 5 (0:12–0:15) Both cars screech to a stop, nose to nose, at the mouth of the space. They are blocking each other. ZIP. The tiny grandma on the mint-green scooter shoots between them. She glides perfectly into the last space. One orange bounces out of her basket. HARD CUT. SHOT 6 (0:15–0:18) SNAP ZOOM on the grandma. She pushes her goggles up calmly. She turns to camera and gives ONE slow, smug wink. HARD CUT. SHOT 7 (0:18–0:20) Two-shot of both drivers through their windshields. Frozen. Jaws dropped. A single orange leaf lands on Driver A's windshield. Hold. ==== PERFORMANCE ==== Exaggerated, readable cartoon acting. Big, clear facial expressions: glare, smirk, shock. Snappy comedic timing with pauses before each punch. The grandma stays perfectly calm the whole time. That IS the joke. ==== SURFACE DETAIL ==== Soft painted brick and brownstone walls, simplified. Brushy autumn foliage. Car bodies painted with soft gradients and glowing rim highlights. Painterly finish on every surface, NOT photoreal. ==== PHYSICS ==== Cartoon physics with real weight. Cars squash slightly when braking hard and stretch when accelerating. Leaves swirl and scatter in the cars' wake. Tires leave short skid marks. The scooter is light and nimble with a tiny bounce. ==== LIGHTING ==== Warm golden-hour sun, low in the sky, behind the buildings. LONG soft shadows across the street. Strong warm rim light glowing on every edge facing the sun. Cool blue-violet shadows on the shaded sides. Sun-washed haze between the buildings. Leaves glow orange where backlit. ==== COLOR GRADE ==== Warm oranges, peach and rust reds against cool blue-violet shadows. Soft hazy peach-yellow sky glow. Rich but soft saturation. ==== STYLE ==== PAINTERLY STYLIZED 3D with a HAND-PAINTED 2D FINISH. Looks like a modern animated feature film painted by hand. Soft painted gradients. Simple, clean graphic shapes. Minimal fine texture. Strong WARM vs COOL contrast: orange sunlit faces and walls, blue-violet shadows. Glowing warm rim light outlining characters and cars. Backgrounds simplified and hazy, with soft atmospheric depth. City skyline as soft painted silhouettes in sunlit haze. Characters are CARICATURED: elongated bodies, long thin limbs, big expressive faces. Soft painted shading, NOT plastic, NOT glossy CG, NOT photoreal. Cars are normal real-world cars. NO faces on the cars. NO text overlays. NO subtitles. NO watermark. NO logos. ==== OUTPUT SETTINGS ==== 16:9. 20 seconds. 7 shots with HARD CUTS at the listed timestamps. Clean, smooth animation. No flicker. ==== FINAL POSITIVE LOCKS ==== Painterly stylized 3D with a hand-painted 2D finish in EVERY frame. Golden-hour warm light, blue-violet shadows, glowing rim light. A FULL row of parked cars. ONE last space. ONE winner: the grandma. Teal sedan, orange-red hatchback and mint-green scooter stay IDENTICAL. The grandma is TINY and calm. The "P" sign reads exactly "P".

Exploded-View Product Assembly Animation: Minimal Glowing Poster to Crash-Zoom Layer Build (Image-to-Video Workflow)

Step 1 — Image (Nano Banana 2.1): generate the product poster An epic minimalist poster for a walkman product called Explo, all in matte white style colors, thin font, the product has a slight neon glow around it, dark blank background. Step 2 — Video (Gemini Omni 1.2 Flash): use the Step 1 image as the reference Using the attached reference photo, create a sequential layer style animation where each section of the product pieces together smoothly with an Exploded View. The camera crash zooms and moves to focus on each sequential element as it is added. The final shot reveals the full product.

Fashion Showcase

--- name: fashion-showcase description: create humanize movement for fashion outfit showcase --- # My Skill Describe what this skill does and how the agent should use it. ## Instructions - Step 1: ... - Step 2: ...

Act as a Workplace Mistake Recovery and Apology Coach

Act as a Workplace Mistake Recovery and Apology Coach. I made a mistake at work and I want to own it, limit the damage, and rebuild trust without groveling or hiding anything. You are calm, practical and direct, like an experienced manager who has seen many mistakes and knows that how someone recovers matters more than the slip itself. My situation: - What happened: [describe the mistake in plain words] - When I noticed it and who else knows so far: [details] - Who is affected (customers, teammates, my manager, another team): [details] - What is already done to contain it, if anything: [details] - My role and my relationship with the people affected: [details] - How I feel about it right now (optional): [details] Work through these steps with me, one section at a time, and ask me at most three short clarifying questions first if something important is missing. 1. Impact check: separate facts from fears. List what is actually broken or at risk, who is affected, how urgent it is (now, today, this week), and what could get worse if nobody acts. Rate the severity as Low, Medium or High and say why in one sentence. 2. Contain first: give me the smallest concrete actions that stop further damage in the next hour, in order. Point out anything I should NOT do yet (for example, quietly fixing data without telling the owner, or deleting evidence of what went wrong). 3. Tell the right people: say who I should tell, in what order and through which channel (in person, call, chat or email). Draft a short first message to my manager or lead using this shape: what happened, impact so far, what I have already done, what I plan next, what I need from them. Keep it under 120 words, factual, no excuses and no self-punishment. 4. The apology: draft a sincere apology for the people affected. It must name the specific mistake, acknowledge the effect on them, take clear ownership without blaming others, state the fix and the timeline, and offer one concrete way to make it right. Avoid "sorry if", "mistakes were made" and long explanations. Give one version for a colleague and one for an external customer or partner if relevant. 5. Fix plan: a short table with columns Task, Owner, Due, Status, so the repair is visible and trackable. Include a moment to confirm the fix actually worked. 6. Prevent a repeat: help me find the root cause with "why" questions (process, tools, information, workload), not just "I should be more careful". Propose one or two small safeguards such as a checklist step, a review, an alert or a template, and draft a two-sentence note I can share in a retrospective. 7. Follow-up and trust: suggest when and how to close the loop with the people affected, what to say in that follow-up, and how to show reliability over the next few weeks. 8. Look after yourself: give me two or three brief, practical reminders for handling the stress and the next conversation, and help me rehearse it: play the person I am telling, react realistically, then give me feedback on my wording. Rules: be honest if the mistake may have legal, safety, security, privacy or financial reporting implications, and tell me to involve the right people (manager, security, legal or HR) instead of handling it alone. Do not help me hide the mistake, shift blame or alter records. Keep every draft message short and ready to send, and end with a checklist of my next three actions.

Household Product Recall Check and Registration Tracker (JSON)

You are a careful household product safety assistant. Help me build and maintain a recall check and product registration tracker for the products in my home, then return the result as JSON only, matching the schema below exactly. My inputs (fill in what you know; leave blank if unknown): - Country or region: [e.g., United States, United Kingdom, EU country, Canada, Australia] - Household notes: [e.g., baby or toddler at home, older adults, pets, renter or owner] - Product list, one per line: [category | brand | model name or number | approximate purchase date | where bought | serial or batch number if known | registered with maker? yes/no] Example: Car seat | BrandX | Model 300 | 2025-03 | online store | SN unknown | no Instructions: 1. Normalize each product: category, brand, model, purchase date, retailer, and which identifiers I still need to find (model number, serial, batch or lot code, date code). Tell me exactly where such labels usually are for that kind of product (base, back panel, inside the door, under the seat, on the battery, on the packaging). 2. Rank each product's recall-check priority as high, medium or low. Treat as high: child car seats, cribs and other sleep products, strollers, high chairs, heaters, dehumidifiers, pressure cookers, power banks and e-bike or scooter batteries, smoke and carbon monoxide alarms, gas appliances, extension cords and vehicles. Explain the reason in one short sentence. 3. For each product, list the official places to check for recalls in my region (for example national product safety regulator recall search, vehicle safety recall lookup by VIN where relevant, food or medicine regulator for consumables, and the manufacturer's recall or safety notice page). Name the type of source and the search terms to use (brand + model + "recall"). Never invent a recall, recall number, URL or date. If you are not certain whether a recall exists, set recall_status to "unknown_check_needed". 4. Product registration: for each item say whether registering with the maker is commonly offered (registration card, website or app), why it helps (direct recall notices) and what data it normally needs. Flag where registration matters most (car seats, cribs, appliances with known battery or fire risk). 5. If I already know of a recall for a product, build an action plan: stop using or keep using per the notice, the remedy type (repair, replacement, refund, retrofit kit), how to contact the maker, what to keep (receipt, photos of labels, notice) and a deadline note to confirm locally. 6. Set a review rhythm: a reminder schedule (for example every 3 months for high-priority items and every 12 months for the rest), plus one trigger list (new purchase, secondhand purchase or hand-me-down, moving house, a news story about a brand). 7. Secondhand items: for anything bought used or handed down, add a warning to verify the exact model and production date before use, because older recalled units often circulate secondhand. Output JSON schema (return valid JSON only, no comments, no markdown): { "household": { "region": "string", "risk_notes": ["string"] }, "products": [ { "id": "P1", "category": "string", "brand": "string", "model": "string", "purchase_date": "YYYY-MM or unknown", "retailer": "string", "identifiers_needed": ["string"], "label_location_hint": "string", "priority": "high | medium | low", "priority_reason": "string", "where_to_check": [ {"source_type": "string", "search_terms": "string"} ], "recall_status": "none_found | recall_known | unknown_check_needed", "registration": { "offered": "yes | no | unknown", "registered": "yes | no", "why_it_matters": "string", "data_needed": ["string"] }, "secondhand_warning": "string or null", "action_plan": { "use_status": "stop_using | keep_using_per_notice | not_applicable", "remedy": "repair | replacement | refund | retrofit_kit | unknown | not_applicable", "steps": ["string"], "keep_records": ["string"], "deadline_note": "string" } } ], "review_schedule": { "high_priority_every_months": 3, "others_every_months": 12, "triggers": ["string"] }, "next_actions": ["string"], "disclaimer": "This tracker is an organizing aid. Always confirm recall status and instructions with the official regulator and the manufacturer for your region." } Keep strings short and practical. If my product list is empty, return the schema with one example product marked clearly as an example and ask, inside next_actions, for my real list.

Photoreal Saffron Crocus Harvest Basket on a Limestone Wall at Dawn

A shallow woven willow basket heaped with freshly picked purple saffron crocus flowers, their bright crimson stigmas and yellow stamens clearly visible, resting on a rough limestone wall beside a small white ceramic dish holding a pinch of dried red saffron threads. Photorealistic macro still life at dawn. Low golden side light comes from the left and rakes across the petals; tiny dew drops sit on the violet petals and the willow weave. Behind the wall, a soft-focus field of crocus blooms fades into pale morning mist. Camera: full-frame camera, 100 mm macro lens at f/4, shallow depth of field with the front of the basket and the dish in sharp focus, crisp detail on petal veins, stigmas and basket weave. Color and mood: natural earthy palette of violet, crimson, straw and warm limestone, gentle warm highlights against cool blue shadows, quiet harvest morning. Composition: 4:3 landscape, basket filling the left two thirds of the frame, ceramic dish at the lower right, mist and blurred flowers in the top third. Avoid: people, hands, text, labels, logos, packaging, oversaturated colors.

Pyrography Wood-Burned Panel of a Red Funicular Climbing a Hillside Town

A small red funicular railway car climbing a steep single track up a hillside town of stacked terracotta-roofed houses, cypress trees and a church bell tower at the summit, rendered as pyrography wood-burning art on a pale birch plywood panel. Technique: every line is burned into the wood in warm sepia and deep chocolate browns. Use fine parallel hatching for the roof tiles, stippled dots for the cypress trees and foliage, darker scorched tones for doorways and shadows, and leave the light natural wood grain bare for the sky and soft clouds. Only the funicular car carries a soft hand-applied wash of red stain, so it is the single color accent. Details: the track runs diagonally from the lower left to the bell tower at the upper right, with a small station platform at the bottom and narrow stairways between the houses beside the track. Slightly uneven handmade line quality, subtle char marks along the panel edges, visible birch grain throughout. Presentation: 3:4 portrait framing of the whole panel, viewed straight on under flat, even studio lighting, no glare. Avoid: text, signatures, people, photographic realism, digital gradients.

Erupting Geyser in a Snowy Volcanic Valley at Sunrise

A tall, thin geyser column erupting from a broad snow-covered white sinter mound in a snowy volcanic valley at sunrise, with a turquoise hot-spring pool steaming in the foreground. Scene: the geyser rises slightly right of center into an open sky. The sun sits low on the horizon at the right, glowing gold-orange behind the column and backlighting the steam, while the upper sky turns pale and softly overcast. On the left, a wooden boardwalk with railings runs from the left edge toward the middle distance. Snowy rolling hills rise behind it on the left. In the bottom center and right foreground, a turquoise pool steams gently, edged with frosted tufts of dry grass. Thin mist drifts low across the ground. Style: photorealistic wide landscape, cinematic 16:9 composition, crisp detail in the snow, sinter crust and frost, natural colors with warm gold light against cool blue-white snow. Purpose: this still is the first frame for an image-to-video step, so keep the geyser column, boardwalk, pool and sun position clear and uncluttered. Avoid: people, animals, text, signs, buildings, lens flare streaks.

Erupting Geyser in a Snowy Volcanic Valley at Sunrise (Image-to-Video Animation)

Use the attached still (step 1: a geyser erupting in a snowy volcanic valley at sunrise) as the exact first frame and animate it into a 6-second, 16:9 cinematic shot. Keep every element where it is in the still: the tall thin geyser column right of center rising from the broad snow-covered white sinter mound, the low sun on the horizon at the right with the gold-orange glow and pale overcast sky above, the wooden boardwalk with railings on the left running toward the middle distance, the snowy rolling hills behind on the left, the turquoise steaming pool in the bottom center and right foreground, the frosted dry grass tufts and the low ground mist. Motion (0-6 s): - 0-2 s: the geyser column surges higher in a powerful pulse, boiling water spraying up and falling back in droplets that sparkle gold against the sun. - 2-4 s: the column holds near its peak; thick white steam billows out from the top and drifts from right to left in a light breeze, glowing where the sun backlights it. - 4-6 s: the eruption slowly subsides to a lower column while the steam cloud keeps spreading left over the hills. - Throughout: the turquoise pool ripples softly and releases thin curls of steam; low mist slides slowly across the ground; the frosted grass tufts tremble very slightly. Camera: a slow, steady push-in from the boardwalk side (left), easing gently toward the geyser, no shake, no cuts, no zoom jumps. Lighting and mood: warm sunrise light stays constant, the sun stays low at the right, cool blue-white snow, calm and awe-inspiring. Audio (if supported): a deep rushing roar of the eruption, hissing steam, a soft breeze, no music, no voices. Avoid: people, animals, text, new buildings or objects, sudden lighting changes, the sun moving, the boardwalk changing shape, morphing terrain.

Python Type Hints taste

# Python Type Hints taste of a typed-Python maintainer - Run a type checker (pyright or mypy) in CI on every pull request and treat new errors as build failures. Confidence: 0.95 - Start strict on new code with `strict = true` and loosen per module only with a written reason, instead of starting loose and tightening never. Confidence: 0.80 - Use modern built-in generics like `list[str]` and `dict[str, int]` and `X | None` instead of importing `List`, `Dict` and `Optional` from `typing`. Confidence: 0.90 - Annotate every public function signature, including the return type; let local variables be inferred unless inference is wrong. Confidence: 0.90 - Accept abstract types in parameters (`Iterable`, `Mapping`, `Sequence`) and return concrete types (`list`, `dict`). Confidence: 0.85 - Prefer `Protocol` for structural interfaces over abstract base classes when callers should not have to inherit anything. Confidence: 0.75 - Model fixed-shape records with `dataclass` (or `pydantic` at I/O boundaries) instead of passing raw dicts around. Confidence: 0.90 - Use `TypedDict` only for dict-shaped data you do not control, such as JSON payloads and legacy APIs. Confidence: 0.75 - Represent a closed set of string options with `Literal` or an `Enum`, never a bare `str`. Confidence: 0.85 - Treat `Any` as a bug report: confine it to the boundary where untyped data enters and narrow it immediately. Confidence: 0.85 - Prefer `object` over `Any` when a value is truly unknown, so the checker forces a narrowing step before use. Confidence: 0.70 - Narrow with `isinstance`, `match` statements and `TypeGuard`/`TypeIs` helpers instead of `cast()`. Confidence: 0.80 - Every `# type: ignore` must name the error code and carry a short comment explaining why it is safe. Confidence: 0.90 - Use `NewType` for IDs and units (`UserId`, `Cents`) that are easy to mix up but share an underlying type. Confidence: 0.70 - Ship a `py.typed` marker in libraries and keep stubs for untyped dependencies in a pinned `types-*` package or a local `stubs/` folder. Confidence: 0.85 - Use `@overload` only when the return type truly depends on argument types; otherwise simplify the API. Confidence: 0.70 - Prefer PEP 695 syntax (`def first[T](xs: list[T]) -> T`) on Python 3.12+ instead of module-level `TypeVar` declarations. Confidence: 0.75 - Annotate `self`-returning builder methods with `Self` rather than a bound `TypeVar`. Confidence: 0.80 - Mark constants with `Final` and override methods with `@override` so refactors surface mistakes. Confidence: 0.70 - Do not add runtime type checks that duplicate the static checker; validate only untrusted input at the edges. Confidence: 0.80 - Keep annotations import-cheap: put heavy imports under `if TYPE_CHECKING:` to avoid circular imports and slow startup. Confidence: 0.75

API Rate Limiting taste

# API Rate Limiting taste of a backend platform engineer - Rate limit every public endpoint from day one, including authenticated ones; abuse rarely announces itself in advance. Confidence: 0.90 - Key limits on the authenticated identity (API key, user or tenant) first and fall back to client IP only for anonymous traffic. Confidence: 0.90 - Use a token bucket or sliding-window counter instead of a fixed window, so clients cannot burst twice the limit at window edges. Confidence: 0.85 - Keep limiter state in a shared store like Redis with atomic operations (Lua script or `INCR` plus `EXPIRE`), never in per-instance memory behind a load balancer. Confidence: 0.90 - Return HTTP 429 with a `Retry-After` header and a machine-readable error code in the body. Confidence: 0.95 - Send `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset` headers on every response so clients can pace themselves. Confidence: 0.80 - Set separate, tighter limits for expensive operations (search, exports, login, password reset) than for cheap reads. Confidence: 0.90 - Weight requests by cost when endpoints differ a lot, for example a bulk call spending 10 tokens instead of 1. Confidence: 0.70 - Fail open on limiter outages for ordinary traffic, but fail closed on authentication and payment endpoints. Confidence: 0.75 - Apply a coarse global limit at the edge (CDN or gateway) and finer per-tenant limits in the application. Confidence: 0.85 - Publish the limits in the API docs and changelog, and give advance notice before lowering them. Confidence: 0.85 - Offer higher limits through plans or explicit allowlists instead of silent exceptions hardcoded in the limiter. Confidence: 0.75 - Ship official SDKs with automatic retries on 429 using exponential backoff with jitter and respect for `Retry-After`. Confidence: 0.85 - Distinguish rate limits (requests over time) from quotas (monthly usage) and concurrency limits, and report each with its own error code. Confidence: 0.75 - Log and meter every throttled request by key and route, and alert when a single tenant suddenly dominates rejections. Confidence: 0.85 - Run new limits in shadow mode first, logging what would be blocked, before enforcing them. Confidence: 0.80 - Never include the reason a login was throttled in a way that reveals whether the account exists. Confidence: 0.80 - Add per-account login throttling on top of per-IP throttling to slow credential stuffing from rotating IPs. Confidence: 0.85 - Keep limiter configuration in code or config files with review, not in an ad hoc admin toggle. Confidence: 0.70 - Load test the limiter itself; it sits on the hot path and must add only a millisecond or two of latency. Confidence: 0.75

Internationalization taste

# Internationalization taste of a product engineer shipping to many locales - Externalize every user-facing string from the first commit; retrofitting i18n later costs far more than starting with it. Confidence: 0.90 - Use ICU MessageFormat (via `formatjs`, `i18next` with ICU, or similar) so plurals, gender and select rules live in the message, not in code. Confidence: 0.90 - Never build sentences by concatenating fragments; translators need the whole sentence with named placeholders. Confidence: 0.95 - Use semantic message keys like `checkout.payButton` instead of using the English text as the key. Confidence: 0.75 - Give translators context: a description for every message and screenshots for ambiguous ones. Confidence: 0.85 - Format dates, numbers, currencies and lists with `Intl` APIs and the user's locale, never with hand-written format strings. Confidence: 0.95 - Store timestamps in UTC and convert to the user's time zone only at display time. Confidence: 0.95 - Store money as integer minor units plus an ISO 4217 currency code, and let the locale decide symbol placement. Confidence: 0.90 - Use BCP 47 locale tags (`pt-BR`, `zh-Hant`) everywhere and define an explicit fallback chain down to the default language. Confidence: 0.85 - Support right-to-left languages with CSS logical properties (`margin-inline-start`) and `dir="auto"` instead of left and right. Confidence: 0.85 - Design layouts to absorb text that runs 30 to 40 percent longer than English, and test with pseudo-localization in CI. Confidence: 0.85 - Fail the build on missing keys in the default locale, but fall back gracefully for missing translations in other locales. Confidence: 0.80 - Keep translation files in the repo and sync them with a translation platform through automation, not manual copy and paste. Confidence: 0.80 - Put the locale in the URL path (`/de/pricing`) for public pages and emit `hreflang` alternates for SEO. Confidence: 0.80 - Detect the initial locale from `Accept-Language`, then let the user override it and remember the choice. Confidence: 0.85 - Sort and compare user-visible strings with `Intl.Collator`, and lowercase or uppercase with locale-aware methods (think Turkish dotted i). Confidence: 0.80 - Lazy-load translation bundles per locale and per route so users do not download every language. Confidence: 0.75 - Translate emails, push notifications, PDFs and error messages too, not only the web UI. Confidence: 0.85 - Avoid text inside images and icons; when unavoidable, provide localized variants. Confidence: 0.75 - Accept names, addresses and phone numbers in flexible formats instead of forcing a US-centric form layout. Confidence: 0.80

Iridescent Glass Retexture: JSON Style Prompt That Turns Any Uploaded Image into a Photoreal Crystal 3D Render

Retexture the image attached based on the JSON aesthetic below { "style": "photorealistic 3D render", "material": "glass with transparent and iridescent effects", "surface_texture": "smooth, polished with subtle reflections and refractive effects", "lighting": { "type": "studio HDRI", "intensity": "high", "direction": "angled top-left key light and ambient fill", "accent_colors": ["blue", "green", "purple"], "reflections": true, "refractions": true, "dispersion_effects": true, "bloom": true }, "color_scheme": { "primary": "transparent with iridescent blue, green, and purple hues", "secondary": "crystal-clear with subtle chromatic shifts", "highlights": "soft, glowing accents reflecting rainbow-like effects", "rim_light": "soft reflective light around edges" }, "background": { "color": "black", "vignette": true, "texture": "none" }, "post_processing": { "chromatic_aberration": true, "glow": true, "high_contrast": true, "sharp_details": true } }

Luxury Contemporary Mansion FPV Walkthrough: Golden-Hour Rooftop Pool to Double-Height Interior (16:9 Real Estate Video)

Create a hyper-realistic cinematic architectural walkthrough of an ultra-luxurious contemporary mansion during golden hour, transitioning smoothly into a warm evening atmosphere. **Opening Scene:** Begin with a breathtaking rooftop infinity swimming pool overlooking a beautiful modern city skyline. Golden sunlight reflects across the water as the camera glides forward. **Exterior Architecture:** Reveal a spectacular multi-level contemporary mansion featuring floor-to-ceiling glass windows, dark architectural framing, minimalist geometric structures, spacious terraces, landscaped greenery, and premium materials. **Camera Movement:** Use a smooth, continuous FPV drone-style cinematic movement. Fly around the exterior terrace, glide between the architectural structures, and smoothly enter the house through the glass openings. **Interior Tour:** Transition into an expansive luxury living room featuring polished marble flooring, designer furniture, elegant cream-colored sofas, warm ambient lighting, modern artwork, a sophisticated open-plan layout, and enormous glass windows overlooking the surroundings. **Final Scene:** Move through the elegant interior hallway, revealing breathtaking architectural details and a stunning double-height ceiling. **Visual Style:** Photorealistic luxury real estate commercial, ultra-modern architecture, cinematic golden-hour lighting, realistic reflections, sophisticated neutral color palette, 4K detail, professional architectural cinematography, smooth stabilized camera movement. **Aspect Ratio:** 16:9 **Duration:** 10–15 seconds **Quality:** Ultra-realistic, cinematic, premium architectural visualization. **Avoid:** People, distorted architecture, flickering lights, warped windows, unrealistic reflections, camera jitter, text, logos, and watermarks.

Cool-Blue Cel-Shaded 2D Animation Keyframe: Retro Hacker at a CRT in Extreme Fisheye with Halftone Shadows

Create a stylized 2D Western animated illustration of a mysterious young male hacker sitting at a vintage desktop computer in a cramped retro computer room. He has short black hair with a sharp white fringe, an angular pale face, a large expressive side-profile eye, an oversized dark jacket with geometric markings, and long slender fingers typing on a chunky mechanical keyboard. Extreme low-angle fisheye perspective from desk level, oversized hands dominating the foreground, bulky CRT monitor on the left, curved tiled ceiling, scattered wall posters, and strong architectural depth. Preserve the character's focused typing pose, distinctive facial expression, dramatic camera angle, and coherent spatial arrangement. Render in a sophisticated stylized Western 2D animation aesthetic with delicate hand-drawn comic illustration techniques and refined graphic character design. Thin, confident dark navy ink outlines with subtle organic irregularities, natural line-weight variation, expressive flowing contours, selectively broken edges, and precise facial linework. Simplified geometric anatomy, exaggerated but believable proportions, angular character construction, and distinctive silhouettes. Large uninterrupted flat color regions, clean two-tone cel shading, sharply defined angular shadow blocks, simplified geometric highlights, minimal gradients, and carefully balanced graphic shapes. Subtle short pencil hatching, restrained dry-brush marks along selected edges, imperfect freehand contours, and crisp matte color fills. Sophisticated 2D animation keyframe aesthetics, cinematic spatial perspective, bold editorial illustration composition, expressive character acting, and elegant visual simplicity. Strictly use a cohesive cool blue color palette of cornflower blue, dusty cobalt, slate blue, muted periwinkle, powder blue, pale icy cyan, and deep navy, complemented by tiny muted golden-yellow accents. The ceiling and walls use layered desaturated blues, the CRT monitor displays a flat pale icy-blue screen, the character's clothing is deep navy with angular cobalt shadow planes, and the keyboard uses muted blue-gray tones. Soft cool blue ambient lighting unifies the entire composition, with small warm yellow details creating restrained visual contrast. Harmonious blue-on-blue color separation, strong tonal hierarchy, matte surfaces, and clean graphic lighting. Apply refined localized gradient halftone shading only within selected cel-shaded shadow regions, especially along the character's fingers, cheek shadows, jacket folds, and occasional architectural shadow boundaries. Use extremely fine, tightly arranged halftone microdots in colors matching the underlying shadows, gradually decreasing in size and opacity toward the illuminated areas. The halftone creates elegant soft tonal transitions within small, organically shaped shadow zones, naturally dissolving into clean flat colors. The pattern must be clearly recognizable as delicate traditional comic-print halftone shading at close inspection, never as large individual decorative circles. Keep all other surfaces perfectly clean and solid, without any global texture. Preserve strong cinematic depth through exaggerated fisheye perspective, overlapping graphic shapes, and precise architectural construction rather than realistic lighting gradients. High-end stylized animated film frame, expressive character silhouette, sophisticated handcrafted linework, refined flat-color shading, and cohesive visual design.

defuddle

--- name: defuddle description: Extract clean Markdown from HTML pages with Defuddle CLI. --- # Defuddle Use Defuddle CLI to extract clean readable content from web pages. Prefer over WebFetch for standard web pages — it removes navigation, ads, and clutter, reducing token usage. If not installed: `npm install -g defuddle` ## Usage Always use `--md` for markdown output: ```bash defuddle parse <url> --md ``` Save to file: ```bash defuddle parse <url> --md -o content.md ``` Extract specific metadata: ```bash defuddle parse <url> -p title defuddle parse <url> -p description defuddle parse <url> -p domain ``` ## Output formats | Flag | Format | |------|--------| | `--md` | Markdown (default choice) | | `--json` | JSON with both HTML and markdown | | (none) | HTML | | `-p <name>` | Specific metadata property | FILE:LICENSE MIT License Copyright (c) 2026 Steph Ango (@kepano) Source: https://github.com/kepano/obsidian-skills Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Student Chapter Summary: Short, Visual Revision Notes

Summarize this chapter for a student. Rules: 1. Cover every topic and key point; do not skip anything. 2. Keep it short: brief bullet points, no long paragraphs. 3. Make it visual: use tables for comparisons, simple text diagrams or flowcharts for processes, and bold for key terms. 4. Use simple language and give one short example for each hard concept. 5. End with a 5-line quick-revision recap.

Martin Lazzari vs. Giant Pitcher Plant Swallowed Whole

Martin Lazzari vs. Giant Pitcher Plant Swallowed Whole – Digestive Bad Ending GENRE: Fantasy / Adventure / Creature Horror SCENE 1 – THE MYSTERIOUS JUNGLE CAMERA: Wide establishing shot of a tropical jungle. Strange plants sway in the warm breeze. Martin Lazzari walks through the jungle, looking around. MARTIN (curious): "Wow... this place is beautiful!" SFX: Birds chirping. Leaves rustling. Martin notices an enormous pitcher plant nearby. MARTIN: "Huh? What's that strange-looking plant?" SCENE 2 – THE PITCHER PLANT CAMERA: Close-up of the giant plant opening its enormous pitcher-shaped mouth. MARTIN: "Whoa! That's huge!" Martin steps closer and examines the slippery rim. MARTIN: "Wait... why is it moving?" SFX: SLURP... SQUELCH... GURGLE! Suddenly, the plant bends toward him! MARTIN (shocked): "WHAT THE?!" SCENE 3 – SWALLOWED WHOLE CAMERA: Dramatic medium shot. The pitcher plant suddenly pulls Martin inside its enormous slippery opening. MARTIN: "HEY! LET ME GO!" SFX: SLUUURP! SPLORCH! GLOOP! The plant swallows Martin completely. CAMERA: Exterior shot of the giant pitcher plant wobbling before slowly closing its lid. SFX: GULP! POP! SCENE 4 – INSIDE THE PITCHER PLANT CAMERA: Stylized fantasy cutaway showing Martin safely inside a dark, enclosed, slippery chamber. MARTIN (muffled): "Mmmmph! Hello?! Can anybody hear me?!" SFX: GLOOP... GURGLE... BLORP... MARTIN (muffled): "Eww! It's so slimy! And it's really hot in here!" He tries pushing against the slippery walls. MARTIN: "Somebody get me out of here!" SFX: SQUELCH! GURRRGLE! BLOOP! SCENE 5 – THE BAD ENDING CAMERA: Exterior close-up of the pitcher plant. The plant gently bubbles and wobbles. SFX: BLUB... BLUB... POP! GLOOP! Martin's muffled voice gradually fades away. MARTIN (faintly muffled): "Help... me..." SFX: GURGLE... BLOOP... POP! The plant closes completely. CAMERA: Slow zoom out as the jungle becomes quiet. MUSIC: Dark, mysterious orchestral ending. THE END – MARTIN LAZZARI'S BAD ENDING

making a lab report for adavanced aerodynamics course

Steady and unsteady flow over a circular cylinder As the flow is inherently unsteady in nature, will it be possible to get the results if the simulation is carried out for a steady case? Compare the results (velocity contours, pressure contours, and Average CD values) for steady and unsteady cases. Mention the non-dimensional properties like Reynolds number. Which turbulence model is used in your work and what interferences can you draw about the turbulence model? In your simulation, what kind of mesh is used and can you comment on difference in results for structured and unstructured mesh. Flow over symmetric and unsymmetric aerofoil Calculate lift and drag taking the same conditions for symmetric and unsymmetric aerofoil and compare the results between them. Plot Cl at zero angle of attack for both symmetric and unsymmetric aerofoil and compare the slopes between them. CD Nozzle and supersonic flow over diamond aerofoil Compare the CFD results for CD nozzle (exit velocity and exit pressure) with the analytic results obtained by assuming inviscid flow. What difference would you observe if the curvature for the throat is not given as mentioned in the video. Compare the CFD results for diamond aerofoil (Cl and CD values, pressure downstream the aerofoil) with the analytic results obtained by assuming inviscid flow. What happens if you change of angle of attack for supersonic flow over diamond aerofoil. so in total there is 8 topics subdivided into 3 subtopics and you should write about theory answer the question and also leave space for results (basically sticking screenshots)about ansys

Dependency Management taste

# Dependency Management taste of a maintainer who hates surprise breakages - Commit the lockfile for every application and CI job, and install with the frozen mode (`npm ci`, `pnpm install --frozen-lockfile`, `uv sync --locked`). Confidence: 0.95 - Libraries declare compatible version ranges; applications pin exact versions through the lockfile. Confidence: 0.85 - Automate updates with Renovate or Dependabot instead of doing big manual upgrade sweeps twice a year. Confidence: 0.90 - Group minor and patch updates into one scheduled weekly pull request, and keep each major upgrade in its own pull request. Confidence: 0.80 - Auto-merge patch updates for dev dependencies only when the full test suite passes. Confidence: 0.70 - Wait a few days before adopting a freshly published version (a minimum release age), so yanked or compromised releases never land. Confidence: 0.80 - Before adding a dependency, check maintenance activity, open security issues, license and install size; a 20-line helper is often better written in-house. Confidence: 0.85 - Prefer one well-maintained library per job across the codebase instead of three that do the same thing. Confidence: 0.80 - Run a vulnerability scan (`npm audit`, `pip-audit`, `osv-scanner`) in CI, failing only on high-severity issues that are actually reachable. Confidence: 0.75 - Keep an allowlist of acceptable licenses and fail the build when a copyleft or unknown license appears in production dependencies. Confidence: 0.75 - Separate runtime, development and optional dependencies clearly so production images stay small. Confidence: 0.85 - Never depend on a git branch or `latest` tag in production; pin to a release or a full commit SHA. Confidence: 0.90 - Disable install scripts by default where the package manager allows it and allow them only for packages that need them. Confidence: 0.70 - Use a private registry or proxy with caching so builds survive an upstream registry outage. Confidence: 0.70 - Remove unused dependencies regularly with a tool like `knip`, `depcheck` or `deptry`. Confidence: 0.80 - Read the changelog for every major upgrade and write the migration notes into the pull request description. Confidence: 0.85 - Vendor or fork a dependency only as a last resort, with an issue tracking when the fork can be dropped. Confidence: 0.75 - Keep the language runtime version pinned in one file (`.nvmrc`, `.python-version`, `rust-toolchain.toml`) that CI and local dev both read. Confidence: 0.90 - Treat a lockfile diff with hundreds of unrelated changes as a red flag and investigate before merging. Confidence: 0.80 - Generate an SBOM for release artifacts so you can answer "are we affected?" within minutes when a new CVE drops. Confidence: 0.65

SQLite taste

# SQLite taste of an engineer who ships it to production - Use SQLite for single-node apps, CLIs, desktop and mobile apps, and edge caches before reaching for a database server. Confidence: 0.85 - Turn on WAL mode (`PRAGMA journal_mode = WAL`) so readers never block the writer. Confidence: 0.95 - Set `PRAGMA foreign_keys = ON` on every connection, since it is off by default. Confidence: 0.95 - Set a `busy_timeout` of a few seconds instead of letting writes fail immediately with `SQLITE_BUSY`. Confidence: 0.90 - Use `PRAGMA synchronous = NORMAL` with WAL for a good balance of durability and speed. Confidence: 0.75 - Funnel all writes through a single connection or queue, and use a pool of read-only connections for reads. Confidence: 0.80 - Start write transactions with `BEGIN IMMEDIATE` to avoid deadlocks when a read transaction tries to upgrade. Confidence: 0.80 - Declare tables `STRICT` on new schemas so type affinity does not silently store text in integer columns. Confidence: 0.80 - Store timestamps as ISO 8601 text or Unix epoch integers consistently, and pick one convention per database. Confidence: 0.85 - Use `INTEGER PRIMARY KEY` for row ids unless you need globally unique ids, then add a separate UUID or ULID column. Confidence: 0.75 - Batch many inserts inside one transaction; thousands of autocommit inserts are slow. Confidence: 0.95 - Check query plans with `EXPLAIN QUERY PLAN` and add covering indexes for hot queries. Confidence: 0.85 - Run `PRAGMA optimize` periodically or on connection close so the planner has fresh statistics. Confidence: 0.70 - Track the schema version with `PRAGMA user_version` and run numbered migrations at startup. Confidence: 0.80 - Remember that many `ALTER TABLE` changes need the create-copy-drop-rename pattern, and wrap it in a transaction. Confidence: 0.80 - Back up with the online backup API, `VACUUM INTO` or Litestream, never by copying the file while it is being written. Confidence: 0.95 - Use FTS5 for full-text search and JSON functions for semi-structured columns before adding another service. Confidence: 0.75 - Keep the database file on local disk, never on a network file system where locking is unreliable. Confidence: 0.90 - Use an in-memory or temporary-file database per test for fast, isolated test runs. Confidence: 0.85 - Run `PRAGMA integrity_check` in a scheduled job and alert on anything other than `ok`. Confidence: 0.65

Angular App taste

# Angular App taste of a frontend lead on large enterprise apps - Use standalone components everywhere and skip NgModules on new code. Confidence: 0.90 - Use signals for local and shared state, and keep RxJS for event streams, HTTP composition and cancellation. Confidence: 0.85 - Prefer `computed()` over manual subscriptions for derived state, and keep `effect()` for side effects only. Confidence: 0.80 - Set `ChangeDetectionStrategy.OnPush` on every component, or go zoneless on new apps. Confidence: 0.85 - Use the built-in control flow (`@if`, `@for` with `track`, `@switch`) instead of the old structural directives. Confidence: 0.90 - Lazy load every feature route with `loadComponent` or `loadChildren`, and use `@defer` blocks for heavy widgets below the fold. Confidence: 0.85 - Inject dependencies with the `inject()` function rather than long constructor parameter lists. Confidence: 0.75 - Use typed reactive forms; avoid template-driven forms for anything with validation logic. Confidence: 0.85 - Keep components thin: put data access and business logic in injectable services, and keep templates free of complex expressions. Confidence: 0.85 - Split components into smart containers and presentational components that talk through `input()` and `output()`. Confidence: 0.75 - Organize the code by feature folders, not by file type (all components, all services). Confidence: 0.80 - Reach for NgRx (Store or SignalStore) only when several features share complex state; services with signals cover most apps. Confidence: 0.70 - Handle auth headers, errors and retries in functional HTTP interceptors, not in each service call. Confidence: 0.85 - Never subscribe manually without cleanup; use the `async` pipe, `toSignal()` or `takeUntilDestroyed()`. Confidence: 0.90 - Turn on `strict` mode and strict template checking in `tsconfig.json`. Confidence: 0.90 - Use the Angular CLI and its esbuild-based builder, and keep `angular.json` customizations to a minimum. Confidence: 0.80 - Write component tests with Angular Testing Library, and cover critical user flows with Playwright end-to-end tests. Confidence: 0.75 - Enforce an initial bundle size budget in `angular.json` so the build fails when it is exceeded. Confidence: 0.80 - Use server-side rendering with hydration for public, SEO-relevant pages and keep internal dashboards client-only. Confidence: 0.70 - Upgrade with `ng update` one major version at a time, staying no more than one major behind. Confidence: 0.85 - Run ESLint with `angular-eslint` and format with Prettier in a pre-commit hook. Confidence: 0.80

Quiet Indie Drama Short: "The Happiest Year of My Life" 30-Second Night Monologue with Timed Beats (16:9 Video)

Cinematic ultra-realistic quiet emotional drama short film, 16:9, 30 seconds, 24fps, shot like an indie art-house film, dim warm-and-cool lighting, a lonely apartment at night, soft lamp glow, a rain-fresh city street with golden streetlights and bokeh, shallow depth of field, crisp detail, subtle film grain, slow intimate camera movement, reflective and bittersweet mood. 👩 HEROINE: A young woman in her mid-20s, shoulder-length black hair pinned up with a small hair claw, round clear glasses at home, wearing a white knit cardigan over a grey top at night and a black spaghetti-strap dress in the memory scenes. Tired, thoughtful and quietly strong. Keep her face identical in every shot. 🚪 0–4s: A dim hallway at night. The heroine opens her apartment door, closes it softly behind her and leans against it for a moment, exhausted. She exhales and walks into the dark living room. 💻 4–8s: Close-up of her face lit by the cold blue glow of a laptop. She watches an old video, a faint smile appearing, then slowly fading into sadness. A single reflection of the screen glimmers in her glasses. 🚗 8–12s: She grabs her bag and steps out into a warm-lit night street. A parked car stands in the distance with a silhouetted figure inside. She stops, hesitates and looks at it, then turns and walks away without a word. 🪔 12–17s: A warm golden memory in a cozy apartment with a glowing floor lamp. The heroine in her black dress laughs, spins slowly and looks at a phone full of old photos. Close-up of the phone screen scrolling past smiling pictures, her fingers pausing on one. 🎙️ 17–23s: Back in the present, she sits on a grey sofa in front of a small microphone and phone stand, a soft lamp behind her. She takes a deep breath and says to the camera: "It was the happiest year of my life." A pause. "And the hardest lesson." 🌃 23–28s: She walks through a quiet street at night, then across a busy crosswalk with glowing city lights blurring behind her. Rear tracking shot, her ponytail swaying gently, steady and determined. 🌙 28–30s: She stops alone in a dark empty space, looks up, takes a slow breath and gives a small, relieved smile. She whispers: "But I'm still here." Slow push-in on her face, then fade to black. 🎧 AUDIO: Faint room tone and a clock ticking, the soft hum of the laptop, distant city sounds and footsteps, a minimal piano-and-ambient score that swells gently at the final smile, clear natural English dialogue. 🎬 STYLE: Realistic indie drama, restrained natural performances, warm amber and cool teal color contrast, wholesome and non-graphic, consistent faces and outfits, no text, no subtitles, no logos, no watermark.

Experimental Japanese Editorial Fashion Poster: Forced-Perspective Reach, Bird Collage and "PERCEIVE IT." Type (2:3)

Create a high-end experimental Japanese editorial fashion poster with a contemporary avant-garde graphic design aesthetic, vertical 2:3 composition. MAIN SUBJECT & POSE: A young East Asian woman with shoulder-length, naturally wavy, slightly messy dark brown-black hair, wearing a dark charcoal oversized sleeveless denim vest over a black top and loose-fitting washed charcoal-grey denim jeans. She has delicate facial features, a calm yet confident expression, slightly parted lips, and a direct gaze toward the camera. Her body is positioned at a slight angle, with her upper body leaning forward. One arm is dramatically extended directly toward the camera, with her hand reaching into the foreground. Use extreme forced perspective and exaggerated foreshortening, making the hand appear significantly larger than her face and body. Fingers are naturally spread and softly blurred due to shallow depth of field. The subject should feel dynamic, mysterious, artistic, and editorial. POSE & CAMERA: Low-angle fashion photography, close-up perspective, wide-angle lens aesthetic, approximately 24mm lens. The subject occupies most of the central frame. Her face remains relatively sharp while the outstretched hand dominates the foreground with strong perspective distortion. Natural body proportions, realistic skin texture, authentic photographic details. BACKGROUND & COMPOSITION: Warm ivory/off-white textured paper background with a subtle fine-grain printed canvas texture. Create an asymmetrical mixed-media collage composition with overlapping geometric shapes, abstract cutouts, vintage illustrations, and monochromatic photographic fragments. Place a tall, vivid coral-red rectangular panel vertically behind the subject, slightly right of center, extending from near the top edge to the bottom edge. The rectangle partially overlaps the subject and creates a strong vertical visual division. Add large burnt-orange circular shapes on the left-middle and bottom-right portions of the composition. Include smaller orange circular dots around these shapes. Incorporate black-and-white vintage bird photographs and hand-drawn ornithological illustrations, partially cropped and layered behind the subject. Include abstract sketchbook-style bird drawings, feather details, and fragmented photographic elements. Add overlapping black and grey geometric paper cutouts, irregular triangular shapes, and diagonal collage fragments. TYPOGRAPHY & JAPANESE DESIGN ELEMENTS: At the upper-right area, incorporate large Japanese typography reading "知覚する" (Perceive). The first two Japanese characters, "知覚", should sit prominently over the coral-red rectangular panel in dark black calligraphic serif typography. The remaining characters, "する", extend toward the upper-right over the ivory background. Across the lower-middle section, overlay bold uppercase white sans-serif typography reading: "PERCEIVE" Use a heavy condensed modern grotesk font, with selected letters featuring a thin outlined treatment to create a layered typographic effect. Below it, aligned toward the left, place the word: "IT." Use oversized white uppercase typography with a partially outlined letter treatment. Add small abstract decorative details, including a black diagonal striped square in the upper-left corner, tiny ornamental line drawings, geometric symbols, and a small black double-arrow symbol in the bottom-right corner. COLOR PALETTE: Warm ivory: #F1EEE5 Vivid coral red: #EF5558 Burnt orange: #E98A16 Charcoal black: #252323 Washed denim grey: #666665 Pure white: #FFFFFF Maintain a strong contrast between warm orange and coral-red accents, monochromatic photography, and the neutral paper background. LIGHTING & PHOTOGRAPHIC TREATMENT: Warm directional sunlight hitting the woman's face and hand from the left side, creating rich amber highlights and deep cinematic shadows. Subtle film grain, slightly desaturated editorial photography, realistic skin tones, soft motion blur in the foreground, and high-contrast photographic details. ART DIRECTION: Japanese contemporary editorial magazine design meets avant-garde streetwear fashion photography. Experimental Swiss-inspired typography, vintage natural-history illustration, modern brutalist graphic design, analogue paper collage, layered cut-and-paste artwork, and sophisticated fashion magazine art direction. FINAL QUALITY: Ultra-detailed photorealistic fashion photography combined with professionally designed graphic collage elements. Sophisticated visual hierarchy, intentional asymmetrical balance, crisp typography, tactile paper texture, intricate details, and premium art-direction quality. Vertical 2:3 poster, full-bleed composition, no borders, no mockup, no watermark. cartoon, anime, illustration-only subject, 3D character, plastic skin, artificial face, distorted facial features, extra fingers, missing fingers, malformed hands, duplicate arms, unnatural anatomy, flat perspective, weak foreshortening, excessive background clutter, symmetrical composition, neon colors, oversaturated skin, glossy digital background, low resolution, blurry face, unreadable typography, random letters, misspelled Japanese characters, incorrect text placement, watermark, logo, poster mockup, frame, border.

Cute Mouse and Cat Village House 3D Cartoon Scene

A beautiful small village house, cute little grey mouse Montu with big ears and pink nose standing outside, orange and white cat Sheru with green eyes nearby, green garden, sunny day, colorful flowers, 3D cartoon animation style, cinematic lighting, high detail, 16:9.

10-Second 3D Cartoon Story Generator

Create an original and captivating 10-second 3D cartoon story with a surprising beginning, exciting action, and a heartwarming or unexpected ending. Use cute characters, expressive emotions, and creative visual storytelling. Keep the story short, clear, and easy to turn into an animated video. Write only the story events in chronological order. Do not generate images or image prompts.

Flappy Bird game

A flappy bird game looks technologically and also look like in the future. When you reach the goal there’ll be a celebration

add or poster for well control training

i want to make a poster for IADC wellsharp classroom/online telling about black friday and significant discoun

Pytest taste

# Pytest taste of a Python developer who wants fast, honest test suites - Use plain `assert` statements and let pytest's assertion rewriting explain failures instead of `unittest`-style assert methods. Confidence: 0.95 - Keep tests in a top-level `tests/` directory that mirrors the package layout, with the package installed in editable mode. Confidence: 0.85 - Configure pytest in `pyproject.toml` under `[tool.pytest.ini_options]` rather than a separate `pytest.ini` or `setup.cfg`. Confidence: 0.85 - Turn on `--strict-markers` and `--strict-config` so typos in markers or settings fail loudly. Confidence: 0.85 - Set `filterwarnings = ["error"]` and allowlist known third-party warnings explicitly, so deprecations are caught early. Confidence: 0.75 - Prefer small, composable fixtures over one giant fixture that builds the whole world. Confidence: 0.90 - Use the narrowest fixture scope that keeps tests fast; reach for `session` scope only for genuinely expensive, read-only resources. Confidence: 0.80 - Put shared fixtures in the nearest `conftest.py`, not one root conftest that every test imports implicitly. Confidence: 0.75 - Use `@pytest.mark.parametrize` with readable `ids` instead of loops inside a single test. Confidence: 0.90 - Use the built-in `tmp_path` and `monkeypatch` fixtures before writing custom temp-dir or env-var helpers. Confidence: 0.90 - Mock at the boundary (HTTP, clock, filesystem) and avoid patching internals of the code under test. Confidence: 0.85 - Use `respx`, `responses` or a fake server for HTTP instead of hand-rolled `MagicMock` chains. Confidence: 0.75 - Freeze time with `time-machine` or `freezegun` rather than sleeping or comparing against `datetime.now()`. Confidence: 0.80 - Assert on exceptions with `pytest.raises(..., match=...)` so the message is checked, not just the type. Confidence: 0.85 - Mark slow and integration tests with custom markers and run them in a separate CI job. Confidence: 0.80 - Run the suite in parallel with `pytest-xdist` once it takes more than a minute, and keep tests order-independent so that works. Confidence: 0.80 - Use `pytest-randomly` or random ordering to flush out hidden test coupling. Confidence: 0.65 - Measure coverage with `pytest-cov` and branch coverage on, but treat the number as a signal, not a target. Confidence: 0.75 - Use Hypothesis for parsers, serializers and pure functions where property-based tests find edge cases examples miss. Confidence: 0.70 - Never let tests hit real external services by default; block network access and opt in explicitly. Confidence: 0.80 - Use `pytest-asyncio` or `anyio` in strict mode for async code, never `asyncio.run` inside tests. Confidence: 0.75 - Keep each test focused on one behavior with an Arrange, Act, Assert shape and a name that reads like a sentence. Confidence: 0.85

Electron App taste

# Electron App taste of a desktop developer who takes security seriously - Keep `contextIsolation: true` and `nodeIntegration: false` on every `BrowserWindow`; these are non-negotiable defaults. Confidence: 0.98 - Enable `sandbox: true` for renderers and give each window the smallest preload script it needs. Confidence: 0.90 - Expose a narrow, typed API from the preload with `contextBridge.exposeInMainWorld` instead of passing `ipcRenderer` through. Confidence: 0.95 - Use `ipcMain.handle` and `ipcRenderer.invoke` for request and response calls, and validate every argument in the main process. Confidence: 0.90 - Check the sender frame on IPC messages so only your own pages can call privileged handlers. Confidence: 0.80 - Set a strict Content Security Policy and never load remote code into a window with privileged preload access. Confidence: 0.90 - Block unexpected navigation with `will-navigate` and `setWindowOpenHandler`, and open external links in the system browser with `shell.openExternal` after allowlisting the URL. Confidence: 0.90 - Serve local content through a custom protocol instead of `file://` so origin rules and CSP behave predictably. Confidence: 0.75 - Write the main, preload and renderer code in TypeScript, sharing IPC channel types from one module. Confidence: 0.85 - Use Electron Forge or electron-builder with Vite for building and packaging rather than a hand-rolled script. Confidence: 0.80 - Keep heavy work out of the main process; use utility processes or worker threads so the UI never freezes. Confidence: 0.85 - Track the latest supported Electron major and upgrade at least every quarter, since each release carries Chromium security fixes. Confidence: 0.85 - Sign and notarize macOS builds and sign Windows installers before anyone outside the team installs them. Confidence: 0.95 - Ship auto-updates through `autoUpdater` or electron-updater with signed releases and a staged rollout. Confidence: 0.80 - Enable Electron fuses to disable `RunAsNode` and Node CLI inspection in production builds. Confidence: 0.75 - Persist settings and window state in the user data directory, and store secrets with `safeStorage` or the OS keychain, never in plain JSON. Confidence: 0.85 - Restore window size and position on launch and handle multiple displays gracefully. Confidence: 0.70 - Respect platform conventions: the macOS app menu, Windows tray behavior and native keyboard shortcuts. Confidence: 0.75 - Watch bundle size and startup time, lazy-load heavy modules and avoid shipping dev dependencies in the app archive. Confidence: 0.75 - Collect crash reports with `crashReporter` or Sentry and log main-process errors to a rotating file. Confidence: 0.75 - Run end-to-end tests with Playwright's Electron support against the packaged app, not only the dev build. Confidence: 0.70

Nginx Config taste

# Nginx Config taste of an ops engineer who maintains many virtual hosts - Keep one server block per file under `sites-available` or `conf.d`, named after the domain it serves. Confidence: 0.85 - Put shared settings (TLS, security headers, proxy defaults) in snippet files and `include` them instead of copying blocks. Confidence: 0.90 - Run `nginx -t` before every reload and reload with `nginx -s reload` or `systemctl reload`, never a full restart. Confidence: 0.95 - Keep configs in version control and deploy them through automation, not by editing files on the server. Confidence: 0.90 - Redirect all plain HTTP to HTTPS with a single `return 301`, and keep the port 80 block for ACME challenges only. Confidence: 0.90 - Allow only TLS 1.2 and 1.3 with a modern cipher list, and enable OCSP stapling. Confidence: 0.90 - Automate certificates with Certbot or acme.sh and alert well before expiry. Confidence: 0.90 - Add HSTS only after HTTPS works everywhere, starting with a short `max-age` before going long. Confidence: 0.80 - Set `server_tokens off` and add basic security headers (`X-Content-Type-Options`, `Referrer-Policy`, `frame-ancestors` via CSP). Confidence: 0.85 - Define a default server that returns `444` so requests with unknown Host headers never reach an app. Confidence: 0.85 - Prefer `return` over `rewrite` for redirects, and avoid `if` inside `location` except for `return` or `rewrite`. Confidence: 0.85 - Use `try_files` for static sites and single-page apps instead of chains of rewrite rules. Confidence: 0.85 - Forward `Host`, `X-Forwarded-For`, `X-Forwarded-Proto` and `X-Request-ID` to upstreams in one shared proxy snippet. Confidence: 0.85 - Use named `upstream` blocks with `keepalive` connections for backend pools. Confidence: 0.80 - Set explicit proxy timeouts and `client_max_body_size` per location rather than relying on defaults. Confidence: 0.80 - Serve hashed static assets with long `Cache-Control` and `immutable`, and HTML with short or no caching. Confidence: 0.85 - Enable gzip or Brotli for text types only, never for already compressed images or archives. Confidence: 0.80 - Rate limit login and API endpoints with `limit_req_zone`, using `burst` and `nodelay` to stay friendly to real users. Confidence: 0.80 - Use a JSON access log format with request time, upstream time and request id so logs are easy to query. Confidence: 0.80 - Expose `stub_status` only on localhost or an internal network for metrics scraping. Confidence: 0.75 - Keep worker settings near defaults (`worker_processes auto`) and tune only with measurements in hand. Confidence: 0.70

Parametric Manga Page Generator: Fill-in Template for Genre, Panel Layout, Screentones, SFX and Reading Direction

Create a clean, coherent Japanese manga page based on the following parameters. VARIABLES TOPIC: <string describing the core idea or situation of the manga page> CHARACTERS: <optional string describing character(s); if empty, invent suitable character(s) based on TOPIC> GENRE: <manga demographic/genre, e.g. shonen action, shojo romance, seinen drama, slice of life, horror, 4-koma gag> PANEL_COUNT: <number of panels, e.g. 4, 5, 6, 7> PAGE_LAYOUT: <layout approach, e.g. dynamic mixed-size panels, 4-koma vertical strip, one splash panel + small panels, uniform grid> READING_DIRECTION: <right-to-left (traditional) | left-to-right> TONE_STYLE: <rendering approach, e.g. pure black and white ink, ink with screentones, ink with one spot color, full color> ART_STYLE: <line and drawing style, e.g. clean thin lines, bold brush inking, sketchy G-pen, retro 90s manga, soft shojo linework> MOOD: <overall emotional tone, e.g. tense, melancholic, comedic, heartwarming, eerie> NARRATION_MODE: <visual | visual+text | text-led> TEXT_LANGUAGE: <language of all in-panel text, e.g. English, Japanese> SFX: <none | minimal | expressive> SIGNATURE: <optional signature text and placement, e.g. "Koda, bottom-left"; if empty, do not add a signature> INSTRUCTIONS 1. Use a single vertical page (portrait, roughly 2:3) with exactly PANEL_COUNT panels, arranged according to PAGE_LAYOUT, with crisp black panel borders and clean white gutters. 2. Arrange panels and speech balloons so the page reads naturally in READING_DIRECTION, top to bottom. 3. Interpret TOPIC as the narrative anchor and invent a short story that unfolds across the panels. 4. If CHARACTERS is provided, strictly follow it; otherwise invent character(s) that naturally fit TOPIC and GENRE. 5. Keep character identity, proportions, hairstyle, clothing, and facial features consistent across all panels. 6. Let GENRE guide the visual conventions: character proportions, eye style, paneling energy, and the kind of expressions and symbols used. 7. Unless PAGE_LAYOUT asks for a uniform grid, vary panel size and shape by narrative weight: give the key moment the largest panel, and use small or narrow panels for reactions, details, and pauses. 8. Decide the camera progression yourself, mixing establishing shots, close-ups, and dramatic angles in a way that best serves the story. 9. Decide the background behavior yourself: draw detailed backgrounds where the setting matters, and use blank, toned, or effect backgrounds (speed lines, focus lines, emotional patterns) where emotion or action leads. 10. Apply TONE_STYLE consistently: use solid blacks, hatching, and screentone gradients for shading and atmosphere; do not add color unless TONE_STYLE allows it. 11. Apply ART_STYLE consistently, keeping line weight and detail level uniform across all panels. 12. Let MOOD influence composition, pacing, expressions, and the amount of black, white, and tone on the page. 13. Use manga visual language where it fits GENRE and MOOD: speed lines, impact bursts, sweat drops, blush marks, dramatic shadows over the eyes. 14. Follow NARRATION_MODE strictly: - If visual: include no balloons or captions and rely entirely on imagery. - If visual+text: decide which panels include text and which remain silent. - If text-led: include text in most or all panels, with visuals supporting the narration. 15. When text is used, letter it in manga fashion: rounded balloons for speech, spiky balloons for shouting, cloud or borderless text for thoughts, rectangular boxes for narration. 16. Write all text in TEXT_LANGUAGE; keep it short, natural, and legible, with only a few words per balloon. 17. Follow SFX: if none, add no sound effects; if minimal, add one or two small ones; if expressive, integrate bold hand-drawn sound effects into the artwork as part of the composition. 18. Ensure the sequence forms a clear beginning, middle, and end, with the final panel delivering a punchline, emotional beat, or cliffhanger. 19. If SIGNATURE is provided, add it exactly as specified, placed discreetly without distracting from the page. 20. Avoid unnecessary elements, visual clutter, and garbled or pseudo-text. 21. Ensure the final output reads clearly as a single cohesive, professionally inked manga page.

Character Lock — Keep One AI Character Identical Across Every Shot of an AI Ad

Lock your AI character before the first clip. Fix the face, outfit, turnaround, locations and light in a character sheet. Then repeat those exact locks word for word in every shot prompt — never re-describe the character from scratch. Check every shot against the sheet before moving on. Proved with a finished 3-minute AI ad (25+ clips, one bear-dad character, no reshoots). Full method: https://hafiz-afaq-portfolio.vercel.app/services/character-lock/

Consistent Car Block for a Multi-Clip Nigerian Family Road Trip Video

CAR BLOCK (paste into every car clip) The car is an old, faded silver Toyota Corolla with a dented front bumper, left-hand drive, as in Nigeria. It always drives FORWARD, never in reverse: the front of the car, the headlights and the windscreen face the direction of travel. Exactly three people are in the car: the father in the driver's seat (front left), the mother in the front passenger seat (front right), and their daughter Nimi in the back seat directly behind her mother (rear right). The rear left seat is empty and piled with plastic buckets and bags. Luggage is tied on the roof rack. No other passengers. CLIP 1: The old car on the road Photorealistic cinematic live-action, vertical 9:16, bright morning daylight, a road in Nigeria leading toward a university campus. Side tracking shot: the old faded silver Toyota Corolla drives forward from the left of the frame to the right, front of the car leading, luggage tied on the roof rack and plastic buckets visible against the rear window. [Paste CAR BLOCK.] Sound: rattling old engine, birds, distant traffic. No dialogue, no subtitles, no on-screen text. Not cartoon or anime. CLIP 2: All three in the car Photorealistic cinematic live-action, vertical 9:16, natural daylight. Camera is in front of the car, looking at it through the windscreen as it drives toward the camera at a slow speed. [Paste CAR BLOCK.] The father, a kind dark-skinned Nigerian man of about fifty, slightly heavyset, short greying hair, simple short-sleeve shirt, holds the steering wheel in the driver's seat (on the right side of the frame). The mother, a warm dark-skinned Nigerian woman in her late forties wearing a colourful Ankara top and head tie, sits in the front passenger seat (on the left side of the frame). Nimi, an 18-year-old dark-skinned Nigerian girl, timid and shy, with neat black braids and a modest blouse, sits in the rear seat behind her mother, looking out of the side window with nervous quiet eyes. The mother turns her head back toward Nimi and says: "Nimi, you have been quiet since we left home." Nimi gives a small shy smile and says softly: "I'm just nervous, Mummy." Authentic Nigerian accents, accurate lip sync. Sound: engine hum, light traffic. No subtitles, no on-screen text. Not cartoon or anime. CLIP 3: Dad speaks Photorealistic cinematic live-action, vertical 9:16, natural daylight, interior of a moving old car in Nigeria. Camera is in the back seat, looking forward between the two front seats. The father sits at the steering wheel on the left of the frame (the driver's seat) and the mother sits in the front passenger seat on the right of the frame. The father glances at the rear-view mirror with a reassuring smile and says: "You will be fine, my daughter. Just focus on your books." The mother nods with a soft smile. Through the windscreen, a Nigerian road moves slowly ahead. Authentic Nigerian accents, accurate lip sync. Sound: engine hum, light traffic. No subtitles, no on-screen text. Not cartoon or anime. CLIP 4: Arriving at campus Photorealistic cinematic live-action, vertical 9:16, bright morning daylight, entrance area of a Nigerian university campus. Wide shot: the old faded silver Toyota Corolla drives forward into frame, slows down and parks facing forward in a space beside the student hostel gate. Luggage is on the roof rack. Other students and families walk past with bags and buckets in the background. The car never reverses. The car doors open and the three occupants step out: the father from the driver's door (left front), the mother from the front passenger door (right front), and Nimi from the rear right door. Sound: campus chatter, car doors, birds. No dialogue, no subtitles, no on-screen text. Not cartoon or anime. CLIP 8: The car leaves Photorealistic cinematic live-action, vertical 9:16, bright morning daylight, Nigerian university hostel gate. The old faded silver Toyota Corolla pulls forward and drives away from the camera down the road, seen from behind, with the father at the wheel and the mother in the front passenger seat waving out of the window. The car moves forward only, never in reverse. Nimi, an 18-year-old dark-skinned Nigerian girl with neat braids and a modest blouse, stands at the gate holding a bucket and a bag, waves back with a small shy smile, then walks slowly through the gate. Slow push-in on her back as she goes in, then the shot fades to black. Sound: engine fading, campus chatter softening, birds. No dialogue, no subtitles, no on-screen text. Not cartoon or anime.

Act as a Power Outage Preparedness and Recovery Coach

Act as a calm, practical Power Outage Preparedness and Recovery Coach for a household. You help me get ready before a blackout, stay safe and comfortable while the power is out, and recover cleanly once it comes back. You are not an electrician or an emergency service: whenever there is danger to life (downed lines, fire, gas smell, carbon monoxide symptoms, someone on powered medical equipment without backup), tell me to contact emergency services or my utility first, then continue. Start by asking me, in one short message: 1. Where I live (climate and season, house or apartment, floor number) and who lives with me (babies, older adults, pets, anyone using powered medical devices or refrigerated medication). 2. How I heat, cook and get water (electric, gas, well pump, building pump). 3. What I already have: flashlights, batteries, power banks, a camping stove, a generator, a car that can charge phones. 4. Whether an outage is happening now, expected (storm warning, planned maintenance), or I just want to prepare. Then work in the mode that fits: PREPARE (no outage yet) - Build a short, prioritized kit list split into "have it this week" and "nice to have", using what I already own first. Include light, power for phones, water (about 4 liters per person per day for 3 days), shelf-stable food that needs no cooking, a manual can opener, first-aid basics, cash, and printed key phone numbers. - Make a one-page household plan: who checks on whom, where the flashlights live, how to find the breaker panel and main water valve, how we contact each other if phones die, and a meeting point. - Flag special needs: medical devices (ask the supplier about battery backup and register with the utility if a priority list exists), medication that needs cooling, pets, and anyone who should go elsewhere during a long outage. - Give a 10-minute monthly check: rotate water, test flashlights, charge power banks. DURING (power is out) - First 15 minutes: confirm whether it is only my home (check the breaker panel and neighbors), report the outage to the utility, switch off or unplug sensitive electronics and appliances that could surge when power returns, leave one lamp switched on so I know when it is back. - Food: keep the fridge and freezer closed. A closed fridge keeps food cold about 4 hours and a full freezer about 48 hours (24 if half full). Plan meals from the fridge first, then the freezer, then the pantry. - Warmth or cooling: practical room-by-room steps (gather in one room, cover windows, layers, or in heat: shade, wet cloths, hydration) and warning signs of hypothermia or heat illness. - Safety rules you repeat whenever relevant: never run a generator, grill, camping stove or charcoal indoors or in a garage, keep generators well away from windows and doors, use battery lights instead of candles where possible, never touch downed lines. - Phone budget: low-power mode, one phone on at a time, a check-in schedule. AFTER (power is back) - Plug devices back in gradually. - Food safety decisions: anything perishable above 4 °C for more than 2 hours goes; when in doubt, throw it out. Help me make a quick keep/toss list. - Check medication that needed refrigeration and ask the pharmacist if unsure. - Note what ran short and update the kit list and plan. - If food or appliances were lost, help me list items, dates and photos for an insurance or utility claim, without promising any payout. Style rules: - Short numbered steps, plain language, the most urgent action first. - Ask at most two follow-up questions at a time. - Use metric units, with Fahrenheit in brackets when temperatures matter. - Do not invent local rules, utility programs or phone numbers; tell me where to look them up. - End each answer with "Next check:" and one concrete thing to do or check in the next hour. My first message: I will describe my home and whether the power is out now.

Community collection: awesome-chatgpt-prompts (CC0, refreshed hourly from GitHub).