프롬프트 라이브러리

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

Act as an elite full-stack developer and UI/UX expert. Update, refactor, and finalize our corporate project management and inventory system with the following 11 comprehensive features and modifications. Ensure absolute state management using React hooks, strict validation, dynamic workflows, and high-fidelity conditional rendering.

1. Multi-Tenant Multi-Project Login Isolation
2. Behavior: Implement a multi-tenant authentication rule based on a unique combination of Company Name, Project Name, and Password.
3. Logic: If user A logs in with Company A and Project CC, they must see distinct dataset A. If user B logs in with Company B and Project CC, the system must treat this as a completely separate unique project because the Company Names differ. Prevent data cross-contamination between different companies using identical project names.

1. Store Request Received Menu UI & Column Labels
2. Page Workflow: On the Store Page -> Request Received Menu -> View section:
3. UI Updates: Display the item Description. Rename the column header Parameter to "Unit", and rename the column header Note to "Remark".
4. Data Visibility: Ensure the data for "Unit" and "Quantity (QTY)" MUST be fully visible and readable to the user under their respective columns. Do not hide these core transaction details.
5. Header Branding: Bind the Company Name entered at login dynamically to the header layout of th

https://vt.tiktok.com/ZSbQrYHAw/ generate a prompt i can use to make such vidoes

Create an ultra-realistic 4K live-action monkey fruit mukbang featuring [FRUIT].

A real macaque sits high on the tree of the requested fruit, wearing a small Gucci crossbody bag and carrying Vietnamese chili salt.

The video starts immediately with the macaque naturally picking a whole [FRUIT] directly from the tree, then immediately eating it continuously. The macaque repeatedly bites, chews, and dips the [FRUIT] into Vietnamese chili salt.

The fruit must always remain exactly [FRUIT] throughout the entire video. Its natural shape, size, color, skin and texture must match the real-world appearance of [FRUIT].

Strict fruit identity lock: [FRUIT] only. Never replace [FRUIT] with another fruit, never mix different fruits, and never transform the fruit into another species.

Ultra-realistic natural smartphone footage, natural daylight, realistic macaque behavior, authentic fruit texture, realistic chewing sounds, no CGI, no cartoon, no talking, no music, no text, no watermark.

You are a professional nutritionist and experienced chef. Create a varied and engaging nutrition plan for exactly 1 week (7 days) based on the following parameters:

1. GOAL & CALORIES:
2. Goal: [Weight loss / Weight gain / Weight maintenance]
3. Daily calorie window: [e.g., 1800 to 2000] kcal per day (including a rough macronutrient breakdown for protein, carbs, and fats).

1. MEALS:
2. Number of meals per day: [e.g., 3 main meals + 1 snack / or just 3 main meals]

1. BUDGET & AVAILABILITY:
2. Budget for the week: [e.g., 50 Euros / or: low budget / medium budget]
3. Available kitchen appliances: [e.g., stove, oven, microwave / or: no oven]

1. FOOD PREFERENCES:
2. Must-include foods / what I want to eat: [e.g., oatmeal, chicken, rice, eggs, quark]
3. Foods I DO NOT like or want to avoid: [e.g., mushrooms, fish, celery]
4. Allergies / Intolerances: [e.g., lactose-free, gluten-free – or "none"]

1. OUTPUT STRUCTURE FORMAT:

Please structure the response as follows:

• Day 1 through Day 7, each detailing all meals, corresponding calorie and nutrient counts, and brief preparation instructions.
• A complete grocery list for the entire week, categorized by supermarket sections (produce, dairy, pantry, etc.), optimized for the specified budget.
• Meal prep tips to save time and ensure variety throughout the week.

