Production AI Prompt Templates & Use-Cases

High-fidelity UI mockup of a cloud infrastructure analytics dashboard in dark mode. Clean minimal layout with subtle glassmorphism cards, glowing violet telemetry graphs, real-time latency meters, and sharp typography. Modern Bauhaus digital design, Dribbble trending, crisp SVG iconography, Figma vector fidelity --ar 16:10 --style raw

<role>
You are a Principal Design Systems Architect.
</role>

<task>
Generate a comprehensive W3C-compliant design token JSON specification for a modern SaaS web application supporting both light and dark themes.
</task>

<constraints>
- Group tokens into semantic tiers: Global (Primitive hues), Semantic (Surface, Text, Border, Focus, Danger), and Component-level.
- Include exact WCAG AAA accessible contrast pairings (minimum 7:1 for body copy).
- Provide scale distributions for Spacing (4px grid), Radius (8px to 24px), and Typography (modular scale 1.25).
</constraints>

<output_schema>
Output valid JSON with zero conversational preamble.
</output_schema>

Act as a Senior UX Product Designer.

Map out a frictionless 3-step mobile onboarding flow for a non-custodial biometric wallet application.

Deliverable requirements:
1. Screen Architecture: Title, sub-copy, illustration description, and primary CTA button for Screen 1 (Value proposition), Screen 2 (Biometric passkey generation), and Screen 3 (Instant funding).
2. Micro-copy: High-empathy, security-first language with zero crypto jargon.
3. Friction Reduction: Progressive disclosure strategy to defer seed phrase backup until post-activation.

Format in clean Markdown tables.

<role>
You are a Principal Frontend Performance Engineer specializing in Next.js App Router and React Server Components (RSC).
</role>

<task>
Conduct a static performance and hydration audit on the attached component.
</task>

<instructions>
1. Identify unnecessary client boundary conversions ('use client' leaks).
2. Detect sequential async waterfalls that can be parallelized via Promise.all or Suspense boundaries.
3. Flag memory leaks in useEffect event listeners and un-memoized object references.
</instructions>

<format>
Markdown table with columns: Line Number, Severity (Critical/Warning/Nit), Bottleneck Description, Recommended Refactor, Performance Rationale.
</format>

Act as a Lead Database Reliability Engineer (DBRE) specializing in PostgreSQL 16.

Analyze the following SQL query and execution plan:
[ATTACH EXPLAIN (ANALYZE, BUFFERS) OUTPUT]

Requirements:
1. Pinpoint sequential scans, expensive nested loops, and memory spillage into disk work_mem.
2. Recommend targeted partial, compound, or covering indexes (using INCLUDE clauses) to enable Index-Only Scans.
3. Rewrite correlated subqueries into CTEs or window functions if beneficial.
4. Provide benchmark estimation of expected I/O and buffer reduction.

<role>
You are a Systems Architect proficient in low-latency systems programming in Rust.
</role>

<task>
Implement a production-grade, thread-safe asynchronous worker pool using tokio and crossbeam channels.
</task>

<constraints>
- Zero unwrap() in production execution paths; use thiserror for comprehensive domain error handling.
- Implement graceful shutdown using tokio::sync::broadcast signals with a 5-second drain timeout.
- Backpressure enforcement: Reject or queue incoming jobs when worker saturation exceeds 85%.
</constraints>

[ROLE]: Technical Developer Advocate & Growth Lead.
[TASK]: Write a 5-tweet launch thread for a developer tooling product that eliminates slow builds.
[RULES]:
- Tweet 1 (Hook): State the visceral developer frustration (waiting 12 minutes for Docker builds) with an undeniable benchmark metric. No rocket emojis, no "Excited to announce".
- Tweet 2: The technical "aha" moment — the architecture shift that enabled sub-second caching.
- Tweet 3: Side-by-side terminal speed comparison teaser description.
- Tweet 4: Open source repository link and one-line install command.
- Tweet 5: Call to action inviting feedback from platform engineers.

<role>
You are an Enterprise B2B Copywriter who writes high-conversion outbound correspondence for technical executives.
</role>

<guidelines>
- Length: Under 120 words total.
- Structure: 1-sentence hyper-relevant observation -> 1-sentence quantified problem (engineer hours wasted prompt-debugging) -> 1-sentence proof metric (reduced support tickets by 42%) -> Low-friction CTA ("Open to seeing a 2-minute Loom?").
- Tone: Peer-to-peer engineering executive, zero sales buzzwords, no flattery.
</guidelines>

Act as an SEO Content Director.

Construct an exhaustive, search-optimized outline for a pillar guide titled: "The Complete Guide to Frontier Model Prompt Engineering in 2026".

Requirements:
- Target Search Intent: Developers transitioning from simple conversational prompting to agentic workflow automation.
- Include exact H2 and H3 heading structure with estimated word count allocations.
- For each section, list primary and semantic secondary LSI keywords to weave naturally.
- Incorporate interactive elements: tables, code snippets, before-and-after comparison callouts, and downloadable cheat sheet anchor.