A character relationship chart maps connections between cast members. It clarifies who likes whom, which factions align, and where conflicts sit. In anime contexts, charts often need to express complex ensemble dynamics, power hierarchies, and evolving ships across seasons.

• Family tree (hierarchical): lineage, clans, adopted ties.
• Ship map (node-link): romance, crushes, one-sided vs mutual; intensity via line weight.
• Faction/Org chart: squads, guilds, ranks; good for shounen ensembles.
• Rivalry/Ally matrix (adjacency matrix): dense casts; readable at scale; color-coded cells.
• Radial hub-and-spoke: one protagonist at center; supporting cast in rings.
• Timeline arcs: relationships forming/breaking per season or arc.
• Location-based map overlay: ties anchored to schools, districts, or bases.

• Color coding: romance=rose/pink, rivalry=red, alliance=blue, family=green, mentorship=purple.
• Line styles: solid=confirmed, dashed=rumored, dotted=one-sided; arrows for directionality.
• Icons: heart, lightning, shield, family crest; keep a legend.
• Portraits: chibi heads or manga busts at nodes for instant ID.
• Screentone textures: subtle halftone for groups or arcs; avoid moiré.
• Typography: high-contrast fonts, 12–16 pt minimum at 1080p export.
• Spacing: minimum 24–32 px between labels to prevent collisions.

Use neutral, descriptive prompts that define layout, labels, and style. Replace placeholders in braces.

1. Circular ship map (poster style) "{art_style}, clean vector anime infographic, circular relationship chart of {series_or_world}, character portraits arranged around a ring, labeled connections: {relationship_list}, color-coded legend (romance pink, rivalry red, alliance blue, family green), minimal background, high readability, 4K, crisp lines"

2. Whiteboard grid (matrix style) "overhead shot of an anime whiteboard relationship matrix for {cast_list}, rows and columns labeled, colored cells for ties (ally, rival, neutral), sticky notes with chibi head sketches, clean sans-serif labels, studio lighting, no clutter"

3. Clan genealogy (scroll style) "anime genealogy chart on parchment scroll for {clans}, branching family tree with crests, portraits in medallions, subtle screentone, leaf-green kinship lines, clear legend, museum-quality scan look"

4. Squad/org chart "anime org chart for {faction}, hierarchical boxes with rank badges, character busts, blue alliance lines, red conflict annotations, minimalistic UI panel style, high contrast"

5. Location overlay "city map with anime relationship overlays for {districts}, paths showing alliances/rivalries, labeled landmarks, thin colored lines, soft pastel palette, legible captions"

1. Define relationships: make a table with columns [Character A, Character B, Type, Strength, Direction, Season/Episode].
2. Pick layout based on cast size (see above).
3. Draft structure: sketch nodes and groups; reserve space for legend and title.
4. Generate base diagram: either prompt an AI for a clean base or produce a vector skeleton in a design tool.
5. Add portraits: keep consistent character descriptors (hair, outfit, emblem); reuse the same naming everywhere.
6. Color/line pass: apply the visual grammar; verify contrast and line weights.
7. Labeling pass: short names, avoid overlaps, add group badges.
8. Export: PNG for sharing (2048×2048 or 3840×2160), SVG/PDF for editing.
9. Version control: date-stamp files; keep a changelog as the story evolves.

• Character sheets: maintain a reference for each character’s name, colors, and emblem.
• Stable descriptors: use the same adjectives and outfit era in prompts.
• Framing: fix aspect ratios across episodes (e.g., all charts 16:9).
• Legend lock: do not change color meanings between charts.
• Batch updates: when relationships change, update the source data first.

• Color-blind-safe palettes; avoid red/green conflicts.
• Minimum text size targets: 14 pt at 1080p; 18 pt for mobile-first.
• High-contrast text over solids; avoid noisy textures under labels.
• RTL/LTR readiness: keep label containers flexible for translation.
• Use short labels and provide a legend for symbols.

• Social feed: 2048×2048 PNG/WebP, <2 MB if possible.
• Wiki/pitch: SVG or PDF for crisp scaling.
• Stream overlay: 1920×1080 with safe margins; test against dark and light themes.
• Archival: keep an SVG + JSON/CSV of relationships for future edits.

• Visual clutter: collapse minor NPCs into groups; use secondary pages for subplots.
• Label collisions: shorten names; rotate labels slightly; add leader lines.
• Confusing colors: switch to icon+line style; strengthen contrast.
• Inconsistent faces: standardize character descriptors and pose; reuse the same portrait crops.
• Ambiguous ties: add arrowheads or one-sided markers; clarify in legend.

Represent characters respectfully and avoid harmful depictions. Be extra careful with minors, parasocial boundaries, and targeted harassment. Use clear legends to prevent misinterpretation. Apply prompt safety practices to avoid generating inappropriate or unsafe content.

Pick a starter and adapt:

• Duo rivalry focus (2–6 chars): radial with red conflict lines.
• Homeroom roster (8–14 chars): grid with club/faction badges.
• Clan saga (12–20 chars): vertical family tree with crests.
• Season recap (15–30 chars): matrix heatmap of alliances/rivalries.
• City factions (10–18 chars): map overlay with zone colors.