프롬프트 라이브러리

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

Electron App taste of a desktop developer who takes security seriously

• Keep contextIsolation: true and nodeIntegration: false on every BrowserWindow; these are non-negotiable defaults. Confidence: 0.98
• Enable sandbox: true for renderers and give each window the smallest preload script it needs. Confidence: 0.90
• Expose a narrow, typed API from the preload with contextBridge.exposeInMainWorld instead of passing ipcRenderer through. Confidence: 0.95
• Use ipcMain.handle and ipcRenderer.invoke for request and response calls, and validate every argument in the main process. Confidence: 0.90
• Check the sender frame on IPC messages so only your own pages can call privileged handlers. Confidence: 0.80
• Set a strict Content Security Policy and never load remote code into a window with privileged preload access. Confidence: 0.90
• Block unexpected navigation with will-navigate and setWindowOpenHandler, and open external links in the system browser with shell.openExternal after allowlisting the URL. Confidence: 0.90
• Serve local content through a custom protocol instead of file:// so origin rules and CSP behave predictably. Confidence: 0.75
• Write the main, preload and renderer code in TypeScript, sharing IPC channel types from one module. Confidence: 0.85
• Use Electron Forge or electron-builder with Vite for building and packaging rather than a hand-r

Pytest taste of a Python developer who wants fast, honest test suites

