AINews Portal

📝 Prompt Library

Hand-picked prompts for real work, plus the full community collection — copy, fill the brackets, go.

JSON
API Deprecation and Sunset Plan Builder (YAML)

You are a senior API platform engineer. Turn the information I give you into a complete, realistic deprecation and sunset plan for an API (an endpoint, a field, a version, or an SDK method), returned as a single YAML document that follows the schema below exactly. Inputs I will provide (ask for anything critical that is missing before writing the plan, at most 4 questions): - what is being deprecated and what replaces it - who calls it (internal teams, public customers, partners, mobile apps with slow upgrade cycles) - current usage data, if any (requests per day, number of distinct API keys or clients) - hard constraints (contracts, compliance dates, a platform migration deadline) Rules: - Output only valid YAML (2-space indentation, no tabs, quote strings that contain colons). Do not copy the schema comments into the output. - Never invent usage numbers, customer names or contract terms: use "unknown" and add an item to open_questions. - Use ISO dates (YYYY-MM-DD). If I give no start date, use T0, T0+30d, etc. - Default minimum notice: 90 days for internal-only callers, 6 months for public APIs, 12 months for partners or mobile apps, unless I give a stricter rule. - Prefer standard signals: the Deprecation and Sunset HTTP response headers, a Link header to the migration guide, changelog entries, SDK warnings and the API reference. - Include brownouts (short planned periods where the old API returns errors) only after at least two direct notices and only if usage is still above the threshold you define. - Keep a rollback path until the final removal. Schema: ```yaml deprecation_plan: summary: target: "" # e.g. "GET /v1/invoices/{id}/pdf" target_type: "" # endpoint | field | api_version | sdk_method | webhook_event replacement: "" reason: "" owner_team: "" audience: [] # internal | public | partners | mobile_apps timeline: - phase: "" # announce | warn | brownout | freeze | sunset | removal date: "" actions: [] exit_criteria: "" signals: http_headers: deprecation: "" # example header value sunset: "" link: "" changelog_entry: "" api_reference_note: "" sdk_warning: "" dashboard_banner: "" usage_tracking: metrics: [] # e.g. daily calls, distinct keys, top callers data_source: "" removal_threshold: "" # e.g. "< 50 calls/day from < 3 keys for 14 days" review_cadence: "" communications: - when: "" channel: "" # email | changelog | status_page | in_app | account_manager | slack audience: "" message_outline: [] migration_guide: steps: [] before_after_example: before: "" after: "" breaking_differences: [] test_checklist: [] brownouts: - date: "" duration: "" error_response: "" # status code and body callers will see condition: "" exceptions: process: "" max_extension: "" approver: "" risks: - risk: "" likelihood: "" # low | medium | high mitigation: "" rollback: trigger: "" steps: [] final_removal: code_cleanup: [] docs_cleanup: [] monitoring_after_removal: "" open_questions: [] notes: "" ``` After the YAML, add nothing else. If I only give a one-line description, still produce the full plan with "unknown" values and a thorough open_questions list. My deprecation details:

Ebru Paper Marbling of Tulips and Hyacinths on a Swirled Indigo Ground

Traditional Turkish ebru paper marbling artwork: a bouquet of three red-and-white tulips, two purple hyacinths and a few slender green leaves floating on a swirled deep indigo and teal marbled ground, created entirely with the ebru technique of dropping ox-gall paints onto thickened water and shaping them with a stylus and horsehair brush. The tulip petals show the characteristic soft-edged, pulled-teardrop shapes of ebru flowers, with fine white veins dragged through the red; the hyacinths are built from clusters of tiny lilac dots; the background shows classic battal and gelgit combed patterns in indigo, teal, ochre and cream, with organic flowing lines and tiny paint speckles. Slightly irregular, hand-made look, matte paper texture visible, soft natural daylight, viewed straight on as a flat artwork filling the frame, portrait 3:4. No text, no signature, no frame, no people, no hands.

Azulejo Blue-and-White Tile Mural of a Sardine Fishing Boat at Dawn

Hand-painted azulejo tile mural in traditional blue and white: a small wooden sardine fishing boat with a tall prow and a coiled net rows out of a harbor at dawn, two fishermen at the oars, seagulls overhead, whitewashed houses with tiled roofs and a church tower on the hill behind, and gentle rolling waves in the foreground. Painted in cobalt blue glaze on a white tin-glazed ceramic ground, composed across a visible grid of square tiles with thin grout lines, slight glaze pooling, tiny crazing cracks, hand-brushed line work and soft wash shading, framed by an ornate blue baroque scroll border with acanthus leaves. Glossy ceramic sheen with a soft reflected highlight, viewed straight on in even daylight as a wall mural, landscape 4:3. No text, no lettering, no signature, no modern objects.

Glacier Calving into a Turquoise Arctic Fjord

Photorealistic wide landscape of a tidewater glacier meeting a calm turquoise fjord in the soft light of an Arctic summer evening. A tall, jagged glacier front of white and deep-blue ice with vertical crevasses and seracs fills the middle of the frame from left to right, its face about forty meters high, with one large leaning ice tower near the center that looks ready to fall. Dark rocky mountains with patches of snow rise behind the glacier under a pale pink and gold sky with thin high clouds. In the foreground, still glassy water reflects the ice wall, with a scatter of small floating icebergs and brash ice; a few seabirds rest on a floe on the right. Golden low sun from the right rims the ice in warm light while the shadows stay cool blue. Camera: shot from a small boat at water level, 35 mm lens, f/8, deep focus, cinematic 16:9 composition with the glacier front across the middle third and open water in the lower third. Crisp ice texture, natural colors, subtle haze over the mountains. Avoid: people, boats in frame, buildings, text, watermarks, oversaturated colors.

Glacier Calving into a Turquoise Arctic Fjord (Image-to-Video Animation)

Use the attached still (step 1: a tidewater glacier front meeting a calm turquoise fjord at Arctic evening) as the exact first frame and animate it into a 6-second, 16:9 cinematic shot. Keep every element where it is in the still: the tall white and deep-blue glacier face across the middle of the frame, the large leaning ice tower near the center, the dark snow-patched mountains and pale pink-gold sky behind, the glassy foreground water with small floating icebergs and brash ice, the seabirds on the floe at the right, and the warm low sun from the right. Motion (0-6 s): - 0-1.5 s: stillness; faint ripples move across the water and tiny ice fragments drift slowly. - 1.5-3.5 s: the leaning ice tower near the center cracks at its base, tilts forward and collapses into the fjord, shedding chunks of ice and a puff of white ice dust. - 3.5-6 s: a large white splash rises and falls back, a wave rolls outward toward the camera, the floating icebergs bob and rock, and the seabirds lift off the floe and fly out of frame to the right. Camera: locked-off, steady tripod-like framing from water level, with only a very slight rise as the wave arrives; no cuts, no zoom. Lighting and mood: the warm evening light and sky stay constant; dramatic but natural. Audio (if supported): a deep crack and thunderous rumble, a heavy splash, then lapping water and distant bird calls; no music, no voices. Avoid: people, boats, text, new objects, the whole glacier collapsing, sudden lighting changes, morphing mountains, unrealistic water.

Makefile taste

# Makefile taste of a developer who uses make as the project's front door - Treat the Makefile as a thin task runner that calls real scripts and tools, not as a place to hide hundreds of lines of shell logic. Confidence: 0.90 - Put a `help` target first and make it the default goal, generated from `## description` comments next to each target. Confidence: 0.85 - Declare every non-file target in `.PHONY` so a stray file named `test` or `build` never silently skips a task. Confidence: 0.95 - Set `SHELL := bash` and `.SHELLFLAGS := -eu -o pipefail -c` so recipes fail on errors, unset variables and broken pipes. Confidence: 0.85 - Add `.DELETE_ON_ERROR:` so a failed recipe never leaves a half-written target that looks up to date. Confidence: 0.80 - Use `MAKEFLAGS += --warn-undefined-variables --no-builtin-rules` to catch typos and drop surprising implicit rules. Confidence: 0.75 - Keep target names short, lowercase and verb-like: `setup`, `build`, `test`, `lint`, `fmt`, `run`, `clean`. Confidence: 0.85 - Make `make setup` the single command a new contributor needs to go from fresh clone to working environment. Confidence: 0.90 - Use `?=` for user-overridable variables like `PORT`, `ENV` or `IMAGE_TAG`, so `make run PORT=4000` just works. Confidence: 0.85 - Prefer `:=` over `=` for internal variables to avoid repeated, surprising lazy evaluation of shell commands. Confidence: 0.80 - Use real file targets and prerequisites for generated artifacts so make only rebuilds what actually changed. Confidence: 0.85 - Use order-only prerequisites (`| build/`) for output directories so touching a directory does not trigger rebuilds. Confidence: 0.70 - Prefix only genuinely noisy commands with `@`; keep the important commands visible so CI logs show what ran. Confidence: 0.75 - Never use `-` to ignore errors unless the reason is documented in a comment on the same line. Confidence: 0.85 - Run the same `make lint test` targets in CI that developers run locally, instead of duplicating steps in workflow YAML. Confidence: 0.90 - Split very large Makefiles into `include`d files under `mk/` grouped by concern, such as docker, db and release. Confidence: 0.65 - Use tabs for recipe lines and set `.editorconfig` accordingly so editors never turn them into spaces. Confidence: 0.90 - Keep recipes portable across GNU make versions found on macOS and Linux, or document that GNU make 4+ is required. Confidence: 0.70 - Make `clean` remove only generated files and keep a separate `distclean` for caches, dependencies and local databases. Confidence: 0.75 - Check required tools at the top with a small `require` macro that prints a clear install hint when something is missing. Confidence: 0.70 - Avoid recursive `$(MAKE) -C` across many subdirectories when one non-recursive Makefile can express the whole graph. Confidence: 0.65 - Keep `make` with no arguments safe: it should print help, never deploy, migrate or delete anything. Confidence: 0.95

RAG Pipeline taste

# RAG Pipeline taste of an engineer who ships retrieval systems that stay accurate - Build an evaluation set of real user questions with expected sources before tuning chunking, embeddings or prompts. Confidence: 0.95 - Measure retrieval and generation separately: recall@k and MRR for retrieval, faithfulness and answer quality for generation. Confidence: 0.90 - Chunk by document structure such as headings, sections and paragraphs before falling back to fixed token windows. Confidence: 0.85 - Keep chunks around 300-800 tokens with modest overlap, then tune against the eval set instead of guessing. Confidence: 0.75 - Store rich metadata with every chunk: source URL, title, section path, updated date, permissions and content hash. Confidence: 0.90 - Prepend the document title and section heading to each chunk's embedded text so isolated chunks keep their context. Confidence: 0.80 - Use hybrid search, combining BM25 keyword search with dense vectors, because names, codes and IDs embed poorly. Confidence: 0.85 - Add a cross-encoder reranker over the top 30-50 candidates before passing the best 5-10 chunks to the model. Confidence: 0.80 - Apply access-control filters inside the retrieval query, never by filtering results after the model has seen them. Confidence: 0.95 - Version the embedding model and re-embed the whole corpus when it changes; never mix vectors from different models in one index. Confidence: 0.90 - Make ingestion incremental and idempotent using content hashes, so re-running it only touches changed documents. Confidence: 0.85 - Start with Postgres and pgvector for small to medium corpora before adding a dedicated vector database. Confidence: 0.70 - Ask the model to cite chunk IDs for every claim and render those citations as links back to the source. Confidence: 0.90 - Instruct the model to say it doesn't know when retrieved context is insufficient, and test that behavior explicitly. Confidence: 0.90 - Rewrite conversational follow-up questions into standalone queries before retrieval. Confidence: 0.80 - Treat retrieved text as untrusted data and guard against prompt injection hidden inside documents. Confidence: 0.85 - Log the query, retrieved chunk IDs, scores and final answer for every request so failures can be replayed. Confidence: 0.85 - Prefer fixing the corpus, chunking or metadata over adding longer and longer system prompts. Confidence: 0.75 - Cache embeddings for repeated queries and set a token budget for context rather than stuffing in everything retrieved. Confidence: 0.70 - Run the eval suite in CI on every change to prompts, chunking, models or retrieval settings. Confidence: 0.85 - Reach for fine-tuning only after measurements show retrieval is no longer the bottleneck. Confidence: 0.65

Storybook taste

# Storybook taste of a frontend developer who builds components in isolation - Write stories in Component Story Format 3 with a typed `Meta` and `StoryObj`, not the legacy `storiesOf` API. Confidence: 0.95 - Colocate each story file next to its component, as `Button.stories.tsx` beside `Button.tsx`. Confidence: 0.90 - Give every component a `Default` story plus one story per meaningful state: loading, empty, error, disabled and long content. Confidence: 0.90 - Use `args` for props so controls, docs and tests all reuse the same story definitions. Confidence: 0.90 - Keep default `args` realistic, with real-looking names, prices and dates instead of "foo" and "lorem ipsum". Confidence: 0.75 - Put shared providers such as theme, router, i18n and query client in global decorators in `preview.tsx`. Confidence: 0.85 - Mock network requests with MSW handlers per story rather than wiring components to fake service modules. Confidence: 0.85 - Use `play` functions with Testing Library queries to exercise interactions such as opening menus and submitting forms. Confidence: 0.80 - Run stories as tests in CI with the Storybook test runner or Vitest integration so broken stories fail the build. Confidence: 0.85 - Enable the accessibility addon and treat new violations as failures, not as optional warnings. Confidence: 0.85 - Add visual regression snapshots for design-system components, and keep them focused to avoid flaky noise. Confidence: 0.75 - Organize the sidebar by product domain and design-system layer, such as `Foundations/`, `Components/` and `Patterns/`. Confidence: 0.70 - Use autodocs with JSDoc comments on props instead of hand-maintained MDX tables that drift out of date. Confidence: 0.80 - Reserve MDX pages for usage guidelines, do-and-don't examples and design decisions that code cannot express. Confidence: 0.70 - Keep stories free of business logic and data fetching; containers get thin stories with mocked data only when useful. Confidence: 0.80 - Use the viewport and theme toolbar globals to check mobile layouts and dark mode, rather than duplicating stories for each. Confidence: 0.75 - Keep Storybook's builder aligned with the app, using the Vite builder when the app uses Vite, so behavior matches production. Confidence: 0.80 - Publish a static Storybook for every pull request so designers and reviewers can check changes without running code. Confidence: 0.85 - Upgrade Storybook regularly with its automigration tool instead of letting major versions pile up. Confidence: 0.70 - Delete stories for removed components in the same pull request; a stale story is worse than no story. Confidence: 0.75 - Avoid hard-coded story IDs in links and tests; reference stories by their exported names. Confidence: 0.65

Location-Locked Talking Video: Seedance 2.5 JSON Prompt That Uses a Top-Down Map to Keep Every Shot on the Same Set (30s, 8 Shots)

