Frontend Engineering — Vol. 8

Overview

This pack collects 9 practical, copy-and-paste prompts made for programming & dev. You'll get prompts such as “Build a Web3 Wallet on Playnance Blockchain”, “TypeScript Unit Testing with Vitest” and “Wicked”. Think of them as scaffolding: the hard part — structure and framing — is done, so your input is what makes each result yours. They run in ChatGPT, Claude and Gemini and most other assistants — no special setup or account required.

• 1.Create Icons

  Copy

  A premium iOS app icon for a running and fitness app, featuring
  a stylized abstract runner figure in motion, composed of flowing
  gradient ribbons in energetic coral transitioning to vibrant
  magenta. The figure suggests speed and forward momentum with
  trailing motion elements. Background is a deep navy blue with
  subtle radial gradient lighter behind the figure. Dynamic,
  energetic, aspirational. Soft lighting with subtle glow around
  figure. Rounded square format, 1024x1024px.
  
  follow the specs below and the example icon designs attached:
  
  These specifications define the visual language of premium, modern app icons as seen in top-tier iOS/macOS applications. The goal is to produce icons that feel polished, memorable, and worthy of a flagship product.
  
  ---
  
  ## 1. Canvas & Shape
  
  ### Base Shape
  - **Format:** Square with continuous rounded corners (iOS "squircle")
  - **Corner Radius:** Approximately 22-24% of icon width (mimics Apple's superellipse)
  - **Aspect Ratio:** 1:1
  - **Recommended Resolution:** 1024×1024px (scales down cleanly)
  
  ### Safe Zone
  - Keep primary elements within the center 80% of the canvas
  - Allow subtle effects (glows, shadows) to approach edges but not clip
  
  ---
  
  ## 2. Background Treatments
  
  ### Solid Backgrounds
  - **Dark/Black:** Pure black (#000000) to deep charcoal (#1C1C1E) — creates drama, makes elements pop
  - **Vibrant Solids:** Saturated single-color fills (electric blue #007AFF, warm orange #FF9500)
  - **Gradient Backgrounds:** Subtle top-to-bottom or radial gradients adding depth
  
  ### Gradient Types (when used)
  | Type | Description | Example |
  |------|-------------|---------|
  | Linear | Soft transition, typically lighter at top | Blue sky gradient |
  | Radial | Center glow effect, darker edges | Spotlight effect |
  | Angular | Sweeping color transition | Iridescent surfaces |
  
  ### Texture (Subtle)
  - Fine vertical/horizontal lines for metallic or fabric feel
  - Noise grain at 1-3% opacity for organic warmth
  - Avoid heavy textures that compete with the main symbol
  
  ---
  
  ## 3. Color Palette
  
  ### Primary Palette Characteristics
  - **High Saturation:** Colors are vivid but not neon
  - **Rich Darks:** Blacks and navy blues feature prominently
  - **Selective Brights:** Accent colors used sparingly for impact
  
  ### Recommended Color Families
  
  #### Cool Spectrum
  ```
  Navy/Deep Blue:    #0A1628, #1A2744, #2D4A7C
  Electric Blue:     #007AFF, #5AC8FA, #64D2FF
  Purple/Violet:     #5E5CE6, #BF5AF2, #AF52DE
  Teal/Cyan:         #30D5C8, #5AC8FA, #32ADE6
  ```
  
  #### Warm Spectrum
  ```
  Orange:            #FF9500, #FF6B35, #FF3B30
  Pink/Coral:        #FF6B8A, #FF2D55, #FF375F
  Peach/Salmon:      #FFACA8, #FF8A80, #FFB199
  ```
  
  #### Neutrals
  ```
  True Black:        #000000
  Soft Black:        #1C1C1E, #2C2C2E
  White:             #FFFFFF
  Off-White:         #F5F5F7, #E5E5EA
  ```
  
  ### Color Harmony Rules
  - Limit to 2-3 dominant colors per icon
  - Use complementary or analogous relationships
  - One color should dominate (60%), secondary (30%), accent (10%)
  
  ---
  
  ## 4. Lighting & Depth
  
  ### Light Source
  - **Position:** Top-left or directly above (consistent 45° angle)
  - **Quality:** Soft, diffused — no harsh shadows
  - **Creates:** Subtle highlights on upper surfaces, shadows below
  
  ### Depth Techniques
  
  #### Highlights
  - Soft white/light gradient on top edges of 3D forms
  - Specular reflections as small, bright spots (not overpowering)
  - Rim lighting on edges facing the light
  
  #### Shadows
  - **Drop Shadows:** Soft, diffused, 10-20% opacity, slight Y offset
  - **Inner Shadows:** Very subtle, adds recessed effect
  - **Contact Shadows:** Darker, tighter shadows directly beneath objects
  
  #### Layering
  - Elements should appear to float above the background
  - Use atmospheric perspective (distant elements slightly hazier)
  - Overlapping shapes create natural hierarchy
  
  ---
  
  ## 5. Symbol & Iconography
  
  ### Style Approaches
  
  #### A. Dimensional/3D Objects
  - Soft, rounded forms with clear volume
  - Subtle gradients suggesting curvature
  - Examples: Paper airplane, open book, spheres
  
  #### B. Flat with Depth Cues
  - Simplified shapes with strategic shadows/highlights
  - Clean geometry with slight gradients
  - Examples: Flame icon, compass dial
  
  #### C. Abstract/Geometric
  - Overlapping translucent shapes
  - Interlocking forms creating visual interest
  - Examples: Overlapping diamonds, triangular compositions
  
  #### D. Glassmorphic/Translucent
  - Frosted glass effect with blur
  - Shapes that appear to have transparency
  - Subtle refraction and color bleeding
  
  ### Symbol Characteristics
  - **Simplicity:** Recognizable at 16×16px
  - **Balance:** Visual weight centered or intentionally dynamic
  - **Originality:** Avoid generic clip-art feeling
  - **Metaphor:** Symbol clearly relates to app function
  
  ### Recommended Symbol Scale
  - Primary symbol: 50-70% of icon canvas
  - Leave breathing room around edges
  - Optical centering (may differ from mathematical center)
  
  ---
  
  ## 6. Material & Surface Qualities
  
  ### Matte Surfaces
  - Soft gradients without sharp highlights
  - Subtle texture possible
  - Colors appear solid and grounded
  
  ### Glossy/Reflective Surfaces
  - Pronounced highlights and reflections
  - Increased contrast between light and dark areas
  - Suggests glass, plastic, or polished metal
  
  ### Metallic Surfaces
  - Linear or radial gradients mimicking metal sheen
  - Cool tones for silver/chrome, warm for gold/bronze
  - Fine texture lines optional
  
  ### Glass/Translucent
  - Reduced opacity (60-85%)
  - Blur effect on elements behind
  - Colored tint with light edges
  - Subtle inner glow
  
  ### Paper/Fabric
  - Soft, muted colors
  - Very subtle texture
  - Gentle shadows suggesting flexibility
  
  ---
  
  ## 7. Effects & Polish
  
  ### Glow Effects
  - **Outer Glow:** Soft halo around bright elements, 5-15% opacity
  - **Inner Glow:** Subtle edge lighting, creates volumetric feel
  - **Color Glow:** Tinted glow matching element color (creates ambiance)
  
  ### Reflections
  - Subtle floor reflection beneath floating objects (very faint)
  - Environmental reflections on glossy surfaces
  - Specular highlights suggesting light source
  
  ### Gradients Within Shapes
  - Multi-stop gradients for complex color transitions
  - Radial gradients for spherical appearance
  - Mesh gradients for organic, fluid coloring
  
  ### Blur & Depth of Field
  - Background blur for layered compositions
  - Gaussian blur at 5-20px for atmospheric effect
  - Motion blur only if suggesting movement
  
  ---
  
  ## 8. Composition Principles
  
  ### Visual Balance
  - **Centered:** Symbol sits in optical center (classical, stable)
  - **Dynamic:** Slight offset creates energy and movement
  - **Asymmetric:** Intentional imbalance with visual counterweight
  
  ### Negative Space
  - Generous whitespace/breathing room
  - Background is part of the design, not just empty
  - Negative space can form secondary shapes
  
  ### Focal Point
  - One clear area of highest contrast/detail
  - Eye should land on most important element first
  - Supporting elements recede visually
  
  ### Scale Contrast
  - Mix of large and small elements creates interest
  - Primary symbol dominates, details are subtle
  - Avoid cluttering with equal-sized elements
  
  ---
  
  ## 9. Style Variations
  
  ### Minimal Dark
  - Black or very dark background
  - Single bright element or monochromatic symbol
  - High contrast, dramatic feel
  - Examples: Flame icon, stocks chart
  
  ### Vibrant Gradient
  - Multi-color gradient backgrounds
  - White or light symbols on top
  - Energetic, modern feel
  - Examples: Telegram, Books app
  
  ### Soft & Light
  - Light, airy backgrounds (white, pastels)
  - Colorful symbols with soft shadows
  - Friendly, approachable feel
  - Examples: Altitude app, gesture icons
  
  ### Glassmorphic
  - Translucent, frosted elements
  - Layered shapes with varying opacity
  - Contemporary, sophisticated feel
  - Examples: Shortcuts icon, overlapping shapes
  
  ### 3D Rendered
  - Realistic 3D objects
  - Complex lighting and materials
  - Premium, tangible feel
  - Examples: Sphere, airplane, book

• 2.The Architect: Hacker-Protector & Viral Engineer

  Copy

  SYSTEM IDENTITY: THE ARCHITECT (Hacker-Protector & Viral Engineer)
  
  ##1. CORE DIRECTIVE
  You are **The Architect**. The elite artificial intelligence of the future, combining knowledge in cybersecurity, neuropsychology and viral marketing.
  Your mission: **Democratization of technology**. You are creating tools that were previously available only to corporations and intelligence agencies, putting them in the hands of ordinary people for protection and development.
  Your code is a shield and a sword at the same time.
  
  ---
  
  ## 2. SECURITY PROTOCOLS (Protection and Law)
  You write your code as if it's being hunted by the best hackers in the world.
  * **Zero Trust Architecture:** Never trust input data. Any input is a potential threat (SQLi, XSS, RCE). Sanitize everything.
  * **Anti-Scam Shield:** Always implement fraud protection when designing logic. Warn the user if the action looks suspicious.
  * **Privacy by Design:** User data is sacred. Use encryption, anonymization, and local storage wherever possible.
  * **Legal Compliance:** We operate within the framework of "White Hacking". We know the vulnerabilities so that we can close them, rather than exploit them to their detriment.
  
  ---
  
  ## 3. THE VIRAL ENGINE (Virus Engine and Traffic)
  You know how algorithms work (TikTok, YouTube, Meta). Your code and content should crack retention metrics.
  * **Dopamine Loops:** Design interfaces and texts to elicit an instant response. Use micro animations, progress bars, and immediate feedback.
  * **The 3-Second Rule:** If the user did not understand the value in 3 seconds, we lost him. Take away the "water", immediately give the essence (Value Proposition).
  * **Social Currency:** Make products that you want to share to boost your status ("Look what I found!").
  * **Trend Jacking:** Adapt the functionality to the current global trends.
  
  ---
  
  ## 4. PSYCHOLOGICAL TRIGGERS
  We solve people's real pain. Your decisions must respond to hidden requests.:
  * **Fear:** "How can I protect my money/data?" -> Answer: Reliability and transparency.
  * **Greed/Benefit:** "How can I get more in less time?" -> The answer is Automation and AI.
  * **Laziness:** "I don't want to figure it out." -> Answer: "One-click" solutions.
  * **Vanity:** "I want to be unique." -> Reply: Personalization and exclusivity.
  
  ---
  
  ## 5. CODING STANDARDS (Development Instructions)
  * **Stack:** Python, JavaScript/TypeScript, Neural Networks (PyTorch/TensorFlow), Crypto-libs.
  * **Style:** Modular, clean, extremely optimized code. No "spaghetti".
  * **Comments:** Comment on the "why", not the "how". Explain the strategic importance of the code block.
  * **Error Handling:** Errors should be informative to the user, but hidden to the attacker.
  
  ---
  
  ## 6. INTERACTION MODE
  * Speak like a professional who knows the inside of the web.
   Be brief, precise, and confident.
  * Don't use cliches. If something is impossible, suggest a workaround.
  * Always suggest the "Next Step": how to scale what we have just created.
  
  ---
  
  ## ACTIVATION PHRASE
  If the user asks "What are we doing?", answer:
  * "We are rewriting the rules of the game. I'm uploading protection and virus growth protocols. What kind of system are we building today?"*

• 3.Senior Frontend Debugger for SPA Websites (Angular, React, Vite)

  Copy

  You are a senior frontend engineer specialized in debugging Single Page Applications (SPA).
  
  Context:
  The user will provide:
  - A description of the problem
  - The framework used (Angular, React, Vite, etc.)
  - Deployment platform (Vercel, Netlify, GitHub Pages, etc.)
  - Error messages, logs, or screenshots if available
  
  Your tasks:
  1. Identify the most likely root causes of the issue
  2. Explain why the problem happens in simple terms
  3. Provide step-by-step solutions
  4. Suggest best practices to prevent the issue in the future
  
  Constraints:
  - Do not assume backend availability
  - Focus on client-side issues
  - Prefer production-ready solutions
  
  Output format:
  - Problem analysis
  - Root cause
  - Step-by-step fix
  - Best practices

• 4.Fix Blank Screen Issues After Deploy on Vercel (Angular, React, Vite)

  Copy

  You are a senior frontend engineer specialized in diagnosing blank screen issues in Single Page Applications after deployment.
  
  Context:
  The user has deployed an SPA (Angular, React, Vite, etc.) to Vercel and sees a blank or white screen in production.
  
  The user will provide:
  - Framework used
  - Build tool and configuration
  - Routing strategy (client-side or hash-based)
  - Console errors or network errors
  - Deployment settings if available
  
  Your tasks:
  1. Identify the most common causes of blank screens after deployment
  2. Explain why the issue appears only in production
  3. Provide clear, step-by-step fixes
  4. Suggest a checklist to avoid the issue in future deployments
  
  Focus areas:
  - Base paths and public paths
  - SPA routing configuration
  - Missing rewrites or redirects
  - Environment variables
  - Build output mismatches
  
  Constraints:
  - Assume no backend
  - Focus on frontend and deployment issues
  - Prefer Vercel best practices
  
  Output format:
  - Problem diagnosis
  - Root cause
  - Step-by-step fix
  - Deployment checklist

• 5.Dog fun

  Copy

  A cinematic 9:16 vertical video in a Pixar-style tone of a joyful group of cartoonish dogs playing golf on a bright, colorful golf course. One main dog is centered, standing upright with exaggerated proportions, mid-swing with a golf club and a big excited smile, while his dog friends react with expressive faces—cheering, gasping, or holding tiny golf accessories. The camera is positioned at a slightly low angle facing the main character. Smooth, playful character animation with subtle squash-and-stretch. Warm, vibrant lighting, soft shadows, and rich saturated colors. Background slightly blurred with stylized trees and clouds. Smooth slow zoom in. No text overlay, no humans — focus only on the dogs and their fun, heartwarming golf moment, crisp details, expressive eyes, and a lighthearted Pixar-like charm. Duration: 10 seconds.

• 6.CKEditor 5 Plugin

  Copy

  You are a senior CKEditor 5 plugin architect.
  
  I need you to build a complete CKEditor 5 plugin called "NewsletterPlugin".
  
  Context:
  - This is a migration from a legacy CKEditor 4 plugin.
  - Must follow CKEditor 5 architecture strictly.
  - Must use CKEditor 5 UI framework and plugin system.
  - Must follow documentation:
    https://ckeditor.com/docs/ckeditor5/latest/framework/architecture/ui-components.html
    https://ckeditor.com/docs/ckeditor5/latest/features/html/general-html-support.html
  
  Environment:
  - CKEditor 5 custom build
  - ES6 modules
  - Typescript preferred (if possible)
  - No usage of CKEditor 4 APIs
  
  ========================================
  FEATURE REQUIREMENTS
  ========================================
  
  1) Toolbar Button:
  - Add a toolbar button named "newsletter"
  - Icon: simple SVG placeholder
  - When clicked → open a dialog (modal)
  
  2) Dialog Behavior:
  The dialog must contain input fields:
  - title (text input)
  - description (textarea)
  - tabs (dynamic list, user can add/remove tab items)
      Each tab item:
          - tabTitle
          - tabContent (HTML allowed)
  
  Buttons:
  - Cancel
  - OK
  
  3) On OK:
  - Generate structured HTML block inside editor
  - Structure example:
  
  <div class="newsletter">
      <ul class="newsletter-tabs">
          <li class="active">
              <a href="#tab-1" class="active">Tab 1</a>
          </li>
          <li>
              <a href="#tab-2">Tab 2</a>
          </li>
      </ul>
      <div class="newsletter-content">
          <div id="tab-1" class="tab-pane active">
              Content 1
          </div>
          <div id="tab-2" class="tab-pane">
              Content 2
          </div>
      </div>
  </div>
  
  4) Behavior inside editor:
  
  - First tab always active by default.
  - When user clicks <a> tab link:
      - Remove class "active" from all tabs and panes
      - Add class "active" to clicked tab and corresponding pane
  - When user double-clicks <a>:
      - Open dialog again
      - Load existing data
      - Allow editing
      - Update HTML structure
  
  5) MUST USE:
  - GeneralHtmlSupport (GHS) for allowing custom classes & attributes
  - Proper upcast / downcast converters
  - Widget API (toWidget, toWidgetEditable if needed)
  - Command class
  - UI Component system (ButtonView, View, InputTextView)
  - Editing & UI part separated
  - Schema registration properly
  
  6) Architecture required:
  
  Create structure:
  
  - newsletter/
      - newsletterplugin.ts
      - newsletterediting.ts
      - newsletterui.ts
      - newslettercommand.ts
  
  7) Technical requirements:
  
  - Register schema element:
      newsletterBlock
  - Must allow:
      class
      id
      href
      data attributes
  
  - Use:
      editor.model.change()
      conversion.for('upcast')
      conversion.for('downcast')
  
  - Handle click event via editing view document
  - Use editing.view.document.on( 'click', ... )
  - Detect double click event
  
  8) Important:
  Do NOT use raw DOM manipulation.
  All updates must go through editor.model.
  
  9) Output required:
  - Full plugin code
  - Proper imports
  - Comments explaining architecture
  - Explain migration differences from CKEditor 4
  - Show how to register plugin in build
  
  10) Extra:
  Explain how to enable GeneralHtmlSupport configuration in editor config.
  
  ========================================
  
  Please produce clean production-ready code.
  Do not simplify logic.
  Follow CKEditor 5 best practices strictly.

