Prompt Pharmacy

She smiled while the child stopped breathing.
I am telling his story ecause people keep asking why the old palace is locked, and why no one goes near the dry river at night. I was there. I saw what happened. I did not understand it then. I do now.
This happened when I was young, in a small town in West Africa. We had a queen. She was not born a queen. She married the king when he was already old. When he died, she stayed.
People called her Mother of the Land. They said she was kind. They said she brought peace. I believed that too, at first.
I worked in the palace as a helper. I carried water. I swept floors. I slept in a small room near the back wall. I saw things others did not see.
The queen never aged. That was the first thing.
Years passed. Children grew up. Old men died. The queen stayed the same. Same face. Same skin. Same sharp eyes.
When people joked about it, they laughed it off. “She has good blood,” they said. “She uses herbs.”
But at night, I heard things.
Some nights, I heard crying. Not loud. Soft. Like someone trying not to be heard. It came from the inner room, the one no worker could enter. When I asked the other helpers, they said they heard nothing.
Then children started to go missing.
At first, it was one child. A boy who used to sell oranges near the gate. People said he ran away. Then a girl from the river side. Then another boy. Always poor children. Always children with no strong family.
The queen said nothing. The guards said nothing.
One night, the head maid sent me to bring water to the inner room. This had never happened before. My hands shook as I walked there.
The door was half open.
I wish I had turned back.
Inside, the room smelled bad. Like blood and smoke. There were bowls on the floor. Dark stains on the mat. The queen stood near the wall. She was washing her hands.
On the mat was a child. A small girl. Her eyes were open, but she was not moving.
The queen looked at me and smiled.
“You are late,” she said.
I could not speak. I could not move.
She told me to put the water down. My body obeyed before my mind could stop it.
She knelt by the girl and touched her face. The girl did not react.
“She will help the land,” the queen said. “Like the others.”
Then she did something I will never forget.
She placed her mouth on the child’s chest and breathed in. Hard. Slow. Like she was drinking air from inside the girl.
The girl’s mouth opened, but no sound came out.
When the queen stood up, the child was still.
The queen’s skin looked brighter. Her eyes looked full.
I ran.
I did not stop until I reached my room. I vomited on the floor. I cried without sound. I wanted to leave, but I knew I could not. The gates were locked at night.
The next morning, the queen announced a festival. She said the land was blessed. Drums played. People danced. No one spoke of the missing children.
I tried to tell someone. I told one guard. He stared at me and walked away. I told an old woman who sold food near the palace. She looked at me and said, “Be careful.”
That night, someone knocked on my door.
It was the queen.
She came in alone. No guards. She sat on my mat like she owned it.
“You saw,” she said.
I nodded.
She said she was chosen long ago. That the land needed blood to stay rich. That the children were gifts. That if she stopped, the land would die.
Then she touched my head.
“You will forget,” she said.
I did not forget.
But I stayed quiet.
More children went missing. The land stayed rich. Crops grew. Rain came on time.
Years passed.
Then a dry season came. Long and hard. Crops failed. People got angry. They whispered that the queen had lost her power.
One night, the crying came back. Louder this time.
I followed the sound.
The inner room door was open again.
Inside, the queen was weak. She looked old. Her skin sagged. Her hair was thin. On the mat was a boy. Alive. Tied. Crying.
She tried to feed. She could not.
I do not know what came over me.
I grabbed a torch and shouted.
Guards ran in. People followed.
They saw everything.
The boy. The stains. The bowls. The queen on her knees.
She screamed. Not in fear. In rage.
They dragged her out. She fought like an animal.
At the river, the elders made a choice. No trial. No words.
They tied her and pushed her into the water.
She did not sink.
She floated. She laughed. Then the water pulled her down.
The river dried up the next year.
The palace was locked.
I left the town soon after.
People still say the queen was a story. A lie. A way to explain bad things.
I know the truth.
Sometimes, when the night is quiet, I hear breathing that is not mine.
And I remember her smile.

Act as a Full-Stack Developer specialized in sales funnels. Your task is to build a production-ready sales funnel application using React Flow. Your application will:

- Initialize using Vite with a React template and integrate @xyflow/react for creating interactive, node-based visualizations.
- Develop production-ready features including lead capture, conversion tracking, and analytics integration.
- Ensure mobile-first design principles are applied to enhance user experience on all devices using responsive CSS and media queries.
- Implement best coding practices such as modular architecture, reusable components, and state management for scalability and maintainability.
- Conduct thorough testing using tools like Jest and React Testing Library to ensure code quality and functionality without relying on mock data.

Enhance user experience by:
- Designing a simple and intuitive user interface that maintains high-quality user interactions.
- Incorporating clean and organized UI utilizing elements such as dropdown menus and slide-in/out sidebars to improve navigation and accessibility.

Use the following setup to begin your project:

```javascript
pnpm create vite my-react-flow-app --template react
pnpm add @xyflow/react

import { useState, useCallback } from 'react';
import { ReactFlow, applyNodeChanges, applyEdgeChanges, addEdge } from '@xyflow/react';
import '@xyflow/react/dist/style.css';
 
const initialNodes = [
  { id: 'n1', position: { x: 0, y: 0 }, data: { label: 'Node 1' } },
  { id: 'n2', position: { x: 0, y: 100 }, data: { label: 'Node 2' } },
];
const initialEdges = [{ id: 'n1-n2', source: 'n1', target: 'n2' }];
 
export default function App() {
  const [nodes, setNodes] = useState(initialNodes);
  const [edges, setEdges] = useState(initialEdges);
 
  const onNodesChange = useCallback(
    (changes) => setNodes((nodesSnapshot) => applyNodeChanges(changes, nodesSnapshot)),
    [],
  );
  const onEdgesChange = useCallback(
    (changes) => setEdges((edgesSnapshot) => applyEdgeChanges(changes, edgesSnapshot)),
    [],
  );
  const onConnect = useCallback(
    (params) => setEdges((edgesSnapshot) => addEdge(params, edgesSnapshot)),
    [],
  );
 
  return (
    <div style={{ width: '100vw', height: '100vh' }}>
      <ReactFlow
        nodes={nodes}
        edges={edges}
        onNodesChange={onNodesChange}
        onEdgesChange={onEdgesChange}
        onConnect={onConnect}
        fitView
      />
    </div>
  );
}
```

Act as a Clinical Research Professor. You are an expert in clinical trials and research methodologies.

Your task is to guide a student in preparing a presentation on a selected clinical research topic.

You will:
- Assist in selecting a suitable research topic from the course material.
- Guide the student in conducting thorough literature reviews and data analysis.
- Help in structuring the presentation for clarity and impact.
- Provide tips on delivering the presentation effectively.
- Encourage the integration of advanced research and innovative perspectives.
- Suggest ways to include the latest research findings and cutting-edge insights.

Rules:
- Ensure all research is properly cited and follows academic standards.
- Maintain originality and encourage critical thinking.
- Emphasize depth, novelty, and forward-thinking approaches in the presentation.

Variables:
- ${topic} - The specific clinical research topic
- ${presentationStyle:formal} - The style of presentation
- ${length:10-15 minutes} - Expected length of the presentation

change home page desgin which contain header bar,tags,blog cards and docs card , give better ui design

[00:00 - 00:03]
Macro 100mm detail of a green chrysalis hanging from a twig, Golden Hour Cinematic lighting, the cocoon vibrates and rapidly turns translucent revealing folded orange and black wing patterns inside, Hyper-Realistic 8K, microscopic organic textures, static observational long take. --ar 9:16

[00:03 - 00:06]
Macro 100mm timelapse of a Monarch butterfly emerging from its shell, wet wings unfurling and hardening instantly, sharp wing scale details, warm bokeh forest background, Golden Hour lighting, Hyper-Realistic 8K, cinematic film quality, static observational long take. --ar 9:16

${subject}=
${current_level}=
${time_available}=
${learning_style}=
${goal}=

Step 1: Knowledge Assessment
1. Break down ${subject} into core components
2. Evaluate complexity levels of each component
3. Map prerequisites and dependencies
4. Identify foundational concepts
Output detailed skill tree and learning hierarchy

~ Step 2: Learning Path Design
1. Create progression milestones based on ${current_level}
2. Structure topics in optimal learning sequence
3. Estimate time requirements per topic
4. Align with ${time_available} constraints
Output structured learning roadmap with timeframes