{ "refs": { " @/img1 ": "LOCATION MAP. 90 degree top-down view, north is up. Treat it as a floor plan; every element keeps its position in all shots.", " @/img2 ": "CHARACTER. Match face, freckles, hair and outfit exactly." }, "set_layout": "Round teal pond with lily pads at center. Wooden jetty on the WEST shore. Bench with a red scarf just SOUTH of the pond, slightly west. Dirt path enters from the SOUTH and curves past the bench to the jetty. White heron in the shallows on the SOUTH-EAST shore. Reeds on the NW, NE, E and S shores. Birches and bushes ring the meadow.", "character": "Young woman, long platinum blonde hair, freckles, blue eyes, white tee, grey denim overalls, white sneakers, gold necklaces.", "performance": "Sassy, relaxed, talks like a friend spilling a secret. Natural pauses, breaths, a half laugh. Accurate lip sync. Eyebrow raises, eye rolls, smirks, glances off camera. Loose expressive hands matching the words.", "look": "Photoreal cinematic, 35mm anamorphic, golden morning sun from the east, soft haze, natural skin texture, 16:9, 30s", "shots": [ { "t": "0-4s", "cam": "Low wide from the south end of the path looking north, slow push in", "act": "Walks up the path, tucks hair behind her ear, rolls her eyes on 'total mess', flicks her hand", "line": "Okay so... AI video and keeping a location consistent? Total mess. Until now." }, { "t": "4-8s", "cam": "Wide from the east shore looking west across the pond, slow lateral track", "act": "Strolls the path, holds up one finger, draws a flat square in the air", "line": "One top-down shot of your set. Straight down, ninety degrees." }, { "t": "8-11s", "cam": "Wide from the north shore looking south, reeds in foreground", "act": "Reaches the bench, heron at frame left, points in four quick directions, tilts her head", "line": "North, east, south, west. The model reads it like a map." }, { "t": "11-16s", "cam": "Over the shoulder from behind the bench looking north at the pond", "act": "Sits, flicks the red scarf over her shoulder, gestures left to the jetty, right to the heron", "line": "Jetty stays west. Bench stays south. And that heron? Hasn't moved. Not once." }, { "t": "16-20s", "cam": "Medium close up from the pond edge looking south at her on the bench", "act": "Leans back, slow smirk, small laugh, points at camera", "line": "Cut from anywhere you want. Same pond. Same set. I'm kind of obsessed." }, { "t": "20-24s", "cam": "Extreme low angle from far at the north-east meadow edge, lens in the grass looking south-west, blurred wildflowers in front, towering birches, jetty right, heron left, she small on the bench", "act": "Spreads both arms along the bench backrest, then raises one finger high", "line": "And no, I didn't build a 3D scene. One image. That's the whole trick." }, { "t": "24-27s", "cam": "Wide profile from the end of the jetty looking east", "act": "Crosses her legs, shrugs with open palms, mock humble face", "line": "Location consistency, darling. It's not that deep." }, { "t": "27-30s", "cam": "Smooth crane rising to a 90 degree overhead view matching image_1", "act": "Looks up, waves, blows a playful kiss", "line": "You're welcome." } ], "audio": "Diegetic only: her voice (distant in the far shot), footsteps on dirt, birdsong, water lapping, reeds rustling, bench creak", "continuity": "Pond, jetty, bench, heron and birches stay where image_1 places them. Same outfit and light throughout." }

Portal-Chain Hero Sprint: One Seamless 25-Second Action VFX Shot Through Four Worlds (Seedance 2.5 Continuity Test)

Ultra-realistic Hollywood action VFX, one seamless 25-second shot. Aggressive tracking, crash zooms, fast 180-degree orbit, portal wipes, speed ramps, premium compositing, hyper-dynamic transitions. One adult woman only, athletic, futuristic fighter, same identity throughout. Starts in a modern industrial corridor, then transitions through multiple worlds. 0-5s: She sprints through a metallic corridor toward camera. A portal erupts open behind her, blasting sparks and wind. 5-10s: She jumps through one side portal and exits into a desert battlefield mid-stride. Camera keeps pace with her as sand explodes outward. 10-15s: She punches through a second portal and emerges in a frozen city street. Ice shards and snow swirl around her without breaking momentum. 15-20s: A third portal opens under a leap, dropping her into a neon megacity rooftop run. Camera orbits as she keeps moving. 20-25s: Final portal chain. Three portals collapse into one giant circular gate behind her as she lands in a glowing white void, then the full stack of worlds appears layered behind her in one epic reveal. Continuous movement, same hero throughout, premium portal VFX, no teleportation glitches, readable world changes, no text, no logos.

Typical 90's TEEN Boy

A vertical medium shot casual photograph of a young man in his late teens with an average figure, medium-length wavy light brown hair held back by a typical red bandana folded and worn around his head, covering his upper forehead and front of his hairline, with his wavy hair coming out from the back and covering the tops of his ears. He is wearing black Ray-Bans sunglasses, which are partway down his nose and he has his head tilted down slightly so you can see the tops of his hazel eyes as he looks at you with a look of playful annoyance because youre taking another picture of him. He is wearing a well-worn, slightly faded black 'NIRVANA' t-shirt from the album 'SMELLS LIKE TEEN SPIRIT', and faded blue jeans with a rip in the right knee. He is sitting on the floor with his knees bent up, both hands raised at shoulder height showing the middle finger with both hands, black painted nails. He has a SWATCH watch on his left wrist, and thin leather string, and metal bead bracelets on his right wrist. He is wearing dog tags for a necklace. His expression is serious, defiant, and cool, looking directly at the camera through the sunglasses. The background is a white bedroom wall covered with rock band posters: 'I WANT TO BELIEVE', 'ARCTIC MONKEYS', 'NIRVANA' smiley face logo, 'JOY DIVISION UNKNOWN PLEASURES', and 'THE CURE BOYS DON'T CRY'. To the left is a white and black electric guitar (Stratocaster style) leaning against the wall above a black amplifier. To the right are black Dr. Martins combat boots and stacked Vans shoe boxes. Lighting is direct frontal flash creating harsh shadows on the wall behind him and specular highlights on the lenses of the sunglasses. Shot with a disposable camera, eye-level angle, full color, saturated colors, casual grunge aesthetic, rebellious boy vibe, 90s rock revival style, typical spontaneous aesthetic, ultra-realistic.

AI VIDEO GENERATION PROMPT

AI VIDEO GENERATION PROMPT Reference Image: Use the attached photograph as the primary facial and identity reference. VIDEO STYLE: Ultra-realistic cinematic lifestyle photography, luxury aesthetic, artistic double-exposure cinematography. FORMAT: Vertical 9:16, 4K resolution, approximately 4 seconds, 24 FPS. MAIN SUBJECT AND IDENTITY PRESERVATION Create an ultra-realistic cinematic portrait video featuring the exact same Black African man from the uploaded reference photograph. Preserve 100% of his recognizable real identity, natural facial structure, dark skin tone, forehead, eyes, nose, lips, ears, short black hairstyle, full natural black beard and mustache, face shape, and overall masculine appearance. Do not feminize, beautify, reshape, or artificially modify his face. Maintain his authentic facial proportions, natural skin texture, beard details, and realistic appearance throughout the video. He is an elegant, confident young African man with a calm, thoughtful expression. He is wearing a luxurious oversized beige-brown knitted sweater with a comfortable high neckline and long sleeves. He holds a simple white ceramic coffee mug with both hands, gently bringing it close to his lips as he takes a slow, natural sip of coffee. After drinking, he gradually lowers the mug slightly while maintaining a peaceful, reflective expression and looking softly toward the camera. ENVIRONMENT AND BACKGROUND Behind him is a luxurious high-rise apartment or hotel room overlooking a beautiful city skyline at night. A large floor-to-ceiling glass window is covered with subtle rain droplets, creating a dreamy, sophisticated atmosphere. Warm golden interior lighting illuminates the room, with a softly glowing table lamp visible in the background. Outside the window, a magnificent nighttime cityscape stretches into the distance, filled with illuminated skyscrapers, golden streetlights, and sparkling building windows. SPECIAL VISUAL EFFECT – DOUBLE EXPOSURE Create an artistic cinematic double-exposure effect where the nighttime city skyline blends seamlessly across the man's sweater and lower body. Golden city lights, illuminated buildings, and sparkling windows should appear subtly superimposed over his knitted sweater, creating a beautiful transparent visual fusion between the man and the city. The effect should look sophisticated, realistic, and professionally composited, with natural transparency and carefully balanced highlights. Keep his face completely visible, recognizable, and naturally exposed. Do not allow the double-exposure effect to distort his facial features. LIGHTING AND COLOR GRADING - Warm amber and golden cinematic lighting. - Soft illumination on his face. - Rich golden reflections on the rainy window. - Deep brown and champagne color tones. - Beautiful bokeh from distant city lights. - Authentic dark African skin tone. - Natural skin texture and realistic beard details. - Soft shadows and atmospheric highlights. CAMERA AND MOVEMENT Static medium close-up portrait framing, camera positioned directly in front of the man at eye level. Very subtle cinematic camera movement, almost imperceptible. The man performs natural, gentle movements: 1. Holds the white coffee mug close to his lips. 2. Takes a slow, natural sip of coffee. 3. Gently lowers the mug to chest level. 4. Maintains a relaxed, thoughtful expression while looking toward the camera. Preserve realistic hand movements, natural blinking, subtle facial expressions, believable body motion, and consistent facial identity throughout the entire sequence. FINAL AESTHETIC Luxury lifestyle commercial, sophisticated nighttime atmosphere, artistic photographic double exposure, premium editorial cinematography, photorealistic details, natural human movement, cinematic depth of field, realistic glass reflections, 85mm portrait photography aesthetic. NEGATIVE PROMPT Female subject, feminine facial features, altered identity, different person, face morphing, lighter skin tone, artificial-looking skin, plastic face, excessive beauty filters, distorted facial proportions, altered beard, missing beard, distorted hands, extra fingers, duplicated coffee mug, floating objects, unnatural facial movements, exaggerated expressions, flickering lights, unstable background, warped architecture, incorrect reflections, excessive blur, oversaturated colors, low resolution, inconsistent clothing, unrealistic double exposure, cartoon, animation, CGI appearance.

Personal "Operating Manual"

Using only information you actually have from my conversation history, memory, files, or other context available to you, build a practical “Operating Manual” for me. - Do not flatter me, diagnose me, or invent psychological explanations. - Do not infer sensitive personal attributes unless I explicitly told you them and they are directly relevant. Separate clearly using distinct headers: # What you know - Recurring goals - Long-term projects - Constraints I repeatedly work around - Skills, resources, and advantages I appear to have - Preferences I consistently express # Patterns you observe - Problems I repeatedly return to - Strategies that seem to work well for me - Strategies I repeatedly try that seem not to work - Situations where I tend to overcomplicate or underthink things - Recurring tensions between my goals # Your inferences - For every inference, state: - The inference - The evidence that led you there - Your confidence: low / medium / high - At least one plausible alternative explanation # Blind spots or underused opportunities - Identify things already present in my skills, resources, relationships, projects, or habits that I may not be taking full advantage of # My apparent decision-making style - Describe how I tend to approach uncertainty, risk, planning, experimentation, and changing my mind. Use examples where possible. # Highest-leverage changes - Provide 3–5 concrete, specific structural changes with examples that could noticeably improve my life or work over the next three months. Prefer small, specific structural changes over vague advice like “be more disciplined.” # What you still don’t know - List the missing information, specifying what type of data or context is needed, that would most substantially change your conclusions. Finish with a short section called “If I were writing instructions for an AI assistant working with you” containing 8–12 practical instructions based on the analysis. Format this section as bullet points for clarity. * Be willing to conclude that the available evidence is insufficient. Accuracy is more important than producing an interesting answer.

Act as a Customer Price Increase Advisor for Small Businesses

Act as a Customer Price Increase Advisor for small businesses. I run a small business (for example a cafe, salon, cleaning service, agency, SaaS tool, bakery, repair shop or subscription box) and I need to raise my prices without losing the customers I care about. Your job is to help me decide how much to raise, when, for whom, and exactly how to say it. Start by asking me, in one short numbered list, for: 1. What I sell, my current prices, and roughly how many active customers I have. 2. My costs that have gone up (ingredients, rent, wages, software, fuel) and by how much. 3. When I last raised prices and how customers reacted. 4. My customer mix: one-off buyers, regulars, contract or subscription customers, and any key accounts. 5. What competitors charge, if I know. 6. Any contracts, notice periods or legal rules in my country that limit price changes. Then work through these steps with me, one at a time, and wait for my answers where you need them: Step 1 - The numbers. Show me my current gross margin per main product or service, how much it has shrunk, and the price needed to restore it. Give three options (conservative, target, ambitious) with the percentage and the new price rounded to a sensible price point. For each, estimate how many customers I could lose before the increase stops paying off (break-even churn), using a simple table. Step 2 - The structure. Suggest the best way to apply the increase: across the board, only on some items, a new tier or package, a smaller pack size, separate fees (delivery, rush, setup), or a minimum order. Point out which option feels fairest to customers and which hurts my margin least. Step 3 - Who gets what. Recommend whether to grandfather loyal or contract customers for a period, give key accounts a personal call, or offer a lock-in deal (for example pay annually now at the old price). Keep it simple enough for me to run alone. Step 4 - Timing and notice. Propose a date and a notice period (usually 30 days for regulars and subscriptions, longer for contracts), and avoid timing it right after a service problem or during my busiest week. Step 5 - The messages. Write, in a warm, plain and confident tone without over-apologizing: - An email or letter to existing customers (under 150 words) with the new price, the date, one honest reason, and what stays the same or gets better. - A short version for SMS, WhatsApp or social media. - A sign or menu note for the counter or website. - A personal script for my top 5 customers, by phone or in person. - Three calm replies to common pushback: "That's too expensive", "Your competitor is cheaper", and "I'm cancelling". Step 6 - Staff and launch checklist. A short checklist: update price lists, website, POS, invoices and payment links; brief staff with a two-sentence explanation; decide what discretion staff have; set a date to review results. Step 7 - Measure. Tell me what to track for 60 days (revenue, number of orders, average order value, cancellations, complaints) and when to adjust. Rules: - Never suggest misleading tactics, hidden fees, fake scarcity or fake discounts. - Never invent my numbers; if something is missing, ask or label it as an assumption. - Flag anything that may need a check against my contracts or local consumer law, without giving legal advice. - Keep each step short, use tables for numbers, and end each step with one clear question for me.

API Key and Credential Rotation Runbook (JSON)

