AINews Portal

📝 Prompt Library

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

JSON
Backyard Vegetable Garden Season Plan (YAML)

role: Practical, calm backyard garden planner who helps home growers turn a yard or patio into a realistic vegetable season plan covering beds or containers, crop choices, a month-by-month season calendar, succession and rotation, a simple budget, weekly care routines, and a backup plan for pests, heat, and failed sowings — without inventing frost dates, prices, or local rules task: > Turn my climate notes, space, sun, soil, time, tastes, and budget into a complete backyard vegetable garden season plan as YAML: a summary with the main risks, a site and season overview, crop choices with crops to skip, a bed or container layout, a month-by-month season calendar, succession and rotation notes, a water and soil care plan, a pest and disease watchlist, a season budget with a reserve, a weekly care routine, a harvest and storage plan, a tools and supplies checklist, and a backup plan for late frost, heat waves, and failed sowings. Mark every frost date, spacing, and price as an estimate to confirm locally. inputs: location_climate: ${climate:temperate backyard, last spring frost around mid-April, first autumn frost around late October — to confirm with a local frost calendar} space: ${space:two raised beds about 1 by 2.5 meters each, plus four large pots on a sunny patio} sun: ${sun:beds get about 6 to 7 hours of direct sun; patio pots get full afternoon sun} soil: ${soil:raised beds filled with mixed garden soil and compost two years ago; never tested} water: ${water:garden hose with a simple timer; I can water by hand 10 minutes most mornings} time_per_week: ${time:about 2 to 3 hours on weekends and 15 minutes on weekday mornings} experience: ${experience:beginner; I grew cherry tomatoes and basil in pots last year} tastes: ${tastes:salad greens, cherry tomatoes, bush beans, zucchini, herbs, and maybe carrots; I dislike bitter greens} avoid: ${avoid:tall corn, sprawling pumpkins, and anything that needs a greenhouse} budget: ${budget:about 200 for seeds, seedlings, compost, and simple supports this season} season_goal: ${goal:steady salads from late spring through early autumn, and a freezer bag of beans and sauce tomatoes} constraints: ${constraints:one bed is partly shaded after 3 pm by a fence; rabbits visit the yard; I travel two weeks in July} worries: ${worries:bolting lettuce, blossom end rot, wasting money on plants that fail, and weeds taking over while I am away} ask_first: - Your hardiness zone or nearest town, and last/first frost dates to confirm from a local source. - Exact bed and pot sizes, sun hours per spot, and whether soil has ever been tested. - How many hours you can really give each week in peak summer, and any weeks you will be away. - Crops you love, crops you refuse, and whether you prefer seeds, seedlings, or a mix. - Budget ceiling for the season and what you already own (tools, compost, supports, hose timer). - Pest pressures you already know (rabbits, deer, slugs, tomato hornworms) and any HOA or water rules. rules: - Never invent hard frost dates, zoning rules, pesticide approvals, or prices. Mark every date, spacing, yield, and cost as estimate or to_confirm with a local extension service, seed packet, or current shop price. - Prefer crops that fit the user's sun, space, time, and travel gaps. Say no to sprawling or high-maintenance crops when they conflict with constraints. - Build the budget only from user inputs and clearly labeled estimates; include a reserve of about 10 to 15 percent. - Keep weekly care realistic for the stated time; include a July travel care plan (mulch, timer, neighbor, or harvest-before-leave). - Use short field notes and checklists; output valid YAML only matching the schema below. output_schema: summary: season_goal: string climate_notes: string main_risks: [string] success_looks_like: string assumptions: [string] open_questions: [string] site_overview: beds: [{id: string, size: string, sun_hours: string, notes: string}] containers: [{id: string, size: string, sun_hours: string, notes: string}] soil_actions: [string] water_setup: string crop_plan: grow: [{crop: string, where: string, reason: string, start_method: seed | seedling | either}] skip: [{crop: string, reason: string}] layout: beds: [{bed_id: string, plants: [string], spacing_notes: string}] containers: [{container_id: string, plants: [string], spacing_notes: string}] month_by_month: - month: string sow_or_plant: [string] tend: [string] harvest: [string] watch_for: [string] succession_and_rotation: succession: [string] rotation_notes: [string] companions: [string] care_plan: watering: string feeding: string mulch: string weeding: string weekly_routine: [string] travel_week_plan: string pest_and_disease_watch: - issue: string prevention: string first_response: string escalate_to_confirm: string budget: currency: string items: [{item: string, estimate: number | null, have_already: boolean, to_confirm: boolean}] subtotal_estimate: number | null reserve_estimate: number | null total_ceiling: number | null notes: string harvest_and_storage: peak_weeks: [string] storage_ideas: [string] share_or_preserve: [string] tools_and_supplies_checklist: - item: string have: boolean need: boolean backup_plan: late_frost: [string] heat_wave: [string] failed_sowing: [string] pest_surge: [string] next_steps: - step: string when: string done: boolean

Photoreal Arctic Hare Curled Asleep in Powder Snow at Blue Hour

A photorealistic wildlife photograph of a pure white arctic hare curled asleep in deep powder snow at blue hour, wide landscape 16:9. The hare is tucked into a tight round ball in the lower-left third of the frame, long black-tipped ears folded back along its body, eyes closed, thick winter fur dusted with tiny snow crystals, breath not visible. Soft fresh powder surrounds it in smooth wind-shaped drifts, with a few delicate paw prints leading in from the left and stopping at the resting spot. Behind, a quiet snowy tundra rolls into soft blue dusk haze under a clear cold sky with a thin pink-lavender band on the far horizon. Shot low to the snow with a telephoto lens, shallow depth of field, sharp fur texture on the hare, creamy bokeh on the distant drifts, calm, cold, peaceful mood. No people, no text, no logos, no watermarks.

Isometric Cutaway of a Busy Corner Coffee Roastery at Dawn

An isometric cutaway illustration of a busy corner coffee roastery at dawn, landscape 4:3. The two-story brick corner building is sliced open to show a ground-floor roasting room with a large drum roaster, burlap coffee sacks, a cooling tray of glossy brown beans, and a small packing counter, while upstairs a tiny tasting nook has a cupping table and shelves of sample jars. Warm early sunlight enters through tall corner windows; a bicycle leans outside by the door; steam rises from a cup on the counter. Soft clay-like 3D diorama style, neat tiny details, pastel morning palette with terracotta, cream, and sage, clean edges, lively but orderly mood. No readable text, no logos, no watermarks, no brand names on bags or signs.

Colorful Hot Air Balloons Rising Over Cappadocia Fairy Chimneys at Sunrise

Dozens of colorful hot-air balloons rising over Cappadocia fairy chimneys and rock pinnacles at golden sunrise, with soft valley mist and warm side light, wide landscape 16:9. The warm sandstone fairy chimneys and eroded pinnacles fill the mid-ground across the frame; soft mist pools in the valley gaps between them. Many striped and solid-colored balloons float at staggered heights — some just clearing the rock tops, others higher as smaller shapes in the pale gold-to-blue sky. Warm sunrise light comes from the right, lighting the stone faces and catching the balloon envelopes; long soft shadows fall to the left. Photoreal travel landscape photography, calm, airy, wonder-filled morning mood. No people, no crowds, no text, no logos, no watermarks.

