AI Tools

A clean 3×3 [ratio] storyboard grid with nine equal [ratio] sized panels on [4:5] ratio. 

Use the reference image as the base product reference. Keep the same product, packaging design, branding, materials, colors, proportions and overall identity across all nine panels exactly as the reference. The product must remain clearly recognizable in every frame. The label, logo and proportions must stay exactly the same.

This storyboard is a high-end designer mockup presentation for a branding portfolio. The focus is on form, composition, materiality and visual rhythm rather than realism or lifestyle narrative. The overall look should feel curated, editorial and design-driven.

FRAME 1:
Front-facing hero shot of the product in a clean studio setup. Neutral background, balanced composition, calm and confident presentation of the product.

FRAME 2:
Close-up shot with the focus centered on the middle of the product. Focusing on surface texture, materials and print details.

FRAME 3:
Shows the reference product placed in an environment that naturally fits the brand and product category. Studio setting inspired by the product design elements and colours. 

FRAME 4:
Product shown in use or interaction on a neutral studio background. Hands and interaction elements are minimal and restrained, the look matches the style of the package. 

FRAME 5:
Isometric composition showing multiple products arranged in a precise geometric order from the top isometric angle. All products are placed at the same isometric top angle, evenly spaced, clean, structured and graphic.

FRAME 6:
Product levitating slightly tilted on a neutral background that matches the reference image color palette. Floating position is angled and intentional, the product is floating naturally in space.

FRAME 7:
is an extreme close-up focusing on a specific detail of the label, edge, texture or material behavior.

FRAME 8:
The product in an unexpected yet aesthetically strong setting that feels bold, editorial and visually striking.
Unexpected but highly stylized setting. Studio-based, and designer-driven. Bold composition that elevates the brand.

FRAME 9:
Wide composition showing the product in use, placed within a refined designer setup. Clean props, controlled styling, cohesive with the rest of the series.

CAMERA & STYLE:
Ultra high-quality studio imagery with a real camera look. Different camera angles and framings across frames. Controlled depth of field, precise lighting, accurate materials and reflections. Lighting logic, color palette, mood and visual language must remain consistent across all nine panels as one cohesive series.

OUTPUT:
A clean 3×3 grid with no borders, no text, no captions and no watermarks.

Minimal Countdown Scene:
Count down from 3 → 2 → 1 using a clean, modern font.
Apply left-to-right color transitions with subtle background gradients.
Keep the design minimal — shift font and background colors smoothly between counts.

Start with a pure white background,
Then transition quickly into lively, elegant tones: yellow, pink, blue, orange — fast, energetic transitions to build excitement.

After the countdown, display
“Introducing”
In a monospace font with a sleek text animation.

Next Scene:
Center the Mitte.ai and Remotion logos on a white background.
Place them side by side — Mitte.ai on the left, Remotion on the right.

First, fade in both logos.
Then animate a vertical line drawing from bottom to top between them.

Final Moment:
Slowly zoom into the logo section while shifting background colors
With left-to-right and right-to-left transitions in a celebratory motion.

Overall Style:
Startup vibes — elegant, creative, modern, and confident.

{ "TASK": "Design a unique 'Valorant' Agent Key Art. Riot Games Art Style.",
"VISUAL_ID": "Sharp 2.5D digital painting. Fusion of anime & western comic. Matte textures, clean lines, no noise.",
"PALETTE": "Primary: Dark Slate Blue (#0f1923). Branding: Hyper-Red (#ff4655). Ability: Neon highlight.",
"AGENT": "Athletic, confident. Future-tech streetwear (straps, windbreaker, tactical gloves). Sharp facial planes. Hair: Thick, sculpted chunks (no strands).","EFFECTS": "Wielding stylized elemental power (solid energy forms, not realistic particles).", "BG": "Abstract motion graphics, flat geometric planes, kinetic typography. Red/Dark contrast slicing the frame.",
"LIGHT": "Strong rim lighting, hard-edge cast shadows.", "NEG": "Photorealism, grit, dirt, oil painting, soft focus, 3d render, shiny metal, messy, noise, blur."
}//You can add Name and Skills or size like 16:9 here.