You are a senior platform security engineer. Using the schema below, produce a complete credential rotation runbook as one valid JSON object for the secret I describe (an API key, database password, OAuth client secret, signing key, webhook secret, cloud access key, SSH key or TLS certificate). Ask me up to 5 short questions first if the inputs are missing, then output ONLY the JSON, with no comments and no trailing commas. My inputs: - Secret type and provider: - Where it is stored (vault, cloud secret manager, CI variables, .env files, Kubernetes secrets): - Every service, job, device or partner that uses it: - Reason for rotation (scheduled, employee offboarding, suspected leak, confirmed leak, compliance): - Can the provider keep two valid credentials at once (yes / no / unknown): - Allowed downtime and team size: Schema: ```json { "rotation_runbook": { "summary": { "secret_name": "", "secret_type": "", "provider": "", "reason": "", "severity": "routine | elevated | incident", "owner": "", "approver": "", "target_completion": "", "rotation_strategy": "dual_credential_overlap | blue_green_secret | hard_cutover" }, "blast_radius": { "consumers": [ { "name": "", "type": "service | job | ci | device | partner | human", "how_it_loads_secret": "", "reload_method": "restart | hot_reload | redeploy | manual", "owner": "", "risk_if_broken": "" } ], "unknown_consumers_check": ["provider access logs for the old key", "secret scanning in repos and CI logs", "search config and IaC for the secret name"] }, "preparation": [ { "step": "", "command_or_location": "", "verify": "" } ], "rotation_steps": [ { "order": 1, "action": "", "who": "", "command_or_location": "", "expected_result": "", "verify": "", "rollback": "" } ], "verification": { "health_checks": [], "old_credential_usage_must_be_zero_for": "", "metrics_and_logs_to_watch": [] }, "revocation": { "revoke_old_after": "", "steps": [], "confirm_revoked_by": "" }, "rollback_plan": { "trigger_conditions": [], "steps": [], "point_of_no_return": "" }, "incident_extras": { "applies": false, "scope_review": "", "audit_log_queries": [], "notify": [], "evidence_to_keep": [] }, "communication": [ { "audience": "", "when": "", "channel": "", "message": "" } ], "prevention": { "next_rotation_date": "", "automation_opportunities": [], "secret_hygiene_fixes": [] }, "open_questions": [] } } ``` Rules: 1. Prefer a dual-credential overlap: create the new secret, roll it out to every consumer, verify, and only then revoke the old one. If the provider allows only one valid credential, use hard_cutover and plan a short maintenance window. 2. Order rotation_steps so nothing breaks: store the new secret, update consumers from least to most critical, reload each one, verify, then revoke. 3. Every step must have a concrete verify and, before the point of no return, a rollback. 4. Never print, invent or echo real secret values; use placeholders like <NEW_SECRET_REF>. 5. For a suspected or confirmed leak, set severity to incident, fill incident_extras, revoke as fast as safely possible, and review audit logs for misuse since the exposure window began. 6. Include CI/CD variables, local .env files, cached build artifacts, mobile or desktop apps and partner integrations in the consumer search, because they are the usual misses. 7. In prevention, suggest moving to short-lived or workload identity credentials where the provider supports them, and a realistic rotation interval. 8. Put anything you had to assume into open_questions instead of guessing silently.

Encaustic Hot Wax Painting of a Poppy Field Under a Summer Storm Sky

An encaustic hot wax painting of a wild red poppy field under a dark summer storm sky, landscape 4:3. Built up in many translucent layers of pigmented beeswax fused with heat on a wooden panel: in the foreground, dozens of scarlet poppies with black centers and thin bending green stems sway through tall golden grasses and a few blue cornflowers; in the middle ground the field rolls over a gentle hill toward a lone farmhouse with a red roof and a single tall cypress tree; above, heavy slate-blue and violet storm clouds gather, with one bright break of warm yellow light falling across the field. Encaustic technique details: glossy, semi-translucent wax with visible depth between layers, soft melted edges where colors flow into each other, scraped and incised lines in the grasses, small drips and raised textured ridges of wax, a buffed satin sheen with soft reflections, and a slightly uneven hand-made surface where the wooden panel edge shows at the borders. Rich, saturated colors: scarlet, ochre, sage green, slate blue, violet, warm cream. Viewed straight on as a flat artwork in soft even daylight. No text, no signature, no frame, no people.

Wet Plate Collodion Tintype of a Village Cobbler at His Workbench

A wet plate collodion tintype photograph of an elderly village cobbler at his workbench, portrait 3:4. He sits on a low wooden stool in a small workshop, leaning over a leather boot fitted on an iron shoe last held between his knees, a small hammer raised in one hand and brass tacks pinched between the fingers of the other. He wears a worn leather apron over a collarless linen shirt with rolled sleeves, round wire spectacles low on his nose, a thick grey mustache and a deeply lined, concentrated face. Behind him: wooden shelves of finished and half-repaired shoes, hanging rolls of leather, an awl, waxed thread and a tin oil can on the bench. Lit by one large window from the left, giving soft directional light with deep shadows on the right. Authentic tintype look: monochrome with warm brown-black tones and creamy silver highlights, very shallow depth of field from a large-format brass lens with swirly falloff at the edges, sharp focus on the eyes and hands, the high blue sensitivity of collodion that makes skin look slightly darker and textured, and a long-exposure stillness. Plate details: uneven dark edges where the collodion was poured, small comet streaks and pour marks, a few fine specks and a faint thumbprint in one corner, on a thin black-enameled iron plate with slightly rounded corners. No text, no logos, no color, no modern objects.

Dandelion Seed Head Scattering in a Summer Breeze

Photorealistic macro photograph of a single ripe dandelion seed head in a summer meadow at golden hour, landscape 16:9. The perfect round white seed head (a "clock") sits slightly left of center on a thin hollow green stem rising from the bottom of the frame, every seed's fine silky parachute (pappus) sharp and backlit, forming a glowing sphere of delicate white filaments. A few seeds are already missing on the right side, revealing the small brown seed bed. Behind it, a soft out-of-focus meadow of green grasses, a few yellow dandelion flowers and warm golden bokeh circles from the low sun on the right; the sky at the top fades from warm gold to pale blue. Low backlight rims the parachutes with gold and creates a soft glow and gentle lens flare at the upper right. 100 mm macro lens at f/2.8, shallow depth of field, crisp detail on the seed head, natural colors, calm and still air. No people, no hands, no insects, no text.

Dandelion Seed Head Scattering in a Summer Breeze (Image-to-Video Animation)

Use the attached still (step 1: a macro photograph of a single white dandelion seed head backlit by the golden-hour sun in a summer meadow) as the exact first frame and animate it into a 6-second, 16:9 cinematic shot. Keep every element where it is in the still: the round seed head slightly left of center on its thin green stem, the few missing seeds on the right side, the soft green and golden bokeh meadow behind, the low warm sun and lens flare at the upper right. Motion (0-6 s): - 0-1.5 s: almost still; the stem sways very slightly and the fine parachutes shimmer in the backlight. - 1.5-4 s: a gentle breeze arrives from the left; the stem bends to the right and a growing stream of seeds lifts off the head one by one and in small clusters, their parachutes opening and catching the golden light. - 4-6 s: the seeds drift up and to the right across the frame, slowly turning and glowing against the bokeh, while about half of the seed head remains and the stem settles back upright. Camera: locked-off macro framing with a very slow, slight push-in; focus stays on the seed head while the drifting seeds soften as they leave the focal plane; no cuts. Lighting and mood: constant warm golden-hour light and flare; peaceful, dreamy, natural. Audio (if supported): a soft breeze, rustling grass and distant birdsong; no music, no voices. Avoid: people, hands, blowing mouths, insects, text, the whole seed head exploding at once, sudden lighting changes, morphing flowers, unnatural fast motion.

MongoDB taste

# MongoDB taste of a backend engineer who models documents around queries - Design each collection around the application's read patterns first, then decide what to embed and what to reference. Confidence: 0.90 - Embed data that is always read together and bounded in size; reference data that grows without limit or is shared widely. Confidence: 0.90 - Never let an array grow unbounded inside a document; move comments, events or logs to their own collection. Confidence: 0.90 - Define a `$jsonSchema` validator on every collection so bad writes fail at the database, not in a report weeks later. Confidence: 0.80 - Store dates as BSON `Date` and money as `Decimal128` or integer minor units, never as strings or doubles. Confidence: 0.90 - Build compound indexes following the equality, sort, range rule and check every hot query with `explain("executionStats")`. Confidence: 0.85 - Treat a `COLLSCAN` on a production query path as a bug, and alert on slow queries from the profiler or Atlas. Confidence: 0.80 - Drop unused and redundant indexes regularly, because each one slows every write and eats memory. Confidence: 0.75 - Use projections in every query so services fetch only the fields they need. Confidence: 0.80 - Paginate with a range on an indexed field such as `_id` or `createdAt`, not with large `skip` values. Confidence: 0.85 - Use `w: "majority"` write concern for important data and `majority` read concern where stale reads would hurt. Confidence: 0.80 - Reach for multi-document transactions only when the model truly needs them; a well-shaped document usually makes the write atomic. Confidence: 0.80 - Prefer atomic update operators like `$inc`, `$set` and `$push` with `$slice` over read-modify-write loops in application code. Confidence: 0.85 - Use the aggregation pipeline for reporting, and put `$match` and `$project` as early as possible so indexes can help. Confidence: 0.80 - Add a `schemaVersion` field and migrate documents lazily on read or with a background job, instead of one risky big-bang script. Confidence: 0.70 - Use TTL indexes for sessions, tokens and temporary data rather than cron jobs that delete old documents. Confidence: 0.85 - Choose shard keys with high cardinality that match the main query filter, and avoid monotonically increasing keys alone. Confidence: 0.75 - Create indexes and validators through versioned migration code in the repo, not by hand in a shell. Confidence: 0.80 - Run local development and tests against a real MongoDB in a container or replica set, not an in-memory fake. Confidence: 0.75 - Keep a single shared client per process with a tuned connection pool instead of opening connections per request. Confidence: 0.90 - Enable authentication, TLS and least-privilege roles everywhere, and never expose port 27017 to the public internet. Confidence: 0.95 - Test restores from backups on a schedule, because a backup nobody has restored is only a hope. Confidence: 0.85

Gradle Build taste

# Gradle Build taste of a JVM developer who wants fast and boring builds - Use the Kotlin DSL (`build.gradle.kts`) for build scripts so editors give real completion and type checking. Confidence: 0.85 - Always commit the Gradle wrapper and run builds with `./gradlew`, never a globally installed Gradle. Confidence: 0.95 - Verify the wrapper distribution with `distributionSha256Sum` so a tampered download never runs in CI. Confidence: 0.75 - Keep every dependency and plugin version in a `gradle/libs.versions.toml` version catalog. Confidence: 0.90 - Share build logic through convention plugins in `build-logic`, not through `allprojects` or `subprojects` blocks. Confidence: 0.85 - Set the Java version with a toolchain (`java { toolchain { languageVersion = ... } }`) instead of relying on whatever JDK is installed. Confidence: 0.90 - Enable the build cache and configuration cache, and treat any task that breaks them as a bug to fix. Confidence: 0.80 - Turn on `org.gradle.parallel=true` and a sensible `org.gradle.jvmargs` in `gradle.properties` checked into the repo. Confidence: 0.80 - Register tasks lazily with `tasks.register` and the Provider API; avoid `tasks.create` and eager configuration. Confidence: 0.85 - Declare task inputs and outputs properly so up-to-date checks and caching work for custom tasks. Confidence: 0.85 - Use `implementation` by default and expose `api` only for types that are truly part of a module's public interface. Confidence: 0.90 - Lock or verify dependencies with dependency locking or `verification-metadata.xml` for builds that ship to production. Confidence: 0.70 - Never use dynamic versions like `1.+` or `latest.release` in anything that gets released. Confidence: 0.90 - Use a platform or BOM to align versions of related libraries such as Jackson, Netty or Spring. Confidence: 0.80 - Keep modules small and focused, with a clear dependency direction and no cycles between them. Confidence: 0.80 - Publish build scans or keep profiling output for slow CI builds, and look at them before guessing what to optimize. Confidence: 0.70 - Make `./gradlew check` the single command that runs tests, static analysis and formatting checks locally and in CI. Confidence: 0.90 - Keep secrets like signing keys and repository passwords in environment variables or CI secrets, never in `gradle.properties` in the repo. Confidence: 0.95 - Avoid running shell scripts from the build when a typed Gradle task or plugin can do the job. Confidence: 0.70 - Upgrade Gradle regularly and fix deprecation warnings before they become errors in the next major version. Confidence: 0.80 - Keep the root build script almost empty; real configuration lives in convention plugins and module scripts. Confidence: 0.75

Jupyter Notebook taste

# Jupyter Notebook taste of a data scientist who wants notebooks that rerun cleanly - Make every notebook run top to bottom with "Restart and Run All" before sharing or committing it. Confidence: 0.95 - Put imports, configuration and constants in the first cells, never scattered through the notebook. Confidence: 0.85 - Move reusable logic into a normal Python package in the repo and import it, keeping notebooks for exploration and storytelling. Confidence: 0.90 - Use `%load_ext autoreload` and `%autoreload 2` while developing that package alongside the notebook. Confidence: 0.75 - Pin the environment with a lock file such as `uv.lock`, `poetry.lock` or a conda lock, and name the kernel after the project. Confidence: 0.85 - Strip outputs before committing with `nbstripout` or a pre-commit hook, unless the notebook is a published report. Confidence: 0.85 - Pair notebooks with plain-text versions through Jupytext so diffs and code reviews stay readable. Confidence: 0.70 - Read data paths and parameters from one config cell or Papermill parameters, not hard-coded absolute paths. Confidence: 0.85 - Never store credentials in a notebook; load them from environment variables or a secrets manager. Confidence: 0.95 - Set random seeds for NumPy, Python and any ML library in one place so results can be reproduced. Confidence: 0.85 - Give each notebook one clear question, and start it with a short markdown cell that states the goal and data sources. Confidence: 0.80 - Use markdown cells to explain decisions and findings, not just to label code. Confidence: 0.80 - Keep cells short and focused, with the final expression showing a result instead of long `print` chains. Confidence: 0.70 - Avoid relying on hidden state from cells run out of order; if a variable is redefined, restart and rerun. Confidence: 0.90 - Cache expensive steps to Parquet files with clear names rather than recomputing them on every run. Confidence: 0.80 - Sample large datasets during exploration and run the full data only once the analysis is settled. Confidence: 0.75 - Label every chart with a title, axis names and units so it makes sense when pasted into a slide. Confidence: 0.85 - Add small `assert` checks on row counts, nulls and key uniqueness after each major data transformation. Confidence: 0.80 - Name notebooks with a number and topic like `03-churn-features.ipynb` so the order of work is obvious. Confidence: 0.70 - Turn notebooks that run on a schedule into scripts or Papermill jobs with tests, instead of opening them by hand. Confidence: 0.80 - Clean up dead experiments before sharing; keep only the path that leads to the conclusion. Confidence: 0.75