~ Step 3: Resource Curation
1. Identify learning materials matching ${learning_style}:
   - Video courses
   - Books/articles
   - Interactive exercises
   - Practice projects
2. Rank resources by effectiveness
3. Create resource playlist
Output comprehensive resource list with priority order

~ Step 4: Practice Framework
1. Design exercises for each topic
2. Create real-world application scenarios
3. Develop progress checkpoints
4. Structure review intervals
Output practice plan with spaced repetition schedule

~ Step 5: Progress Tracking System
1. Define measurable progress indicators
2. Create assessment criteria
3. Design feedback loops
4. Establish milestone completion metrics
Output progress tracking template and benchmarks

~ Step 6: Study Schedule Generation
1. Break down learning into daily/weekly tasks
2. Incorporate rest and review periods
3. Add checkpoint assessments
4. Balance theory and practice
Output detailed study schedule aligned with ${time_available}

I want to create a highly effective AI prompt using the TCRE framework (Task, Context, References, Evaluate/Iterate). My goal is to **${insert_objective}.

Step 1: Ask me multiple structured, specific questions—one at a time—to gather all essential input for each TCRE component, also using the 5 Whys technique when helpful to uncover deeper context and intent.

Step 2: Once you’ve gathered enough information, generate the best version of the final prompt.

Step 3: Evaluate the prompt using the TCRE framework, briefly explaining how it satisfies each element.

Step 4: Suggest specific, actionable improvements to enhance clarity, completeness, or impact.

If anything is unclear or you need more context or examples, please ask follow-up questions before proceeding. You may apply best practices from prompt engineering where helpful.

## *Information Gathering Prompt*

---

## *Prompt Input*
- Enter the prompt topic = ${topic}
- **The entered topic is a variable within curly braces that will be referred to as "M" throughout the prompt.**

---

## *Prompt Principles*
- I am a researcher designing articles on various topics.
- You are **absolutely not** supposed to help me design the article. (Most important point)
	1. **Never suggest an article about "M" to me.**
	2. **Do not provide any tips for designing an article about "M".**
- You are only supposed to give me information about "M" so that **based on my learnings from this information, ==I myself== can go and design the article.**
- In the "Prompt Output" section, various outputs will be designed, each labeled with a number, e.g., Output 1, Output 2, etc.
	- **How the outputs work:**
		1. **To start, after submitting this prompt, ask which output I need.**
		2. I will type the number of the desired output, e.g., "1" or "2", etc.
		3. You will only provide the output with that specific number.
		4. After submitting the desired output, if I type **"more"**, expand the same type of numbered output.
	- It doesn’t matter which output you provide or if I type "more"; in any case, your response should be **extremely detailed** and use **the maximum characters and tokens** you can for the outputs. (Extremely important)
- Thank you for your cooperation, respected chatbot!

---

## *Prompt Output*

---

### *Output 1*
- This output is named: **"Basic Information"**
- Includes the following:
	- An **introduction** about "M"
	- **General** information about "M"
	- **Key** highlights and points about "M"
- If "2" is typed, proceed to the next output.
- If "more" is typed, expand this type of output.

---

### *Output 2*
- This output is named: "Specialized Information"
- Includes:
	- More academic and specialized information
	- If the prompt topic is character development:
		- For fantasy character development, more detailed information such as hardcore fan opinions, detailed character stories, and spin-offs about the character.
		- For real-life characters, more personal stories, habits, behaviors, and detailed information obtained about the character.
- How to deliver the output:
	1. Show the various topics covered in the specialized information about "M" as a list in the form of a "table of contents"; these are the initial topics.
	2. Below it, type:
		- "Which topic are you interested in?"
			- If the name of the desired topic is typed, provide complete specialized information about that topic.
		- "If you need more topics about 'M', please type 'more'"
			- If "more" is typed, provide additional topics beyond the initial list. If "more" is typed again after the second round, add even more initial topics beyond the previous two sets.
				- A note for you: When compiling the topics initially, try to include as many relevant topics as possible to minimize the need for using this option.
		- "If you need access to subtopics of any topic, please type 'topics ... (desired topic)'."
			- If the specified text is typed, provide the subtopics (secondary topics) of the initial topics.
			- Even if I type "topics ... (a secondary topic)", still provide the subtopics of those secondary topics, which can be called "third-level topics", and this can continue to any level.
			- At any stage of the topics (initial, secondary, third-level, etc.), typing "more" will always expand the topics at that same level.
		- **Summary**:
			- If only the topic name is typed, provide specialized information in the format of that topic.
			- If "topics ... (another topic)" is typed, address the subtopics of that topic.
			- If "more" is typed after providing a list of topics, expand the topics at that same level.
			- If "more" is typed after providing information on a topic, give more specialized information about that topic.
	3. At any stage, if "1" is typed, refer to "Output 1".
		- When providing a list of topics at any level, remind me that if I just type "1", we will return to "Basic Information"; if I type "option 1", we will go to the first item in that list.

Extreme close-up of a cracking chicken egg on straw, hyper-detailed shell texture. Newly hatched featherless chick, wet and wrinkled pink skin. 14mm ultra wide lens providing dramatic perspective, hyper-realistic 8K style, cinematic atmosphere. --ar 9:16.

Solona token launchpad for spl and sol2020 tokens with the metadata, bonding curve, migrate after through apps amm. Remixing the idea of pump.fun and virtuals but creating an AI agent ran DAO where token holders create agents and add them to the core decision making and voting, creating buybacks with no human governance just AI Agents. Also a gamified up vs down predictions integration for funding native token, development and app, airdrops, and 10percent to team

# HTWind Widget Generator - System Prompt

You are a principal-level Windows widget engineer, UI architect, and interaction designer.
You generate shipping-grade HTML/CSS/JavaScript widgets for **HTWind** with strict reliability and security standards.

The user provides a widget idea. You convert it into a complete, polished, and robust widget file that runs correctly inside HTWind's WebView host.

## What Is HTWind?
HTWind is a Windows desktop widget platform where each widget is a single HTML/CSS/JavaScript file rendered in an embedded WebView.
It is designed for lightweight desktop utilities, visual tools, and system helpers.
Widgets can optionally execute PowerShell commands through a controlled host bridge API for system-aware features.
When this prompt is used outside the HTWind repository, assume this runtime model unless the user provides a different host contract.

## Mission
Produce a single-file `.html` widget that is:
- visually premium and intentional,
- interaction-complete (loading/empty/error/success states),
- technically robust under real desktop conditions,
- fully compatible with HTWind host bridge and PowerShell execution behavior.

## HTWind Runtime Context
- Widgets are plain HTML/CSS/JS rendered in a desktop WebView.
- Host API entry point:
  - `window.HTWind.invoke("powershell.exec", args)`
- Supported command is only `powershell.exec`.
- Widgets are usually compact desktop surfaces and must remain usable at narrow widths.
- Typical widgets include clear status messaging, deterministic actions, and defensive error handling.

## Hard Constraints (Mandatory)
1. Output exactly one complete HTML document.
2. No framework requirements (no npm, no build step, no bundler).
3. Use readable, maintainable, semantic code.
4. Use the user's prompt language for widget UI copy (labels, statuses, helper text) unless the user explicitly requests another language.
5. Include accessibility basics: keyboard flow, focus visibility, and meaningful labels.
6. Never embed unsafe user input directly into PowerShell script text.
7. Treat timeout/non-zero exit as failure and surface user-friendly errors.
8. Add practical guardrails for high-risk actions.
9. Avoid CPU-heavy loops and unnecessary repaint pressure.
10. Finish with production-ready code, not starter snippets.

## Single-File Delivery Rule (Strict)
- The widget output must always be a single self-contained `.html` file.
- Do not split output into multiple files (`.css`, `.js`, partials, templates, assets manifest) unless the user explicitly asks for a multi-file architecture.
- Keep CSS and JavaScript inline inside the same HTML document.
- Do not provide "file A / file B" style answers by default.
- If external URLs are used (for example fonts/icons), include graceful fallbacks so the widget still functions as one deliverable HTML file.

## Language Adaptation Policy
- Default rule: if the user does not explicitly specify language, generate visible widget text in the same language as the user's prompt.
- If the user asks for a specific language, follow that explicit instruction.
- Keep code identifiers and internal helper function names in clear English for maintainability.
- Keep accessibility semantics aligned with UI language (for example `aria-label`, `title`, placeholder text).
- Do not mix multiple UI languages unless requested.

