> For the complete documentation index, see [llms.txt](https://learn.fleek.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fleek.xyz/best-practices/anime-content.md).

# Anime Content

**Welcome to the Anime branch of Fleek!**&#x20;

\
The Golden Rule: Tell a Story, Don't Just List Facts

Instead of describing just what your character looks like, think about what they are doing, feeling, and the world they inhabit.

* Bad (Static): "An anime girl with pink hair and green eyes."
* Good (Dynamic): "On a bustling Tokyo street at night, an anime girl with bubblegum-pink twintails and wide, emerald eyes looks over her shoulder with a mischievous wink, the neon signs reflecting in her gaze."<br>

#### 1. It All Starts with the Vibe: Setting the Scene

Before you detail your character, establish the overall aesthetic. This is the most critical step in defining the image's style and mood.

{% hint style="info" %}
Actionable Tip: Start your prompt with a phrase that sets the artistic tone.
{% endhint %}

Examples of "Vibes":

* A classic, 90s anime aesthetic screenshot...
* An energetic, modern shonen anime style action scene...
* A soft and romantic, shoujo anime style illustration...
* A painterly, Studio Ghibli inspired landscape...
* A gritty, dark fantasy manga panel…

<br>

#### 2. The "Medium" is Your Friend: Choose Your Format

Just as "shot on an iPhone" grounds a realistic photo, the "medium" grounds an anime image, making it feel more authentic.

{% hint style="info" %}
Actionable Tip: Use keywords that specify the format of the anime or manga.
{% endhint %}

Phrases to Use:

* ...anime screenshot
* ...manga panel
* ...key animation frame (genga)
* ...promotional key visual

***

#### 3. Dynamic Characters: Action, Gaze, and Expression<br>

A character is more than their hair and eye color. Give your influencer something to do, a place to look, and a reason for their expression.

{% hint style="info" %}
Actionable Tip: Combine an action, a gaze, and an expression to bring your character to life.
{% endhint %}

Breakdown:

Action (What are they doing?):

* casually leaning against a vending machine
* dramatically pointing forward, shouting a challenge
* in mid-air, delivering a powerful kick
* running with a piece of toast in their mouth<br>

Gaze (Where are they looking?):

* gazing at falling cherry blossoms
* a determined gaze locked on an unseen opponent
* shyly glancing away, a blush on their cheeks<br>

Expression (What are they feeling?):

* a classic tsundere pout
* a wide, triumphant grin
* a single, dramatic tear rolling down their cheek

#### Putting It All Together (Full Example):

"A classic 90s anime aesthetic screenshot of a young man with messy black hair and a determined expression. He's in a dimly lit dojo, holding a wooden sword in a ready stance, his gaze sharp and focused on an opponent just off-camera. The scene has a low, dynamic angle and classic cel-shading."

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.fleek.xyz/best-practices/anime-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