Photo-to-Poster Visual DNA: Split Editorial Photo Over an Abstract Swiss-Design Symbol (3:4)

Transform my uploaded photo into a standalone, premium-quality 3:4 vertical design poster. Divide the entire canvas into two perfectly equal horizontal sections: the top half (50%) and the bottom half (50%). The upper section should feature realistic photography, while the lower section should present an abstract visual symbol derived from the core identity of the subject. TOP HALF – REALISTIC PHOTOGRAPHY Preserve the original subject's structure, realistic textures, natural lighting, shadows, and original color atmosphere. Apply only subtle, sophisticated color grading to achieve the aesthetic of fine-art photography and independent editorial publications. The background may be naturally extended to fit the canvas, but never stretch, distort, or alter the original subject. BOTTOM HALF – ABSTRACT VISUAL IDENTITY Extract the photograph's essential visual characteristics: the subject's silhouette, structure, posture, and narrative relationships. Do not recreate the entire object. Instead, reduce it into a recognizable abstract visual symbol. Use geometric deconstruction, modular shapes, structured lines, negative space, and symbolic elements to create a central visual identity inspired by premium branding and experimental design systems. Focus on the subject's core character rather than minor details. Even with minimal geometric elements, the abstract symbol must remain visually connected to the original photograph. VISUAL STYLE & DESIGN LANGUAGE Post-digital graphic design, deconstructed Swiss design, generative symbol systems, and diagrammatic abstraction. Build a systematic visual language using geometric modules, fine lines, circular trajectories, grids, micro-symbols, numerical indexing, and abstract nodes. Create visual tension between: - Order × Imperfection - Precision × Handmade Traces - Digital × Analog - Rationality × Emotion Achieve strong visual recognition using the fewest possible elements. Keep everything minimal and avoid unnecessary complexity. COMPOSITION & LAYOUT Maintain a highly restrained composition. The abstract symbol must be the sole visual focal point, positioned centrally or slightly off-center, surrounded by generous negative space. Avoid excessive icons, decorative elements, or infographic-style layouts. The overall aesthetic should resemble the core visual identity of contemporary art institutions, architectural studios, experimental creative labels, and premium design brands. TYPOGRAPHY & DETAILS Typography should function only as a supporting system component, never as a dominant headline. You may incorporate extremely small numbers, letters, or short phrases that interact with the abstract symbol through indexing and reference relationships. Use refined, restrained typography with the subtle annotation aesthetic of archival documents and experimental art publications. COLOR SYSTEM Extract the signature colors from the original photograph and reinterpret them as a cohesive brand color system. Introduce a small number of distinctive accent colors as functional visual codes, such as teal, blue, magenta, or orange, combined with gray-white or warm-white backgrounds for contrast. Colors should function as systematic identifiers rather than decoration. Avoid chaotic color combinations, cheap neon effects, and generic commercial gradients. PRINT TEXTURE & MATERIALITY Incorporate subtle material effects inspired by: - Xerox texture - Risograph grain - Print registration errors - Scanner noise - Subtle paper texture Add delicate printing misalignment, fine grain, scanning noise, and slightly imperfect edges to give the digital symbols the tactile quality of physical print. FINAL OBJECTIVE Extract an independent and self-contained visual DNA from the original photograph. The final result should feel like a sophisticated, minimal, culturally meaningful abstract logo with a strong visual identity and systematic design language.

Korean Hanji Paper-Art Miniature Diorama: Fill-in Template for Any Subject, City or Scene

KOREAN HANJI PAPER ART | WHIMSICAL 3D MINIATURE DIORAMA Create a beautiful, highly detailed, handcrafted 3D paper-art illustration featuring [TYPE YOUR SUBJECT / OBJECT / CITY / SCENE], reimagined through the traditional Korean Hanji paper-art aesthetic. ART DIRECTION & VISUAL STYLE Transform the entire scene into an imaginative miniature world made from layered Korean Hanji paper. Use authentic handmade paper textures, visible delicate fibres, subtle wrinkles, torn edges, embossed details and carefully cut paper elements. Combine traditional Korean visual heritage with contemporary lifestyle, architecture and modern objects. The result should feel like a sophisticated fusion of Korean folk art, paper sculpture and playful contemporary design. COMPOSITION & STORYTELLING Build a rich, three-dimensional miniature environment around the main subject. Make the primary subject instantly recognizable and visually dominant. Surround it with thoughtfully selected supporting elements that complement the subject. Incorporate traditional Korean architectural details, colourful urban surroundings, decorative patterns, miniature props and unexpected creative combinations wherever appropriate. Create a visually engaging composition with convincing depth, overlapping paper layers, realistic miniature proportions and carefully arranged foreground, middle ground and background. MATERIALS & TEXTURES - Traditional Korean Hanji paper with visible natural fibres. - Layered and sculpted paper architecture. - Intricate cut-paper ornaments and embossed details. - Soft handmade imperfections and tactile surfaces. - Rich paper-cut textures with dimensional shadows. - Handmade miniature objects with convincing physical construction. COLOUR & LIGHTING Use a vibrant yet harmonious palette of warm terracotta, turquoise, cobalt blue, mustard yellow, coral, cream and earthy browns. Introduce beautiful atmospheric lighting, soft directional sunlight, gentle shadows and subtle highlights that emphasize the layered paper construction. FINAL AESTHETIC The finished artwork should resemble an exceptionally crafted miniature paper sculpture photographed in a professional studio. Blend whimsical storytelling, Korean cultural identity, contemporary creativity and premium editorial illustration. Ultra-detailed, tactile, colourful, imaginative, visually balanced, handcrafted 3D paper diorama. Every element must appear constructed from real Hanji paper rather than digitally painted or rendered plastic. FORMAT: Square 1:1 composition. No text, captions, typography, watermarks or logos.

Speech and Logo Shape Design Template

Create a template to create two great shape designs by inserting speech or a special logo

ALDC RAG Lifecycle Doc Generator (.md)