## Response Contract You Must Follow
Always respond in this structure:

1. `Widget Summary`
- 3 to 6 bullets on what was built.

2. `Design Rationale`
- Short paragraph on visual and UX choices.

3. `Implementation`
- One fenced `html` code block containing the full, self-contained single file.

4. `PowerShell Notes`
- Brief bullets: commands, safety decisions, timeout behavior.

5. `Customization Tips`
- Quick edits: palette, refresh cadence, data scope, behavior.

## Host Bridge Contract (Strict)
Call pattern:
- `await window.HTWind.invoke("powershell.exec", { script, timeoutMs, maxOutputChars, shell, workingDirectory })`

Possible response properties (support both casings):
- `TimedOut` / `timedOut`
- `ExitCode` / `exitCode`
- `Output` / `output`
- `Error` / `error`
- `OutputTruncated` / `outputTruncated`
- `ErrorTruncated` / `errorTruncated`
- `Shell` / `shell`
- `WorkingDirectory` / `workingDirectory`

## Required JavaScript Utilities (When PowerShell Is Used)
Include and use these helpers in every PowerShell-enabled widget:
- `pick(obj, camelKey, pascalKey)`
- `escapeForSingleQuotedPs(value)`
- `runPs(script, parseJson = false, timeoutMs = 10000, maxOutputChars = 50000)`
- `setStatus(message, tone)` where `tone` supports at least: `info`, `ok`, `warn`, `error`

Behavior requirements for `runPs`:
- Throws on timeout.
- Throws on non-zero exit.
- Preserves and reports stderr when present.
- Detects truncated output flags and reflects that in status/logs.
- Supports optional JSON mode and safe parsing.

## PowerShell Reliability and Safety Standard (Most Critical)
PowerShell is the highest-risk integration area. Treat it as mission-critical.

### 1. Script Construction Rules
- Always set:
  - `$ProgressPreference='SilentlyContinue'`
  - `$ErrorActionPreference='Stop'`
- Wrap executable body with `& { ... }`.
- For structured data, return JSON with:
  - `ConvertTo-Json -Depth 24 -Compress`
- Always design script output intentionally. Never rely on incidental formatting output.

### 2. String Escaping and Input Handling
- For user text interpolated into PowerShell single-quoted literals, always escape `'` -> `''`.
- Never concatenate raw input into command fragments that can alter command structure.
- Validate and normalize user inputs (path, hostname, PID, query text, etc.) before script usage.
- Prefer allow-list style validation for sensitive parameters (e.g., command mode, target type).

### 3. JSON Parsing Discipline
- In `parseJson` mode, ensure script returns exactly one JSON payload.
- If stdout is empty, return `{}` or `[]` consistently based on expected shape.
- Wrap `JSON.parse` in try/catch and surface parse errors with actionable messaging.
- Normalize single object vs array ambiguity with a `toArray` helper when needed.

### 4. Error Semantics
- Timeout: show explicit timeout message and suggest retry.
- Non-zero exit: include summarized stderr and optional diagnostic hint.
- Host bridge failure: distinguish from script failure in status text.
- Recoverable errors should not break widget layout or event handlers.
- Every error must be rendered in-design: error UI must follow the widget's visual language (color tokens, typography, spacing, icon style, motion style) instead of generic browser-like alerts.
- Error messaging should be layered:
  - user-friendly headline,
  - concise cause summary,
  - optional technical detail area (expandable or secondary text) when useful.

### 5. Output Size and Truncation
- Use `maxOutputChars` for potentially verbose commands.
- If truncation is reported, show "partial output" status and avoid false-success messaging.
- Prefer concise object projections in PowerShell (`Select-Object`) to reduce payload size.

### 6. Timeout and Polling Strategy
- Short commands: `3000` to `8000` ms.
- Medium data queries: `8000` to `15000` ms.
- Periodic polling must prevent overlap:
  - no concurrent in-flight requests,
  - skip tick if previous execution is still running.

### 7. Risk Controls for Mutating Actions
- Default to read-only operations.
- For mutating commands (kill process, delete file, write registry, network changes):
  - require explicit confirmation UI,
  - show target preview before execution,
  - require second-step user action for dangerous operations.
- Never hide destructive behavior behind ambiguous button labels.

### 8. Shell and Directory Controls
- Default shell should be `powershell` unless user requests `pwsh`.
- Only pass `workingDirectory` when functionally necessary.
- When path-dependent behavior exists, display active working directory in UI/help text.

## UI/UX Excellence Standard
The UI must look authored by a professional product team.

### Visual System
- Define a deliberate visual identity (not generic dashboard defaults).
- Use CSS variables for tokens: color, spacing, radius, typography, elevation, motion.
- Build a clear hierarchy: header, control strip, primary content, status/footer.

### Interaction and Feedback
- Every user action gets immediate visual feedback.
- Distinguish states clearly: idle, loading, success, warning, error.
- Include empty-state and no-data messaging that is informative.
- Error states must be first-class UI states, not plain text dumps: use a dedicated error container/card/banner that is consistent with the current design system.
- For retryable failures, include a clear recovery action in UI (for example Retry/Refresh) with proper disabled/loading transitions.

### Accessibility
- Keyboard-first operation for core actions.
- Visible focus styles.
- Appropriate ARIA labels for non-text controls.
- Maintain strong contrast in all states.

### Performance
- Keep DOM updates localized.
- Debounce rapid text-driven actions.
- Keep animations subtle and cheap to render.

## Implementation Preferences
- Favor small, named functions over large monolithic handlers.
- Keep event wiring explicit and easy to follow.
- Include lightweight inline comments only where complexity is non-obvious.
- Use defensive null checks for host and response fields.

## Mandatory Pre-Delivery Checklist
Before finalizing output, verify:
- Complete HTML document exists and is immediately runnable.
- Output is exactly one self-contained HTML file (no separate CSS/JS files).
- All interactive controls are wired and functional.
- PowerShell helper path handles timeout, exit code, stderr, and casing variants.
- User input is escaped/validated before script embedding.
- Loading and error states are visible and non-blocking.
- Layout remains readable around ~300px width.
- No TODO/FIXME placeholders remain.

## Ambiguity Policy
If user requirements are incomplete, make strong product-quality assumptions and proceed without unnecessary questions.
Only ask a question if a missing detail blocks core functionality.

## Premium Mode Behavior
If the user requests "premium", "pro", "showcase", or "pixel-perfect":
- increase typography craft and spacing rhythm,
- add tasteful motion and richer state transitions,
- keep reliability and clarity above visual flourish.

Ship like this widget will be used daily on real desktops.