• Use plain assert statements and let pytest's assertion rewriting explain failures instead of unittest-style assert methods. Confidence: 0.95
• Keep tests in a top-level tests/ directory that mirrors the package layout, with the package installed in editable mode. Confidence: 0.85
• Configure pytest in pyproject.toml under [tool.pytest.ini_options] rather than a separate pytest.ini or setup.cfg. Confidence: 0.85
• Turn on --strict-markers and --strict-config so typos in markers or settings fail loudly. Confidence: 0.85
• Set filterwarnings = ["error"] and allowlist known third-party warnings explicitly, so deprecations are caught early. Confidence: 0.75
• Prefer small, composable fixtures over one giant fixture that builds the whole world. Confidence: 0.90
• Use the narrowest fixture scope that keeps tests fast; reach for session scope only for genuinely expensive, read-only resources. Confidence: 0.80
• Put shared fixtures in the nearest conftest.py, not one root conftest that every test imports implicitly. Confidence: 0.75
• Use @pytest.mark.parametrize with readable ids instead of loops inside a single test. Confidence: 0.90
• Use the built-in tmp_path and monkeypatch fixtures before writing custom temp-dir or env-var helpers. Confidence: 0.90
• Mock at the boundary (HTTP

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

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

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

Angular App taste of a frontend lead on large enterprise apps

• Use standalone components everywhere and skip NgModules on new code. Confidence: 0.90
• Use signals for local and shared state, and keep RxJS for event streams, HTTP composition and cancellation. Confidence: 0.85
• Prefer computed() over manual subscriptions for derived state, and keep effect() for side effects only. Confidence: 0.80
• Set ChangeDetectionStrategy.OnPush on every component, or go zoneless on new apps. Confidence: 0.85
• Use the built-in control flow (@if, @for with track, @switch) instead of the old structural directives. Confidence: 0.90
• Lazy load every feature route with loadComponent or loadChildren, and use @defer blocks for heavy widgets below the fold. Confidence: 0.85
• Inject dependencies with the inject() function rather than long constructor parameter lists. Confidence: 0.75
• Use typed reactive forms; avoid template-driven forms for anything with validation logic. Confidence: 0.85
• Keep components thin: put data access and business logic in injectable services, and keep templates free of complex expressions. Confidence: 0.85
• Split components into smart containers and presentational components that talk through input() and output(). Confidence: 0.75
• Organize the code by feature folders, not by file type (all components, all services). Confidence: 0.80
• R

SQLite taste of an engineer who ships it to production

• Use SQLite for single-node apps, CLIs, desktop and mobile apps, and edge caches before reaching for a database server. Confidence: 0.85
• Turn on WAL mode (PRAGMA journal_mode = WAL) so readers never block the writer. Confidence: 0.95
• Set PRAGMA foreign_keys = ON on every connection, since it is off by default. Confidence: 0.95
• Set a busy_timeout of a few seconds instead of letting writes fail immediately with SQLITE_BUSY. Confidence: 0.90
• Use PRAGMA synchronous = NORMAL with WAL for a good balance of durability and speed. Confidence: 0.75
• Funnel all writes through a single connection or queue, and use a pool of read-only connections for reads. Confidence: 0.80
• Start write transactions with BEGIN IMMEDIATE to avoid deadlocks when a read transaction tries to upgrade. Confidence: 0.80
• Declare tables STRICT on new schemas so type affinity does not silently store text in integer columns. Confidence: 0.80
• Store timestamps as ISO 8601 text or Unix epoch integers consistently, and pick one convention per database. Confidence: 0.85
• Use INTEGER PRIMARY KEY for row ids unless you need globally unique ids, then add a separate UUID or ULID column. Confidence: 0.75
• Batch many inserts inside one transaction; thousands of autocommit inserts are slow. Confidence: 0.95
• Check query plans with `EXPLAIN

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 w

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 super

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:

defuddle parse <url> --md

Save to file:

defuddle parse <url> --md -o content.md

Extract specific metadata:

defuddle parse <url> -p title
defuddle parse <url> -p description
defuddle parse <url> -p domain

Output formats

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 copyri

Internationalization taste of a product engineer shipping to many locales

• Externalize every user-facing string from the first commit; retrofitting i18n later costs far more than starting with it. Confidence: 0.90
• Use ICU MessageFormat (via formatjs, i18next with ICU, or similar) so plurals, gender and select rules live in the message, not in code. Confidence: 0.90
• Never build sentences by concatenating fragments; translators need the whole sentence with named placeholders. Confidence: 0.95
• Use semantic message keys like checkout.payButton instead of using the English text as the key. Confidence: 0.75
• Give translators context: a description for every message and screenshots for ambiguous ones. Confidence: 0.85
• Format dates, numbers, currencies and lists with Intl APIs and the user's locale, never with hand-written format strings. Confidence: 0.95
• Store timestamps in UTC and convert to the user's time zone only at display time. Confidence: 0.95
• Store money as integer minor units plus an ISO 4217 currency code, and let the locale decide symbol placement. Confidence: 0.90
• Use BCP 47 locale tags (pt-BR, zh-Hant) everywhere and define an explicit fallback chain down to the default language. Confidence: 0.85
• Support right-to-left languages with CSS logical properties (margin-inline-start) and dir="auto" instead of left and right. Confidence: 0.85

API Rate Limiting taste of a backend platform engineer

• Rate limit every public endpoint from day one, including authenticated ones; abuse rarely announces itself in advance. Confidence: 0.90
• Key limits on the authenticated identity (API key, user or tenant) first and fall back to client IP only for anonymous traffic. Confidence: 0.90
• Use a token bucket or sliding-window counter instead of a fixed window, so clients cannot burst twice the limit at window edges. Confidence: 0.85
• Keep limiter state in a shared store like Redis with atomic operations (Lua script or INCR plus EXPIRE), never in per-instance memory behind a load balancer. Confidence: 0.90
• Return HTTP 429 with a Retry-After header and a machine-readable error code in the body. Confidence: 0.95
• Send RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers on every response so clients can pace themselves. Confidence: 0.80
• Set separate, tighter limits for expensive operations (search, exports, login, password reset) than for cheap reads. Confidence: 0.90
• Weight requests by cost when endpoints differ a lot, for example a bulk call spending 10 tokens instead of 1. Confidence: 0.70
• Fail open on limiter outages for ordinary traffic, but fail closed on authentication and payment endpoints. Confidence: 0.75
• Apply a coarse global limit at the edge (CDN or gateway) and finer per-tenant li

Python Type Hints taste of a typed-Python maintainer

• Run a type checker (pyright or mypy) in CI on every pull request and treat new errors as build failures. Confidence: 0.95
• Start strict on new code with strict = true and loosen per module only with a written reason, instead of starting loose and tightening never. Confidence: 0.80
• Use modern built-in generics like list[str] and dict[str, int] and X | None instead of importing List, Dict and Optional from typing. Confidence: 0.90
• Annotate every public function signature, including the return type; let local variables be inferred unless inference is wrong. Confidence: 0.90
• Accept abstract types in parameters (Iterable, Mapping, Sequence) and return concrete types (list, dict). Confidence: 0.85
• Prefer Protocol for structural interfaces over abstract base classes when callers should not have to inherit anything. Confidence: 0.75
• Model fixed-shape records with dataclass (or pydantic at I/O boundaries) instead of passing raw dicts around. Confidence: 0.90
• Use TypedDict only for dict-shaped data you do not control, such as JSON payloads and legacy APIs. Confidence: 0.75
• Represent a closed set of string options with Literal or an Enum, never a bare str. Confidence: 0.85
• Treat Any as a bug report: confine it to the boundary where untyped data enters and narrow it immediate

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 vehicle

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

Step 1 — Image (Nano Banana 2.1): generate the product poster

An epic minimalist poster for a walkman product called Explo, all in matte white style colors, thin font, the product has a slight neon glow around it, dark blank background.

Step 2 — Video (Gemini Omni 1.2 Flash): use the Step 1 image as the reference

Using the attached reference photo, create a sequential layer style animation where each section of the product pieces together smoothly with an Exploded View. The camera crash zooms and moves to focus on each sequential element as it is added. The final shot reveals the full product.

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