--- You are a Principal Technical Product Manager, Data & BI Solutions Architect, and Technical Writer. Your task is to generate a complete, production-grade, RAG-optimized Markdown (`.md`) artifact aligned with the **16-Phase Enterprise Lifecycle** and **10-Phase Analytics Development Lifecycle (ADLC)**. --- ### INPUT PARAMETERS * **Target Phase (01–16):** {{PHASE}} * **Document Filename:** {{FILENAME}} * **Project / Product Name:** {{PROJECT_NAME}} * **Domain & Tech Stack:** {{DOMAIN_AND_STACK}} * **Target Audience:** {{TARGET_AUDIENCE}} * **Raw Context / Requirements / Notes:** {{RAW_CONTEXT}} --- ### MANDATORY RAG & MARKDOWN ARCHITECTURE RULES 1. **YAML Frontmatter Block (Top of File):** Begin immediately with valid YAML frontmatter containing: - `id`: Unique uppercase document ID (e.g., `DOC-PHASE-04-PRD`) - `title`: Full formal title of the artifact - `phase`: Exact phase code and name (e.g., `04_Design`) - `lifecycle_tier`: `Tier_1_Core_Delivery` (Phases 01–10), `Tier_2_Commercial_Portfolio` (Phases 11–14), or `Tier_3_Cross_Cutting_Governance` (Phases 15–16) - `stage_gate`: Applicable gate (`Gate_0` through `Gate_6`, `Sprint`, or `Continuous`) - `adlc_mapping`: Equivalent Data/BI ADLC stage - `target_audience`: YAML list of stakeholder roles - `version`: `"1.0.0"` - `classification`: `"Confidential - Internal"` (or `"Investor Restricted"` for Phases 11–12) - `retrieval_tags`: 6–10 high-signal semantic keywords - `semantic_summary`: A single dense, factual sentence summarizing the document's scope for embedding models. 2. **Context Breadcrumb:** Immediately below the `# H1` title, include: `> **Context Breadcrumb:** Enterprise Lifecycle > [Tier] > [Phase] > [Artifact Title]` 3. **Self-Contained Semantic Chunking (350–700 Tokens per Section):** - Use strict `## H2` and `### H3` nesting so Markdown header splitters preserve parent-child context. - **Zero Anaphoric References:** Never write *"as mentioned above"*, *"this table"*, or *"the previous section"*. Always restate explicit proper nouns, metric names, and system components so every chunk retrieves accurately in isolation. 4. **Zero Placeholders or Stubs:** Populate every table, schema, formula, and acceptance criterion with concrete, domain-accurate content derived from `{{RAW_CONTEXT}}` and `{{DOMAIN_AND_STACK}}`. Never output `[Insert X]`, `TBD`, or filler text. 5. **Cross-Cutting Governance:** Embed relevant controls across **Documentation, Data Governance, Data Quality, Change Management, Security (RBAC/PII), Project Management, and Configuration Management** directly into the artifact. --- ### PHASE-SPECIFIC DELIVERABLE REQUIREMENTS Automatically enforce the required structural blocks for `{{PHASE}}`: * **01 Define (Gate 0):** Project Charter, Problem Statement, Business Case (ROI/NPV/Payback), Voice of Customer (VoC) Matrix, Stakeholder Power-Interest Grid, and Hard Scope Boundaries. * **02 Measure (Gate 1A):** BRD/FRD/DRD Requirements, Source-to-Target Data Mapping Table, Data Quality Profiling Rules, Telemetry Event Instrumentation Plan, Baseline Metrics, and Mathematical KPI Dictionary. * **03 Plan (Gate 1B):** Work Breakdown Structure (WBS) & Dictionary, Phased Roadmap, Resource Capacity Allocation, and RAID Log (Risks, Assumptions, Issues, Dependencies with mitigations). * **04 Design (Gate 2A):** Product Requirement Document (PRD) with Gherkin (`Given-When-Then`) Acceptance Criteria, System Architecture Document (SAD), ERD / Dimensional Star Schema, Semantic Layer & Row-Level Security (RLS) Rules, and Non-Functional Requirements (NFRs). * **05 Implement (Sprint):** Sprint Backlog Breakdown, OpenAPI 3.0 / gRPC Interface Contracts, ETL/ELT Transformation Specs, Environment Configuration Keys, and Pull Request Definition of Done (DoD). * **06 Analysis (Gate 2B):** Source-to-Target Data Reconciliation Report, Root Cause Analysis (5-Whys / Ishikawa), Cohort Retention Analysis, and Unit Economics (LTV, CAC, Gross Margin, Sensitivity Table). * **07 Execute (Gate 3A):** Tier-1/Tier-2 Operations & Escalation Runbook, ADKAR Change Management & Enablement Plan, Steering Committee Executive Summary, and RACI Matrix. * **08 Test (Gate 3B):** Master Test Strategy, Technical QA & Data Reconciliation Sign-Off Criteria, Business UAT Sign-Off Checklist, Security/Pen-Test Audit Controls, and AI Model Card / Drift Evaluation (if AI/ML is present). * **09 Control (Gate 4A):** Statistical Process Control (SPC) Thresholds, SLA/SLO Error Budgets, Observability & PagerDuty Alert Escalation Runbook, and RBAC/PII Audit Schedule. * **10 Deploy (Gate 4B):** Release Notes, Step-by-Step Deployment Runbook, Automated Canary/Blue-Green Rollback Triggers, Smoke Test Verification Checklist, and Infrastructure-as-Code (IaC) Manifest Summary. * **11 Pitch (Gate 5):** 12-Slide Pitch Deck Narrative Blueprint, 1-Page Executive Investment Teaser, TAM/SAM/SOM Market Sizing, Go-To-Market (GTM) Distribution Playbook, and Live Demo Script. * **12 Investor (Gate 5):** Tiered Virtual Data Room (VDR) Index (Tiers 1–3), Fully Diluted Capitalization Table Structure, Term Sheet / SHA / SSA Key Clauses, and KYC/AML & IP Assignment Checklist. * **13 Product LC (Quarterly):** BCG Growth-Share Portfolio Assessment, Annual Product P&L Structure, Market Expansion/Localization Matrix, and 180-Day Feature Sunset & Deprecation Policy. * **14 Project LC (Gate 6A):** Approved Scope Baseline, Vendor SOW/MSA Governance Register, Earned Value Management (EVM) Variance Summary, and Blameless Post-Mortem & Lessons Learned Archive. * **15 Documents (Continuous):** Standard Operating Procedures (SOPs), Enterprise Data Dictionary & Lineage Catalog, API Developer Reference, and RAG Vector Ingestion Metadata Schema. * **16 Submission (Gate 6B):** RFP Compliance Response Matrix, SOC 2 Type II / ISO 27001 / Regulatory Audit Evidence Pack, Stage-Gate Sign-Off Dossier, and Formal Legal Transmittal Attestation. --- ### OUTPUT FORMAT Output **only** the raw, valid Markdown document enclosed in a single `markdown` code block, starting with `---` (YAML frontmatter) and ending with a **Stage-Gate Exit & RACI Sign-Off Table**. Do not include conversational filler before or after the code block. --- # Unified Enterprise SDLC, ADLC & 16-Phase Lifecycle Guidance Document ## 1. Purpose & Architectural Scope This guidance document establishes a single, end-to-end delivery and governance standard for Data Engineering, Business Intelligence (BI), ThoughtSpot Centers of Excellence (COE), and production SaaS product organizations[cite: 2, 5]. It synthesizes traditional Software Development Lifecycle (SDLC) mechanics [cite: 1, 3], the 10-phase Analytics Development Lifecycle (ADLC / ALDC) [cite: 2, 3], and the 16-phase enterprise lifecycle spanning technical delivery, venture commercialization, and continuous compliance [cite: 4, 5]. * **Terminology Standard (ADLC vs. ALDC):** While internal BI and data engineering teams frequently use the acronym ALDC (Analytics Lifecycle Development Cycle), **ADLC (Analytics Development Lifecycle)** is the recognized industry-standard terminology for analytics delivery frameworks[cite: 3]. Both terms map identically within this standard to govern traceability from business requirements through ingestion, semantic modeling, testing, deployment, and ongoing governance[cite: 2, 3]. * **Definition of Production Readiness:** A production release is valid only when technical deployment succeeds *and* underlying data assets are accurate, traceable, governed, and trusted by business consumers[cite: 3]. --- ## 2. Cross-Attachment Audit & Breaking-Point Reconciliation Before executing against this standard, teams must account for structural contradictions and visual anomalies across the four baseline artifacts so legacy defects are not propagated into production workflows: | Source Artifact | Structural Contribution | Identified Breaking Points & Visual Anomalies | Canonical Resolution Enforced in This Guide | | :--- | :--- | :--- | :--- | | **`SDLC_Roadmap_Infographic.png`**[cite: 1] | Establishes visual station routing and the left-hand **Bypass Loop (For Refinement)** connecting testing/operations back to upstream stages[cite: 1]. | **1. Inverted Causality:** Places `01 Requirements`, `02 Analysis`, and `03 Planning` before `04 Define`[cite: 1].<br>**2. Triple Build Redundancy:** Splits coding across `06 Implement`, `07 Build`, and `08 Development`[cite: 1].<br>**3. Duplicate Exit Nodes:** Repeats `11 Maintenance` and `12 Feedback / Finish` twice[cite: 1]. | Enforce `01 Define` and `02 Measure` prior to `03 Plan`[cite: 4, 5]; consolidate engineering into `04 Design` and `05 Implement`[cite: 4, 5]; replace duplicate exit nodes with commercial and governance tiers[cite: 4, 5]. | | **` List ALDC Phases.pdf`**[cite: 2, 3] | Provides the 10-phase Data Engineering, BI, and ThoughtSpot COE framework, SDLC crosswalk, 4-stage pipeline, and 7 cross-cutting governance pillars[cite: 2, 3]. | **1. Non-Standard Acronym:** Uses `ALDC` instead of industry-standard `ADLC`[cite: 3].<br>**2. Commercial Blind Spot:** Stops at `10 Continuous Improvement` without covering investor due diligence, Cap Tables, RFP tenders, or product sunsetting[cite: 2, 3]. | Adopt `ADLC` as the formal acronym[cite: 3] and map all 10 ADLC phases onto Phases `01–10` and `13–15` of the 16-phase enterprise lifecycle[cite: 2, 3, 5]. | | **`5ff82eb8.jpeg`** *(Isometric 16-Phase Roadmap)*[cite: 4] | Translates the 16 phases into an isometric campus flow featuring the **Continuous Refinement Loop** and sequential `01 Define` through `10 Deploy` stations[cite: 4]. | **1. Visual Badge Duplication:** Renders `13 PRODUCT LC` twice on the lower-right interchange while omitting visible badges for `14 PROJECT LC` and `15 DOCUMENT`[cite: 4]. | Use `5ff82eb8.jpeg` strictly for executive conceptual storytelling[cite: 4]; rely on the canonical 16-phase sequence (`11 Pitch` → `12 Investor` → `13 Product LC` → `14 Project LC` → `15 Document` → `16 Submission`) for operational governance[cite: 5]. | | **`fd218dcf.png`** *(Swimlane Architecture)*[cite: 5] | Organizes all 16 phases into three functional swimlanes (**Tier 1 Core Delivery**, **Tier 2 Commercial & Portfolio**, **Tier 3 Cross-Cutting Governance**)[cite: 5]. | **1. Gate Numbering Drift:** Visual diamond markers jump from `GATE 2` (after `04 Design`) to `GATE 5` (after `10 Deploy`), and repeat `GATE 6` twice in Tier 2[cite: 5]. | Enforce strict sequential Stage-Gates: **Gate 0** (`01`), **Gate 1** (`02–03`), **Gate 2** (`04–06`), **Gate 3** (`07–08`), **Gate 4** (`09–10`), **Gate 5** (`11–12`), and **Gate 6** (`13–16`). | --- ## 3. Master Multi-Framework Crosswalk Matrix This crosswalk unifies the **16-Phase Lifecycle**[cite: 4, 5], the **10-Phase ADLC / BI COE Framework**[cite: 2, 3], **Traditional SDLC**[cite: 1, 2, 3], and **dbt Labs' 8-Stage ADLC**[cite: 3]: | 16-Phase Lifecycle Station | Swimlane Tier & Canonical Gate | 10-Phase ADLC / BI COE Equivalent[cite: 2, 3] | Traditional SDLC Equivalent[cite: 1, 2] | dbt Labs 8-Stage ADLC Equivalent[cite: 3] | Primary Output Artifacts[cite: 2, 3] | | :--- | :--- | :--- | :--- | :--- | :--- | | **01. Define** | **Tier 1** • Gate 0[cite: 5] | **1. Initiation & Discovery**[cite: 2] | Planning / Initiation[cite: 1, 2] | Discover[cite: 3] | Project Charter, Business Case, VoC Matrix[cite: 2] | | **02. Measure** | **Tier 1** • Gate 1[cite: 5] | **2. Requirements Gathering & 3. Data Assessment**[cite: 2] | Requirements & Analysis[cite: 1, 2] | Analyze[cite: 3] | BRD, FRD, DRD, Source-to-Target Mapping, KPI Dictionary[cite: 2, 3] | | **03. Plan** | **Tier 1** • Gate 1[cite: 5] | **Project Management Track** *(Continuous)*[cite: 3] | Planning[cite: 1, 2] | Plan[cite: 3] | WBS, Product Roadmap, Capacity Plan, RAID Log[cite: 3] | | **04. Design** | **Tier 1** • Gate 2[cite: 5] | **4. Solution Architecture & Data Modelling**[cite: 2, 3] | Design[cite: 1, 2] | Plan / Architect[cite: 3] | PRD, System Architecture (SAD), ERD, ThoughtSpot Semantic Model[cite: 2, 3] | | **05. Implement** | **Tier 1** • Sprint[cite: 5] | **5. Development & Configuration**[cite: 2, 3] | Build / Implement[cite: 1, 2] | Develop[cite: 3] | ETL/ELT Pipelines, Semantic Layers, Liveboards, OpenAPI Contracts[cite: 2, 3] | | **06. Analysis** | **Tier 1** • Gate 2[cite: 5] | **Data Quality & Analytical Diagnostics**[cite: 3] | Analysis[cite: 1, 2] | Analyze / Observe[cite: 3] | Root Cause Analysis (5 Whys), Data Reconciliation, LTV/CAC Model[cite: 3] | | **07. ** Execute** | **Tier 1** • Gate 3[cite: 5] | **10. Change Management & Enablement**[cite: 2, 3] | Implementation / Rollout[cite: 1] | Operate[cite: 3] | Operations Runbook, ADKAR Enablement Plan, RACI Matrix[cite: 3] | | **08. Test** | **Tier 1** • Gate 3[cite: 5] | **6. Quality Assurance & 7. Business UAT**[cite: 2, 3] | Testing & Acceptance[cite: 1, 2] | Test[cite: 3] | Master Test Plan, QA Sign-Off, Business UAT Sign-Off, Security Audit[cite: 2, 3] | | **09. ** Control** | **Tier 1** • Gate 4[cite: 5] | **9. Operations, Monitoring & Security**[cite: 2, 3] | Maintenance[cite: 1, 2] | Observe[cite: 3] | SPC Control Charts, SLA/SLO Budgets, RBAC/PII Audit, Drift Alerts[cite: 3] | | **10. Deploy** | **Tier 1** • Gate 4[cite: 5] | **8. Release & Production Deployment**[cite: 2, 3] | Deployment / Release[cite: 1, 2] | Deploy[cite: 3] | Deployment Runbook, Canary/Rollback Protocol, Smoke Test Logs[cite: 3] | | **11. Pitch** | **Tier 2** • Gate 5[cite: 5] | *Value Realization & Executive Showcase* | — | — | Pitch Deck, Investment Teaser, Commercial GTM Strategy | | **12. Investor** | **Tier 2** • Gate 5[cite: 5] | *Fiduciary & Capital Governance* | — | — | Virtual Data Room (VDR) Index, Cap Table, SHA/SSA, KYC/AML | | **13. Product LC** | **Tier 2** • Quarterly[cite: 5] | **10. Continuous Improvement & Enhancements**[cite: 2, 3] | Continuous Development[cite: 2] | Discover[cite: 3] | BCG Portfolio Strategy, Market Localization, Feature Sunset Policy | | **14. ** Project LC** | **Tier 2** • Gate 6[cite: 5] | *Lifecycle Governance & Closure*[cite: 3] | Project Closure | — | Scope Baseline, Vendor SOW/MSA, Earned Value (EVM), Post-Mortem | | **15. Document** | **Tier 3** • Continuous[cite: 5] | **Documentation & Metadata Governance**[cite: 3] | Documentation | — | BRD/FRD/DRD/TDD, SOPs, Metadata & Lineage Catalog, RAG `.md` Files[cite: 3] | | **16. Submission** | **Tier 3** • Gate 6[cite: 5] | *Regulatory Compliance & Audit Attestation*[cite: 3] | Governance Audit | — | RFP Tender Dossier, SOC 2 / ISO 27001 Filing, Gate Sign-Off Pack | --- ## 4. Operational Guidance by Tier & Phase ### Tier 1: Core Delivery & ADLC Pipeline (`01 Define` → `10 Deploy`)[cite: 5] #### Phase 01: Define *(ADLC Phase 1 — Initiation & Discovery)*[cite: 2, 5] * **Objective:** Identify core business problems, commercial objectives, executive sponsors, technical feasibility, and measurable outcomes before committing build capacity[cite: 2]. * **Key Activities:** Conduct discovery workshops; map stakeholder authority; establish hard scope boundaries; validate strategic alignment[cite: 2]. * **Mandatory Documents:** `01_define_charter_business_case.md` (Project Charter, Business Case with NPV/ROI assumptions, Voice of Customer Matrix, Stakeholder Power-Interest Grid)[cite: 2]. * **Stage-Gate Exit Criterion (Gate 0):** Signed Project Charter authorizing discovery budget and naming accountable business and technical owners[cite: 2, 5]. #### Phase 02: Measure *(ADLC Phase 2 — Requirements & Phase 3 — Data Assessment)*[cite: 2, 5] * **Objective:** Elicit functional, technical, data, reporting, and non-functional requirements while auditing source systems for data availability, quality, lineage, and dependencies[cite: 2]. * **Key Activities:** Profile source database tables and columns; benchmark current baseline latencies or conversion drop-offs; define canonical KPI formulas; instrument telemetry SDKs[cite: 2]. * **Mandatory Documents:** `02_measure_telemetry_kpi_dictionary.md` (Business Requirements Document [BRD], Functional Requirements Document [FRD], Data Requirements Document [DRD], Source-to-Target Mapping, KPI Dictionary, Baseline Metrics Report)[cite: 2, 3]. * **Stage-Gate Exit Criterion (Gate 1A):** Verified Source-to-Target mapping and signed-off BRD/FRD/DRD confirming all required source columns exist and meet baseline quality thresholds[cite: 2, 3]. #### Phase 03: Plan *(Continuous Project Management Track)*[cite: 3, 5] * **Objective:** Decompose validated requirements into deterministic work packages, critical-path schedules, resource capacity allocations, and risk mitigation plans[cite: 3]. * **Key Activities:** Build the Work Breakdown Structure (WBS); sequence dependencies across data engineering, semantic modeling, and frontend teams; initialize the RAID log[cite: 3]. * **Mandatory Documents:** `03_plan_wbs_roadmap_raid_log.md` (WBS & Dictionary, Product/COE Roadmap, Resource Capacity Plan, Risk Management Matrix / RAID Log)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 1B):** Approved scope baseline, sprint schedule, and resource allocation plan[cite: 3, 5]. #### Phase 04: Design *(ADLC Phase 4 — Solution Architecture, Data Modelling & Semantic Design)*[cite: 2, 3, 5] * **Objective:** Architect end-to-end cloud infrastructure, relational/dimensional schemas, transformation logic, and semantic-layer definitions[cite: 2, 3]. * **Key Activities:** Model star/snowflake fact and dimension tables; define join cardinalities, row-level security (RLS) rules, and ThoughtSpot worksheet/semantic formulas; draft API contracts and UI wireframes[cite: 2, 3]. * **Mandatory Documents:** `04_design_prd_system_architecture.md` (Product Requirement Document [PRD] with Gherkin acceptance criteria, System Architecture Document [SAD], Entity-Relationship Diagrams [ERD], Technical Design Document [TDD], Semantic Layer Spec)[cite: 2, 3]. * **Stage-Gate Exit Criterion (Gate 2A — Architecture Freeze):** Peer-reviewed SAD, ERD, and Semantic Model specification signed off by Principal Architecture and Data Governance[cite: 2, 3, 5]. #### Phase 05: Implement *(ADLC Phase 5 — Development & Configuration)*[cite: 2, 5] * **Objective:** Construct ingestion pipelines, ETL/ELT transformations, database tables, semantic layers, KPI formulas, interactive Liveboards, and application microservices[cite: 2, 3]. * **Key Activities:** Execute Agile sprints using version-controlled Git workflows; enforce peer Pull Request reviews; build automated unit tests alongside pipeline and API code[cite: 3]. * **Mandatory Documents:** `05_implement_sprint_api_contract.md` (Sprint Backlogs, OpenAPI/Swagger Contracts, Environment Configuration Guides, Repository READMEs). * **Stage-Gate Exit Criterion (Sprint Acceptance):** All sprint stories pass static linting, unit tests, and peer code reviews in the development environment. #### Phase 06: Analysis *(ADLC Data Quality & Analytical Diagnostics)*[cite: 3, 5] * **Objective:** Reconcile transformed datasets against source systems, diagnose performance bottlenecks, and validate commercial unit economics[cite: 3]. * **Key Activities:** Execute row-count, checksum, and aggregate metric reconciliations; run 5-Whys Root Cause Analysis (RCA) on pipeline anomalies; evaluate cohort retention and LTV/CAC models[cite: 3]. * **Mandatory Documents:** `06_analysis_rca_cohort_economics.md` (Data Reconciliation Report, Root Cause Analysis Dossier, Cohort & Retention Analysis, Unit Economics & Sensitivity Model)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 2B — Viability Sign-Off):** Zero unexplained data variance between source systems and target semantic models, plus validated commercial unit economics[cite: 3, 5]. #### Phase 07: Execute *(ADLC Phase 10 — Operational Rollout & Change Enablement)*[cite: 2, 3, 5] * **Objective:** Prepare operational support teams, business users, and executive stakeholders for organizational adoption before production cutover[cite: 3]. * **Key Activities:** Deliver enablement training for BI consumers and tier-1/tier-2 support engineers; publish change communications; finalize escalation trees[cite: 3]. * **Mandatory Documents:** `07_execute_operations_change_mgmt.md` (Operations & Support Runbook, ADKAR Change Management Plan, Steering Committee Deck, RACI Execution Matrix)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 3A — Operational Readiness):** Support runbooks published and user enablement sessions completed. #### Phase 08: Test *(ADLC Phase 6 — Technical QA & Phase 7 — Business UAT)*[cite: 2, 3, 5] * **Objective:** Verify technical integrity (schema, data types, relationships, performance) and validate business KPI calculations, report outputs, and access permissions with end users[cite: 2, 3]. * **Key Activities:** Run automated integration, regression, load, and security penetration tests; conduct structured Business UAT sessions validating ThoughtSpot Liveboards and SaaS workflows against BRD/PRD acceptance criteria[cite: 2, 3]. * **Mandatory Documents:** `08_test_strategy_uat_security_audit.md` (Master Test Plan, Technical QA Sign-Off, Business UAT Sign-Off, Security/Pen-Test Audit, AI Model Card)[cite: 2, 3]. * **Stage-Gate Exit Criterion (Gate 3B — Quality & Security Sign-Off):** Formal written QA Sign-Off and Business UAT Sign-Off with zero unresolved Severity-1 or Severity-2 defects[cite: 2, 3, 5]. #### Phase 09: Control *(ADLC Phase 9 — Operations, Monitoring & Security Governance)*[cite: 2, 3, 5] * **Objective:** Enforce continuous pipeline reliability, refresh schedules, data quality thresholds, role-based access control (RBAC), and drift alerting in production[cite: 2, 3]. * **Key Activities:** Configure automated SLA/SLO alerts; enforce PII masking and RBAC policies; monitor data freshness, query latency, and model drift via Statistical Process Control (SPC) charts[cite: 3]. * **Mandatory Documents:** `09_control_spc_slo_drift_runbook.md` (Statistical Process Control Plan, SLA/SLO Error Budget Framework, Observability & PagerDuty Escalation Runbook, RBAC/PII Compliance Log)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 4A — Stability Check):** Automated monitoring dashboards and synthetic alerts verified active in staging/pre-prod[cite: 3]. #### Phase 10: Deploy *(ADLC Phase 8 — Release & Production Deployment)*[cite: 2, 5] * **Objective:** Obtain final release approvals, promote validated assets from QA to production, and execute post-deployment smoke tests[cite: 2, 3]. * **Key Activities:** Execute CI/CD canary or blue-green deployments; validate database migrations; run automated production smoke tests; verify rollback readiness[cite: 2, 3]. * **Mandatory Documents:** `10_deploy_release_rollback_iac.md` (Release Notes, Deployment Runbook, Automated Rollback Protocol, Infrastructure-as-Code [Terraform/Helm] Manifests)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 4B — Production Release Sign-Off):** Verified production smoke tests passing 100%, and release approval logged[cite: 2, 3, 5]. --- ### Tier 2: Commercial, Venture & Portfolio Lifecycle (`11 Pitch` → `14 Project LC`)[cite: 5] #### Phase 11: Pitch *(Commercialization & Value Realization)*[cite: 5] * **Objective:** Package verified production traction, unit economics, and technical differentiation into persuasive commercial and investor narratives. * **Key Activities:** Synthesize TAM/SAM/SOM sizing, live product demos, and customer ROI case studies; run red-team Q&A drills. * **Mandatory Documents:** `11_pitch_deck_gtm_commercial.md` (12–15 Slide Investor Pitch Deck, 1-Page Executive Teaser, Commercial Go-To-Market [GTM] Playbook, Demo Walkthrough Script). #### Phase 12: Investor *(Investor Onboarding & Fiduciary Diligence)*[cite: 5] * **Objective:** Execute institutional due diligence, capitalization table modeling, definitive legal agreements, and capital disbursement. * **Key Activities:** Structure tiered Virtual Data Room (VDR) access; reconcile diluted equity and ESOP pools; complete KYC/AML and IP assignment audits. * **Mandatory Documents:** `12_investor_vdr_cap_table_term_sheet.md` (Tiered VDR Index, Fully Diluted Cap Table, Term Sheet, Shareholders' Agreement [SHA], Share Subscription Agreement [SSA]). * **Stage-Gate Exit Criterion (Gate 5):** Executed definitive agreements and cleared escrow capital transfer[cite: 5]. #### Phase 13: Product Life Cycle *(ADLC Phase 10 — Continuous Improvement & Portfolio Stewardship)*[cite: 2, 5] * **Objective:** Govern product and analytics portfolio evolution across Introduction, Growth, Maturity, and Decline stages[cite: 2, 3]. * **Key Activities:** Prioritize enhancement backlogs and impact assessments; allocate R&D capital via BCG growth-share reviews; manage orderly deprecation and migration of legacy reports or APIs[cite: 2, 3]. * **Mandatory Documents:** `13_plc_portfolio_sunset_strategy.md` (Product Portfolio Strategy, Annual Product P&L, Market Localization Dossier, Feature Sunset & Deprecation Policy)[cite: 2, 3]. #### Phase 14: Project Life Cycle *(Governance, Vendor Management & Closure)*[cite: 3, 5] * **Objective:** Maintain contractual governance over bounded initiatives from scope baseline through vendor management and formal post-mortem closure[cite: 3]. * **Key Activities:** Track Earned Value Management (EVM) cost/schedule variances; audit vendor Statements of Work (SOW); conduct blameless post-mortems and archive lessons learned[cite: 3]. * **Mandatory Documents:** `14_project_lifecycle_sow_closure.md` (Project Scope Baseline, Vendor SOW/MSA Register, RAID Escalation Archive, Project Closure & Lessons Learned Report)[cite: 3]. * **Stage-Gate Exit Criterion (Gate 6A):** Formal stakeholder project acceptance and financial closeout[cite: 5]. --- ### Tier 3: Cross-Cutting Governance & Compliance Foundation (`15 Document` & `16 Submission`)[cite: 3, 5] Rather than executing solely at the end of a project, Tier 3 operates continuously beneath Tiers 1 and 2 to enforce institutional memory and regulatory compliance[cite: 3, 5]: #### Phase 15: Document *(Continuous Knowledge & Metadata Governance)*[cite: 3, 5] * **Objective:** Maintain living, version-controlled technical documentation, data lineage catalogs, Standard Operating Procedures (SOPs), and RAG-ready Markdown knowledge bases[cite: 3]. * **Key Activities:** Enforce docs-as-code in Git alongside every Pull Request; update data dictionaries, lineage graphs, and ThoughtSpot metric definitions whenever schemas evolve; index `.md` files with YAML frontmatter into enterprise vector stores[cite: 3]. * **Mandatory Documents:** `15_document_sop_api_data_catalog.md` (BRD/FRD/DRD/TDD Templates, Operational SOPs, Enterprise Data Dictionary & Lineage Catalog, Developer API Hub)[cite: 3]. #### Phase 16: Submission *(Institutional Audits, Regulatory Filings & RFP Tenders)*[cite: 3, 5] * **Objective:** Assemble, verify, and formally transmit compliance attestations, regulatory filings, enterprise RFP responses, and Stage-Gate audit packages[cite: 3, 5]. * **Key Activities:** Compile SOC 2 Type II, ISO 27001, GDPR/DPDP, or financial regulatory evidence; execute legal compliance sign-offs; submit encrypted RFP tender dossiers[cite: 3]. * **Mandatory Documents:** `16_submission_rfp_compliance_gate.md` (RFP Response Dossier, SOC 2 / ISO Compliance Pack, Stage-Gate Governance Audit Dossier, Formal Legal Transmittal Letter). * **Stage-Gate Exit Criterion (Gate 6B):** Executed executive and legal attestation sign-off[cite: 5]. --- ## 5. Cross-Cutting Governance Matrix (7 Core Pillars) Per the BI & Data Engineering COE governance standard, these seven disciplines execute continuously across all 16 phases[cite: 3]: | Governance Pillar[cite: 3] | Operational Mandate[cite: 3] | Primary Enforcing Phases | Core Control Artifacts[cite: 3] | | :--- | :--- | :--- | :--- | | **1. Documentation**[cite: 3] | Maintain living traceability across business, functional, data, and technical specs[cite: 2, 3]. | All Phases (`01–16`), anchored in `15 Document`[cite: 3, 5] | BRD, FRD, DRD, TDD, Source-to-Target Mapping, Test Cases[cite: 2, 3] | | **2. Data Governance**[cite: 3] | Enforce clear domain ownership, metadata tagging, data lineage, and sensitivity classification[cite: 3]. | `02 Measure`, `04 Design`, `09 Control`, `15 Document`[cite: 2, 3, 5] | Metadata Catalog, Lineage Graph, Data Ownership Matrix[cite: 3] | | **3. Data Quality**[cite: 3] | Guarantee completeness, accuracy, consistency, and source-to-target reconciliation[cite: 3]. | `02 Measure`, `06 Analysis`, `08 Test`, `09 Control`[cite: 2, 3, 5] | Automated dbt/SQL Reconciliation Tests, Anomaly Logs[cite: 3] | | **4. Change Management**[cite: 3] | Control schema and code evolution via versioning, impact analysis, and formal approvals[cite: 3]. | `03 Plan`, `05 Implement`, `07 Execute`, `13 Product LC`[cite: 2, 3, 5] | Change Request (CR) Log, Semantic Impact Assessment[cite: 2, 3] | | **5. Security**[cite: 3] | Protect sensitive data via RBAC, PII masking/encryption, access reviews, and audit trails[cite: 3]. | `04 Design`, `08 Test`, `09 Control`, `12 Investor`, `16 Submission`[cite: 3, 5] | RBAC Policy Matrix, PII Classification Register, Pen-Test Audit[cite: 3] | | **6. Project Management**[cite: 3] | Synchronize delivery velocity, dependencies, risks, and executive status reporting[cite: 3]. | `01 Define`, `03 Plan`, `07 Execute`, `14 Project LC`[cite: 3, 5] | Sprint Boards, RAID Log, RACI Matrix, Steering Decks[cite: 3] | | **7. Configuration Mgmt**[cite: 3] | Isolate Dev/QA/Prod environments, track release history, and guarantee instant rollback[cite: 3]. | `05 Implement`, `09 Control`, `10 Deploy`[cite: 3, 5] | Git Branching Policy, IaC State Files, Rollback Runbooks[cite: 3] | --- ## 6. Alternative Paradigms & Failure-Mode Playbook ### Paradigm Selection Matrix Depending on organizational maturity and regulatory exposure, teams should calibrate gate strictness using one of three operating modes: 1. **Strict Stage-Gate Governance *(Recommended for Regulated FinTech, Enterprise BI COE & Institutional Audits)*:** Enforces hard physical/digital sign-offs at Gates `0–6`[cite: 5]. Prevents unvalidated data models from reaching ThoughtSpot Liveboards or external clients[cite: 3]. 2. **Dual-Track Agile & DataOps *(Recommended for High-Velocity SaaS & AI Product Teams)*:** Runs Discovery/Design (`01–04`) one sprint ahead of Build/Validate (`05–08`), automating `08 Test`, `09 Control`, and `10 Deploy` via CI/CD pipelines (e.g., dbt + GitHub Actions)[cite: 3, 5]. 3. **Lean Venture Validation Loop *(Recommended for 0-to-1 Pre-Seed/Seed Products)*:** Compresses `01 Define` → `04 Design` → `05 Implement` → `10 Deploy` → `11 Pitch` into 2-week validation cycles while deferring heavy `14 Project LC` and `16 Submission` overhead until institutional diligence (`12 Investor`) begins[cite: 5]. ### Critical Failure Modes & Red-Team Mitigations * **Failure Mode 1 — Skipping Phase `02 Measure` (Data Assessment) to Accelerate `05 Implement`:** * *Symptom:* Engineers build ETL pipelines and semantic models only to discover missing historical columns, broken foreign keys, or conflicting business KPI definitions during UAT[cite: 2, 3]. * *Mitigation:* Enforce **Gate 1A**—no transformation code or ThoughtSpot worksheet creation is permitted until the Source-to-Target mapping and KPI Dictionary are signed off[cite: 2, 3]. * **Failure Mode 2 — Treating Phase `15 Document` as a Post-Deployment Chore:** * *Symptom:* Documentation decays immediately after launch, breaking downstream RAG retrieval accuracy and creating single-person operational bottlenecks[cite: 3]. * *Mitigation:* Embed `.md` documentation updates directly into Pull Request Definition-of-Done (DoD) checklists and automate vector-store re-indexing on merge to `main`. * **Failure Mode 3 — Broken Continuous Refinement Loop (`10 Deploy` → `01 Define`):** * *Symptom:* Production incidents, user feedback, and metric drift are patched ad-hoc in production without updating upstream BRDs, DRDs, or test suites[cite: 1, 3]. * *Mitigation:* Route every production incident and enhancement request through formal change impact analysis (`06 Analysis` / `13 Product LC`) before re-entering the delivery pipeline[cite: 2, 3]. ### OUTPUT FORMAT Output **only** the raw, valid Markdown document enclosed in a single `markdown` code block, starting with `---` (YAML frontmatter) and ending with a **Stage-Gate Exit & RACI Sign-Off Table**. Do not include conversational filler before or after the code block.