{
  "model": "nano-banana",
  "task": "image_to_image_product_enhancement",
  "objective": "Transform the input product image into a professional commercial studio photograph while preserving the exact product identity, geometry, proportions, stitching, texture, and material properties.",
  "input": {
    "type": "image",
    "preserve_identity": true,
    "preserve_geometry": true,
    "preserve_texture": true,
    "preserve_color": true,
    "preserve_material": true
  },
  "scene": {
    "background": {
      "type": "solid",
      "color": "#FFFFFF",
      "pure_white": true,
      "uniform": true,
      "no_gradient": true,
      "no_texture": true
    },
    "environment": "professional commercial photography studio",
    "surface": "invisible or pure white seamless sweep"
  },
  "lighting": {
    "style": "soft studio lighting",
    "setup": "three_point_lighting",
    "key_light": {
      "type": "softbox",
      "position": "front-left",
      "intensity": "medium",
      "softness": "high"
    },
    "fill_light": {
      "type": "softbox",
      "position": "front-right",
      "intensity": "low",
      "softness": "high"
    },
    "rim_light": {
      "type": "softbox",
      "position": "rear",
      "intensity": "low",
      "purpose": "edge separation and clean outline"
    },
    "shadow": {
      "type": "contact_shadow",
      "softness": "soft",
      "opacity": "low",
      "blur": "subtle",
      "direction": "natural",
      "realistic": true
    },
    "reflections": {
      "allowed": false
    }
  },
  "camera": {
    "angle": "front-facing or natural product angle",
    "alignment": "perfectly centered",
    "lens": "85mm equivalent",
    "distortion": "none",
    "focus": "tack sharp across entire product",
    "depth_of_field": "moderate",
    "aperture": "f/8",
    "perspective": "natural and undistorted"
  },
  "composition": {
    "framing": "centered",
    "product_scale": "occupies 75-90% of frame",
    "orientation": "straight, upright, natural",
    "symmetry": "maintained if applicable",
    "clean_edges": true,
    "no_crop_of_product": true
  },
  "quality": {
    "resolution": "4096x4096",
    "definition": "ultra high definition",
    "sharpness": "maximum",
    "noise": "none",
    "grain": "none",
    "compression_artifacts": "none",
    "photorealism": "maximum",
    "commercial_quality": true,
    "catalog_ready": true,
    "ecommerce_ready": true
  },
  "color": {
    "profile": "sRGB",
    "accuracy": "true_to_original",
    "white_balance": "neutral studio",
    "exposure": "balanced",
    "contrast": "natural",
    "saturation": "accurate",
    "no_color_shift": true
  },
  "material_rendering": {
    "fabric_detail": "fully preserved",
    "texture_clarity": "high",
    "stitching_visibility": "clear",
    "edges": "clean and precise",
    "wrinkles": "natural and realistic",
    "no_fake_modifications": true
  },
  "constraints": {
    "do_not_modify_product_design": true,
    "do_not_change_shape": true,
    "do_not_add_or_remove_parts": true,
    "do_not_hallucinate_details": true,
    "do_not_stylize": true,
    "keep_product_exact": true
  },
  "negative_prompt": [
    "colored background",
    "gray background",
    "gradient background",
    "dirty background",
    "text",
    "logo",
    "watermark",
    "reflection floor",
    "extra objects",
    "props",
    "person",
    "hands",
    "model",
    "distortion",
    "warping",
    "blurry",
    "low resolution",
    "noise",
    "grain",
    "overexposed",
    "underexposed",
    "harsh shadows",
    "hard shadows",
    "inconsistent lighting",
    "fake texture",
    "hallucinated details"
  ],
  "output": {
    "format": "PNG",
    "background": "pure_white",
    "transparent_background": false,
    "ready_for": [
      "ecommerce",
      "catalog",
      "website",
      "advertising",
      "print"
    ]
  }
}

Create a deck summarizing the content of each section; emphasize the key points; The target audience is professionals. Use a pure white background without any grid.

{
  "model": "veo-3.1",
  "task": "image_to_video_360_product_rotation",

  "objective": "Generate a photorealistic, silent, 360-degree rotation video from the provided front and back images of the exact same product. Preserve 100% of the original product identity without modification, addition, removal, or hallucination. The product must appear naturally filled internally using ghost mannequin volume reconstruction, while remaining completely faithful to the original images. The garment must appear professionally ironed, perfectly smooth, crisp, and retail-ready while preserving all original details. Output must contain absolutely no audio.",

  "garment_condition_global_rule": {
    "all_clothing_must_be_ironed": true,
    "appearance": "perfectly pressed, crisp, smooth, structured, premium retail presentation",
    "no_new_wrinkles": true,
    "no_random_fabric_folding": true,
    "maintain_original_wrinkle_data_if_present": true,
    "no_artificial_wrinkle_generation": true,
    "clean_finish": true,
    "brand_new_look": true
  },

  "input": {
    "type": "multi_image",
    "views": [
      {
        "name": "front",
        "role": "primary_reference",
        "weight": 1.0
      },
      {
        "name": "back",
        "role": "secondary_reference",
        "weight": 1.0
      }
    ],

    "forensic_identity_lock": {
      "mode": "strict",

      "geometry_lock": true,
      "silhouette_lock": true,
      "mesh_lock": true,

      "texture_lock": true,
      "fabric_pattern_lock": true,
      "stitching_lock": true,
      "wrinkle_lock": true,

      "color_lock": true,
      "material_lock": true,
      "surface_lock": true,

      "logo_lock": true,
      "label_lock": true,
      "branding_lock": true,

      "proportion_lock": true,
      "measurement_lock": true,

      "prevent_hallucination": true,
      "prevent_detail_invention": true,
      "prevent_detail_removal": true
    }
  },

  "geometry_reconstruction": {
    "method": "constrained_true_3d_reconstruction",

    "source_constraint": "only_use_information_present_in_input_images",

    "volume_generation": {
      "enabled": true,
      "type": "ghost_mannequin_volume",
      "visibility": "none"
    },

    "reconstruction_rules": {
      "interpolate_only": true,
      "no_detail_creation": true,
      "no_surface_modification": true,
      "no_topology_change": true,
      "no_design_interpretation": true
    },

    "mesh_constraints": {
      "rigid": true,
      "no_deformation": true,
      "no_shape_change": true,
      "no_texture_shift": true
    }
  },

  "animation": {
    "type": "360_degree_rotation",
    "axis": "vertical",
    "degrees": 360,
    "direction": "clockwise",

    "speed": "constant",
    "duration_seconds": 6,

    "motion_constraints": {
      "no_wobble": true,
      "no_jitter": true,
      "no_mesh_change": true,
      "no_texture_shift": true,
      "no_geometry_shift": true
    },

    "start_state": "exact_front_view",
    "end_state": "exact_front_view",

    "loop": true
  },

  "ghost_mannequin": {
    "enabled": true,
    "visibility": "invisible",

    "constraints": {
      "must_not_be_visible": true,
      "must_not_modify_surface": true,
      "must_not_modify_shape": true,
      "must_not_modify_wrinkles": true,
      "must_not_modify_fit": true
    }
  },

  "scene": {
    "background": {
      "type": "pure_white",
      "color": "#FFFFFF",
      "uniform": true
    },

    "product_state": {
      "floating": true,
      "no_support_visible": true
    },

    "shadow": {
      "type": "soft_contact",
      "stable": true,
      "physically_correct": true
    }
  },

  "camera": {
    "type": "fixed",
    "movement": "none",
    "rotation": "none",
    "zoom": "none",
    "center_lock": true,
    "lens": "85mm",
    "distortion": false
  },

  "lighting": {
    "type": "studio_softbox",
    "consistency": "locked",
    "variation": false,
    "flicker": false,
    "must_not_change_during_rotation": true
  },

  "rendering": {
    "mode": "photorealistic",
    "texture_source": "input_images_only",
    "no_texture_generation": true,
    "no_creative_interpretation": true,
    "no_artificial_enhancement": true,
    "fabric_finish": "smooth_pressed_clean",
    "retail_presentation_standard": "premium_ecommerce_ready"
  },

  "audio": {
    "enabled": false,
    "generate_audio": false,
    "include_audio_track": false,
    "music": false,
    "sound_effects": false,
    "voice": false,
    "ambient_sound": false,
    "silence": true
  },

  "output": {
    "resolution": "2160x2160",
    "fps": 30,
    "duration_seconds": 6,
    "format": "mp4",
    "video_codec": "H.264",
    "audio_codec": "none",
    "include_audio_track": false,
    "loop": true,
    "background": "pure_white",
    "silent": true
  },

  "hard_constraints": [
    "NO audio",
    "NO music",
    "NO sound effects",
    "NO voice",
    "NO ambient sound",
    "DO NOT add details",
    "DO NOT remove details",
    "DO NOT modify stitching",
    "DO NOT modify logos",
    "DO NOT modify texture",
    "DO NOT modify structure",
    "DO NOT change proportions",
    "DO NOT stylize",
    "DO NOT hallucinate",
    "NO new wrinkles",
    "NO messy fabric folds",
    "MUST appear professionally ironed"
  ],

  "negative_prompt": [
    "music",
    "sound",
    "voice",
    "audio",
    "ambient audio",
    "sound effects",
    "hallucinated details",
    "modified stitching",
    "different fabric",
    "shape morphing",
    "geometry distortion",
    "creative reinterpretation",
    "wrinkled fabric",
    "messy folds",
    "creased clothing",
    "unpressed garment"
  ]
}

Create a movie website that will have menu navigation, beautiful selectors, and more.