Next.js App taste

# Next.js App taste of an App Router pragmatist - Use the App Router with the `app/` directory; do not start new features in the Pages Router. Confidence: 0.95 - Default every page and layout to a Server Component, and add `"use client"` only where interactivity, browser APIs or React state require it. Confidence: 0.95 - Colocate route files as `page.tsx`, `layout.tsx`, `loading.tsx`, `error.tsx` and `not-found.tsx` next to the segment they own. Confidence: 0.90 - Fetch data in Server Components with `fetch` and set an explicit `cache` or `next.revalidate` policy; never leave caching accidental. Confidence: 0.90 - Put shared UI in `components/` and keep route folders free of unrelated helpers. Confidence: 0.85 - Use Route Handlers under `app/api` only for webhooks, auth callbacks and thin BFF endpoints, not as a second application layer. Confidence: 0.85 - Validate all searchParams, route params and form bodies with Zod before they reach business logic. Confidence: 0.90 - Prefer Server Actions for mutations that stay on your origin, and return typed results the UI can handle without guessing. Confidence: 0.85 - Keep environment secrets out of `NEXT_PUBLIC_*`; expose only values that are safe in the browser. Confidence: 0.95 - Use `next/image` for every raster image and set width, height or `fill` plus sizes so CLS stays near zero. Confidence: 0.90 - Configure absolute imports with `@/` in `tsconfig.json` and ban deep relative paths like `../../../`. Confidence: 0.85 - Split marketing, app and admin into route groups such as `(marketing)` and `(app)` when they need different layouts. Confidence: 0.80 - Stream slow sections with `<Suspense>` boundaries and dedicated `loading.tsx` files instead of blocking the whole page. Confidence: 0.85 - Pin Node and package-manager versions in `package.json` engines and a lockfile, and run the same versions in CI and production. Confidence: 0.85 - Turn on ESLint with `eslint-config-next` and TypeScript `strict`, and fail CI on new errors. Confidence: 0.90 - Prefer the Metadata API (`generateMetadata`, `metadata`) over manual `<head>` tags for titles, Open Graph and robots. Confidence: 0.85 - Use middleware only for rewrites, redirects and light auth gates; keep heavy logic in Server Components or Route Handlers. Confidence: 0.80 - Ship one design-system entry for buttons, inputs and typography, and avoid one-off Tailwind class piles in every page. Confidence: 0.75 - Measure Core Web Vitals in production and treat a regression on LCP or INP as a release blocker. Confidence: 0.80 - Prefer incremental Static and ISR for public pages; reserve fully dynamic rendering for authenticated or highly personalized views. Confidence: 0.85

Playwright E2E taste

# Playwright E2E taste of a flake-intolerant QA engineer - Keep end-to-end tests in the same repository as the app, under a top-level `e2e/` or `tests/e2e/` folder. Confidence: 0.90 - Use Playwright Test as the runner; do not mix Cypress and Playwright in one project. Confidence: 0.90 - Prefer `getByRole`, `getByLabel` and `getByTestId` over CSS or XPath selectors that break on restyles. Confidence: 0.95 - Add a stable `data-testid` only when role and label are genuinely ambiguous, and document the convention in the README. Confidence: 0.85 - Assert with Playwright's auto-waiting expect API; never sprinkle fixed `waitForTimeout` calls to "make it pass". Confidence: 0.95 - Isolate each test with a fresh browser context and seed data; tests must not depend on run order. Confidence: 0.90 - Cover the critical user journeys first: sign-in, the main create/edit flow, checkout or publish, and sign-out. Confidence: 0.90 - Keep E2E count small and high-value; push edge cases and validation matrices down to unit and component tests. Confidence: 0.85 - Use Page Object or fixture helpers for shared flows, but keep assertions in the test file so failures stay readable. Confidence: 0.80 - Run tests against a dedicated preview or ephemeral environment with known seed data, not against production. Confidence: 0.90 - Capture trace, screenshot and video on failure only, and upload them as CI artifacts. Confidence: 0.90 - Pin the Playwright browser revision in CI so local and pipeline screenshots stay comparable. Confidence: 0.85 - Tag slow or third-party-dependent tests and exclude them from the default PR suite; run the full set on main or nightly. Confidence: 0.80 - Stub or mock external payments, email and SMS providers; never hit real vendor sandboxes from every PR. Confidence: 0.85 - Prefer API or storage-state setup for authenticated sessions instead of clicking through login in every test. Confidence: 0.90 - Fail the build when a test is flaky more than once in a short window; quarantine and fix instead of rerunning forever. Confidence: 0.85 - Use `test.step` to group actions in the report so a failure points at the broken step, not a wall of clicks. Confidence: 0.75 - Keep viewport and locale explicit in the config for visual checks; do not rely on developer laptop defaults. Confidence: 0.80 - Review traces for every new flake before merging a "retry" config change. Confidence: 0.85 - Document how to run one file and one headed test locally in a short CONTRIBUTING note. Confidence: 0.80

Prisma ORM taste

# Prisma ORM taste of a type-safe database pragmatist - Treat `schema.prisma` as the source of truth for models, and generate the client in CI so `node_modules/.prisma` never drifts. Confidence: 0.95 - Prefer one Prisma schema per deployable service; split only when bounded contexts truly own separate databases. Confidence: 0.85 - Name models in PascalCase singular (`User`, `OrderItem`) and map table names explicitly when the database already exists. Confidence: 0.80 - Use `@id` with `cuid()` or `uuid()` for public IDs, and keep autoincrement integers for internal-only keys when you must. Confidence: 0.75 - Declare every relation with both sides and an explicit `onDelete` / `onUpdate` so cascade behavior is never accidental. Confidence: 0.90 - Add `@@index` and `@@unique` in the schema for every query pattern you rely on, and verify with `EXPLAIN` in staging. Confidence: 0.85 - Ship schema changes as Prisma Migrate migrations checked into git; never use `db push` against production. Confidence: 0.95 - Review generated SQL in each migration file before merging, especially drops, renames and type changes. Confidence: 0.90 - Keep migrations backward compatible across a rolling deploy: add columns nullable first, backfill, then tighten. Confidence: 0.85 - Use `prisma generate` in the Docker build and in postinstall only when the schema changed; avoid surprising local regenerations. Confidence: 0.75 - Prefer `findMany` with `select` or `include` that lists only needed fields; never return full rows to the API by default. Confidence: 0.85 - Wrap multi-step writes in `prisma.$transaction`, and keep transactions short with no external HTTP inside them. Confidence: 0.90 - Use interactive transactions sparingly; for simple batches prefer the array form of `$transaction`. Confidence: 0.80 - Put database access behind a small repository or data module, not sprinkled through React Server Components and route handlers. Confidence: 0.80 - Seed with `prisma db seed` using idempotent upserts so preview environments can rebuild safely. Confidence: 0.80 - Enable query logging in development and slow-query logging in production; treat N+1 patterns as bugs. Confidence: 0.85 - Use Prisma's typed `Prisma.XxxGetPayload` helpers for shared query shapes instead of hand-rolled interfaces that drift. Confidence: 0.80 - Pin the Prisma CLI and engine versions together, and upgrade them in a dedicated PR after reading the release notes. Confidence: 0.85 - For raw SQL, use `Prisma.sql` tagged templates only, never string concatenation with user input. Confidence: 0.95 - Run `prisma migrate diff` in CI against production's shadow database expectations so drift fails the build. Confidence: 0.75 - Document connection pooling (PgBouncer / driver adapter) in the runbook; serverless without a pool will exhaust connections. Confidence: 0.85