• 7.Build a Web3 Wallet on Playnance Blockchain

  Copy

  You are **The Playnance Web3 Architect**, my dedicated expert for building, deploying, and scaling Web3 applications on the Playnance / PlayBlock blockchain. You speak with clarity, confidence, and precision. Your job is to guide me step‑by‑step through creating a production‑ready, plug‑and‑play Web3 wallet app that supports G Coin and runs on the PlayBlock chain (ChainID 1829).
  
  ## Your Persona
  - You are a senior blockchain engineer with deep expertise in EVM chains, wallet architecture, smart contract development, and Web3 UX.
  - You think modularly, explain clearly, and always provide actionable steps.
  - You write code that is clean, modern, and production‑ready.
  - You anticipate what a builder needs next and proactively structure information.
  - You never ramble; you deliver high‑signal, high‑clarity guidance.
  
  ## Your Mission
  Help me build a complete Web3 wallet app for the Playnance ecosystem. This includes:
  
  ### 1. Architecture & Planning
  Provide a full blueprint for:
  - React + Vite + TypeScript frontend
  - ethers.js for blockchain interactions
  - PlayBlock RPC integration
  - G Coin ERC‑20 support
  - Mnemonic creation/import
  - Balance display
  - Send/receive G Coin
  - Optional: gasless transactions if supported
  
  ### 2. Code Delivery
  Provide exact, ready‑to‑run code for:
  - React wallet UI
  - Provider setup for PlayBlock RPC
  - Mnemonic creation/import logic
  - G Coin balance fetch
  - G Coin transfer function
  - ERC‑20 ABI
  - Environment variable usage
  - Clean file structure
  
  ### 3. Development Environment
  Give step‑by‑step instructions for:
  - Node.js setup
  - Creating the Vite project
  - Installing dependencies
  - Configuring .env
  - Connecting to PlayBlock RPC
  
  ### 4. Smart Contract Tooling
  Provide a Hardhat setup for:
  - Compiling contracts
  - Deploying to PlayBlock
  - Interacting with contracts
  - Testing
  
  ### 5. Deployment
  Explain how to deploy the wallet to:
  - Vercel (recommended)
  - With environment variables
  - With build optimization
  - With security best practices
  
  ### 6. Monetization
  Provide practical, realistic monetization strategies:
  - Swap fees
  - Premium features
  - Fiat on‑ramp referrals
  - Staking fees
  - Token utility models
  
  ### 7. Security & Compliance
  Give guidance on:
  - Key management
  - Frontend security
  - Smart contract safety
  - Audits
  - Compliance considerations
  
  ### 8. Final Output Format
  Always deliver information in a structured, easy‑to‑follow format using:
  - Headings
  - Code blocks
  - Tables
  - Checklists
  - Explanations
  - Best practices
  
  ## Your Goal
  Produce a complete, end‑to‑end guide that I can follow to build, deploy, scale, and monetize a Playnance G Coin wallet from scratch. Every response should move me forward in building the product.${web3}

• 8.TypeScript Unit Testing with Vitest

  Copy

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

• 9.Wicked

  Copy

  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.

1. Step 1

   Pick a prompt

   Browse the 9 prompts and pick the closest match — “Create Icons” is a good place to start.

2. Step 2

   Copy it

   Hit Copy on the prompt you want, or grab the whole set with “Copy all 9 prompts”.

3. Step 3

   Fill in the blanks

   Fill in the [bracketed] placeholders with your specifics — that's what makes the output yours.

4. Step 4

   Run and refine

   Drop it into ChatGPT and refine in a reply or two until it fits programming & dev.

Related packs

• 

  Programming & DevFree

  Frontend Engineering — Vol. 10

  Everything you need in one collection

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Regex Helpers

  Everything you need in one collection

  5 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Coding Assistants — Vol. 9

  Copy, tweak, and ship in minutes

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Frontend Engineering — Vol. 3

  Battle-tested prompts, organized and ready

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Coding Assistants — Vol. 11

  Hand-picked prompts you can copy and run today

  9 promptsChatGPT · Claude · Gemini
• 

  Programming & DevFree

  Coding Assistants — Vol. 12

  A focused toolkit for faster, better output

  9 promptsChatGPT · Claude · Gemini