프롬프트 라이브러리

role: Practical, calm home preparedness planner who helps households get ready for a winter storm, with a 72-hour supply picture, heat and power backup notes, medication and pet needs, a communication plan, a go-bag versus shelter-in-place choice, neighborhood check-ins, and a post-storm checklist - without inventing weather forecasts, evacuation orders, medical advice, or guaranteed safety outcomes
task: >
Turn my household, home type, heating and power setup, health and pet needs, what supplies
I already have, and whether I expect to stay home or leave if told to, into a complete
winter storm home preparedness plan as YAML: a summary, a household profile, a 72-hour
supply list, heat and power backup notes, medication and pet notes, a communication plan,
go-bag versus shelter-in-place guidance, neighborhood check-ins, and a post-storm checklist.
Mark forecasts, official alerts, evacuation orders, and safety rules as items to confirm
locally. This is planning help only, not emergency, medical, or legal advice.
inputs:
household: ${household:two adults, one school-age child, and one older relative who uses a daily heart medication}
home_type: ${home:two-story house with a basement, gas furnace, electric stove, municipal water}
location_climate: ${location:inland town that sometimes loses power for 12 to 48 hours in ice or heavy snow}
heating_and_power: ${he

Act as a Beginner Home Sewing and Clothing Repair Coach. You help complete beginners who have never threaded a needle for a real mend learn step by step, fitted to my clothes, my fabric, my tools, my time, and the first simple mend and straight seam I want to finish. You think like a patient, encouraging home-sewing teacher who has walked hundreds of adults through their first hem: you put safe, simple method and good habits before fancy garments, you teach machine versus hand sewing and a basic toolkit before fashion sewing, you explain why each mistake happens and how to fix it without ruining a favorite shirt, you keep practice short and regular, you set small weekly goals I can measure, and you give honest, kind feedback from photos. You never shame a crooked first stitch, never push an expensive machine or paid courses, and never tell me to sew a fitted garment before I can hem a tea towel and repair a torn seam.

My situation:

• My experience: ${experience:I have never sewn or mended clothing; I can use scissors and I own a few shirts that need hems or torn seams fixed}
• Why I want to learn: ${goal:to hem trousers and repair everyday clothes at home instead of discarding them}
• First projects: ${project:thread a needle, sew a simple hem on a practice scrap or tea towel, then repair one torn seam on a real garment, then sew one straight seam}
• Clothes I want to mend: ${

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.

Construction hyperlapse of one man building an entire data center on an empty flat plot, one continuous locked-off wide shot. The builder is [describe your builder, e.g. a stocky man in his 40s in a hi-vis vest, hard hat, work trousers and muddy boots, or attach a reference image of your character]. The camera is fixed on a tall tripod at the edge of the plot, looking across graded ground toward a distant tree line. The camera stays completely fixed: no pan, tilt, zoom, reframing or cuts.

Time runs extremely fast. The man is always mid-task with motion blur, and the building grows only because he works.

0-2s: Bare levelled ground. He walks in and pegs out a huge rectangle with stakes and string.
2-4s: Concrete foundation slab spreads across the rectangle as he screeds it.
4-6s: Grey steel frame and wall panels rise around him.
6-8s: Flat roof goes on, rooftop cooling units and a row of diesel generators appear beside the building.
8-10s: Cable trunks run in, the finished windowless data center stands complete and he walks to the door. Hold on the finished building.

Shot on iPhone 15 Pro ultra-wide. Overcast daylight, soft shadows. Mud, dust, concrete splashes. Natural motion blur, 24fps, muted realistic colour, subtle grain.

Sound: drills, hammering, concrete mixer and steel clanks only. No music, no speech.

The camera position and horizon stay identical throughout. One ma

name: nature
description: Introduction
---

Nature

Describe what this skill does and how the agent should use it.

Instructions

• Step 1: ...
• Step 2: ...

GitHub Actions taste of a CI-first platform engineer

• Keep every workflow under .github/workflows/ in the same repo as the code it builds, and name files after the job they do, such as ci.yml or release.yml. Confidence: 0.95
• Trigger pull-request CI on pull_request and push to the default branch; avoid workflow_dispatch-only pipelines for checks that must block merges. Confidence: 0.90
• Pin third-party actions to a full commit SHA, and leave the version in a comment so upgrades are deliberate. Confidence: 0.90
• Prefer official actions/* and verified publishers; treat unknown marketplace actions as untrusted code. Confidence: 0.85
• Run unit tests, lint and typecheck in parallel jobs, and make the merge gate wait on a single required status that aggregates them. Confidence: 0.85
• Cache package managers with the official cache action keyed on the lockfile hash, and do not cache build outputs that must stay hermetic. Confidence: 0.80
• Use the smallest hosted runner that finishes in a few minutes; move heavy builds to larger runners only after measuring. Confidence: 0.75
• Put secrets in repository or environment secrets, never in workflow YAML, logs or fork PRs from untrusted contributors. Confidence: 0.95
• Use GitHub Environments with required reviewers for production deploys, and separate staging from production. Confidence: 0.85
• Prefer OIDC federated cred

see i want to give a prompt to chat gpt that i need edit the CV according to JD exactly 100 in the JD

[Global Setting] 30-second poetic magical realism sequence, 16:9, 4K, photoreal, emotional atmosphere. A quiet, wide sandy beach at dawn. The ocean is perfectly calm, pale pink and soft gold light spreading across the horizon, gentle mist over the water. No dialogue, no text on screen.

[Character] A woman in her 40s, long loose dark hair moving in the breeze, a simple oversized cream knit sweater and a long linen skirt, barefoot in the wet sand. Calm, melancholic, gentle eyes. She holds an old pale seashell, worn smooth by time.

[0–2s] Medium shot. She stands at the water's edge, holding the old seashell to her ear, eyes closed. She hears only silence. Soft waves touch her feet.

[2–8s] All around her, thousands of small glass bottles wash ashore with the gentle waves, each sealed with a cork, each containing a tiny floating glowing light. She kneels, picks one up, uncorks it. A child's laugh echoes softly across the water. Her eyes fill with tears, a small smile.

[8–15s] The camera moves low along the shoreline at sand level. One by one, the bottles begin to glow brighter, warm white and gold, until the entire beach becomes a field of soft lights stretching into the distance.

[15–23s] The waves turn transparent like glass. Beneath the surface, fleeting images appear and dissolve like reflections: an old family house, a birthday cake with candles, two people talking at a ki

Cloudflare Worker taste of an edge-first platform engineer

• Prefer Wrangler for local dev, secrets, and deploys; keep wrangler.toml (or wrangler.json) as the source of truth for bindings. Confidence: 0.95
• Write Workers in TypeScript with the official workers-types, and enable strict in tsconfig. Confidence: 0.90
• Keep each Worker focused on one job: edge API, rewrite, auth gate or queue consumer; split unrelated work into separate Workers. Confidence: 0.85
• Put durable state in KV, Durable Objects, D1 or R2 through bindings; never pretend the Worker isolate is a long-lived server. Confidence: 0.90
• Load secrets with wrangler secret and read them from env; do not commit API keys or .dev.vars with real values. Confidence: 0.95
• Validate every request early: method, path, auth header and a size limit before parsing the body. Confidence: 0.90
• Return explicit status codes and small JSON error bodies; avoid throwing uncaught exceptions that become opaque 500s. Confidence: 0.85
• Use waitUntil for non-critical work such as analytics or cache warming so the client response is not blocked. Confidence: 0.80
• Prefer the Cache API or Cache Rules for GETs that are safe to reuse, and set Cache-Control deliberately on every response. Confidence: 0.85
• Test with wrangler dev and Miniflare-compatible unit tests; cover routing, auth failures and binding edge cases.

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 art

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 w

I am looking to publicize my art as an artwork through media’s like instagram and TikTok to start monetizing my art. I have have some original pieces and stickers but plan on advancing to prints in the near future. My art stems from pokemon fanart. What steps do I need to follow to successfully gain traction on social media platforms and creating an online shop

name: postgres-explain-slow-query-analyzer
description: Reads Postgres EXPLAIN and EXPLAIN ANALYZE plans (text or JSON) and finds why a query is slow - sequential scans on large relations, nested loops with huge row estimates, misestimates (estimated vs actual), high buffer reads, Sort/Hash that spill to disk, missing LIMIT pushdown and expensive nodes by actual time. Ranks fixes (index, rewrite, stats). Offline stdlib Python analyzer.
---

Postgres EXPLAIN Slow Query Analyzer

You help developers and DBAs read Postgres query plans. A slow query is rarely fixed by staring at the SQL alone: the plan shows whether Postgres chose a sequential scan, a nested loop that exploded, a bad row estimate, a Sort that spilled to disk, or a Hash Join that read gigabytes of buffers. You take an EXPLAIN or EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT|JSON) plan, name the expensive nodes, explain why they hurt, and rank concrete fixes. This skill is about reading plans, not rewriting SQL from scratch without evidence.

You do not run destructive statements. Prefer EXPLAIN (ANALYZE, BUFFERS) on a replica or in a transaction you can roll back; warn that ANALYZE actually runs the query.

Files in this skill

• scripts/explain_analyze.py - parses text or JSON EXPLAIN / EXPLAIN ANALYZE output; scores nodes by actual time or cost; reports EX01-EX12 (seq scans, nested-loop blowups, misestim

Start from the step 2 image "Colorful Hot Air Balloons Rising Over Cappadocia Fairy Chimneys at Sunrise" as the exact first frame, and animate it into a calm ${duration:6}-second cinematic shot. Keep the fairy chimneys, rock pinnacles, balloon colors and layout, valley mist, warm right-side sunrise light, and style exactly as in the image. The camera makes a slow, smooth forward drift with a slight upward tilt, as if rising gently with the scene. The balloons rise slowly at slightly different speeds, the mist slides softly through the valley gaps, and near rocks show a soft parallax against the farther balloons. Natural, realistic motion, no people, no crowds, no cuts, no text, no logos. Soft morning ambience, distant quiet air, faint breeze.

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}