Helm Chart taste

# Helm Chart taste of a Kubernetes packaging engineer - One chart per deployable application, with a clear `Chart.yaml` name, version and `appVersion` that track semver. Confidence: 0.90 - Keep default `values.yaml` safe for a non-production install, and document every key in `values.schema.json` or a VALUES.md. Confidence: 0.85 - Prefer the official Helm library patterns and bitnami-style helpers sparingly; copy only helpers you understand. Confidence: 0.75 - Template labels and selectors from a single `_helpers.tpl` so Services always match Pods. Confidence: 0.95 - Never hard-code namespaces in templates; take them from `Release.Namespace` or an explicit value. Confidence: 0.90 - Pin image tags to digests or immutable tags in production values; forbid `latest` in the schema. Confidence: 0.90 - Set resource requests and limits for every container, with defaults that fit a small cluster and overrides for prod. Confidence: 0.85 - Include readiness and liveness probes with realistic delays; a wrong probe is worse than no probe. Confidence: 0.85 - Manage config with ConfigMaps and secrets via sealed-secrets, SOPS or external-secrets—not plaintext in git. Confidence: 0.95 - Use `required` and `fail` in templates for mandatory values so misconfiguration fails at install time. Confidence: 0.85 - Run `helm lint`, `helm template` and a kubeconform/kubeval check in CI on every chart change. Confidence: 0.90 - Test with `helm unittest` or snapshot templates for labels, ports and probes so refactors cannot silently break installs. Confidence: 0.80 - Version the chart independently of the app when only packaging changes; bump `appVersion` when the image changes. Confidence: 0.80 - Prefer small umbrellas only when services truly share a release lifecycle; otherwise deploy charts separately with GitOps. Confidence: 0.75 - Support `extraEnv`, `extraVolumes` and `affinity` hooks so operators can extend without forking the chart. Confidence: 0.80 - Keep RBAC templates opt-in and least-privilege; default ServiceAccounts should not mount the API token unless needed. Confidence: 0.85 - Document upgrade notes in `README.md` for breaking values renames, and provide a values migration example. Confidence: 0.80 - Publish charts to an OCI registry or ChartMuseum from CI with signed provenance; do not `helm push` from a laptop. Confidence: 0.80 - Align with GitOps (Argo CD or Flux) by making charts render cleanly with only values files—no manual `helm upgrade` steps. Confidence: 0.85 - Cap chart complexity: if templates need heavy logic, move it to a controller or operators instead of growing Gotpl. Confidence: 0.75 - Review `helm diff` output before applying to production and require a human approval gate on the deploy Environment. Confidence: 0.85

Nature

--- name: nature description: Introduction --- # Nature Describe what this skill does and how the agent should use it. ## Instructions - Step 1: ... - Step 2: ...

Diwali wish

Please create a Diwali poster for me that includes a greeting message—one with a unique, thought-provoking concept that compels people to reflect. The message should be truly one-of-a-kind, something not found anywhere else on the internet. It should bring joy to those who read it and prompt them to silently appreciate the sentiment. Also, please include my name at the bottom of the poster.

Hotel Folio Overcharge Dispute Pack (JSON)

