Monster Maker · সর্বজনীন Open Skill

Monster Maker

Monster Maker Digen-এ একটি সর্বজনীন Open Skill। খুলে দেখুন এই ওয়ার্কফ্লো কী তৈরি করে।

@ExploreFly

Custom

0 0 1

https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/3656543/2026-10-14/bth4edq4.jpg

# Monster Maker

Design and render original monsters for concept art, game assets, or illustration. Use the anatomy lexicon in `references/` to keep prompts specific and visually coherent. There is no structured project state—carry the chosen design brief in the conversation and on the canvas.

## When to use

- User asks for a new monster, creature, beast, or horror/fantasy hybrid from text.
- User wants **weird anatomy**: extra eyes, asymmetric limbs, fused organs, unusual silhouettes, etc.
- User uploads a rough sketch or photo and wants it turned into or refined as a monster (**image-to-image**).
- User wants variants (color pass, more detail, different angle) while keeping the same creature.

## Reference file (read before prompting)

| File | Purpose | When to read |
|------|---------|--------------|
| `references/monster-anatomy-lexicon.md` | Vocabulary for silhouettes, skin, limbs, heads, odd organs, and prompt patterns | Before the first `generate_image` in a session, and again when adding new bizarre parts |

Do **not** paste the entire lexicon into the user chat. Pull only the sections that match the current design.

## Workflow

1. **Brief** — Confirm (or infer): mood (cute / uncanny / body-horror / epic fantasy), setting, and one anchor trait (e.g. “ jellyfish skull ”, “ too many elbows ”). If the user attached an image, call `recognize_image` once to list visible subjects, then plan how to **monsterize** them.
2. **Lexicon** — `read_skill_file(monster-maker, references/monster-anatomy-lexicon.md)` and pick 3–6 concrete traits (silhouette + surface + one “signature” oddity).
3. **Prompt** — Write a single **English** image prompt: subject + anatomy details + materials + lighting + camera + style suffix. Avoid copyrighted character names.
4. **Generate** — Call `generate_image` with the channel rules below. Use short **`name`** (creature nickname) and **`entity_type='characters'`** (or `'props'` for isolated body-part studies).
5. **Iterate** — On success, summarize what was generated. For edits, reuse the last canvas asset URL/`asset_id` in `input_urls` and pick the appropriate **i2i** channel.

Use `write_todos` when the user requests a batch (e.g. lineup of three monsters or turnarounds).

## Image model channels (required)

Always pass **`model` as a channel**, never a physical model name.

### Text-to-image (no reference image)

- **`model='t2i'`** — Default for new monsters from text only.
- Do **not** pass `input_urls` for pure text-to-image.

Example:

```text
generate_image(
  prompt=<English prompt built from lexicon>,
  model='t2i',
  name=<creature name>,
  entity_type='characters',
  orientation=<landscape|portrait|square per user>,
)
```

### Image-to-image (user or canvas reference)

Requires **`input_urls`** with one primary reference (sketch, photo, or last generated monster). **`prompt`** describes what to change or enhance.

| Channel | Use when |
|---------|----------|
| **`i2i.hd.lite`** | Fast iterations, light polish, small pose or color tweaks, preserving overall composition |
| **`i2i.hd`** | Default monsterization or detail pass: sharper anatomy, textures, lighting; moderate prompt changes |
| **`i2i.hd.gpt`** | Complex multi-part edits, strong adherence to long anatomical instructions, combining several lexicon traits at once |

Selection rule:

1. First refinement from a user upload → prefer **`i2i.hd`** unless the user asked for a quick draft → then **`i2i.hd.lite`**.
2. After **`i2i.hd`**, if anatomy still misses the brief or the prompt lists many structural changes → **`i2i.hd.gpt`**.
3. Minor touch-ups on an already good render → **`i2i.hd.lite`**.

Example:

```text
generate_image(
  prompt=<English edit instructions>,
  input_urls=[<reference asset_id or url>],
  model='i2i.hd',
  name=<creature name>,
  entity_type='characters',
)
```

**NSFW / gore:** `.hd*` channels do **not** support NSFW. Keep designs stylized fantasy/horror within platform policy; refuse explicit sexual or ex