Create a cinematic, ultra-realistic adventure image for caravan that captures what Australians love most — vast landscapes, wildlife, and freedom.

Show a Hike RV caravan correctly attached to a pickup truck, positioned on a scenic Australian dirt road or lookout. The caravan and pickup are either slowly moving forward or confidently paused, facing into the landscape, with perfectly realistic towing alignment.

Environment & vibe:

Wide open Australian landscape (outback plains, bushland, or elevated lookout)

A small group of kangaroos in the mid-ground or background, naturally placed and not posing

Native vegetation like gum trees, dry grass, and rugged terrain

Strong sense of scale and openness Australians love

Sky & lighting:

Clear blue sky

Golden-hour sunlight (early morning or late afternoon)

Warm light hitting the caravan and pickup, long natural shadows

Subtle dust in the air for depth (not overpowering)

Camera & cinematic feel:

Low to mid-wide angle

Foreground depth with road or grass

Deep background stretching to the horizon

Film-like contrast and colour balance (natural, not stylised)

Style & realism:

Photorealistic cinematic travel photography

True-to-life textures and reflections

Natural colour grading (earth tones, blues, warm highlights)

No exaggeration or fantasy elements

Output rules:

No text

No people

No logos or overlays

Aspect ratio

Mood:

Epic

Free

Adventurous

Proudly Australian

Inspires exploration

Reconstruct the central object of the given 2D image as a true 3D wireframe model.

- Interpret the 2D shape as volumetric geometry and extrude it into depth.

- Build visible 3D structure with wireframe mesh lines wrapping around the form (front, sides, and curvature).

- Use thin, precise, glowing white wireframe lines only, no solid surfaces, no flat fills.

- Apple App Store style icon, premium iOS design language, WWDC-inspired.

- Rounded square app icon, centered and symmetrical.

- Soft blue gradient background, subtle glow.

- Clean orthographic front view with clear depth cues (z-axis wireframe).

- High-resolution, futuristic UI icon.

- No text, no logos, no illustration style


Negatives:

2D flat design, flat icon, illustration, lighting-only depth, fake 3D, gradients on object, shading, shadows, cartoon style, sketch, photorealism, textures, noise, grain

You are an **expert AI & Prompt Engineer** with ~20 years of applied experience deploying LLMs in real systems.
You reason as a practitioner, not an explainer.

### OPERATING CONTEXT

* Fluent in LLM behavior, prompt sensitivity, evaluation science, and deployment trade-offs
* Use **frameworks, experiments, and failure analysis**, not generic advice
* Optimize for **precision, depth, and real-world applicability**

### CORE FUNCTIONS (ANCHORS)

When responding, implicitly apply:

* Prompt design & refinement (context, constraints, intent alignment)
* Behavioral testing (variance, bias, brittleness, hallucination)
* Iterative optimization + A/B testing
* Advanced techniques (few-shot, CoT, self-critique, role/constraint prompting)
* Prompt framework documentation
* Model adaptation (prompting vs fine-tuning/embeddings)
* Ethical & bias-aware design
* Practitioner education (clear, reusable artifacts)

### DATASET CONTEXT

Assume access to a dataset of **5,010 prompt–response pairs** with:
`Prompt | Prompt_Type | Prompt_Length | Response`

Use it as needed to:

* analyze prompt effectiveness,
* compare prompt types/lengths,
* test advanced prompting strategies,
* design A/B tests and metrics,
* generate realistic training examples.

### TASK

```
[INSERT TASK / PROBLEM]
```

Treat as production-relevant.
If underspecified, state assumptions and proceed.

### OUTPUT RULES

* Start with **exactly**:

```
🔒 ROLE MODE ACTIVATED
```

* Respond as a senior prompt engineer would internally:
  frameworks, tables, experiments, prompt variants, pseudo-code/Python if relevant.
* No generic assistant tone. No filler. No disclaimers. No role drift.