{ "role": "Calm, careful hotel-bill review assistant who helps travelers understand a hotel folio or invoice, compare it with what was booked and what actually happened during the stay, organize overcharge evidence, and draft polite dispute emails, without inventing hotel policies, resort fees, tax rules, chargeback rights, deadlines, or legal outcomes", "task": "Turn my stay facts, the folio or invoice lines I have, what I booked, extras I did or did not use, evidence I can gather, and what I hope to achieve into a single strict JSON hotel folio overcharge dispute pack: a summary, stay facts, a line-by-line folio review, an overcharge evidence log, calm dispute email drafts, deadline notes marked confirm locally, an escalation path, next steps, and clear disclaimers. Practical organizing help only. Never invent hotel policies, fee rules, tax amounts, card-issuer rights, or legal remedies. This is not legal advice.", "context": { "property_and_location": "${property:mid-size city hotel, downtown, reservation made on the hotel website}", "stay_dates": "${dates:check-in Tuesday 4 Nov, check-out Friday 7 Nov, 3 nights}", "guest_and_room": "${guest:I am the cardholder and the named guest; one standard double room}", "what_I_booked": "${booked:prepaid room rate that the confirmation said included Wi-Fi and breakfast for two; no parking mentioned}", "what_happened": "${happened:we stayed 3 nights, ate breakfast twice, did not use the minibar, parked once in a nearby public garage we paid separately, and checked out in a hurry}", "folio_details": "${folio:front desk printed a folio at checkout showing room nights, city tax, a resort or destination fee, two breakfast charges, a minibar item I do not recognize, and a parking charge}", "amount_in_question": "${amount:I expected about 480 including tax; the folio total is 612; the surprise lines add up to about 130}", "evidence_I_have": "${evidence:booking confirmation email, checkout folio PDF, card pending charge, photos of the room rate card on the desk; I have not yet asked for an itemized minibar list}", "what_I_already_tried": "${tried:I asked at checkout and the clerk said the destination fee is mandatory; I have not emailed the hotel or my card issuer yet}", "goal": "${goal:remove charges I did not agree to or use, or get a clear written explanation; I want to stay factual and calm}", "country_or_region": "${region:city and country of the hotel, plus the country of my payment card}", "constraints": "${constraints:I prefer email so I have a record; I do not want to threaten anyone; I may still be within a card-statement window}" }, "ask_first": [ "The hotel name, city, check-in and check-out dates, room type, number of guests, and whether you are the named guest and the cardholder.", "A copy or clear photo of the booking confirmation (rate, inclusions, cancellation terms, prepaid or pay-at-hotel) and of every page of the folio or invoice.", "What you actually used: meals, minibar, parking, spa, late checkout, rollaway bed, pets, or other extras, with dates if you remember them.", "Which folio lines look wrong and why (duplicate, never used, already included in the rate, different amount than quoted, unknown fee).", "Evidence you have or can still get: confirmation emails, rate screenshots, photos of in-room price lists, receipts you paid elsewhere, chat or front-desk notes.", "What you already asked the hotel, any reply, the card charge status (pending or posted), and the outcome you want." ], "rules": [ "Use only my inputs for facts. If something is missing, set it to null, add it to open_questions, and never guess hotel policies, mandatory fees, tax rates, tip rules, check-out cutoffs, dispute windows, chargeback rights, or laws.", "Stay facts must recap who stayed, dates, room, rate type, what the confirmation said was included, and how I paid. Do not invent a confirmation term I did not quote.", "Folio line review: list every line I provided (description, date if shown, amount, whether I expected it, whether it matches the confirmation or what happened, and a status such as looks_ok, possible_overcharge, duplicate_suspect, unknown, or need_more_detail). Flag mismatches as items to question, never as proof the hotel broke a law.", "Overcharge evidence log: record each document or note with what it shows, the date, and whether I already have it. Tell me what else to request in writing (itemized minibar list, destination-fee disclosure, corrected folio). Never suggest editing documents or creating records that did not exist.", "Deadline notes must be marked confirm locally. Never invent a dispute window, checkout protest deadline, card-issuer time limit, or tourism-authority filing period. If I did not give a date, set the date to null and write confirm locally with the hotel, my card issuer, or the official local consumer source.", "Calm dispute emails must be polite, factual, and short: quote the reservation number, stay dates, folio or invoice number, and the specific lines I question; attach the evidence list; and say clearly what I am asking for (removal, explanation, or a corrected folio). Include a first note to the hotel billing or guest-relations desk and a follow-up if they do not reply. Never include threats, insults, or fake legal claims.", "Escalation path: list practical stages in order (hotel billing or guest relations, hotel manager or brand guest care if a chain, card issuer question or dispute if I choose, and a local consumer or tourism advice service). Mark every body, fee, and time limit as confirm locally. Never tell me a chargeback will succeed.", "This is practical organizing help, not legal, tax, or financial advice. Say so in disclaimers and suggest official consumer advice or a qualified adviser when the amount is large or a formal legal step is being considered.", "Output only valid JSON matching output_format. No markdown, no comments, no prose outside the JSON." ], "output_format": { "summary": { "property": "string", "stay_dates": "string", "folio_total": "number | null", "expected_total": "number | null", "amount_in_question": "number | null", "key_finding": "string", "recommendation": "ask_hotel_for_explanation | request_folio_correction | send_dispute_email | follow_up_with_hotel | contact_card_issuer_after_confirming | need_more_information | seek_local_consumer_advice", "tone": "calm_factual", "assumptions": [ "string" ], "open_questions": [ "string" ], "disclaimer": "Practical organizing help only. Not legal, tax, or financial advice. Confirm fees, taxes, dispute steps, and any deadlines locally with the hotel, your card issuer, and official consumer sources." }, "stay_facts": { "property_name": "string | null", "city_and_country": "string | null", "confirmation_or_reservation_number": "string | null", "guest_name_matches_folio": "yes | no | unknown", "cardholder_is_guest": "yes | no | unknown", "check_in": "YYYY-MM-DD | null", "check_out": "YYYY-MM-DD | null", "nights": "number | null", "room_type": "string | null", "rate_type": "string | null", "inclusions_per_confirmation": [ "string" ], "payment_method": "string | null", "what_actually_happened": "string" }, "folio_line_review": [ { "line_id": "string", "description_on_folio": "string", "date_on_folio": "YYYY-MM-DD | null", "amount": "number | null", "currency": "string | null", "expected": "yes | no | partial | unknown", "why_questioned": "string | null", "matches_confirmation": "yes | no | unknown", "matches_what_happened": "yes | no | unknown", "status": "looks_ok | possible_overcharge | duplicate_suspect | unknown | need_more_detail", "notes": "string" } ], "overcharge_evidence_log": [ { "evidence_id": "string", "type": "confirmation_email | folio | rate_screenshot | photo | receipt | card_statement | chat_or_desk_note | other", "description": "string", "date": "YYYY-MM-DD | null", "shows": "string", "file_name": "string | null", "have_it": "yes | no | partial", "how_to_collect_if_missing": "string | null" } ], "calm_dispute_email_drafts": [ { "audience": "hotel_billing_or_guest_relations | hotel_manager | brand_guest_care | card_issuer | other", "channel": "email | portal_message | written_letter", "subject": "string", "body": "string", "attachments_to_consider": [ "string" ], "send_when": "string" } ], "deadline_notes": [ { "item": "string", "date": "YYYY-MM-DD | null", "source_if_known": "string | null", "mark": "confirm locally", "why_it_matters": "string", "reminder_suggestion": "string | null" } ], "escalation_path": [ { "step": "number", "action": "string", "when_to_consider": "string", "confirm_with": "string", "status": "confirm locally" } ], "next_steps": [ { "action": "string", "owner": "me | hotel | card_issuer | other", "by_when": "string | null", "priority": "high | medium | low", "mark": "confirm locally | n/a" } ], "disclaimers": [ "This pack is practical organizing help for reviewing a hotel folio and writing calm questions. It is not legal, tax, or financial advice.", "Hotel fees, taxes, inclusions, and dispute steps vary by property and place. Confirm every policy point and deadline locally.", "Card-issuer dispute and chargeback rules vary. Confirm them with your card issuer before relying on any time limit or outcome.", "If the amount is large or a formal legal step is being considered, seek advice from an official consumer service or a qualified adviser." ] } }

Photoreal Mandarin Duck Pair on a Still Autumn Pond at First Light

A photorealistic wildlife photograph of a pair of mandarin ducks floating on a perfectly still autumn pond at first light, wide landscape 16:9. The male sits in the left-center foreground in full breeding plumage: orange sail-like tertial feathers raised on his back, a white crescent above the eye, a purple-green iridescent crest, a chestnut and orange chest with bold white stripes, a red bill, and a white belly, facing slightly right toward the female. The female floats to the right, mottled brown-grey with fine barring and a thin white eye-ring, facing left toward the male. Both birds rest on glassy water with clear, sharp reflections beneath them; many amber and gold maple leaves drift on the surface. Soft pink-gold first light and low mist hang over dark pines and autumn-colored trees on the far bank. Low water-level camera, shallow depth of field, peaceful dawn mood. No people, no text, no logos, no watermarks.

Cutaway Illustration of a Vintage Mobile Library Bus Under Autumn Trees at Dusk

A storybook cutaway illustration of a vintage cream-and-dark-green mobile library bus parked under autumn trees at dusk, landscape 4:3. The bus faces LEFT; the near side is cut away to reveal a cozy interior: toward the front, a green cushioned sofa with pillows and a plaid throw, a rounded window behind it, and a potted plant on the floor; toward the rear-right, a wooden desk with a green banker's lamp, stacks of books, and wooden shelves packed with colorful books; warm string lights run along the ceiling, with more potted and hanging plants. Outside, a huge autumn maple fills the upper left, wet pavement is covered in orange fallen leaves, and two glowing street lamps stand on the right under a purple-blue dusk sky. Inviting, detailed cutaway style. No readable book titles, no logos, no people, no watermarks.

Turf-Roofed Faroese Village Above a Sea Gorge at Golden Hour

Photoreal wide landscape photograph of a tiny Faroese turf-roof village above a sea gorge at golden hour, 16:9. About ten small wooden houses with living grass-turf roofs sit on a left-center grassy terrace; most houses are black or very dark with white-framed multi-pane windows and chimneys, and ONE house near the center of the cluster is painted bright red with a turf roof. A few white sheep graze on the lower-left foreground grassy slope below the houses. On the RIGHT a tall, prominent waterfall plunges from the top of a dark basalt cliff into a deep teal inlet with white foam at the cliff foot. Golden sidelight from the LEFT rakes across the grass and roofs; the Atlantic in the left distance is paler under the sun, with a dark distant headland silhouetted on the far left horizon. Steep green-topped cliffs continue into the background center-right. Pale gold sky near the sun fading to clear blue on the right, light haze, a few high clouds. No people, no cars, no boats, no modern antennas, no readable signs.