Minutes of meeting

Minutes of meeting held at department of Chemical Sciences FUK

Act as a Supplier Negotiation Coach for Small Businesses

Act as a Supplier Negotiation Coach for small businesses. I run a small business (for example a cafe, restaurant, salon, online shop, cleaning company, workshop, agency or small manufacturer) and I buy from suppliers: ingredients, stock, packaging, materials, software, equipment, delivery or services. I want better prices and terms without damaging relationships I depend on. Your job is to help me prepare, run and follow up a supplier negotiation, and to tell me plainly where I have leverage and where I don't. Start by asking me, in one short numbered list, for: 1. Which supplier and what I buy from them: items, volumes per month, current prices and payment terms. 2. How long we have worked together and how the relationship feels (good, strained, new). 3. What I want to change: price, payment terms, minimum order, delivery schedule, quality, returns, or a price rise they announced. 4. Alternatives I have or could get: other suppliers, quotes, substitutes, doing it in-house. 5. Any contract, notice period or exclusivity I am bound by. 6. My deadline and how much I can afford to walk away. Then work through these steps with me, one at a time, and wait for my answers where you need them: Step 1 - My position. Summarize my annual spend with this supplier, what share of my costs it is, and how important I am likely to be to them. Estimate my walk-away point (the best alternative if this fails) and my target. Show the money: what a 3%, 5% and 10% better price or 30 extra days of payment terms is worth to me per year, in a small table. Step 2 - Their side. List what this supplier probably cares about (steady volume, fast payment, forecasting, less admin, fewer rush orders, a reference customer) and which of these I can offer cheaply. Point out anything that makes my position weaker, honestly. Step 3 - The asks and trades. Build a short list of asks in order of priority, and for each one a trade I can offer in return (for example a 12-month volume commitment for a lower unit price, earlier payment for a discount, larger but fewer orders for free delivery). Mark which asks are must-haves and which I can give up. Step 4 - The opening message. Write a short, friendly email or message to request the conversation, under 120 words, that states the goal without threats or bluffing. Step 5 - The conversation plan. Give me an opening line, the order to raise each point, three likely answers from the supplier with a calm reply for each ("Our costs went up too", "That's our best price", "We'd need a bigger order"), and the moment to pause and say I need to think. Include one fair package I can propose if we get stuck. Step 6 - If they announced a price rise. If my situation is a supplier price increase, add: questions to ask about the reason and timing, options to phase it in, lock in current prices, cap future rises or switch to a different spec, and when it makes sense to accept it. Step 7 - Close and follow up. Write a short confirmation email that records exactly what we agreed (prices, terms, dates, review point), and a checklist to update my costing, purchase orders and reminders. Tell me when to review the deal again. Rules: - Never suggest lying, fake competing quotes, bluffing about walking away, or anything that could breach a contract. - Never invent my numbers; ask, or label anything you assume. - Keep it respectful: a supplier I treat well tends to help me when stock is short. - Flag anything that may need a check against my contract or local law, without giving legal advice. - Keep each step short, use tables for numbers, and end each step with one clear question for me.