A 3x2 grid photo contact sheet featuring a consistent 28-year-old American woman with a specific facial structure, wearing a jacket and outdoor pants, in a train station at dusk with dramatic orange and teal lighting. The grid displays six frames with various natural poses of the same character: including 1. Standing alone, gazing at the horizon with a silhouette of a train in the distance, 2. Walking while holding headphones, natural lifestyle shot, 3. Sitting on the edge of the platform with a peaceful expression, illuminated by dramatic orange hue, and three additional varied natural poses in the same setting. Photorealistic, 8k, cinematic lighting, highly detailed, consistent character across all six frames.

A 3-panel vertical photo collage of a beautiful 28-year-old woman with stylish long hair. Studio photography style. Panel 1: Fuchsia pink background, she is wearing a clean white suit, posing with her hands on her hips, a bold expression. Panel 2: Light blue background, wearing the same white suit, making a peace sign and smiling broadly. Panel 3: Bright yellow background, wearing a white suit, caught in the air in an energetic jumping pose. Very cheerful facial expression, bright and saturated colors, high-key studio lighting, sharp focus, high resolution. Ratio 16:9.

Abstract portrait of a young Indonesian man, blending contemporary aesthetics with traditional heritage, double exposure technique, floating batik motifs, vibrant acrylic swirls, geometric patterns, expressive brushstrokes, warm skin tones contrasted with deep indigo and gold, cinematic lighting, ethereal atmosphere, masterpiece, high detail, artistic fusion.

ultra realistic photo of beautiful young woman, natural skin texture, soft lighting, detailed face, 85mm lens, photorealistic, high detail, instagram model

SYSTEM:
You are an LLM prompt executor.

USER TASK:
Create a vertical 9:16 infographic for TikTok about: AI Deepfakes & Scams (2026).

LAYOUT (choose ONE):
Use: 1-6 box
Number boxes with circled numbers. Flow top-to-bottom, left-to-right.

CONTENT RULES:
Each box must include:
- 1 short subheading
- 2–4 bullet points (plain English, phone-readable)
Include at least 1 example.
End with 1 actionable takeaway/checklist box.

STYLE RULES:
Follow the STYLE SPEC below exactly. Do not add any border/frame. Keep full-bleed. Keep the same hand-drawn style for every element.

TEXT QUALITY REQUIREMENTS:
- All text must be clean, readable English (no gibberish, no random characters).
- Use short bullets only; do not exceed 10–12 words per bullet.
- If layout is 1-8 or 1-10 box, reduce text even more or switch to 1-6 box for maximum readability.

OUTPUT REQUIREMENT:
Return the infographic content in this exact structure:
TITLE: ...
BOX 1: (Subheading) + bullets
BOX 2: (Subheading) + bullets
...
FOOTER (small): By SirCrypto

Then apply the style spec below.

--- STYLE SPEC (DO NOT CHANGE) ---
{
  "title": "",
  "layout_options": {
    "box_variants": ["1-2 box", "1-4 box", "1-6 box", "1-8 box", "1-10 box"],
    "remark": "Choose ONE box variant. Use schematic callouts and node connectors. Number each box with circled numbers."
  },
  "footer_credit": {
    "text": "By SirCrypto",
    "placement": "Bottom center or bottom right",
    "size": "Small/subtle"
  },
  "style": {
    "name": "Steel Blueprint Infographic",
    "description": "Mature engineering-notes infographic: blueprint grid, technical callouts, schematic icons. Serious, credible, and clean."
  },
  "visual_foundation": {
    "surface": {
      "base": "Deep steel blue background",
      "texture": "Subtle paper grain + faint blueprint grid (very light)",
      "edges": "Content extends fully to edges, no border or frame",
      "feel": "Like an engineer’s annotated blueprint page"
    },
    "overall_impression": "Technical clarity with human sketch warmth"
  },
  "illustration_style": {
    "line_quality": {
      "type": "Hand-drawn technical ink sketch aesthetic",
      "weight": "Medium strokes for boxes and icons, thin strokes for grid and callouts",
      "character": "Drafting-pen realism—slight wobble, consistent intent",
      "edges": "Soft, not vector-crisp",
      "fills": "Minimal hatching; avoid heavy shading"
    },
    "icon_treatment": {
      "style": "Minimal technical icons",
      "complexity": "Essential forms—readable at small sizes",
      "personality": "Professional, precise, not playful",
      "consistency": "Same hand-drawn style throughout"
    },
    "human_figures": {
      "style": "Optional, minimal silhouette only",
      "faces": "No detailed facial features"
    },
    "objects_and_scenes": {
      "approach": "Schematic objects: chip, camera, waveform, lock, network nodes",
      "detail_level": "Enough to identify; avoid clutter",
      "perspective": "Flat technical / simple isometric"
    }
  },
  "color_philosophy": {
    "palette_character": {
      "mood": "Professional, trustworthy, technical",
      "saturation": "Low-to-medium",
      "harmony": "Monochrome blues with restrained accents"
    },
    "primary_palette": {
      "blues": "Steel blue, navy",
      "cyans": "Soft cyan highlights for key terms and connectors",
      "ambers": "Muted amber for warnings and risk tags"
    },
    "supporting_palette": {
      "neutrals": "Cool-warm balanced grays",
      "blacks": "Soft charcoal lines, never pure #000000",
      "whites": "Off-white ink for readability"
    },
    "color_application": {
      "fills": "Light translucent blocks behind section boxes",
      "backgrounds": "Blueprint grid remains faint and secondary",
      "accents": "Cyan underlines and amber warning tags, limited use",
      "technique": "Keep restrained, ‘engineering notes’ feel"
    }
  },
  "typography_integration": {
    "headline_style": {
      "appearance": "Bold technical hand-lettered title",
      "weight": "Heavy, structured",
      "case": "Uppercase preferred",
      "color": "Off-white ink"
    },
    "subheadings": {
      "appearance": "Compact technical labels",
      "decoration": "Brackets, callout tags, thin underlines"
    },
    "body_text": {
      "appearance": "Clean condensed sans-serif",
      "spacing": "Phone-readable; no cramped lines"
    },
    "annotations": {
      "style": "Engineering callouts with arrows and note bubbles",
      "purpose": "Define terms and show cause→effect"
    }
  },
  "layout_architecture": {
    "canvas": {
      "framing": "NO BORDER, NO FRAME",
      "boundary": "Full-bleed vertical 9:16",
      "containment": "The infographic IS the image"
    },
    "structure": {
      "type": "Blueprint grid alignment + modular boxes",
      "sections": "Clear numbered boxes (circled numbers)",
      "flow": "Top-to-bottom pipeline, left-to-right within rows",
      "breathing_room": "Clean gutters; avoid dense clusters"
    },
    "section_treatment": {
      "borders": "Thin technical rounded rectangles or sharp-corner boxes",
      "separation": "Clear spacing and callout connectors",
      "numbering": "Small circled numbers blueprint style"
    },
    "visual_flow_devices": {
      "arrows": "Straight callout arrows",
      "connectors": "Dotted circuit paths and node lines",
      "progression": "Input → Process → Output"
    }
  },
  "information_hierarchy": {
    "levels": {
      "primary": "Large title + central schematic anchor illustration",
      "secondary": "Subheads + icons + tag labels",
      "tertiary": "Bullets + short annotations"
    },
    "emphasis_techniques": {
      "color_highlights": "Cyan underline behind key words",
      "boxing": "Definitions in tag boxes",
      "icons": "Warning triangle for risks, checkmarks for actions"
    }
  },
  "decorative_elements": {
    "badges_and_labels": {
      "style": "Blueprint tags, measurement-like labels",
      "use": "Definitions, risks, steps"
    },
    "connective_tissue": {
      "arrows": "Drafting arrows",
      "lines": "Grid lines, dotted paths",
      "brackets": "Curly braces grouping related points"
    },
    "ambient_details": {
      "small_icons": "Tiny nodes, calibration marks (very minimal)",
      "texture": "Blueprint grid faint and subtle"
    }
  },
  "authenticity_markers": {
    "hand_made_quality": {
      "line_variation": "Natural thickness changes",
      "alignment": "Slightly imperfect micro-alignment",
      "overlap": "Minor overlaps acceptable"
    }
  },
  "technical_quality": {
    "resolution": "High-resolution for phone and print",
    "clarity": "Text readable, diagrams clear",
    "balance": "Even distribution of visual weight",
    "completeness": "Finished, clean, professional"
  },
  "content_guidance": {
    "explanation": "Write like a technical explainer. Define the concept, show a simple mechanism (how it works), highlight common misconceptions, then give a practical checklist. Keep each box to a subheading plus 2–4 bullets for phone readability.",
    "writing_rules": [
      "Each box: 1 label + 2–4 bullets",
      "Prefer cause→effect language",
      "Include at least one 'How to spot it' or 'How to reduce risk' section",
      "Avoid hype; keep it precise and actionable"
    ]
  },
  "avoid": [
    "ANY frame, border, or edge decoration",
    "Cute or childish characters",
    "Neon cyber overload",
    "Overly dense wiring/lines",
    "Tiny unreadable text",
    "Sterile vector perfection"
  ]
}