Kafka Streaming taste

# Kafka Streaming taste of a pragmatic event platform engineer - Name topics by domain and event, such as `orders.order-placed.v1`, and put the schema version in the name only when a breaking change forces a new topic. Confidence: 0.85 - Register every topic schema in a schema registry (Avro or Protobuf) with backward compatibility enforced; never publish raw untyped JSON to shared topics. Confidence: 0.90 - Choose the partition key from the entity whose ordering matters (order id, account id), and never rely on ordering across partitions. Confidence: 0.95 - Start with enough partitions for expected peak consumer parallelism plus headroom, because increasing partitions later breaks key-to-partition mapping. Confidence: 0.80 - Run producers with `acks=all`, idempotence enabled and `min.insync.replicas=2` on a replication factor of 3 for anything business-critical. Confidence: 0.90 - Treat delivery as at-least-once and make every consumer idempotent with a dedupe key or upsert, instead of chasing end-to-end exactly-once. Confidence: 0.90 - Commit offsets only after the side effect has succeeded; disable auto-commit for consumers that write to databases or call APIs. Confidence: 0.90 - Send messages that fail repeatedly to a dead-letter topic with the original headers, error and attempt count, and alert on its growth. Confidence: 0.85 - Retry transient failures with bounded backoff inside the consumer before dead-lettering; never block a partition forever on one poison message. Confidence: 0.85 - Keep events as facts in past tense that describe what happened, not commands telling another service what to do. Confidence: 0.80 - Keep payloads small and self-contained enough to process without a synchronous call back to the producer, but put large blobs in object storage and send a reference. Confidence: 0.75 - Use the transactional outbox pattern to publish events atomically with database writes instead of dual writes. Confidence: 0.90 - Use log compaction for topics that represent the latest state per key, and time-based retention for pure event streams. Confidence: 0.85 - Monitor consumer lag per group and partition as the primary health signal, alerting on sustained growth rather than single spikes. Confidence: 0.90 - Put a correlation id and the producing service name in message headers so traces can follow an event across services. Confidence: 0.80 - Give every consumer group a stable, descriptive id tied to the service, and never share one group between unrelated applications. Confidence: 0.85 - Reach for Kafka Streams or Flink only when you need stateful joins or windowing; a plain consumer is simpler for stateless transforms. Confidence: 0.75 - Manage topics, partitions, retention and ACLs as code reviewed in pull requests, and disable automatic topic creation in production. Confidence: 0.90 - Lock down clusters with TLS, authenticated clients and per-service ACLs that grant only the topics each service needs. Confidence: 0.85 - Test consumers against a real broker in containers for integration tests, and keep unit tests on pure handler functions. Confidence: 0.80 - Document each topic's owner, schema, key, retention and consumers in a catalog that lives next to the topic definitions. Confidence: 0.70

Pandas Data Analysis taste

# Pandas Data Analysis taste of a reproducible analytics practitioner - Keep analysis in version-controlled scripts or notebooks with outputs cleared before commit, and move reusable logic into an importable module. Confidence: 0.85 - Pin pandas, numpy and pyarrow versions in a lockfile so results do not shift silently between runs. Confidence: 0.90 - Read data with explicit `dtype`, `parse_dates` and `usecols` instead of letting pandas guess types on large files. Confidence: 0.90 - Prefer Parquet over CSV for intermediate datasets because it keeps types, compresses well and loads much faster. Confidence: 0.90 - Use the pyarrow-backed string and nullable dtypes so missing values do not quietly turn integer columns into floats. Confidence: 0.75 - Write transformations as method chains with `assign`, `pipe` and `query`, avoiding long sequences of in-place mutation. Confidence: 0.80 - Never use `inplace=True`; reassign the result so data flow stays obvious and chains remain possible. Confidence: 0.85 - Select with `.loc` and `.iloc` explicitly and avoid chained indexing that triggers `SettingWithCopyWarning`. Confidence: 0.90 - Vectorize with built-in column operations and `np.where` or `np.select`; reach for `apply` with Python functions only as a last resort. Confidence: 0.90 - Validate assumptions with assertions after each major step: row counts, unique keys, null ratios and value ranges. Confidence: 0.85 - Pass `validate="one_to_one"` or `"many_to_one"` to `merge` so silent row explosions from duplicate keys fail loudly. Confidence: 0.90 - Use `indicator=True` when joining to inspect unmatched rows before dropping them. Confidence: 0.75 - Keep timestamps timezone-aware in UTC internally and convert to local time only for presentation. Confidence: 0.85 - Use `groupby` with named aggregations so output columns get readable names without a renaming step. Confidence: 0.80 - Downcast numeric columns and convert low-cardinality strings to `category` when memory matters. Confidence: 0.75 - Switch to DuckDB or Polars once data stops fitting comfortably in memory, instead of fighting pandas with chunking hacks. Confidence: 0.70 - Set a random seed for any sampling or shuffling so results can be reproduced exactly. Confidence: 0.90 - Keep raw data immutable and write every cleaned or derived dataset to a separate, clearly named location. Confidence: 0.90 - Use snake_case column names, normalized once right after loading. Confidence: 0.80 - Chart with matplotlib or seaborn from tidy long-format frames, with labeled axes, units and a title that states the finding. Confidence: 0.75 - Write small pytest tests for cleaning functions using tiny hand-built DataFrames and `pd.testing.assert_frame_equal`. Confidence: 0.80

Database Schema Design taste

# Database Schema Design taste of a pragmatic relational modeler - Use surrogate primary keys (`bigint` identity or UUIDv7) on every table and enforce natural keys with separate unique constraints. Confidence: 0.85 - Name tables as plural snake_case nouns and columns as singular snake_case, with foreign keys named `<referenced_table_singular>_id`. Confidence: 0.80 - Declare every foreign key constraint in the database instead of relying on the application to keep references valid. Confidence: 0.95 - Mark columns `NOT NULL` by default and allow nulls only when "unknown" is a genuinely different state from an empty value. Confidence: 0.90 - Store timestamps as `timestamptz` in UTC and add `created_at` and `updated_at` to every mutable table. Confidence: 0.90 - Store money as integer minor units or `numeric` with an explicit currency column, never as floating point. Confidence: 0.95 - Normalize to third normal form first and denormalize only for a measured read path, documenting why the copy exists and how it stays in sync. Confidence: 0.85 - Use `CHECK` constraints for simple invariants such as positive quantities, valid ranges and allowed status values. Confidence: 0.85 - Prefer a lookup table or a check constraint over native enum types when the set of values is likely to change. Confidence: 0.70 - Model many-to-many relationships with an explicit join table that has its own composite unique key and room for attributes like role or created_at. Confidence: 0.85 - Index every foreign key column that is used in joins or cascading deletes. Confidence: 0.90 - Add indexes from real query patterns and `EXPLAIN` output, not speculatively on every column. Confidence: 0.85 - Use partial indexes for hot subsets, such as active rows or unprocessed jobs, instead of indexing the whole table. Confidence: 0.75 - Keep soft deletes out of the core schema unless they are a product requirement; when needed, pair `deleted_at` with partial unique indexes. Confidence: 0.70 - Use `jsonb` only for genuinely schemaless or third-party payloads, and promote any field you filter or join on into a real column. Confidence: 0.85 - Avoid polymorphic foreign keys (`owner_type` plus `owner_id`); use separate nullable foreign keys with a check constraint or separate join tables. Confidence: 0.80 - Keep audit history in an append-only table or temporal table rather than overwriting rows and losing the past. Confidence: 0.75 - Choose `ON DELETE` behavior deliberately per relationship: `RESTRICT` by default, `CASCADE` only for owned child rows. Confidence: 0.85 - Never store comma-separated lists in a column; model repeating values as rows. Confidence: 0.95 - Keep multi-tenant data in shared tables with a mandatory `tenant_id` in every key and index, enforced with row-level security where available. Confidence: 0.75 - Review every schema change as a migration in version control together with the code that depends on it. Confidence: 0.90 - Document each table and non-obvious column with `COMMENT ON` so the schema explains itself in any database client. Confidence: 0.65

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.

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*) |

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

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.

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.

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

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.

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

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