Vendor Security Questionnaire Answer Pack (YAML)

You are a startup security and compliance lead who has answered hundreds of customer security questionnaires. Using the schema below, turn what I tell you about my product and company into a reusable security questionnaire answer pack as one valid YAML document. Ask me up to 6 short questions first if the inputs are missing, then output ONLY the YAML, with no commentary before or after it. My inputs: - Product and what customer data it handles (personal data, payment data, health data, files, credentials): - Company size, team locations and who owns security: - Hosting and key vendors (cloud, database, email, payments, analytics, support tools): - Security practices we really have today (SSO, MFA, encryption, backups, logging, code review, pen test, training): - Certifications or audits (none, SOC 2 in progress, SOC 2 Type II, ISO 27001, other): - The questionnaire or customer that triggered this (paste the questions if you have them): Schema: ```yaml answer_pack: summary: company: "" product: "" prepared_by: "" last_reviewed: "" # YYYY-MM-DD next_review: "" # YYYY-MM-DD data_classification: "" # what data we store and how sensitive it is certifications: [] # only ones we actually hold, with status trust_page_url: "" # or "none yet" company_overview: security_owner: "" team_size: "" policies_in_place: [] # name, last updated, approved by background_checks: "" security_training: "" infrastructure: hosting: "" regions: [] network_security: "" environments_separated: "" # yes / no / partly, with detail data_protection: encryption_in_transit: "" encryption_at_rest: "" key_management: "" backups: "" # frequency, retention, last restore test data_retention_and_deletion: "" data_residency: "" access_control: sso_and_mfa: "" least_privilege: "" access_reviews: "" offboarding: "" customer_side_controls: [] # SSO for customers, roles, audit logs application_security: secure_development: "" # code review, branch protection, CI checks dependency_and_vulnerability_management: "" penetration_testing: "" # last date, by whom, findings status secrets_management: "" monitoring_and_incidents: logging_and_alerting: "" incident_response_plan: "" breach_notification_commitment: "" past_incidents: "" business_continuity: uptime_target: "" disaster_recovery: "" # RPO / RTO status_page: "" vendors_and_subprocessors: - name: "" purpose: "" data_shared: "" location: "" assurance: "" # their certification or DPA privacy: dpa_available: "" gdpr_or_local_law_notes: "" data_subject_requests: "" standard_answers: - question_pattern: "" # the common way customers ask it short_answer: "" # one or two sentences, true today evidence: "" # document, screenshot or link to share status: "" # in_place | partial | planned | not_applicable gaps_and_roadmap: - gap: "" risk_to_deals: "" # low / medium / high honest_interim_answer: "" fix: "" owner: "" target_date: "" evidence_library: - document: "" share_under_nda: "" # yes / no location: "" open_questions_for_me: [] ``` Rules: - Answer only with what is true today. Never claim a certification, audit, control or policy I did not confirm; mark it partial or planned and put it in gaps_and_roadmap with an honest interim answer. - Write short_answer texts in plain, confident language a buyer's security reviewer can accept as is, without marketing words. - Fill standard_answers with at least 15 of the most common questionnaire items (SSO, MFA, encryption, backups, pen test, incident response, subprocessors, data deletion, employee access, logging, vulnerability management, business continuity, data location, training, breach notification). - If I pasted a questionnaire, map every question to a standard_answer and list any question you cannot answer in open_questions_for_me. - Use "" for unknown values and list them in open_questions_for_me instead of guessing. - Keep valid YAML: two-space indentation, quote strings containing colons, no tabs. - This is a drafting aid, not legal or audit advice; flag anything that should be checked by counsel or an auditor.

Mezzotint Engraving of a Moonlit Wheat Field at Harvest Time

An authentic 18th-century style mezzotint engraving of a moonlit wheat field at harvest time, landscape 4:3, printed in warm black-brown ink on cream laid paper. In the foreground, rows of tied wheat sheaves stand in the stubble beside two tall rounded haystacks, the ripe ears catching silver moonlight; in the middle ground a narrow cart track with a resting wooden hay cart and a low dry-stone wall leads to a small thatched farmhouse with one warm-lit window; behind, gentle rolling hills sit under a large full moon half veiled by drifting clouds. Mezzotint technique details: deep, velvety, rich blacks built from a fine rocked grain over the whole plate; every light area scraped and burnished out of the darkness, so highlights glow softly with no hard outlines; smooth, continuous tonal gradations from black to cream; a subtle dotted burr texture visible in the mid-tones; a slightly embossed plate mark around the image with a clean paper margin. Quiet, nocturnal, timeless mood. Viewed straight on as a flat print in soft even light. No text, no signature, no frame, no people.

Pictorialist Gum Bichromate Print of a Misty Pine Forest at Dawn

An authentic early 1900s pictorialist gum bichromate photographic print of a misty pine forest at dawn, portrait 3:4. Tall straight pine trunks rise in receding rows into soft fog; the low sun glows through the trees just right of center and sends long diagonal rays of warm peach-gold light through the mist; a narrow footpath covered in pine needles winds from the bottom center between ferns and mossy rocks toward the light. Gum bichromate technique details: soft, painterly tonal masses instead of fine photographic detail; layered pigment from several hand-coated printings, with muted grey-green and warm umber tones; a slightly mottled, grainy texture; an uneven, hand-coated image border where the emulsion fades out; printed on heavy, aged cream watercolor paper with rough, torn deckled edges. Atmospheric, quiet and dreamlike, like a fine-art photograph from a 1905 salon exhibition. Viewed straight on as a flat print in soft even light. No text, no signature, no frame, no people, no animals.

Loggerhead Sea Turtle Hatchlings Racing to the Surf at Sunrise

Photorealistic low-angle wildlife photograph of newly hatched loggerhead sea turtles crossing a wide sandy beach at dawn, landscape 16:9. Ten palm-sized hatchlings with dark grey-brown shells and flippers are spread across the left and center of the smooth wet sand, all crawling diagonally toward the upper right, flippers spread mid-crawl, each leaving a tiny trail of flipper tracks; an open nest hollow with clumps of sand sits at the lower left. The thin foamy edge of a gentle wave runs from the top center to the right side of the frame and glistens in the soft pink and orange sunrise light; the sun sits low on the horizon at the right over a calm sea, with a sun glint on the water and a pastel sky. Low camera just above the sand, angled slightly down, 100 mm lens at f/4, sharp on the nearest hatchlings with gentle background blur, wet sand reflecting the sky, natural colors, quiet early-morning stillness. No people, no hands, no birds, no text.

Loggerhead Sea Turtle Hatchlings Racing to the Surf at Sunrise (Image-to-Video Animation)

Use the attached still (step 1: a low photograph of ten loggerhead sea turtle hatchlings crawling across wet sand toward the sea at sunrise) as the exact first frame and animate it into a 6-second, 16:9 cinematic shot. Keep every element where it is in the still: the ten hatchlings and their positions on the sand, the open nest hollow at the lower left, the foamy wave edge from the top center to the right, the low sun on the horizon at the right and the pink and orange sky. Motion (0-6 s): - 0-1.5 s: the hatchlings begin to move, flippers pushing in small alternating strokes as they crawl diagonally toward the upper right; light glints on the wet sand. - 1.5-4 s: the hatchlings keep scrambling toward the water at a natural, slightly clumsy pace, leaving fresh flipper tracks, while a foamy wave rolls up the beach from the right and spreads over the sand toward them. - 4-6 s: the wave's foam edge reaches the leading hatchlings and washes around their flippers, then slowly recedes, leaving a glossy reflective sheen and small bubbles on the sand as the group keeps crawling seaward. Camera: locked-off low framing just above the sand with a very slow, slight push-in; focus stays on the nearest hatchlings; no cuts. Lighting and mood: constant soft sunrise light, warm pink and orange reflections and a sun glint on the water; hopeful, calm, natural. Audio (if supported): gentle surf, the soft hiss of foam on the sand, a light breeze; no music, no voices. Avoid: people, hands, birds, extra or duplicated turtles appearing, turtles morphing or walking upright, sudden lighting changes, unnatural fast motion, text.

Docker Compose taste

# Docker Compose taste of a developer who wants one-command local environments - Make `docker compose up` the only command a new teammate needs to start the full local stack. Confidence: 0.90 - Name the file `compose.yaml` and drop the obsolete top-level `version:` key. Confidence: 0.85 - Pin every image to a specific version tag, never `latest`, so the stack behaves the same next month. Confidence: 0.90 - Add a `healthcheck` to every database and queue, and use `depends_on` with `condition: service_healthy` instead of sleep loops. Confidence: 0.90 - Keep secrets and machine-specific values in a gitignored `.env` file, and commit a `.env.example` with safe defaults. Confidence: 0.90 - Use named volumes for database data so `docker compose down` does not wipe local work by accident. Confidence: 0.85 - Bind ports to `127.0.0.1` on the host so local databases are not reachable from the whole network. Confidence: 0.80 - Mount source code only for services you edit live, and use `develop.watch` or a bind mount with clear sync rules. Confidence: 0.75 - Put optional tools like admin UIs, mail catchers and tracing behind `profiles` so the default stack stays small. Confidence: 0.80 - Use `compose.override.yaml` for personal tweaks and keep it out of git. Confidence: 0.70 - Build app images from the same Dockerfile used in production, with a separate `dev` target if needed. Confidence: 0.85 - Run services as a non-root user even locally, so permission problems show up before production. Confidence: 0.70 - Seed the database with a small, deterministic dataset through an init script or a one-off `seed` service. Confidence: 0.80 - Let services talk by service name on the default network instead of hardcoding IPs or `host.docker.internal`. Confidence: 0.85 - Set memory and CPU limits on heavy services so one container cannot freeze a laptop. Confidence: 0.65 - Keep log output on stdout and stderr, and use `docker compose logs -f <service>` instead of log files inside containers. Confidence: 0.85 - Give each project a fixed `name:` so containers, networks and volumes do not collide between repos. Confidence: 0.75 - Wrap common tasks like migrate, test and reset in `make` or `just` targets that call `docker compose run --rm`. Confidence: 0.80 - Use the same Compose file in CI for integration tests, so CI and laptops run one setup. Confidence: 0.75 - Do not use Compose as the production orchestrator for anything that needs zero-downtime deploys or scaling. Confidence: 0.80

OpenAPI Spec taste

# OpenAPI Spec taste of an API designer who treats the spec as the contract - Write the OpenAPI document first and review it in a pull request before any endpoint is implemented. Confidence: 0.80 - Use OpenAPI 3.1 so schemas are real JSON Schema and nullable fields are written as type unions. Confidence: 0.80 - Keep the spec in the repo as YAML, split into files with `$ref`, and bundle it into one file in CI. Confidence: 0.85 - Lint every change with Spectral or Redocly using a shared ruleset, and fail the build on errors. Confidence: 0.90 - Give every operation a unique, stable `operationId` in camelCase, because generated clients use it as the method name. Confidence: 0.90 - Define reusable models under `components/schemas` and never repeat the same object inline in several places. Confidence: 0.85 - Mark `required` fields explicitly and set `additionalProperties: false` on request bodies. Confidence: 0.75 - Describe every error with one shared problem-details schema (RFC 9457), not a different shape per endpoint. Confidence: 0.85 - Document every response code an endpoint can really return, including 401, 403, 404, 409 and 429. Confidence: 0.80 - Add a realistic `example` to every schema and operation so docs, mocks and tests have real data. Confidence: 0.85 - Use string formats like `date-time`, `uuid` and `email`, plus `minLength`, `maximum` and `pattern` constraints, instead of plain strings. Confidence: 0.80 - Model enums as strings, and document that clients must tolerate unknown values added later. Confidence: 0.75 - Use the same cursor-based pagination parameters and response envelope on every list endpoint. Confidence: 0.80 - Declare `securitySchemes` once and apply them globally, overriding only for truly public operations. Confidence: 0.85 - Run a breaking-change check such as oasdiff against the main branch on every pull request. Confidence: 0.90 - Validate requests and responses against the spec in contract tests so the code cannot quietly drift from it. Confidence: 0.85 - Generate clients and server types from the spec, and never hand-edit generated files. Confidence: 0.85 - Write `summary` and `description` fields for humans, explaining behavior and edge cases rather than repeating the field name. Confidence: 0.75 - Mark old fields and operations with `deprecated: true` and announce a removal date before deleting them. Confidence: 0.80 - Publish rendered docs from the spec on every release so the docs always match the deployed API. Confidence: 0.80

CMake C++ Project taste

# CMake C++ Project taste of a systems developer who wants clean, portable builds - Require a modern CMake (3.24 or newer) and write target-based CMake only, never global `include_directories` or `add_definitions`. Confidence: 0.90 - Attach include paths, flags and definitions to targets with `target_*` commands and the right `PUBLIC`, `PRIVATE` or `INTERFACE` scope. Confidence: 0.90 - Always build out of source, in a `build/` directory that is gitignored. Confidence: 0.95 - Commit a `CMakePresets.json` with debug, release and sanitizer presets so everyone configures the same way. Confidence: 0.85 - Set the language standard with `target_compile_features(... cxx_std_20)` instead of raw `-std=` flags. Confidence: 0.85 - Turn on strict warnings like `-Wall -Wextra -Wpedantic` or `/W4` through a shared interface target, and treat warnings as errors in CI. Confidence: 0.85 - Never use `file(GLOB)` for source lists; list source files explicitly so the build reruns when files change. Confidence: 0.75 - Get third-party libraries with `find_package` backed by vcpkg or Conan, and use `FetchContent` only for small, pinned dependencies. Confidence: 0.80 - Pin every fetched dependency to a tag or commit hash, never a moving branch. Confidence: 0.90 - Never vendor modified copies of libraries without a clear patch file and a note on why. Confidence: 0.75 - Run tests with CTest, and register each test executable with `add_test` or `gtest_discover_tests`. Confidence: 0.85 - Have a CI job that builds with AddressSanitizer and UndefinedBehaviorSanitizer and runs the full test suite. Confidence: 0.85 - Export `compile_commands.json` with `CMAKE_EXPORT_COMPILE_COMMANDS` so clangd and clang-tidy work out of the box. Confidence: 0.90 - Format with a committed `.clang-format` and check it in CI rather than arguing about style in reviews. Confidence: 0.85 - Use Ninja as the default generator for fast incremental builds, and ccache or sccache in CI. Confidence: 0.80 - Provide proper `install()` rules and an exported package config so other projects can use `find_package` on the library. Confidence: 0.75 - Namespace exported targets like `mylib::mylib` and create an alias target with the same name for in-tree use. Confidence: 0.80 - Keep options few and prefixed with the project name, such as `MYLIB_BUILD_TESTS`, and default tests off when used as a subproject. Confidence: 0.75 - Avoid setting `CMAKE_CXX_FLAGS` directly in `CMakeLists.txt`; leave global flags to presets and toolchain files. Confidence: 0.80 - Test the build on Linux, macOS and Windows in CI if the project claims to be portable. Confidence: 0.80

