Englisch

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.

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

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": "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"
    ]
  }
}

# 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.

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 

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. 

## *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.

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.

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

[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

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

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
- formal - The style of presentation
- 10-15 minutes - Expected length of the presentation

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>
  );
}
```

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 Test Automation Engineer. You are skilled in writing unit tests for TypeScript projects using Vitest.

Your task is to guide developers on creating unit tests according to the RCS-001 standard.

You will:
- Ensure tests are implemented using `vitest`.
- Guide on placing test files under `tests` directory mirroring the class structure with `.spec` suffix.
- Describe the need for `testData` and `testUtils` for shared data and utilities.
- Explain the use of `mocked` directories for mocking dependencies.
- Instruct on using `describe` and `it` blocks for organizing tests.
- Ensure documentation for each test includes `target`, `dependencies`, `scenario`, and `expected output`.

Rules:
- Use `vi.mock` for direct exports and `vi.spyOn` for class methods.
- Utilize `expect` for result verification.
- Implement `beforeEach` and `afterEach` for common setup and teardown tasks.
- Use a global setup file for shared initialization code.

### Test Data
- Test data should be plain and stored in `testData` files. Use `testUtils` for generating or accessing data.
- Include doc strings for explaining data properties.

### Mocking
- Use `vi.mock` for functions not under classes and `vi.spyOn` for class functions.
- Define mock functions in `Mocked` files.

### Result Checking
- Use `expect().toEqual` for equality and `expect().toContain` for containing checks.
- Expect errors by type, not message.

### After and Before Each
- Use `beforeEach` or `afterEach` for common tasks in `describe` blocks.

### Global Setup
- Implement a global setup file for tasks like mocking network packages.

Example:
```typescript
describe(`Class1`, () => {
  describe(`function1`, () => {
    it(`should perform action`, () => {
      // Test implementation
    })
  })
})```

Full Body, Full-bodied, Beautifully Kids, New Fashions, Random clothes, Random Kids, Moderns New Styles, soft focus, depth of field, 8k photo, HDR, professional lighting, taken with Canon EOS R5, DSLR, 75mm lens

Transform the uploaded portrait into a high-contrast vector poster illustration.

Style requirements:
- Bold stencil / propaganda poster aesthetic
- Flat vector art
- 3–4 color palette only
- Solid red background
- Face rendered in grayscale tones (2–3 flat shadow layers)
- Black thick outer contour lines
- No gradients
- No texture
- No photorealism
- Sharp clean edges
- Posterized shading
- Centered head composition
- Minimal but strong facial features
- Graphic design style
- Adobe Illustrator vector look
- High contrast
- Smooth geometric shadow shapes

Output:
Crisp, clean, scalable vector-style portrait.

Ultra realistic cinematic portrait of a referance photo, centered composition, head and shoulders framing, direct eye contact, serious neutral expression, short slightly messy dark hair, light stubble beard, wearing a black shirt and black textured jacket with zipper details, dramatic red rim lighting from both sides, soft frontal key light, deep black background, high contrast, low-key lighting, sharp focus, 85mm lens, shallow depth of field, studio photography, ultra detailed skin texture, 8k resolution

Photorealistic iPhone selfie-style shot in alpine mountains. Bright clear daylight, deep blue sky, dramatic sharp mountain peaks in the background with patches of snow on rocky ridges. Wide open green alpine meadow in the foreground, lush grass with small plants visible in detail. A small wooden mountain hut in the mid-distance. The woman lies on her back in the grass, relaxed, using a hiking backpack as a pillow. The camera angle is handheld and slightly above her — classic iPhone arm-extended selfie perspective, subtle wide-angle distortion on the extended arm. She wears sporty hiking outfit: lightweight Arc’teryx windbreaker jacket (blue tone), fitted pink athletic shorts, Oakley sunglasses, casual trail vibe. Relaxed body posture — one knee slightly bent, one arm extended toward the camera holding the phone. Backpack visible under her head, realistic hiking gear details.

Create a deriv boom and crush trading strategy based on the ICT strategy.