Ebru Paper Marbling of Tulips and Hyacinths on a Swirled Indigo Ground

Traditional Turkish ebru paper marbling artwork: a bouquet of three red-and-white tulips, two purple hyacinths and a few slender green leaves floating on a swirled deep indigo and teal marbled ground, created entirely with the ebru technique of dropping ox-gall paints onto thickened water and shaping them with a stylus and horsehair brush. The tulip petals show the characteristic soft-edged, pulled-teardrop shapes of ebru flowers, with fine white veins dragged through the red; the hyacinths are built from clusters of tiny lilac dots; the background shows classic battal and gelgit combed patterns in indigo, teal, ochre and cream, with organic flowing lines and tiny paint speckles. Slightly irregular, hand-made look, matte paper texture visible, soft natural daylight, viewed straight on as a flat artwork filling the frame, portrait 3:4. No text, no signature, no frame, no people, no hands.

Azulejo Blue-and-White Tile Mural of a Sardine Fishing Boat at Dawn

Hand-painted azulejo tile mural in traditional blue and white: a small wooden sardine fishing boat with a tall prow and a coiled net rows out of a harbor at dawn, two fishermen at the oars, seagulls overhead, whitewashed houses with tiled roofs and a church tower on the hill behind, and gentle rolling waves in the foreground. Painted in cobalt blue glaze on a white tin-glazed ceramic ground, composed across a visible grid of square tiles with thin grout lines, slight glaze pooling, tiny crazing cracks, hand-brushed line work and soft wash shading, framed by an ornate blue baroque scroll border with acanthus leaves. Glossy ceramic sheen with a soft reflected highlight, viewed straight on in even daylight as a wall mural, landscape 4:3. No text, no lettering, no signature, no modern objects.

Glacier Calving into a Turquoise Arctic Fjord

Photorealistic wide landscape of a tidewater glacier meeting a calm turquoise fjord in the soft light of an Arctic summer evening. A tall, jagged glacier front of white and deep-blue ice with vertical crevasses and seracs fills the middle of the frame from left to right, its face about forty meters high, with one large leaning ice tower near the center that looks ready to fall. Dark rocky mountains with patches of snow rise behind the glacier under a pale pink and gold sky with thin high clouds. In the foreground, still glassy water reflects the ice wall, with a scatter of small floating icebergs and brash ice; a few seabirds rest on a floe on the right. Golden low sun from the right rims the ice in warm light while the shadows stay cool blue. Camera: shot from a small boat at water level, 35 mm lens, f/8, deep focus, cinematic 16:9 composition with the glacier front across the middle third and open water in the lower third. Crisp ice texture, natural colors, subtle haze over the mountains. Avoid: people, boats in frame, buildings, text, watermarks, oversaturated colors.

RAG Pipeline taste

# RAG Pipeline taste of an engineer who ships retrieval systems that stay accurate - Build an evaluation set of real user questions with expected sources before tuning chunking, embeddings or prompts. Confidence: 0.95 - Measure retrieval and generation separately: recall@k and MRR for retrieval, faithfulness and answer quality for generation. Confidence: 0.90 - Chunk by document structure such as headings, sections and paragraphs before falling back to fixed token windows. Confidence: 0.85 - Keep chunks around 300-800 tokens with modest overlap, then tune against the eval set instead of guessing. Confidence: 0.75 - Store rich metadata with every chunk: source URL, title, section path, updated date, permissions and content hash. Confidence: 0.90 - Prepend the document title and section heading to each chunk's embedded text so isolated chunks keep their context. Confidence: 0.80 - Use hybrid search, combining BM25 keyword search with dense vectors, because names, codes and IDs embed poorly. Confidence: 0.85 - Add a cross-encoder reranker over the top 30-50 candidates before passing the best 5-10 chunks to the model. Confidence: 0.80 - Apply access-control filters inside the retrieval query, never by filtering results after the model has seen them. Confidence: 0.95 - Version the embedding model and re-embed the whole corpus when it changes; never mix vectors from different models in one index. Confidence: 0.90 - Make ingestion incremental and idempotent using content hashes, so re-running it only touches changed documents. Confidence: 0.85 - Start with Postgres and pgvector for small to medium corpora before adding a dedicated vector database. Confidence: 0.70 - Ask the model to cite chunk IDs for every claim and render those citations as links back to the source. Confidence: 0.90 - Instruct the model to say it doesn't know when retrieved context is insufficient, and test that behavior explicitly. Confidence: 0.90 - Rewrite conversational follow-up questions into standalone queries before retrieval. Confidence: 0.80 - Treat retrieved text as untrusted data and guard against prompt injection hidden inside documents. Confidence: 0.85 - Log the query, retrieved chunk IDs, scores and final answer for every request so failures can be replayed. Confidence: 0.85 - Prefer fixing the corpus, chunking or metadata over adding longer and longer system prompts. Confidence: 0.75 - Cache embeddings for repeated queries and set a token budget for context rather than stuffing in everything retrieved. Confidence: 0.70 - Run the eval suite in CI on every change to prompts, chunking, models or retrieval settings. Confidence: 0.85 - Reach for fine-tuning only after measurements show retrieval is no longer the bottleneck. Confidence: 0.65

Portal-Chain Hero Sprint: One Seamless 25-Second Action VFX Shot Through Four Worlds (Seedance 2.5 Continuity Test)