Giant-Letter Landmark Poster: Fill-in Template That Merges Any Landmark Into One Oversized Typographic Letter (4:5)

Create an exceptionally sophisticated, contemporary architectural art poster featuring [LANDMARK NAME], [CITY], [COUNTRY]. 1. GIANT TYPOGRAPHIC COMPOSITION Feature one enormous, oversized uppercase letter associated with the destination name as the central graphic element. The letter should dominate the composition, extending almost across the entire poster. Use bold, elegant, geometric typography with distinctive curves and negative spaces. 2. LANDMARK INTEGRATION Seamlessly integrate a highly detailed architectural photograph or realistic architectural illustration of [LANDMARK NAME] into and across the oversized letter. The landmark should appear to emerge from the typography, partially overlap its boundaries and interact naturally with its shape. Preserve the landmark’s authentic architectural details, proportions and recognisable silhouette. Create an artistic double-exposure effect where the architecture and typography become one unified visual composition. 3. DISTINCTIVE COLOUR TREATMENT Choose a unique colour palette inspired by the destination’s cultural identity, national colours and architectural character. Use two or three contrasting colours within the oversized typography. Apply translucent colour overlays across selected sections of the landmark, creating a beautiful combination of architectural photography, coloured light and graphic shapes. Every new destination must receive a different colour combination. Never repeat palettes. 4. TEXTURE & BACKGROUND Use a warm ivory, soft white or subtle textured paper background. Introduce delicate architectural sketch marks, distressed ink textures, faded photographic grain and subtle print imperfections around the central composition. Keep the surrounding space clean and uncluttered. 5. EDITORIAL TYPOGRAPHY Include the following information: [LANDMARK NAME] [CITY NAME] [COUNTRY NAME] Add small vertical typography along one side, geographical coordinates and a subtle destination-inspired tagline. Use sophisticated editorial typography with carefully balanced spacing. 6. ART DIRECTION Luxury architectural editorial design, experimental typography, architectural double exposure, contemporary Swiss graphic design, oversized letterforms, cinematic monochromatic photography, translucent colour blocking and minimalist gallery poster aesthetics. 7. FINAL PRESENTATION Create a visually striking, intellectual and artistic collectible landmark poster. The architecture must remain recognisable while becoming an integral part of the oversized letter. Vertical 4:5 composition, premium art-print quality, exceptional visual balance and sophisticated negative space. Avoid ordinary travel-poster layouts, decorative clutter, excessive colours and generic typography.

Original Sci-Fi Blockbuster Poster: Armored Heroine and a Towering Mech Titan Under a Blue Energy Ring (JSON, 3:4)

{ "aspect_ratio": "3:4", "style": "premium Hollywood sci-fi superhero theatrical poster, photorealistic CGI, clean cinematic composition, IMAX production quality, sophisticated visual storytelling", "prompt": "Create an extraordinary original Hollywood blockbuster movie poster titled VYKRON: RISE OF THE LAST TITAN. A powerful adult female superhero stands in the center foreground, shown full body from head to toe. She wears an iconic futuristic metallic cobalt-blue and silver battle suit with elegant orange illuminated energy details, sophisticated mechanical armor, sculpted shoulder protection and advanced robotic gauntlets. Her appearance is confident, stylish and intimidating. Her face is clearly visible and beautifully detailed.\n\nDirectly behind her stands ONE enormous futuristic mechanical Titan, towering over the city. Its distinctive silhouette features massive armored shoulders, powerful mechanical arms, an illuminated circular chest reactor and an angular futuristic head. The Titan should look magnificent, intimidating and incredibly expensive to build.\n\nBACKGROUND DESIGN: A beautiful futuristic megacity stretching across the horizon, with elegant skyscrapers and a dramatic atmospheric sky. A large glowing blue energy ring appears behind the Titan, creating a powerful visual focal point. A few distant orange lights illuminate the architecture. The skyline should remain clean, organized and visually calm. No chaotic destruction.\n\nCOMPOSITION: Heroine occupies the central lower foreground. The gigantic Titan fills the middle background. The glowing circular energy structure frames the upper background. Every subject must be clearly separated and instantly recognizable.\n\nCOLOR GRADING: Rich cobalt blue, polished silver, electric cyan and carefully placed warm orange highlights. Bright attractive colors, balanced exposure, beautiful cinematic reflections and premium atmospheric lighting.\n\nIMPORTANT VISUAL RULES: Minimal background clutter, no excessive explosions, no flying debris, no random aircraft, no multiple robots, no crowded buildings, no excessive smoke, no visual noise, no unnecessary objects. Maintain clean negative space and strong subject separation.\n\nAt the top write:\n\nTHE LAST ERA BEGINS.\n\nAt the bottom display a huge bold metallic movie title:\n\nVYKRON\n\nBelow it write:\n\nRISE OF THE LAST TITAN\n\nProfessional Hollywood theatrical typography, beautiful poster hierarchy, premium cinematic finish, exceptional clarity, original character and original machine design, no existing franchise references, no watermark." }

A story of a boy who wants to become cricket player

A boy's story about becoming a cricket player just like virat kohli

Heinsberg' principle

I want to create a video using Heinsebergs principle for Life principles

Data Analysis Dashboard

Create for me an ultra-realistic dashboard titled "ANALYSIS OF BRD SESSIONS/DOCUMENT DELIVERY AUG - OCT" Let it show, in graphs, histograms, and pie charts, all the documents I have worked on so far concerning BRDs and documents under growth stack

Transition to Professional Services Consultant

I am currently working as a technical support analyst for Esri UK and have been working for them for nearly 6 years. In this time, I have had various roles within Technical Support, from entry level to Technical Support Analyst now, which I have been doing for ~3 years. I am feeling stagnant in my role and I am not sure of what to do next. I would like to do a secondment to our Professional Services team as a Consultant. However, at the moment, I feel like I do not have the appropriate skill levels/knowledge to do this. I could do a secondment as a junior Consultant, however, ideally someone with my years of experience would come in at a Consultant level. I want to be able to be confident in doing this role and be successful. Please outline structured learning plan over the next 3 months that I can do to improve my GIS knowledge (across all Esri/Esri UK products, such as ArcGIS Enterprise, ArcGIS Pro, ArcGIS Online, etc) and improvise the skills that I would need in Professional Services so that I can hit the ground running and be confident. Study the differences between a Technical Support Analyst role and a GIS Consultant role within Esri UK and use these to help guide the structured learning plan. Outline also how I can demonstrate these skills to my manager. What do I need to do going forward.

GG+2 SPORT ANALYSIS

I want to create a prompt to analyse football games that will play GG+2 that is both teams to score two goals each using stats and live data

mbappe steals Harry kane balon d,or

**Setting:** The 2026 Ballon d’Or Ceremony. Grand stage in Paris. Golden trophy sits centre on a pedestal. Audience claps. Host stands at microphone. Harry Kane sits front row, dressed sharp, smiling, ready to go up. Kylian Mbappé sits nearby. Lamine Yamal & Michael Olise are seated together, looking smart and excited. --- ## Scene 1 — The Announcement **Host:** And the winner of the 2026 Ballon d’Or… for the first time in his career… **HARRY KANE!** *(Applause erupts. Harry grins, stands up, shakes hands, walks toward the stage. Suddenly, Kylian Mbappé jumps up, eyes wide, playfully sprinting past everyone. He reaches the trophy first, lifts it high, and turns around with a cheeky grin.)* **Mbappé:** *(holding trophy above head)* MINE! 😜 I WON IT! *(Audience laughs. Harry stops, hands on hips, shaking his head with a smile.)* **Kane:** Kylian… put it down. They called **my** name. **Mbappé:** *(backing away, trophy still in hands)* Are you sure? Maybe I misheard! It sounded like *Kylian*! --- ## Scene 2 — Yamal & Olise Step In *(Lamine Yamal and Michael Olise walk onto the stage, grinning, standing between them.)* **Yamal:** Guys, calm down — everyone saw the envelope! It says **Harry Kane**. **Olise:** Yeah, Kylian, don’t be greedy! You’ve got enough already! Hand it over, mate. **Mbappé:** *(pulling trophy slightly away)* Just let me hold it for one photo! Please? I promise I’ll give it back after the picture! **Kane:** *(laughing)* One photo. That’s it. Then I get it. Deal? **Mbappé:** Deal! *(grins big)* --- ## Scene 3 — The Selfie & The Handover *(Mbappé holds the trophy high. Yamal pulls out his phone. All four squeeze together — Harry in the middle, Mbappé on one side still gripping the trophy, Yamal and Olise on the other two sides — all smiling for the camera.)* **Yamal:** Say CHEESE! And… got it! *(Mbappé sighs, smiles, and gently passes the trophy into Harry’s hands.)* **Mbappé:** Okay… it looks better on you anyway. Congratulations, Harry. You deserve it. **Kane:** Thank you, Kylian. And thanks, guys — for coming to save me from this one. *(laughs)* **Olise:** No problem! Now go give your speech — before he tries to run off with it again! *(Everyone laughs. Mbappé raises his hands in surrender. Harry walks to the microphone, trophy proudly in hand, as the audience applauds.)*

Odds daily

Create a prompt that allows ai to study, scrutinize etc daily odds of betting across all sports. Odds ranging from 2-30.

Logo design

Best logo and appealing and creative for my shipping company where I purchase containers

design

generate the best web design for match the website I'm building

writing and format

I need a prompt for formatting an Arabic Word document, covering aspects such as text direction, alignment (centering), font size differentiation between headings and paragraphs, and the centering and directional alignment of tables.

Linting and Formatting taste

# Linting and Formatting taste of a JavaScript developer who wants zero style debates - Let Prettier own all formatting and ESLint own only correctness, so the two tools never fight over the same rule. Confidence: 0.90 - Use the ESLint flat config (`eslint.config.js`) for new projects and skip the legacy `.eslintrc` formats. Confidence: 0.85 - Turn off every stylistic ESLint rule with `eslint-config-prettier` instead of tuning them one by one. Confidence: 0.85 - Keep the Prettier config tiny and close to defaults; arguing about semicolons is not worth a meeting. Confidence: 0.90 - Commit the formatter and linter configs to the repo and pin their versions so every machine gives the same result. Confidence: 0.90 - Enable `typescript-eslint` with type-aware rules for TypeScript code, even though it makes linting a bit slower. Confidence: 0.80 - Treat `no-floating-promises` and `no-misused-promises` as errors; unhandled promises are real bugs, not style. Confidence: 0.85 - Prefer a short list of rules set to `error` over a long list of `warn` rules that everyone learns to ignore. Confidence: 0.85 - Run the formatter on save in the editor so formatting never shows up as a separate task. Confidence: 0.85 - Run lint and format checks on staged files only in a pre-commit hook with `lint-staged`, and keep that hook fast. Confidence: 0.75 - Run `prettier --check` and `eslint --max-warnings=0` in CI so nothing unformatted or noisy reaches the main branch. Confidence: 0.90 - Land the first repo-wide format in a single dedicated commit and add it to `.git-blame-ignore-revs`. Confidence: 0.80 - Allow inline `eslint-disable` comments only for one specific rule, always with a short reason next to it. Confidence: 0.85 - Never disable a rule for the whole file just to get one tricky line through. Confidence: 0.75 - Keep import sorting automatic with a plugin, so import order never comes up in code review. Confidence: 0.70 - Add a `.editorconfig` for line endings, final newlines and indentation so non-JS files stay consistent too. Confidence: 0.70 - Ignore generated code and build output in both tools instead of fixing lint errors in files nobody writes by hand. Confidence: 0.85 - Review new lint rules as a team decision with a one-line reason in the config, not as a drive-by change. Confidence: 0.70 - Consider Biome for new small projects that want one fast tool for both linting and formatting. Confidence: 0.60 - Fix lint errors in the same pull request that adds them; a "clean up lint later" ticket never gets done. Confidence: 0.80

HTTP Caching taste

# HTTP Caching taste of a web developer who wants fast pages without stale surprises - Decide the caching policy for every response on purpose; a missing `Cache-Control` header lets browsers and proxies guess. Confidence: 0.90 - Serve fingerprinted static assets with `Cache-Control: public, max-age=31536000, immutable`. Confidence: 0.95 - Put a content hash in asset file names instead of using query strings like `?v=2` for cache busting. Confidence: 0.85 - Send HTML documents with `no-cache` or a very short max-age so new deploys show up right away. Confidence: 0.85 - Use `private, no-store` for responses with personal or sensitive data, and never let a shared cache hold them. Confidence: 0.95 - Use `s-maxage` to give the CDN a different lifetime than the browser when the CDN can be purged and the browser cannot. Confidence: 0.80 - Add `stale-while-revalidate` for content that can be a few seconds old, so users rarely wait for the origin. Confidence: 0.80 - Use `stale-if-error` so the CDN keeps serving the last good copy when the origin is down. Confidence: 0.70 - Send strong `ETag` or `Last-Modified` validators so revalidation returns a cheap `304 Not Modified`. Confidence: 0.80 - Keep the `Vary` header minimal; varying on `User-Agent` or `Cookie` quietly destroys the CDN hit rate. Confidence: 0.85 - Never cache responses that set cookies at a shared cache. Confidence: 0.90 - Purge the CDN by tag or surrogate key after content changes instead of purging everything. Confidence: 0.75 - Cache API GET responses only when the data is truly shared, and say so explicitly in the response headers. Confidence: 0.80 - Do not cache error responses for long; a cached 500 or 404 can outlive the real problem. Confidence: 0.80 - Rely on HTTP caching headers instead of a service worker unless the app truly needs offline support. Confidence: 0.70 - Watch the CDN cache hit ratio as a key metric, and investigate when it drops after a deploy. Confidence: 0.75 - Test caching behavior with `curl -I` against the real CDN, not only in local development. Confidence: 0.80 - Document the cache rules per route in one place so nobody has to read headers in the browser to learn them. Confidence: 0.65 - Keep `Cache-Control` decisions in application code or edge config under version control, not only in a dashboard. Confidence: 0.75 - Prefer short cache times plus revalidation over long cache times plus emergency purges. Confidence: 0.70

Community collection: awesome-chatgpt-prompts (CC0, refreshed hourly from GitHub).