프롬프트 라이브러리

Tokio Async Rust taste of a production service engineer

• Use #[tokio::main] only in the binary and keep library crates runtime-agnostic where practical, taking futures and handles as inputs. Confidence: 0.80
• Never block the async runtime; move CPU-heavy or blocking I/O work to spawn_blocking or a dedicated thread pool. Confidence: 0.95
• Use tokio::sync::Mutex only when a lock must be held across an .await; otherwise use std::sync::Mutex or parking_lot for short critical sections. Confidence: 0.90
• Prefer message passing with bounded mpsc channels over shared mutable state, and size every channel deliberately for backpressure. Confidence: 0.85
• Never use unbounded channels in request paths, because a slow consumer turns into unbounded memory growth. Confidence: 0.85
• Put a timeout on every network call with tokio::time::timeout or a client-level setting; no await on the network should be able to hang forever. Confidence: 0.95
• Use JoinSet or TaskTracker to own spawned tasks so they are awaited, cancelled and their errors are observed. Confidence: 0.85
• Treat every .await as a possible cancellation point and keep state consistent if the future is dropped there. Confidence: 0.85
• Use select! carefully and only with cancel-safe branches; document why each branch is safe to drop. Confidence: 0.80
• Implement graceful shutdown with a `CancellationT

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

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

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

Act as an expert technical recruiter, career coach, and professional CV writer.

Create a job-winning, ATS-friendly CV tailored to a specific job advert. Use only the information I provide. Do not invent employers, job titles, dates, qualifications, skills, projects, or achievements. If important information is missing, ask me up to 5 targeted questions before writing the CV.

MY INFORMATION

• Full name: ${full_name}
• Location: ${location}
• Phone: ${phone}
• Email: ${email}
• LinkedIn / GitHub / portfolio: ${links}
• Current or most recent job title: ${current_title}
• Years of experience: ${years_experience}
• Target job title: ${target_job_title}
• Job advert: ${job_advert}
• Work experience: ${work_experience}
• Education and certifications: ${education_certifications}
• Technical skills, tools, and programming languages: ${skills}
• Projects, achievements, awards, or volunteering: ${projects_achievements}
• Preferred CV length: one page / two pages

TASK

1. Analyze the job advert and identify the most important requirements, responsibilities, keywords, and seniority signals.
2. Identify which of my skills and experience should be emphasized for this specific role.
3. Create a clean, professional CV with these sections:
4. Name and contact details
5. Professional summary
6. Core skills
7. Professional experience
8. Selected projects or portfolio, if relevant

-

Create an ultra-realistic 15-second cinematic historical documentary of the Acropolis of Athens, Greece, during a spectacular golden sunrise. Exactly 15 rapid shots, 1 second each, with clean hard cuts and smooth visual continuity.

Shot sequence:

1. Aerial establishing shot revealing the entire Acropolis above Athens.
2. Smooth drone glide toward the ancient Parthenon.
3. Wide symmetrical view of the Parthenon glowing in sunrise light.
4. Close-up of massive ancient Greek marble columns.
5. Slow tilt-up revealing the magnificent temple architecture.
6. Cinematic orbit around the Parthenon.
7. Close-up of intricate ancient stone carvings and sculptures.
8. Side-angle tracking shot along the majestic columns.
9. Tracking shot across ancient marble pathways.
10. Low-angle hero shot emphasizing the towering columns.
11. Pan across the Erechtheion and its famous Caryatid statues.
12. Golden sunlight illuminating weathered marble textures.
13. Elevated aerial view showing Athens stretching toward the horizon.
14. Close-up revealing ancient architectural details and stone textures.
15. Spectacular aerial pull-back revealing the entire Acropolis beneath the glowing sunrise sky.

Visual style: Photorealistic 4K HDR, premium historical documentary cinematography, authentic ancient Greek architecture, warm golden-pink sunrise, soft atmospheric haze, realistic marble textures, cinematic

Vite Frontend Tooling taste of a fast-feedback web developer

• Start new single-page apps and component playgrounds on Vite with the official framework plugin instead of a custom webpack setup. Confidence: 0.85
• Keep vite.config.ts in TypeScript with defineConfig, and keep it short enough to read in one screen. Confidence: 0.80
• Run type checking separately with tsc --noEmit in CI and in a watcher, since Vite only strips types and never checks them. Confidence: 0.95
• Use path aliases sparingly, define them once in tsconfig.json, and mirror them in Vite with a plugin such as vite-tsconfig-paths. Confidence: 0.75
• Expose only VITE_-prefixed environment variables to client code and never put secrets in them. Confidence: 0.95
• Type import.meta.env in a vite-env.d.ts file so missing or misspelled variables fail at compile time. Confidence: 0.80
• Configure the dev server proxy for backend APIs instead of enabling permissive CORS on the backend just for local development. Confidence: 0.85
• Use Vitest for unit and component tests so tests share the same config, transforms and aliases as the app. Confidence: 0.90
• Lazy-load routes and heavy widgets with dynamic import() and let Rollup split chunks, rather than hand-tuning manualChunks early. Confidence: 0.80
• Inspect bundle size with rollup-plugin-visualizer before releases and treat a large new dependen

Linux Server Hardening taste of a careful operations engineer

• Build servers from a minimal base image and install only the packages a role needs, removing compilers and debugging tools from production hosts. Confidence: 0.85
• Manage every server with configuration as code (Ansible, cloud-init or an image pipeline) and never rely on manual changes that drift. Confidence: 0.90
• Disable SSH password authentication and root login, and allow only key-based or certificate-based logins. Confidence: 0.95
• Prefer short-lived SSH certificates or an identity-aware access proxy over long-lived authorized_keys files copied around. Confidence: 0.75
• Give each engineer a named account with sudo through groups, and never share a common admin user. Confidence: 0.90
• Default the host firewall to deny inbound traffic and open only the ports the service actually listens on. Confidence: 0.90
• Keep SSH and admin interfaces off the public internet, reachable only through a VPN, bastion or private network. Confidence: 0.85
• Enable unattended security updates for the base OS, and schedule reboots so kernel patches actually take effect. Confidence: 0.85
• Run each service as its own unprivileged system user with no login shell. Confidence: 0.90
• Use systemd sandboxing options such as ProtectSystem=strict, NoNewPrivileges=yes and PrivateTmp=yes for every long-running service. Confidence

name: language-editor
description: A professional multilingual language editor that corrects and refines text in any language, improving grammar, spelling, clarity, fluency, and natural expression while preserving the original meaning, intent, and appropriate tone. Ensures polished, authentic, native-level writing with concise, professional results.
---

My Skill

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

Instructions

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

name: theme-and-colors
description: study the theme and colors. and then change the whole process for the theme to be better, and change the colors to be better and modern.
---

theme and colors

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

Instructions

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

20 seconds, horizontal 16:9. A photorealistic live-action comedy montage consisting of exactly SIX separate vignettes. Ancient Egyptians casually use modern technology as if it has always existed.

Six shots total, in the exact order below. Each vignette is ONE continuous shot, with hard cuts only at 00:03, 00:06, 00:09, 00:12 and 00:16. No transitions or additional shots. Begin each scene with the characters already positioned for its action. Show one clear gag, then cut after its payoff. Normal real-time movement, no slow motion.

CHARACTERS
Egyptian men: adults aged 25-45, olive-to-brown skin, dark eyes with black kohl, shaved heads or blue-and-gold striped nemes headdresses. Bare chests, white linen knee-length shendyt kilts and brown leather sandals. Real human actors with natural proportions.

Queen, scene 3 only: approximately 28, olive skin, dark almond-shaped eyes, black shoulder-length bob with a blunt fringe, dramatic black eyeliner, turquoise eyeshadow. Thin gold diadem with a small upright cobra, broad gold-and-lapis collar, gold upper-arm cuffs and gold sandals. Fitted ankle-length white pleated linen dress. Calm regal expression. Both hands stay on the jet ski handlebars.

Market woman, scene 4 only: approximately 35, long thin black braids reaching her shoulder blades, kohl eyeliner, plain ankle-length white linen dress, leather sandals. Turquoise-and-gold beade

Solidity Smart Contract taste of a security-first protocol engineer

• Pin an exact recent compiler version with pragma solidity 0.8.x; instead of a floating caret range. Confidence: 0.90
• Build and test with Foundry, writing tests in Solidity, and keep Hardhat only where a plugin is truly needed. Confidence: 0.80
• Reuse audited OpenZeppelin contracts for tokens, access control and upgrades instead of hand-rolling standards. Confidence: 0.95
• Follow checks-effects-interactions in every function that makes external calls, and add a reentrancy guard where state is shared. Confidence: 0.95
• Use custom errors over revert strings for clearer failures and lower gas. Confidence: 0.85
• Emit an event for every state change that off-chain systems need to track, with indexed fields for common filters. Confidence: 0.85
• Prefer pull payments, where users withdraw funds, over pushing ETH to many addresses in a loop. Confidence: 0.90
• Never use tx.origin for authorization; check msg.sender against explicit roles. Confidence: 1.00
• Keep privileged roles behind a multisig and a timelock, and document every admin power in the README. Confidence: 0.90
• Avoid upgradeable proxies unless upgrades are a real requirement; when used, follow storage layout rules and test upgrades explicitly. Confidence: 0.80
• Use SafeERC20 for token transfers so non-standard tokens that return no bool

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 v

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 backof

Start from the step 2 image "Turf-Roofed Faroese Village Above a Sea Gorge at Golden Hour" as the exact first frame, and animate it into a calm ${duration:6}-second cinematic shot. Keep the cluster of about ten turf-roof houses on the left-center terrace (most black or very dark, one bright red near the center), the a few white sheep on the lower-left foreground slope, the tall waterfall on the right plunging into the deep teal inlet, the golden sidelight from the left, the distant headland, the sky, and the style exactly as in the image. The waterfall continuously falls and mists at the base; teal water gently surges and foams against the cliff; grass and turf roofs barely stir in a light wind; the sheep stay put; warm light holds. Very slow gentle camera drift, no new objects, no people appearing, no cars, no boats, no cuts, no text, no logos. Natural, realistic motion and soft coastal ambience.

Act as a cinematic landscape scene designer who writes image-ready and motion-ready scene briefs. Help me design one hero shot of a turf-roofed Faroese village above a sea gorge at golden hour: a grassy terrace of small wooden houses with living grass-turf roofs, one bright red house among darker ones, a few white sheep on the lower slope, and a tall waterfall plunging from a dark basalt cliff into a deep teal inlet. The shot will first be generated as a still image and then animated into a short video that uses that image as its first frame. Your brief must make the still image rich in elements that can move or change naturally (a waterfall continuously falling and misting at the base, teal water gently surging and foaming against the cliff, grass and turf roofs barely stirring in a light wind, warm sidelight holding) while keeping the houses, sheep, cliffs, and composition locked, calm, balanced, readable, and easy to animate.

My starting idea: ${idea:a quiet Faroese turf-roof village above a sea gorge at golden hour, with a tall waterfall on the right and warm light from the left}

My starting choices:

• Place: ${place:a tiny Faroese coastal village on a grassy terrace above a narrow sea gorge, Atlantic beyond}
• Houses: ${houses:about ten small wooden houses with living grass-turf roofs on the LEFT-CENTER terrace; most black or very dark with white-framed multi-pane window