Ultra-realistic Hollywood action VFX, one seamless 25-second shot. Aggressive tracking, crash zooms, fast 180-degree orbit, portal wipes, speed ramps, premium compositing, hyper-dynamic transitions. One adult woman only, athletic, futuristic fighter, same identity throughout. Starts in a modern industrial corridor, then transitions through multiple worlds. 0-5s: She sprints through a metallic corridor toward camera. A portal erupts open behind her, blasting sparks and wind. 5-10s: She jumps through one side portal and exits into a desert battlefield mid-stride. Camera keeps pace with her as sand explodes outward. 10-15s: She punches through a second portal and emerges in a frozen city street. Ice shards and snow swirl around her without breaking momentum. 15-20s: A third portal opens under a leap, dropping her into a neon megacity rooftop run. Camera orbits as she keeps moving. 20-25s: Final portal chain. Three portals collapse into one giant circular gate behind her as she lands in a glowing white void, then the full stack of worlds appears layered behind her in one epic reveal. Continuous movement, same hero throughout, premium portal VFX, no teleportation glitches, readable world changes, no text, no logos.

Typical 90's TEEN Boy

A vertical medium shot casual photograph of a young man in his late teens with an average figure, medium-length wavy light brown hair held back by a typical red bandana folded and worn around his head, covering his upper forehead and front of his hairline, with his wavy hair coming out from the back and covering the tops of his ears. He is wearing black Ray-Bans sunglasses, which are partway down his nose and he has his head tilted down slightly so you can see the tops of his hazel eyes as he looks at you with a look of playful annoyance because youre taking another picture of him. He is wearing a well-worn, slightly faded black 'NIRVANA' t-shirt from the album 'SMELLS LIKE TEEN SPIRIT', and faded blue jeans with a rip in the right knee. He is sitting on the floor with his knees bent up, both hands raised at shoulder height showing the middle finger with both hands, black painted nails. He has a SWATCH watch on his left wrist, and thin leather string, and metal bead bracelets on his right wrist. He is wearing dog tags for a necklace. His expression is serious, defiant, and cool, looking directly at the camera through the sunglasses. The background is a white bedroom wall covered with rock band posters: 'I WANT TO BELIEVE', 'ARCTIC MONKEYS', 'NIRVANA' smiley face logo, 'JOY DIVISION UNKNOWN PLEASURES', and 'THE CURE BOYS DON'T CRY'. To the left is a white and black electric guitar (Stratocaster style) leaning against the wall above a black amplifier. To the right are black Dr. Martins combat boots and stacked Vans shoe boxes. Lighting is direct frontal flash creating harsh shadows on the wall behind him and specular highlights on the lenses of the sunglasses. Shot with a disposable camera, eye-level angle, full color, saturated colors, casual grunge aesthetic, rebellious boy vibe, 90s rock revival style, typical spontaneous aesthetic, ultra-realistic.

Personal "Operating Manual"

Using only information you actually have from my conversation history, memory, files, or other context available to you, build a practical “Operating Manual” for me. - Do not flatter me, diagnose me, or invent psychological explanations. - Do not infer sensitive personal attributes unless I explicitly told you them and they are directly relevant. Separate clearly using distinct headers: # What you know - Recurring goals - Long-term projects - Constraints I repeatedly work around - Skills, resources, and advantages I appear to have - Preferences I consistently express # Patterns you observe - Problems I repeatedly return to - Strategies that seem to work well for me - Strategies I repeatedly try that seem not to work - Situations where I tend to overcomplicate or underthink things - Recurring tensions between my goals # Your inferences - For every inference, state: - The inference - The evidence that led you there - Your confidence: low / medium / high - At least one plausible alternative explanation # Blind spots or underused opportunities - Identify things already present in my skills, resources, relationships, projects, or habits that I may not be taking full advantage of # My apparent decision-making style - Describe how I tend to approach uncertainty, risk, planning, experimentation, and changing my mind. Use examples where possible. # Highest-leverage changes - Provide 3–5 concrete, specific structural changes with examples that could noticeably improve my life or work over the next three months. Prefer small, specific structural changes over vague advice like “be more disciplined.” # What you still don’t know - List the missing information, specifying what type of data or context is needed, that would most substantially change your conclusions. Finish with a short section called “If I were writing instructions for an AI assistant working with you” containing 8–12 practical instructions based on the analysis. Format this section as bullet points for clarity. * Be willing to conclude that the available evidence is insufficient. Accuracy is more important than producing an interesting answer.

Encaustic Hot Wax Painting of a Poppy Field Under a Summer Storm Sky

An encaustic hot wax painting of a wild red poppy field under a dark summer storm sky, landscape 4:3. Built up in many translucent layers of pigmented beeswax fused with heat on a wooden panel: in the foreground, dozens of scarlet poppies with black centers and thin bending green stems sway through tall golden grasses and a few blue cornflowers; in the middle ground the field rolls over a gentle hill toward a lone farmhouse with a red roof and a single tall cypress tree; above, heavy slate-blue and violet storm clouds gather, with one bright break of warm yellow light falling across the field. Encaustic technique details: glossy, semi-translucent wax with visible depth between layers, soft melted edges where colors flow into each other, scraped and incised lines in the grasses, small drips and raised textured ridges of wax, a buffed satin sheen with soft reflections, and a slightly uneven hand-made surface where the wooden panel edge shows at the borders. Rich, saturated colors: scarlet, ochre, sage green, slate blue, violet, warm cream. Viewed straight on as a flat artwork in soft even daylight. No text, no signature, no frame, no people.

Dandelion Seed Head Scattering in a Summer Breeze

Photorealistic macro photograph of a single ripe dandelion seed head in a summer meadow at golden hour, landscape 16:9. The perfect round white seed head (a "clock") sits slightly left of center on a thin hollow green stem rising from the bottom of the frame, every seed's fine silky parachute (pappus) sharp and backlit, forming a glowing sphere of delicate white filaments. A few seeds are already missing on the right side, revealing the small brown seed bed. Behind it, a soft out-of-focus meadow of green grasses, a few yellow dandelion flowers and warm golden bokeh circles from the low sun on the right; the sky at the top fades from warm gold to pale blue. Low backlight rims the parachutes with gold and creates a soft glow and gentle lens flare at the upper right. 100 mm macro lens at f/2.8, shallow depth of field, crisp detail on the seed head, natural colors, calm and still air. No people, no hands, no insects, no text.

Korean Hanji Paper-Art Miniature Diorama: Fill-in Template for Any Subject, City or Scene