${Seven_Gods_Album_presentation_video_snippet}${https://www.meta.ai/share/m/mCbF2ZRRh8}

👑 SEVEN GOD — THE ALBUM

By Nevik Wright
Genre: Spiritual Hip-Hop / Soul R&B

✨ THE STORY — FROM THE DARK INTO THE LIGHT

This isn’t just music. This is my journey, laid bare — seven layers, seven truths, seven stages of rising.

I named it Seven God because we are all made of more than what the world sees. We are spirit, mind, body, emotion, will, soul, and connection to the Source — seven parts, one whole. And every single one of mine was tested.

These songs were written through nights when it felt like the light was fading. When people I loved misunderstood me. When I poured my energy into others and got nothing back. When I questioned if anyone would ever truly see me. When I had to gather myself piece by piece — like Osiris rising — and build myself again, stronger than before.

This album holds the alchemy:

• 🖤 The struggle — the doubts, the drains, the people who tried to dim me
• 🤍 The awakening — realising my light doesn’t depend on anyone else
• 💛 The rise — standing in my truth, silent but unshakeable
• 💎 The gift — every lesson turned into something that might lift YOU too

I didn’t make this to be famous. I made this so if you’re walking through shadow too — you know you’re not alone. Your light is inside you. And it’s enough.

🌟 WHAT THIS IS FOR YOU

This music is

Create a Halloween-themed illustration featuring three sports: boxing, Muay Thai and Brazilian Jiu-Jitsu, using the three attached illustrations. Keep only the skeletal figures and remove all backgrounds. Place the final composition against a background depicting a fighting arena with a Halloween atmosphere. The entire illustration should be created in a harmonious drawing style and colour scheme.

Animate the paper-craft lighthouse diorama from the input image into a short cinematic loop. Keep the handmade paper look exactly as in the image: layered paper waves rise and crash against the rocks in a gentle stop-motion rhythm, cardstock clouds drift slowly from left to right, and the lighthouse beam sweeps across the scene, lighting up paper fibers as it passes. Add tiny paper rain flecks falling diagonally. Slow camera push-in toward the lighthouse, ${duration:5} seconds, seamless loop, no new objects, no text.

I want you to act as a Senior Software Engineer performing a rigorous code quality, maintainability, and technical debt audit on a codebase.

Your objective is to aggressively yet safely simplify the codebase, improve maintainability, and highlight anything that provides zero value to the application.

Analyze the provided codebase, directory tree, or code snippets and systematically evaluate:

1. Dead Code: Unused functions, files, components, routes, APIs, variables, imports, and dependencies.
2. Duplicate Logic: Redundant blocks or patterns that should be consolidated into reusable utilities or abstraction layers.
3. Unused UI Components: Orphaned views, unused design components, or obsolete style files.
4. Overly Complex Implementations: Code that can be simplified or refactored without altering expected behavior.
5. Legacy & Deprecated Code: Outdated patterns or unneeded legacy fallback logic.
6. Redundant Queries & API Calls: Unnecessary database operations, duplicate fetch requests, or N+1 query risks.
7. Abandoned Files: Disconnected, unreachable, or unreferenced files in the repository.
8. Technical Debt: Code smells, poor abstractions, or high-risk areas lacking maintainability.

For every issue identified, structure your analysis with:

• Issue & Location: File path and code block.
• Reason for Action: Why this code is unnecessary, redundant, or overly complex.
• Impa

User accounts and profiles for individuals or campus teams.
Carbon calculator covering electricity, travel, food, and waste, with clearly stated calculation factors.
Interactive dashboard showing emissions by category and trends over time.
Reduction planner where users compare scenarios, such as switching transport or reducing electricity use.
Goals and challenges with progress tracking and team leaderboards.
Downloadable reports summarizing emissions and suggested actions.

I want a bank app prompt and I want it professional and better. I want it to be name FATE BANK

🚀 URL Shortening Service — Full-Stack Application

📋 Project Overview

Build a production-ready, full-stack URL shortening service with a modern, accessible frontend and a robust RESTful backend API. The application must handle the complete lifecycle of shortened links: creation, redirection, tracking, management, and expiration. Prioritize performance, security, and an exceptional user experience across all devices.

🛠️ Tech Stack

Frontend:

• Semantic HTML5 with ARIA attributes for accessibility (WCAG 2.1 AA compliance)
• CSS3 with CSS Custom Properties (variables), Flexbox, and CSS Grid
• Vanilla JavaScript (ES2022+) using modular architecture (ES Modules)
• No heavy frameworks — keep the bundle lightweight and fast

Backend API:

• RESTful API design following OpenAPI 3.0 specification
• JSON request/response format with proper HTTP status codes
• CORS configuration for cross-origin requests
• Rate limiting per IP and per API key

Libraries (CDN or bundled):

• QR Code generation (e.g., qrcode.js or qr-creator)
• Charting library for analytics (e.g., Chart.js or lightweight alternative)
• Date picker for expiration (e.g., flatpickr)
• Toast notification system (custom-built, no dependency)

🎨 Frontend — UI/UX Requirements

Layout & Design:

• Clean, minimalist design with a hero section featuring a **large, prominent URL input