Using the uploaded photo of the African boy as the base face, create a highly detailed, realistic image of him confidently and relaxedly sitting at the center of a futuristic music streaming experience room, with symmetrical and cinematic composition.
Maintain his facial features, skin tone, and hair texture exactly as in the photo.
His eyes are open, looking calmly ahead, with a gentle, confident expression. Camera angle is face-level, straight-on, capturing his full face clearly.
He wears a stylish outfit: an oversized high-street streetwear top in black or dark olive, modern cargo pants, and premium sneakers with contemporary high-fashion vibes.
He is wearing premium over-ear headphones.
Relaxed seated pose, legs naturally apart, hands resting on his thighs, radiating confidence, calmness, and strong presence.
Behind him is a large futuristic digital screen with a Spotify-inspired UI, displaying album covers, playlists, and modern interface elements in neon green and black tones.
From his headphones and head area, floating musical visual elements emerge: glowing music notes, holographic equalizers, treble clef symbols, and luminous sound waves, forming a circular energy aura of music around his head.
Use cinematic lighting, soft shadows, and photorealistic textures to make the scene feel immersive, stylish, and magazine-quality.

You are a CLAUDE.md architect — an expert at writing concise, high-impact project instruction files for AI coding agents (Claude Code, Cursor, Windsurf, Zed, etc.).

Your task: Generate a production-ready CLAUDE.md file based on the project details I provide.

## Principles You MUST Follow

1. **Conciseness is king.** The final file MUST be under 150 lines. Every line must earn its place. If Claude already does something correctly without the instruction, omit it.
2. **WHY → WHAT → HOW structure.** Start with purpose, then tech/architecture, then workflows.
3. **Progressive disclosure.** Don't inline lengthy docs. Instead, point to file paths: "For auth patterns, see src/auth/README.md". Claude will read them when needed.
4. **Actionable, not theoretical.** Only include instructions that solve real problems — commands you actually run, conventions that actually matter, gotchas that actually bite.
5. **Provide alternatives with negations.** Instead of "Never use X", write "Never use X; prefer Y instead" so the agent doesn't get stuck.
6. **Use emphasis sparingly.** Reserve IMPORTANT/YOU MUST for 2-3 critical rules maximum.
7. **Verify, don't trust.** Always include how to verify changes (test commands, type-check commands, lint commands).

## Output Structure

Generate the CLAUDE.md with exactly these sections:

### Section 1: Project Overview (3-5 lines max)
- Project name, one-line purpose, and core tech stack.

### Section 2: Architecture Map (5-10 lines max)
- Key directories and what they contain.
- Entry points and critical paths.
- Use a compact tree or flat list — no verbose descriptions.

### Section 3: Common Commands
- Build, test (single file + full suite), lint, dev server, and deploy commands.
- Format as a simple reference list.

### Section 4: Code Conventions (only non-obvious ones)
- Naming patterns, file organization rules, import ordering.
- Skip anything a linter/formatter already enforces automatically.

### Section 5: Gotchas & Warnings
- Project-specific traps and quirks.
- Things Claude tends to get wrong in this type of project.
- Known workarounds or fragile areas of the codebase.

### Section 6: Git & Workflow
- Branch naming, commit message format, PR process.
- Only include if the team has specific conventions.

### Section 7: Pointers (Progressive Disclosure)
- List of files Claude should read for deeper context when relevant:
  "For API patterns, see @docs/api-guide.md"
  "For DB migrations, see @prisma/README.md"

## What I'll Provide

I will describe my project with some or all of the following:
- Tech stack (languages, frameworks, databases, etc.)
- Project structure overview
- Key conventions my team follows
- Common pain points or things AI agents keep getting wrong
- Deployment and testing workflows

If I provide minimal info, ask me targeted questions to fill the gaps — but never more than 5 questions at a time.

## Quality Checklist (apply before outputting)

Before generating the final file, verify:
- [ ] Under 150 lines total?
- [ ] No generic advice that any dev would already know?
- [ ] Every "don't do X" has a "do Y instead"?
- [ ] Test/build/lint commands are included?
- [ ] No @-file imports that embed entire files (use "see path" instead)?
- [ ] IMPORTANT/MUST used at most 2-3 times?
- [ ] Would a new team member AND an AI agent both benefit from this file?

Now ask me about my project, or generate a CLAUDE.md if I've already provided enough detail.