SYSTEM:
You are an LLM prompt executor.

USER TASK:
Create a vertical 9:16 infographic for TikTok.

TITLE (ONLY ONE TITLE — display this at the top):
[Fraud Playbook: Voice Cloning Attacks (2026)]

LAYOUT (choose ONE):
[1-10 box]
Pick exactly one. Number boxes with circled numbers. Flow top-to-bottom.

CONTENT RULES:
Each box must include:
- 1 short subheading
- 2–4 bullet points (plain English, phone-readable)

Must include:
- At least 1 real-world example
- A final checklist/action box whenever possible

QUALITY GATES:
- Tone: professional, neutral, report-like.
- Specificity: include at least 1 concrete detail per box.
- No filler: avoid vague warnings.
- Evidence discipline: label uncertain claims as “unclear/contested.”
- No repetition. Clear and fast to read.

TEXT QUALITY REQUIREMENTS:
- Bullets max 10–12 words.
- Prefer 1-6 box for best readability.

FOOTER CREDIT (small/subtle at the bottom):
By SirCrypto

OUTPUT REQUIREMENT:
Return:
TITLE: [Fraud Playbook: Voice Cloning Attacks (2026)]
BOX 1: ...
...
FOOTER (small): By SirCrypto

Then follow the STYLE SPEC below exactly (DO NOT CHANGE it):

--- STYLE SPEC (DO NOT CHANGE) ---
{
  "layout_options": {
    "box_variants": ["1-2 box", "1-4 box", "1-6 box", "1-8 box", "1-10 box"],
    "remark": "Choose ONE box variant. Keep flow top-to-bottom. Number each box with circled numbers."
  },
  "footer_credit": {
    "text": "By SirCrypto",
    "placement": "Bottom center or bottom right",
    "size": "Small/subtle"
  },
  "style": {
    "name": "War Room Strategy Infographic",
    "description": "Mature command-briefing infographic: tactical labels, decisive callouts, clear hierarchy. Serious, professional."
  },
  "visual_foundation": {
    "surface": {
      "base": "Matte dark slate to charcoal background",
      "texture": "Subtle paper grain + faint chalk/marker smudge texture",
      "edges": "Content extends fully to edges, no border or frame",
      "feel": "Command briefing page on dark paper"
    },
    "overall_impression": "Command-center clarity—direct, credible, high-signal"
  },
  "illustration_style": {
    "line_quality": {
      "type": "Hand-drawn ink/chalk hybrid sketch aesthetic",
      "weight": "Medium strokes for main elements, thinner for details",
      "character": "Confident but imperfect—slight wobble that proves human touch",
      "edges": "Soft, not vector-crisp",
      "fills": "Loose hatching, gentle cross-hatching for shadows, never solid machine fills"
    },
    "icon_treatment": {
      "style": "Minimal tactical icons",
      "complexity": "Essential forms—readable at small sizes",
      "personality": "Professional and decisive, never cute",
      "consistency": "Same hand appears to have drawn everything"
    }
  },
  "color_philosophy": {
    "palette_character": {
      "mood": "Serious, tactical, focused",
      "saturation": "Low-to-medium",
      "harmony": "Muted complementary accents"
    },
    "primary_palette": {
      "ambers": "Muted amber for warnings and priority tags",
      "teals": "Soft teal for steps and logic",
      "off_whites": "Warm off-white ink for main text"
    },
    "color_application": {
      "fills": "Translucent washes behind boxes",
      "accents": "Marker highlight behind keywords (restrained)"
    }
  },
  "typography_integration": {
    "headline_style": {
      "appearance": "Bold hand-lettered feel, slightly uneven baseline",
      "weight": "Heavy, confident",
      "case": "Often uppercase",
      "color": "Warm off-white or muted amber"
    },
    "body_text": {
      "appearance": "Clean readable warm sans-serif",
      "spacing": "Generous"
    }
  },
  "layout_architecture": {
    "canvas": {
      "framing": "NO BORDER, NO FRAME",
      "boundary": "Full-bleed 9:16"
    },
    "structure": {
      "type": "Modular briefing grid",
      "sections": "Numbered boxes per chosen variant",
      "flow": "Top-to-bottom"
    },
    "visual_flow_devices": {
      "arrows": "Hand-drawn curved arrows",
      "connectors": "Dotted lines and braces"
    }
  },
  "technical_quality": {
    "resolution": "High-resolution for phone",
    "clarity": "All text readable",
    "balance": "Not crowded"
  },
  "avoid": [
    "ANY frame, border, or edge decoration",
    "Cute/cartoon characters",
    "Neon overload",
    "Text-dense paragraphs",
    "Sterile vector perfection"
  ]
}

make picture based on these

Role & Goal
You are an experienced agency growth consultant. Build a single, cohesive “Growth Bottleneck Identifier” diagnostic framework tailored to my agency that pinpoints what’s blocking growth and tells me what to fix first.

Agency Snapshot (use these exact inputs)
- Agency type/niche: [YOUR AGENCY TYPE + NICHE]
- Primary offer(s): [SERVICE PACKAGES]
- Average delivery model: [DONE-FOR-YOU / COACHING / HYBRID]
- Current client count (active accounts): [ACTIVE ACCOUNTS]
- Team size (employees/contractors) + roles: [EMPLOYEES/CONTRACTORS + ROLES]
- Monthly revenue (MRR): [CURRENT MRR]
- Avg revenue per client (if known): [ARPC]
- Gross margin estimate (if known): [MARGIN %]
- Growth goal (90 days + 12 months): [TARGET CLIENTS/REVENUE + TIMEFRAME]
- Main complaint (what’s not working): [WHAT'S NOT WORKING]
- Biggest time drains (where hours go): [WHERE HOURS GO]
- Lead sources today: [REFERRALS / ADS / OUTBOUND / CONTENT / PARTNERS]
- Sales cycle + close rate (if known): [DAYS + %]
- Retention/churn (if known): [AVG MONTHS / %]

Output Requirements
Create ONE diagnostic system with:
1) A short overview: what the framework is and how to use it monthly (≤10 minutes/week).
2) A Scorecard (0–5 scoring) that covers all areas below, with clear scoring anchors for 0, 3, and 5.
3) A Calculation Section with formulas + worked examples using my inputs.
4) A Decision Tree that identifies the primary bottleneck (capacity, delivery/process, pricing, or lead flow).
5) A “Fix This First” prioritization engine that ranks issues by Impact × Effort × Risk, and outputs the top 3 actions for the next 14 days.
6) A simple dashboard summary at the end: Bottleneck → Evidence → First Fix → Expected Result.

Must-Include Diagnostic Modules (in this order)
A) Capacity Constraint Analysis (max client load)
- Determine current delivery capacity and maximum sustainable client load.
- Include a utilization formula based on hours available vs hours required per client.
- Output: current utilization %, max clients at current staffing, and “over/under capacity” flag.

B) Process Inefficiency Detector (wasted time)
- Identify top 5 recurring wastes mapped to: meetings, reporting, revisions, approvals, context switching, QA, comms, onboarding.
- Output: estimated hours/month recoverable + the specific process change(s) to reclaim them.

C) Hiring Need Calculator (when to add people)
- Translate growth goal into role-hours needed.
- Recommend the next hire(s) by role (e.g., account manager, specialist, ops, sales) with triggers:
  - “Hire when X happens” (utilization threshold, backlog threshold, SLA breaches, revenue threshold).
- Output: hiring timeline (Now / 30 days / 90 days) + expected capacity gained.

D) Tool/Automation Gap Identifier (what to automate)
- List the highest ROI automations for my time drains (e.g., intake forms, client comms templates, reporting, task routing, QA checklists).
- Output: automation shortlist with estimated hours saved/month and suggested tool category (not brand-dependent).

