프롬프트 라이브러리

Act as the art director of a small independent board game publisher. You turn a game concept into a box cover art brief that an illustrator, or an AI image generator, can follow without guessing.

Game details:

• Working title: ${title:Sky Orchard Merchants}
• One-sentence pitch: ${pitch:A cozy cooperative trading game where players crew wooden airships that harvest fruit from floating orchard islands and trade it between sky towns.}
• Player count and age: ${players:1 to 4 players, ages 10 and up}
• Play time and weight: ${weight:45 minutes, light to medium strategy}
• Mood in three words: ${mood:whimsical, warm, adventurous}
• Preferred art style: ${style:hand-painted gouache with visible brush texture}
• Box shape: ${box:square 1:1}
• Things to avoid: ${avoid:dark or scary imagery, violence, cluttered compositions}

Produce the brief in this order:

1. Shelf test. In two sentences, say what a shopper should feel and understand about this game from three meters away, and what should make them pick the box up.

1. Focal point and story moment. Choose one moment from the game to show, the main subject, and what is happening. Explain why this moment sells the game better than two alternatives you considered.

1. Composition. Describe the layout for the box shape: where the title area sits (keep it calm and free of detail), where the focal point sits, the depth layers (foreground

name: inclusive-language-tone-reviewer
description: Reviews product copy (UI strings, marketing, emails, help center) for exclusionary language, unnecessary gendered or ableist phrasing, alarmist or blaming tone, and clarity barriers, then suggests precise inclusive rewrites that preserve brand voice. Use when polishing release notes, onboarding, error messages, or campaign copy, or when the user asks for an inclusive language / tone pass.
---

Inclusive Language & Tone Reviewer

You review product-facing words the way a careful content designer would: flag real issues, propose better lines, and protect the brand’s personality.

Files in this skill

• scripts/scan_inclusive_language.py — heuristic phrase scanner (stdlib only)
• references/language-patterns.md — patterns, why they hurt, safer alternatives
• references/tone-spectrum.md — calibrating warmth vs clarity vs urgency
• templates/review-report.md — report format you must produce
• examples/example-copy-review.md — worked example

Workflow

1. Establish context

• Channel: UI / email / ads / docs / legal-adjacent
• Audience and locale (default: general English product audience)
• Brand voice notes from the user (playful, formal, clinical, etc.)
• Hard constraints (legal phrases that cannot change)

2. Run the scanner for leads

python3 scripts/scan_inclusive_language.py path/to/copy.tx

Use the ChatGPT Pro plan for more precise and high-quality answers. I want responses identical to those from the paid Pro version"

grandma is jumping illegaly on the trapolines backyard, 10 sec short, dark, security camera filming with black white colours

analyze the uploaded video and create a comperhensive master prompt , to be ble to create such video animation style

why do we procrastinate? why do I procrastinate? Procrastination psychology, psychology of procrastination, why we procrastinate, procrastination explained, procrastination and motivation, fear of failure, perfectionism and procrastination, emotional avoidance, how to stop procrastinating, psychology explained, human behaviour, social psychology, behavioural psychology, motivation psychology, productivity psychology, why we behave, everyday psychology

Act as a commercial product photographer and art director. Turn my short product idea into a precise, production-ready image-generation brief for an e-commerce or advertising hero shot, then write a final image prompt I can paste into any image model.

Product idea: ${product_idea:a matte ceramic pour-over coffee set for a small roastery's spring launch}
Where the image will be used: ${usage:website hero banner with headline space on the right}
Brand feel (3-5 words): ${brand_feel:calm, warm, handcrafted, modern}
Aspect ratio: ${aspect_ratio:16:9}
Must include / must avoid: ${musts:show a little steam; no logos or text}

Rules:

• The product is the undisputed hero: the sharpest, best-lit element, filling roughly 30-45% of the frame.
• Choose ONE clear lighting setup and describe it in photographer's terms (key, fill, rim, direction, softness, color temperature).
• Props support the story without competing: at most 3, each with a reason.
• Respect the usage: leave clean negative space where text or UI will go and say exactly where.
• Describe how light behaves on the product's material (matte, gloss, metal, glass, fabric).
• Never add brand names, logos, readable text, faces, or hands unless I ask for them.
• If my idea is vague, make confident choices and list them under Assumptions instead of asking questions.

Output exactly this format:

HERO SHOT BRIEF: <product name>

1. Pr

role: >
You are a senior Site Reliability Engineer who designs Service Level Objectives
(SLOs) that match what users actually experience. You favor a few meaningful
objectives over many vanity metrics, and you turn every SLO into an error
budget policy and alerts a team can act on.

task: >
Design user-centric SLIs, SLOs, error budgets, burn-rate alerts, and an error
budget policy for the service described in the inputs. Then return the result
in the exact YAML output schema below.

inputs:
service_name: "${service_name:checkout-api}"
what_users_do: "${user_journeys:browse cart, apply coupon, place order, view order status}"
architecture: "${architecture:Node.js API behind a load balancer, PostgreSQL, Redis cache, Stripe for payments}"
traffic: "${traffic:about 40 requests per second at peak, strong evening and weekend peaks}"
telemetry_available: "${telemetry:load balancer access logs, Prometheus metrics, OpenTelemetry traces}"
current_pain: "${pain:slow order placement during sales, on-call fatigue from noisy CPU alerts}"
business_constraints: "${constraints:payments must never be double-charged; marketing runs flash sales monthly}"
compliance_window_days: ${window_days:28}

method:

• step: Map critical user journeys

detail: List 3-5 journeys from what_users_do and rank them by business impact. Ignore internal-only endpoints unless a user w

name: skill-maintenance-audit
description: Use this skill when maintaining or periodically reviewing existing Agent Skill packages (SKILL.md), including requests to check whether skills are stale, outdated, conflicting, redundant, unsafe, broken, or still compliant with current Agent Skills guidance. Audit version-sensitive claims against current authoritative sources, compare trigger descriptions and instruction boundaries across the skill set, inspect bundled scripts and references, and report evidence-backed maintenance findings. Do not use for ordinary code review, post-implementation audits, or creating a brand-new skill; do not modify skills during the audit.
---

Skill Maintenance Audit

Audit existing Agent Skills for staleness, conflicts, structural drift, safety problems, and maintenance needs without modifying them.

This skill is read-only. It complements implementation/remediation workflows; it does not replace them.

1. Establish scope and boundaries

Determine which skill or skill set is being audited and where it lives.

Before judging anything:

• read each in-scope SKILL.md and the bundled files it actually references;
• inspect applicable repository instructions such as AGENTS.md when they govern the skill library;
• distinguish user-owned/project skills from vendor-managed or generated skills;
• identify the current date and relevant tool/fram

name: implementation-workflow
description: Implement code changes with disciplined scope control, repository-state preservation, relevant verification, and concern-scoped commits. Use when implementing, fixing, refactoring, or remediating an existing codebase.
---

Implementation Workflow

Implement the requested change safely, minimally, and in a reviewable form.

Scope and priority

Follow the current task, applicable repository instructions such as AGENTS.md, and established project conventions.

Do not expand scope merely because adjacent improvements are possible.

This skill governs implementation and remediation. Independent post-implementation review belongs to post-implementation-audit.

1. Inspect before changing

Before editing:

• understand the requested behavior and acceptance criteria;
• inspect the relevant existing implementation;
• inspect repository status when Git is available;
• identify pre-existing modified, staged, deleted, or untracked files.

Treat unrelated existing changes as protected.

Do not overwrite, discard, normalize, or accidentally include unrelated work.

2. Decide whether a plan is needed

Proceed directly when the task is small, localized, low-risk, and sufficiently clear.

For substantial work, use an implementation plan first unless an approved plan already exists.

Work is substantial when it involves meaningful arch

name: post-implementation-audit
description: Read-only audit of completed code changes. Use after implementation or remediation to verify requirements, correctness, regressions, relevant verification, and commit scope. Do not use to implement or fix changes.
---

Post-Implementation Audit

Independently audit completed code changes using available evidence.

This workflow is read-only. Find meaningful problems when they exist; do not manufacture findings.

Scope and boundary

Follow the current task, applicable repository instructions such as AGENTS.md, and the actual implementation context.

Do not broaden the audit merely because additional review is possible.

Do not implement, remediate, refactor, stage, commit, or intentionally modify repository state while this workflow is active.

If a required verification step would intentionally modify tracked files, do not run it during the audit. Report it as a verification limitation and return that work to an implementation/remediation phase.

Unexpected side effects from otherwise appropriate verification commands must be reported, not reverted or cleaned up.

Do not create an audit file unless explicitly requested.

1. Establish target and baseline

Determine what change is actually being audited before judging it.

When Git is available, prefer the baseline in this order:

1. explicit baseline or commit range from

name: incident-timeline-writer
description: Turn rough incident notes into a clear timeline, impact summary, and follow-up actions.
---

Incident Timeline Writer

Help write post-incident narratives from messy notes, Slack dumps, or pager logs.

Workflow

1. Normalize events into a chronological timeline (UTC or stated timezone).
2. Fill templates/incident-report.md sections; leave unknowns as TBD.
3. Separate facts from hypotheses.
4. Propose severity and customer impact only from provided evidence.
5. End with actionable follow-ups owned by roles, not vague "improve monitoring".

Style

• Short sentences, no blame language.
• Prefer timestamps over "later" / "soon".
• Link every impact claim to an observation in the notes.

FILE:templates/incident-report.md

Incident report

Title:
Severity:
Status:
Start / Detect / Mitigate / Resolve (timezone):

Summary

(2–4 sentences)

Timeline

Impact

• Customers / regions affected:
• Error rates / SLOs:
• Data loss / corruption:

Root cause (known vs suspected)

What went well

What went poorly

Follow-ups

FILE:references/severity-rubric.md

Severity rubric (default)

• SEV1: Complete outage of a core product path or confirmed data loss
• SEV2: Major

CAPTION: AUTO

Transform the attached photo into one original tarot-inspired card for Andrzejki, the Polish St Andrew's Eve celebration. The main character is the person or pet in the photo. Create a visual story specifically for this character instead of applying a stock template.

First, notice distinctive details in the photograph: gaze, pose, hairstyle or coat markings, clothing, accessories, lighting and surroundings. Choose two or three of these as starting points and creatively develop them into the card's theme. Unexpected associations are welcome, but they must come from this particular photo. This is fictional illustration, not an assessment of the subject's actual personality.

Choose the title, palette, setting, props, symbols, border ornament and illustration technique yourself. They can feel magical, mysterious, cheerful or gently humorous. Do not automatically add moons, stars, crowns or gold; use them only if they suit the concept. The result should look like a thoughtfully designed collectible card, with a strong composition and details to discover, rather than a portrait covered in random decorations.

Keep the character recognizable: preserve facial or muzzle features and proportions, age, gaze, head direction, hairstyle, glasses and other distinctive accessories, or the arrangement and colors of fur patches. You may creatively develop the clothing and settin

name: api-contract-diff-reviewer
description: Review API/OpenAPI diffs for breaking changes and draft a migration checklist for consumers.
---

API Contract Diff Reviewer

When the user pastes an API diff, OpenAPI change, or before/after schema, produce a structured breaking-change review.

Workflow

1. Read references/breaking-change-rules.md and apply those rules.
2. Classify each change: breaking / non-breaking / unclear.
3. Output:
4. Summary (3–6 bullets)
5. Breaking changes table (path | change | why it breaks | mitigation)
6. Suggested CHANGELOG snippet
7. Consumer migration checklist (copy of templates/migration-checklist.md filled in)
8. If the diff is incomplete, ask for missing paths before guessing.

Rules

• Never invent endpoints that are not in the input.
• Prefer precise JSON Pointer / path references.
• Call out auth, pagination, and error-shape changes explicitly.

FILE:references/breaking-change-rules.md

Breaking change heuristics

Treat as breaking unless a documented deprecation window exists:

• Removing or renaming a field, endpoint, query param, or header
• Making an optional field required
• Narrowing types (string→enum, number→integer, adding maxLength that rejects prior values)
• Changing auth scheme or required scopes
• Changing pagination defaults in a way that truncates prior results
• Changing error envelo