KOREAN HANJI PAPER ART | WHIMSICAL 3D MINIATURE DIORAMA Create a beautiful, highly detailed, handcrafted 3D paper-art illustration featuring [TYPE YOUR SUBJECT / OBJECT / CITY / SCENE], reimagined through the traditional Korean Hanji paper-art aesthetic. ART DIRECTION & VISUAL STYLE Transform the entire scene into an imaginative miniature world made from layered Korean Hanji paper. Use authentic handmade paper textures, visible delicate fibres, subtle wrinkles, torn edges, embossed details and carefully cut paper elements. Combine traditional Korean visual heritage with contemporary lifestyle, architecture and modern objects. The result should feel like a sophisticated fusion of Korean folk art, paper sculpture and playful contemporary design. COMPOSITION & STORYTELLING Build a rich, three-dimensional miniature environment around the main subject. Make the primary subject instantly recognizable and visually dominant. Surround it with thoughtfully selected supporting elements that complement the subject. Incorporate traditional Korean architectural details, colourful urban surroundings, decorative patterns, miniature props and unexpected creative combinations wherever appropriate. Create a visually engaging composition with convincing depth, overlapping paper layers, realistic miniature proportions and carefully arranged foreground, middle ground and background. MATERIALS & TEXTURES - Traditional Korean Hanji paper with visible natural fibres. - Layered and sculpted paper architecture. - Intricate cut-paper ornaments and embossed details. - Soft handmade imperfections and tactile surfaces. - Rich paper-cut textures with dimensional shadows. - Handmade miniature objects with convincing physical construction. COLOUR & LIGHTING Use a vibrant yet harmonious palette of warm terracotta, turquoise, cobalt blue, mustard yellow, coral, cream and earthy browns. Introduce beautiful atmospheric lighting, soft directional sunlight, gentle shadows and subtle highlights that emphasize the layered paper construction. FINAL AESTHETIC The finished artwork should resemble an exceptionally crafted miniature paper sculpture photographed in a professional studio. Blend whimsical storytelling, Korean cultural identity, contemporary creativity and premium editorial illustration. Ultra-detailed, tactile, colourful, imaginative, visually balanced, handcrafted 3D paper diorama. Every element must appear constructed from real Hanji paper rather than digitally painted or rendered plastic. FORMAT: Square 1:1 composition. No text, captions, typography, watermarks or logos.

Minutes of meeting

Minutes of meeting held at department of Chemical Sciences FUK

Mezzotint Engraving of a Moonlit Wheat Field at Harvest Time

An authentic 18th-century style mezzotint engraving of a moonlit wheat field at harvest time, landscape 4:3, printed in warm black-brown ink on cream laid paper. In the foreground, rows of tied wheat sheaves stand in the stubble beside two tall rounded haystacks, the ripe ears catching silver moonlight; in the middle ground a narrow cart track with a resting wooden hay cart and a low dry-stone wall leads to a small thatched farmhouse with one warm-lit window; behind, gentle rolling hills sit under a large full moon half veiled by drifting clouds. Mezzotint technique details: deep, velvety, rich blacks built from a fine rocked grain over the whole plate; every light area scraped and burnished out of the darkness, so highlights glow softly with no hard outlines; smooth, continuous tonal gradations from black to cream; a subtle dotted burr texture visible in the mid-tones; a slightly embossed plate mark around the image with a clean paper margin. Quiet, nocturnal, timeless mood. Viewed straight on as a flat print in soft even light. No text, no signature, no frame, no people.

Loggerhead Sea Turtle Hatchlings Racing to the Surf at Sunrise

Photorealistic low-angle wildlife photograph of newly hatched loggerhead sea turtles crossing a wide sandy beach at dawn, landscape 16:9. Ten palm-sized hatchlings with dark grey-brown shells and flippers are spread across the left and center of the smooth wet sand, all crawling diagonally toward the upper right, flippers spread mid-crawl, each leaving a tiny trail of flipper tracks; an open nest hollow with clumps of sand sits at the lower left. The thin foamy edge of a gentle wave runs from the top center to the right side of the frame and glistens in the soft pink and orange sunrise light; the sun sits low on the horizon at the right over a calm sea, with a sun glint on the water and a pastel sky. Low camera just above the sand, angled slightly down, 100 mm lens at f/4, sharp on the nearest hatchlings with gentle background blur, wet sand reflecting the sky, natural colors, quiet early-morning stillness. No people, no hands, no birds, no text.

Giant-Letter Landmark Poster: Fill-in Template That Merges Any Landmark Into One Oversized Typographic Letter (4:5)

Create an exceptionally sophisticated, contemporary architectural art poster featuring [LANDMARK NAME], [CITY], [COUNTRY]. 1. GIANT TYPOGRAPHIC COMPOSITION Feature one enormous, oversized uppercase letter associated with the destination name as the central graphic element. The letter should dominate the composition, extending almost across the entire poster. Use bold, elegant, geometric typography with distinctive curves and negative spaces. 2. LANDMARK INTEGRATION Seamlessly integrate a highly detailed architectural photograph or realistic architectural illustration of [LANDMARK NAME] into and across the oversized letter. The landmark should appear to emerge from the typography, partially overlap its boundaries and interact naturally with its shape. Preserve the landmark’s authentic architectural details, proportions and recognisable silhouette. Create an artistic double-exposure effect where the architecture and typography become one unified visual composition. 3. DISTINCTIVE COLOUR TREATMENT Choose a unique colour palette inspired by the destination’s cultural identity, national colours and architectural character. Use two or three contrasting colours within the oversized typography. Apply translucent colour overlays across selected sections of the landmark, creating a beautiful combination of architectural photography, coloured light and graphic shapes. Every new destination must receive a different colour combination. Never repeat palettes. 4. TEXTURE & BACKGROUND Use a warm ivory, soft white or subtle textured paper background. Introduce delicate architectural sketch marks, distressed ink textures, faded photographic grain and subtle print imperfections around the central composition. Keep the surrounding space clean and uncluttered. 5. EDITORIAL TYPOGRAPHY Include the following information: [LANDMARK NAME] [CITY NAME] [COUNTRY NAME] Add small vertical typography along one side, geographical coordinates and a subtle destination-inspired tagline. Use sophisticated editorial typography with carefully balanced spacing. 6. ART DIRECTION Luxury architectural editorial design, experimental typography, architectural double exposure, contemporary Swiss graphic design, oversized letterforms, cinematic monochromatic photography, translucent colour blocking and minimalist gallery poster aesthetics. 7. FINAL PRESENTATION Create a visually striking, intellectual and artistic collectible landmark poster. The architecture must remain recognisable while becoming an integral part of the oversized letter. Vertical 4:5 composition, premium art-print quality, exceptional visual balance and sophisticated negative space. Avoid ordinary travel-poster layouts, decorative clutter, excessive colours and generic typography.

A story of a boy who wants to become cricket player

A boy's story about becoming a cricket player just like virat kohli

Data Analysis Dashboard

Create for me an ultra-realistic dashboard titled "ANALYSIS OF BRD SESSIONS/DOCUMENT DELIVERY AUG - OCT" Let it show, in graphs, histograms, and pie charts, all the documents I have worked on so far concerning BRDs and documents under growth stack

Transition to Professional Services Consultant

I am currently working as a technical support analyst for Esri UK and have been working for them for nearly 6 years. In this time, I have had various roles within Technical Support, from entry level to Technical Support Analyst now, which I have been doing for ~3 years. I am feeling stagnant in my role and I am not sure of what to do next. I would like to do a secondment to our Professional Services team as a Consultant. However, at the moment, I feel like I do not have the appropriate skill levels/knowledge to do this. I could do a secondment as a junior Consultant, however, ideally someone with my years of experience would come in at a Consultant level. I want to be able to be confident in doing this role and be successful. Please outline structured learning plan over the next 3 months that I can do to improve my GIS knowledge (across all Esri/Esri UK products, such as ArcGIS Enterprise, ArcGIS Pro, ArcGIS Online, etc) and improvise the skills that I would need in Professional Services so that I can hit the ground running and be confident. Study the differences between a Technical Support Analyst role and a GIS Consultant role within Esri UK and use these to help guide the structured learning plan. Outline also how I can demonstrate these skills to my manager. What do I need to do going forward.

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