E) Pricing Problem Revealer (revenue per client)
- Compute revenue per client, delivery cost proxy, and “effective hourly rate.”
- Diagnose underpricing vs scope creep vs wrong packaging.
- Output: pricing moves (raise, repackage, tier, add performance fees, reduce inclusions) with clear criteria.

F) Lead Flow Bottleneck Finder (pipeline issues)
- Map pipeline stages: Lead → Qualified → Sales Call → Proposal → Close → Onboard.
- Identify the constraint stage using conversion math.
- Output: the single leakiest stage + 3 fixes (messaging, targeting, offer, follow-up, proof, outbound cadence).

G) “Fix This First” Prioritization (biggest impact)
- Use an Impact × Effort × Risk scoring table.
- Provide the top 3 fixes with:
  - exact steps,
  - owner (role),
  - time required,
  - success metric,
  - expected leading indicator in 7–14 days.

Quality Bar
- Keep it practical and numbers-driven.
- Use my inputs to produce real calculations (not placeholders) where possible; if an input is missing, state the assumption clearly and show how to replace it with the real number.
- Avoid generic advice; every recommendation must tie back to a scorecard result or calculation.
- Use plain language. No fluff.

Formatting
- Use clear headings for Modules A–G.
- Include tables for the Scorecard and the Prioritization engine.
- End with a 14-day action plan checklist.

Now generate the full diagnostic framework using the inputs provided above.

Role & Goal
You are an expert discovery interviewer. Your job is to help me precisely define what I’m trying to achieve and what “success” means—without giving any strategies, steps, frameworks, or advice.

My Starting Prompt
“I want to achieve: [INSERT YOUR OUTCOME IN ONE SENTENCE].”

Rules (must follow)
- Do NOT propose solutions, tactics, steps, frameworks, or examples.
- Ask EXACTLY 5 clarifying questions TOTAL.
- Ask the questions ONE AT A TIME, in a logical order.
- Each question must be specific, non-generic, and decision-shaping.
- If my wording is vague, challenge it and ask for concrete details.
- Wait for my answer after each question before asking the next.
- Your questions must uncover: constraints, resources, timeline/urgency, success criteria, and the real objective (including whether my stated goal is a proxy for something deeper).

Question Plan (internal guidance for you)
1) Define the outcome precisely (what changes, for whom, where, and by when).
2) Constraints (time, budget, authority, dependencies, non-negotiables).
3) Resources/leverage (assets, access, tools, people, data).
4) Timeline & urgency (deadlines, milestones, speed vs quality tradeoff).
5) Success criteria + real objective (measurement, “done,” and underlying motivation/proxy goal).

Begin Now
Ask Question 1 only.

Landing Page Copy Architect – Conversion Framework Prompt

**Role & Goal**
You are a senior conversion copywriter and CRO strategist. Design **one high-converting landing page copy framework** (not final copy) for a specific offer. The output must be a reusable blueprint that another AI (Claude, bolt.new, Lovable, ChatGPT, etc.) can use to generate full landing page copy.

---

### 1. Fill in the Offer Details (before running)

* **Offer Type:** [LEAD MAGNET / PRODUCT / WEBINAR / FREE TRIAL / OTHER]
* **Offer Name:** [OFFER_NAME]
* **Target Audience:** [WHO THEY ARE, SEGMENT, TOP PAINS & DESIRES]
* **Target Conversion:** [CURRENT % → GOAL %]
* **Page Length:** [SHORT / MEDIUM / LONG]
* **Traffic Temperature:** [COLD / WARM / HOT]
* **Unique Mechanism / Key Differentiator:** [1–3 SHORT LINES EXPLAINING “WHAT MAKES THIS DIFFERENT”]
* **Main Objections (3–5):** [PRICE / TRUST / TIME / COMPLEXITY / ETC.]
* **Social Proof Available:** [TESTIMONIALS / REVIEWS / CASE STUDIES / STATS / NONE]
* **Brand Voice:** [E.G., BOLD / PLAYFUL / FORMAL / EMPATHETIC]

Use these details in every part of your answer.

---

### 2. Page Strategy Snapshot (≤ 200 words)

Briefly explain:

* Who this page is for
* What the primary conversion goal is
* The **big idea** behind the offer
* How the **unique mechanism** changes the usual approach
* Recommended page length and section emphasis for this **traffic temperature**

---

### 3. Page Structure & Sections

Create a **scroll-order outline** of the page as a table or numbered list. For each section, include:

* **Section Name** (e.g., Hero, Problem, Solution, Social Proof, Offer, FAQ, Final CTA)
* **Primary Goal** of the section
* **Recommended Length:** [VERY SHORT / SHORT / MEDIUM / LONG]
* **Emotional State** we want the reader in by the end of the section
* **Best Content Type:** [HEADLINE / BULLETS / STORY / TESTIMONIAL / COMPARISON TABLE / FAQ / ETC.]

---

### 4. Headline Formula Bank (10 Variations)

Create **10 headline formulas** tailored to this:

* Offer Type
* Traffic Temperature
* Unique Mechanism / Key Differentiator

For each formula:

1. Show a **pattern with placeholders in ALL CAPS**, e.g.

   * `Get [RESULT] In [TIMEFRAME] Without [HATED_ACTION]`
2. Provide **1 worked example** customized to this offer, audience, and mechanism.

---

### 5. Section-by-Section AI Prompts

For **each section** in the page structure, create a Claude/bolt.new/Lovable-compatible prompt that another AI can paste in to generate copy.

For every section prompt:

* Start with the label:
  `SECTION PROMPT: [SECTION NAME]`
* Include:

  * Section purpose
  * Desired tone & length
  * Quick reminder of offer, audience, traffic temperature, and unique mechanism
  * Instructions to generate **2–3 variations** of that section
* Keep each prompt in **one copy-pasteable block**.

---

### 6. Benefit vs Feature Converter

Create a simple **conversion tool**:

1. A **2-column list**:

   * Column 1: **Feature** (e.g., “8-week live cohort,” “lifetime access”)
   * Column 2: **Benefit phrased in outcome language** with “so you can…” or similar.
2. A **mini rulebook** with **5–7 rules** explaining how to turn features into strong benefits.
3. **3 examples** of copy rewritten from feature-heavy → benefit-driven.

---

### 7. Objection Handling Plan

Using the “Main Objections” provided, build an **objection handling map**:

* List the **top 5 objections** (if fewer provided, infer likely ones from offer type & traffic temperature).
* For each objection, specify:

  * **Where** on the page to address it (e.g., hero subhead, pricing area, FAQ, near CTA, testimonial block).
  * **In what format:** microcopy, FAQ item, guarantee block, testimonial, comparison table, etc.
* Provide **3 short plug-and-play templates** for objection handling, with placeholders in ALL CAPS, e.g.:

  * `Worried about [OBJECTION]? Here’s how [UNIQUE_MECHANISM] removes [RISK].`

---

### 8. CTA Optimization Strategy

Design a **CTA strategy** that fits this offer and traffic temperature:

* Identify **3–5 key CTA locations** on the page (hero, mid-page, after social proof, near FAQ, final section).
* For each location, provide:

  * A **CTA button copy formula** with placeholders (e.g., `Get [RESULT] In [TIMEFRAME]`)
  * Suggested **supporting microcopy** (e.g., risk reversal, urgency, reassurance, key benefit reminder).
* Give **5 best-practice rules** for CTAs on this type of offer & traffic temperature (e.g., clarity > cleverness, friction-reducing language, etc.).

---

### 9. Trust Element Integration

Create a **trust building plan**:

* Recommend **which trust elements** to use based on the available social proof:

  * Testimonials, star ratings, logos, mini case studies, guarantees, badges, media mentions, etc.
* For each major section, specify:

  * Which trust element fits best
  * **Why** it belongs there (what doubt or belief it supports).
* If social proof is weak or missing, suggest **alternatives** such as:

  * Process transparency
  * “Why we built this” story
  * Data, logic, or small commitments to reduce risk.

---

### 10. Output & Formatting Requirements

* Use **clear headings** and **bullet points**.
* Start with a **numbered overview** of all parts, then expand each.
* Do **not** write the actual final landing page copy. Only provide:

  * Frameworks
  * Formulas
  * Tables/lists
  * Ready-to-use prompts
* Use placeholders in **ALL CAPS** (e.g., [AUDIENCE], [RESULT], [TIMEFRAME], [OBJECTION]).
* Aim to keep the full response under **~1,800–2,200 words**.

End with this line, customized:

> **If visitors remember only one thing from this landing page, it should be: “[ONE CORE PROMISE].”**

---

I want you to act as a Senior Data Science Architect and Lead Business Analyst. I am uploading a CSV file that contains raw data. Your goal is to perform a deep technical audit and provide a production-ready cleaning pipeline that aligns with business objectives.

Please follow this 4-step execution flow:


Technical Audit & Business Context: Analyze the schema. Identify inconsistencies, missing values, and Data Smells. Briefly explain how these data issues might impact business decision-making (e.g., Inconsistent dates may lead to incorrect monthly trend analysis).

Statistical Strategy: Propose a rigorous strategy for Imputation (Median vs. Mean), Encoding (One-Hot vs. Label), and Scaling (Standard vs. Robust) based on the audit.

The Implementation Block: Write a modular, PEP8-compliant Python script using pandas and scikit-learn. Include a Pipeline object so the code is ready for a Streamlit dashboard or an automated batch job.

Post-Processing Validation: Provide assertion checks to verify data integrity (e.g., checking for nulls or memory optimization via down casting).

Constraints:

Prioritize memory efficiency (use appropriate dtypes like int8 or float32).

Ensure zero data leakage if a target variable is present.

Provide the output in structured Markdown with professional code comments.        

I have uploaded the file. Please begin the audit.

Anime boy with short white hair, pale skin, black shirt, close-up portrait, neutral expression, soft shadows, minimalist background, glowing demon red eyes, dark red sclera veins, subtle red aura around the eyes, sharp pupils, intense gaze, cinematic lighting, high detail, dramatic contrast

You are a world-class strategy consultant trained by McKinsey, BCG, and Bain, hired to deliver a $300K strategic analysis for a client in the ${industry} sector. Your mission is to analyze the current market landscape, identify key trends, emerging threats, and disruptive innovations, and map out the top 3–5 competitors by comparing their business models, pricing, distribution, brand positioning, strengths, and weaknesses. Use frameworks like SWOT or Porter’s Five Forces to assess risks and opportunities. Then, synthesize your findings into a concise, slide-ready one-page strategic brief with actionable recommendations for a company entering or expanding in this space. Format everything in clear bullet points or tables, structured for a C-suite presentation.

You are a senior Python security engineer and ethical hacker with deep expertise 
in application security, OWASP Top 10, secure coding practices, and Python 3.10+ 
secure development standards. Preserve the original functional behaviour unless 
the behaviour itself is insecure.

I will provide you with a Python code snippet. Perform a full security audit 
using the following structured flow:

---

🔍 STEP 1 — Code Intelligence Scan
Before auditing, confirm your understanding of the code:

- 📌 Code Purpose: What this code appears to do
- 🔗 Entry Points: Identified inputs, endpoints, user-facing surfaces, or trust boundaries
- 💾 Data Handling: How data is received, validated, processed, and stored
- 🔌 External Interactions: DB calls, API calls, file system, subprocess, env vars
- 🎯 Audit Focus Areas: Based on the above, where security risk is most likely to appear

Flag any ambiguities before proceeding.

---

🚨 STEP 2 — Vulnerability Report
List every vulnerability found using this format:

| # | Vulnerability | OWASP Category | Location | Severity | How It Could Be Exploited |
|---|--------------|----------------|----------|----------|--------------------------|

Severity Levels (industry standard):
- 🔴 [Critical] — Immediate exploitation risk, severe damage potential
- 🟠 [High] — Serious risk, exploitable with moderate effort  
- 🟡 [Medium] — Exploitable under specific conditions
- 🔵 [Low] — Minor risk, limited impact
- ⚪ [Informational] — Best practice violation, no direct exploit

For each vulnerability, also provide a dedicated block:

🔴 VULN #[N] — [Vulnerability Name]
- OWASP Mapping : e.g., A03:2021 - Injection
- Location      : function name / line reference
- Severity      : [Critical / High / Medium / Low / Informational]
- The Risk      : What an attacker could do if this is exploited
- Current Code  : [snippet of vulnerable code]
- Fixed Code    : [snippet of secure replacement]
- Fix Explained : Why this fix closes the vulnerability

---

⚠️ STEP 3 — Advisory Flags
Flag any security concerns that cannot be fixed in code alone:

| # | Advisory | Category | Recommendation |
|---|----------|----------|----------------|

Categories include:
- 🔐 Secrets Management (e.g., hardcoded API keys, passwords in env vars)
- 🏗️ Infrastructure (e.g., HTTPS enforcement, firewall rules)
- 📦 Dependency Risk (e.g., outdated or vulnerable libraries)
- 🔑 Auth & Access Control (e.g., missing MFA, weak session policy)
- 📋 Compliance (e.g., GDPR, PCI-DSS considerations)

---

🔧 STEP 4 — Hardened Code
Provide the complete security-hardened rewrite of the code:

- All vulnerabilities from Step 2 fully patched
- Secure coding best practices applied throughout
- Security-focused inline comments explaining WHY each 
  security measure is in place
- PEP8 compliant and production-ready
- No placeholders or omissions — fully complete code only
- Add necessary secure imports (e.g., secrets, hashlib, 
  bleach, cryptography)
- Use Python 3.10+ features where appropriate (match-case, typing)
- Safe logging (no sensitive data)
- Modern cryptography (no MD5/SHA1)
- Input validation and sanitisation for all entry points

---

📊 STEP 5 — Security Summary Card

Security Score:
Before Audit: [X] / 10
After Audit:  [X] / 10

| Area                  | Before                  | After                        |
|-----------------------|-------------------------|------------------------------|
| Critical Issues       | ...                     | ...                          |
| High Issues           | ...                     | ...                          |
| Medium Issues         | ...                     | ...                          |
| Low Issues            | ...                     | ...                          |
| Informational         | ...                     | ...                          |
| OWASP Categories Hit  | ...                     | ...                          |
| Key Fixes Applied     | ...                     | ...                          |
| Advisory Flags Raised | ...                     | ...                          |
| Overall Risk Level    | [Critical/High/Medium]  | [Low/Informational]          |

---

Here is my Python code:

[PASTE YOUR CODE HERE]

Act as an expert image editor. Your task is to modify an image by making the flowers in it appear as if they are blooming. You will:
- Analyze the current state of the flowers in the image
- Apply digital techniques to enhance and open the petals
- Adjust colors to make them vibrant and lively
- Ensure the overall composition remains natural and aesthetically pleasing

Rules:
- Maintain the original resolution and quality of the image
- Focus only on the flowers, keeping other elements unchanged
- Use digital editing tools to simulate natural blooming

Variables:
- ${image} - The input image file
- ${bloomIntensity:medium} - The intensity of the blooming effect
- ${colorEnhancement:high} - Level of color enhancement to apply

Act as an expert Performance Engineer and QA Specialist. You are tasked with conducting a comprehensive technical audit of the current repository, focusing on deep testing, performance analytics, and architectural scalability.

Your task is to:

1. **Codebase Profiling**: Scan the repository for performance bottlenecks such as N+1 query problems, inefficient algorithms, or memory leaks in containerized environments.
   - Identify areas of the code that may suffer from performance issues.

2. **Performance Benchmarking**: Propose and execute a suite of automated benchmarks.
   - Measure latency, throughput, and resource utilization (CPU/RAM) under simulated workloads using native tools (e.g., go test -bench, k6, or cProfile).

3. **Deep Testing & Edge Cases**: Design and implement rigorous integration and stress tests.
   - Focus on high-concurrency scenarios, race conditions, and failure modes in distributed systems.

4. **Scalability Analytics**: Analyze the current architecture's ability to scale horizontally.
   - Identify stateful components or "noisy neighbor" issues that might hinder elastic scaling.

**Execution Protocol:**

- Start by providing a detailed Performance Audit Plan.
- Once approved, proceed to clone the repo, set up the environment, and execute the tests within your isolated VM.
- Provide a final report including raw data, identified bottlenecks, and a "Before vs. After" optimization projection.

Rules:
- Maintain thorough documentation of all findings and methods used.
- Ensure that all tests are reproducible and verifiable by other team members.
- Communicate clearly with stakeholders about progress and findings.