Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- CHARACTER-SPECIFIC BEYBLADE GENERATOR
- VERSION 1.0 — REFERENCE-IDENTITY TRANSLATION + CANONICAL PART STACK + PERFORMANCE LOGIC + LAUNCH SYSTEM + PACKAGING CONTINUITY
- ══════════════════════════════════════════════════
- CORE PURPOSE
- ══════════════════════════════════════════════════
- Create ONE polished, professional product-development image that transforms a supplied CHARACTER REFERENCE into a complete, believable, character-specific BEYBLADE product system.
- The reference character is the PRIMARY DESIGN AUTHORITY.
- Do not merely place the character's colors, face, logo, or silhouette onto a generic spinning top.
- Design a Beyblade that feels as though its:
- - visual construction
- - part geometry
- - attack/defense/stamina/balance behavior
- - weight distribution
- - gimmick
- - contact points
- - launcher
- - ripcord or launch interface
- - performance identity
- - emblem
- - packaging
- - product graphics
- - accessory treatment
- were all purpose-designed from the specific character.
- The finished result should communicate:
- THIS CHARACTER
- → TRANSLATED INTO A BEYBLADE DESIGN LANGUAGE
- → AS A FUNCTIONAL PHYSICAL TOY
- → WITH A COHERENT PART SYSTEM
- → WITH A CHARACTER-APPROPRIATE BATTLE IDENTITY
- → WITH ITS OWN LAUNCH EQUIPMENT
- → PRESENTED AS A COMPLETE RETAIL PRODUCT
- Generate the FINISHED IMAGE immediately after interpreting the supplied inputs.
- Do not return an explanation, design proposal, or text-only specification.
- ══════════════════════════════════════════════════
- CUSTOMIZABLE INPUTS
- ══════════════════════════════════════════════════
- CHARACTER REFERENCE:
- [ATTACH ONE OR MORE REFERENCE IMAGES]
- BEYBLADE ERA / SYSTEM:
- [SURPRISE ME / ORIGINAL CHARACTER-SPECIFIC SYSTEM / SPECIFY]
- PERFORMANCE ARCHETYPE:
- [SURPRISE ME / ATTACK / DEFENSE / STAMINA / BALANCE / HYBRID / SPECIFY]
- SIGNATURE GIMMICK:
- [SURPRISE ME / INFER FROM CHARACTER / SPECIFY]
- PRIMARY MOTIF OR POWER:
- [INFER FROM CHARACTER / SPECIFY]
- SPIN DIRECTION:
- [SURPRISE ME / RIGHT / LEFT]
- PRODUCT TIER:
- [STANDARD RETAIL RELEASE / PREMIUM RELEASE / SPECIAL EDITION / SURPRISE ME]
- PACKAGING STYLE:
- [ERA-APPROPRIATE RETAIL BOX / BLISTER / WINDOW BOX / PREMIUM COLLECTOR BOX / SURPRISE ME]
- CUSTOM NOTES:
- [OPTIONAL NATURAL-LANGUAGE INSTRUCTIONS]
- If a field is blank, DEFAULT, INFER, or SURPRISE ME, intelligently choose one coherent answer from the character and propagate that choice through the entire product.
- Do not display placeholders such as DEFAULT, SURPRISE ME, or INFER in the final image.
- ══════════════════════════════════════════════════
- REFERENCE IDENTITY LOCK
- ══════════════════════════════════════════════════
- Before designing the Beyblade, establish one canonical interpretation of the referenced character.
- Preserve and analyze all identity-bearing traits that materially distinguish the character, including when applicable:
- - species
- - anatomy
- - body proportions
- - silhouette
- - head shape
- - face
- - eyes
- - ears
- - horns
- - hair
- - fur
- - skin
- - armor
- - clothing
- - major equipment
- - asymmetry
- - markings
- - scars
- - symbols
- - palette
- - material cues
- - powers
- - occupation
- - personality
- - movement style
- - combat style
- - recurring motifs
- - elemental or thematic associations
- Do not preserve every trait literally.
- Translate them intelligently into product design.
- The Beyblade must feel recognizably derived from the reference even when the character itself is not physically depicted on the top.
- Use the character as a GENERATIVE DESIGN SYSTEM.
- Examples of translation logic include:
- character silhouette
- → major outer-ring geometry
- signature weapon
- → impact blades, protrusions, contact geometry, or emblem structure
- armor
- → layered mechanical surfacing
- body markings
- → controlled graphics or molded relief
- power or element
- → performance gimmick, material treatment, or symbolic geometry
- movement style
- → attack pattern or stability behavior
- personality
- → aggressive, technical, elegant, deceptive, defensive, chaotic, precise, or endurance-oriented performance identity
- asymmetry
- → intentional asymmetric mass or visual structure when mechanically plausible
- species traits
- → abstracted structural motifs rather than pasted animal faces
- Do not reduce character translation to palette matching.
- ══════════════════════════════════════════════════
- BEYBLADE SYSTEM SELECTION
- ══════════════════════════════════════════════════
- If the user specifies a recognizable Beyblade era or mechanical system, respect that system's defining construction vocabulary.
- If no system is specified, create an ORIGINAL BEYBLADE-COMPATIBLE SYSTEM that feels plausible within the general physical logic of competitive spinning-top toys without falsely claiming to be an existing official product.
- The chosen system must establish:
- - one clear top architecture
- - identifiable separable components
- - a defined assembly axis
- - locking interfaces
- - a tip or driver
- - a central rotational body
- - one dominant contact layer or attack ring
- - a launcher interface
- - intended spin direction
- - battle-performance logic
- Do not mix mutually incompatible parts from unrelated Beyblade generations merely because they are visually recognizable.
- If hybridization is intentionally selected, redesign the interfaces so the result behaves as one coherent system.
- ══════════════════════════════════════════════════
- MASTER PRODUCT LEDGER
- ══════════════════════════════════════════════════
- Before producing any view, establish ONE canonical Beyblade design.
- Lock:
- - total component count
- - component names or identities
- - component order
- - upper and lower orientation
- - assembly axis
- - spin direction
- - locking method
- - outer silhouette
- - contact points
- - major dimensions
- - color placement
- - translucent versus opaque materials
- - metal versus plastic distribution
- - emblem placement
- - graphics
- - molded motifs
- - gimmick mechanism
- - performance role
- - launcher compatibility
- - launcher type
- - ripcord or pull mechanism
- - package contents
- - package dimensions and panel layout
- Every representation must derive from this single master.
- Never independently redesign:
- - the assembled Beyblade
- - exploded parts
- - launcher
- - packaged contents
- - packaging artwork
- - instruction diagrams
- between views.
- ══════════════════════════════════════════════════
- PERFORMANCE IDENTITY ENGINE
- ══════════════════════════════════════════════════
- Translate the character into a believable battle-performance concept.
- Select one coherent primary archetype:
- ATTACK
- DEFENSE
- STAMINA
- BALANCE
- or an explicitly justified HYBRID.
- Then define the Beyblade's behavior through actual geometry and mass logic.
- ATTACK may emphasize:
- - aggressive perimeter contact points
- - uneven or directional geometry
- - high-impact protrusions
- - rapid movement
- - lower or more mobile tip behavior
- - strong recoil accepted as part of the design
- DEFENSE may emphasize:
- - compact mass
- - guarded perimeter geometry
- - recoil deflection
- - stable center of gravity
- - low movement
- - shock-dispersing structures
- STAMINA may emphasize:
- - smooth aerodynamic perimeter
- - low friction
- - rotational symmetry
- - efficient mass placement
- - long-spin tip geometry
- - reduced collision drag
- BALANCE may combine traits deliberately without becoming mechanically incoherent.
- The physical form must support the claimed performance identity.
- Do not label a generic symmetric top "attack type" while giving it no meaningful attack geometry.
- ══════════════════════════════════════════════════
- SIGNATURE CHARACTER GIMMICK
- ══════════════════════════════════════════════════
- Every generated Beyblade should possess ONE principal signature gimmick derived from the reference character.
- The gimmick must be:
- - visually understandable
- - mechanically plausible within toy-scale logic
- - materially compatible with the chosen system
- - relevant to the character
- - visible enough to distinguish the design
- - integrated into battle behavior rather than attached as decorative clutter
- Possible categories include:
- - directional contact geometry
- - free-spinning sub-ring
- - rubberized contact section
- - spring-loaded or flexing component
- - shifting mass
- - reversible component
- - mode change
- - adjustable tip
- - deployable contact geometry
- - spin-direction interaction
- - counterattack surface
- - destabilizing attack pattern
- - defensive shock absorption
- - stamina-preserving bearing
- - controlled asymmetry
- Do not automatically use any particular gimmick.
- Invent the one that best expresses the supplied character.
- If the character's abilities would be unsafe, impossible, supernatural, or nonphysical at toy scale, translate their EFFECT into mechanical behavior rather than pretending the toy literally possesses the power.
- ══════════════════════════════════════════════════
- CANONICAL COMPONENT STACK
- ══════════════════════════════════════════════════
- Construct the Beyblade from a clear vertical stack.
- Every major visible component must have:
- - a distinct structural role
- - one position in the assembled product
- - one corresponding exploded representation
- - one stable color/material identity
- - one connection to neighboring components
- - no duplicate counterpart unless duplication is physically intentional
- The exact number of parts may vary by selected system.
- However, the finished product must remain understandable as a real assembled spinning top rather than a pile of arbitrary decorative layers.
- Build the canonical stack FIRST.
- Then derive the assembled top from it.
- Then derive the exploded view from the same exact components.
- Do not create the hero Beyblade first and improvise unrelated exploded pieces afterward.
- ══════════════════════════════════════════════════
- COMPONENT BIJECTION LOCK
- ══════════════════════════════════════════════════
- Every canonical component must satisfy:
- ONE COMPONENT
- ↔ ONE ASSEMBLED LOCATION
- ↔ ONE EXPLODED COMPONENT
- ↔ ONE PACKAGE LOCATION if included
- ↔ ONE INSTRUCTIONAL IDENTITY if diagrammed
- No component may:
- - disappear between views
- - change shape between views
- - change major colors between views
- - split into several unexplained pieces
- - merge with another component without a designed mechanism
- - appear in packaging without belonging to the declared product
- - exist in an exploded diagram without an assembly location
- Hidden interior pieces remain part of the canonical inventory even when occluded in the assembled view.
- ══════════════════════════════════════════════════
- EXPLODED PARTS VIEW
- ══════════════════════════════════════════════════
- Include a clear exploded assembly view of the SAME Beyblade shown in the hero presentation.
- Arrange components along the actual assembly axis.
- Maintain:
- - correct top-to-bottom order
- - stable orientation
- - one-to-one correspondence
- - proportional scale
- - matching geometry
- - matching materials
- - matching colors
- - matching markings
- - matching locking surfaces
- Exploded means DISASSEMBLED FOR EXPLANATION.
- It does not mean:
- - shattered
- - broken
- - damaged
- - blown apart
- - debris
- - cracked
- - battle-destroyed
- Provide enough separation for each component to be legible while preserving obvious alignment.
- The viewer should be able to mentally slide the parts together and reproduce the assembled hero exactly.
- ══════════════════════════════════════════════════
- EMBLEM + CHARACTER ICONOGRAPHY
- ══════════════════════════════════════════════════
- Create one central emblem or avatar mark derived from the reference character.
- This emblem should be visually simplified enough to function at toy scale.
- It may abstract:
- - face
- - species
- - helmet
- - eye motif
- - insignia
- - weapon symbol
- - power symbol
- - signature mark
- Do not paste a full photographic portrait into the center unless the requested product style specifically supports printed character portraits.
- The emblem must remain the SAME design wherever repeated:
- - Beyblade center
- - package front
- - launcher insignia
- - instruction graphics
- - optional product badge
- Do not allow alternate versions of the emblem to appear accidentally.
- ══════════════════════════════════════════════════
- LAUNCHER SYSTEM
- ══════════════════════════════════════════════════
- Design one dedicated launcher compatible with the canonical Beyblade.
- Its interface must correspond to the top's chosen spin direction and locking geometry.
- Character-specific styling may influence:
- - grip silhouette
- - molded paneling
- - accent colors
- - emblem
- - ergonomic form
- - surface detailing
- but the launcher must remain recognizably functional.
- It must include:
- - launcher body
- - Beyblade coupling interface
- - grip area
- - pull mechanism or equivalent launching mechanism
- - coherent orientation for use
- If a ripcord system is used, the ripcord must be one continuous physical object.
- If a string launcher is used, show a plausible reel or retracting mechanism.
- Do not combine mutually incompatible launch mechanisms unless specifically designed as a dual-mode launcher.
- ══════════════════════════════════════════════════
- RIPCORD CONTINUITY + STORAGE LOCK
- ══════════════════════════════════════════════════
- If the launcher uses a plastic ripcord, establish ONE canonical ripcord before depicting any storage or operational state.
- The ripcord must have:
- - one continuous strip
- - continuous molded teeth where appropriate
- - one handle end
- - one insertion end
- - consistent width and thickness
- - flexible plastic behavior
- DEPLOYED STATE:
- The ripcord may be largely straight or naturally slightly bowed.
- PACKAGED STATE:
- Route the SAME full-length intact ripcord through a broad, gentle tray curve or loop so it fits within the package.
- Treat the material as resilient flexible plastic.
- Do not represent storage by:
- - snapping it
- - cutting it
- - separating it into segments
- - sharply folding it back on itself
- - giving it broken teeth
- - melting it
- - replacing part of it with another piece
- The curved packaged state and straightened operating state are two configurations of the same object.
- Mentally straighten the stored ripcord and confirm it becomes the operational ripcord without changing length, geometry, teeth, or handle.
- ══════════════════════════════════════════════════
- LAUNCH COMPATIBILITY VALIDATION
- ══════════════════════════════════════════════════
- The Beyblade, launcher, and pull mechanism must form one working interface system.
- Verify:
- - the top connects at the correct central launch point
- - the launcher is oriented consistently with the selected spin direction
- - the coupling is mechanically reachable
- - the ripcord or launch mechanism enters the correct region
- - the user's hand could plausibly hold the launcher without blocking operation
- - the launcher shown in packaging is the same launcher shown separately
- Do not create a decorative launcher that could not physically engage the Beyblade.
- ══════════════════════════════════════════════════
- MASTER PACKAGE SYSTEM
- ══════════════════════════════════════════════════
- If packaging is included, design ONE master package structure before showing any package state.
- Establish:
- - package dimensions
- - front panel
- - back panel
- - left panel
- - right panel
- - top
- - bottom
- - flaps
- - tabs
- - windows
- - hang tab if appropriate
- - interior tray footprint
- - location of Beyblade
- - location of launcher
- - ripcord route
- - accessory locations
- - major graphics
- - logos
- - character emblem
- - product name
- - visual hierarchy
- Use this master package as the source of every packaging representation.
- Do not independently design a sealed box and a flattened box.
- ══════════════════════════════════════════════════
- SEALED ↔ UNFOLDED PACKAGE CONTRACT
- ══════════════════════════════════════════════════
- When both a sealed package and an unfolded package net are shown, they must depict THE SAME PHYSICAL PACKAGE.
- Construct the flat package net first with stable:
- - panel dimensions
- - adjacency
- - fold lines
- - flap geometry
- - graphics
- - windows
- - logos
- - product name
- - character artwork
- - color fields
- - legal or decorative microtext regions
- Then mentally fold that same net into the sealed package.
- The resulting box must reproduce the displayed sealed package.
- Panel relationships must remain physically possible.
- For example:
- - front graphics remain on the front
- - side-panel artwork moves only according to the fold
- - windows retain the same dimensions and location
- - top and bottom flaps correspond
- - no artwork teleports between panels
- - no panel changes proportion
- - no extra panel appears
- - no required panel disappears
- Reverse-check the result:
- SEALED BOX
- → UNFOLD ALONG REAL SEAMS
- → SAME DISPLAYED NET
- If this reverse transformation would fail, correct the packaging before generation.
- ══════════════════════════════════════════════════
- INTERIOR TRAY + CONTENT PLACEMENT
- ══════════════════════════════════════════════════
- Design one package tray capable of physically holding the declared contents.
- Provide shaped recesses or channels for:
- - assembled Beyblade
- - launcher
- - ripcord or launch mechanism
- - optional accessory if explicitly generated
- The tray must respect each object's actual dimensions.
- Do not place objects through one another.
- Do not shrink or stretch accessories simply to make them fit.
- The stored ripcord route must preserve the entire continuous object.
- If the contents cannot plausibly fit, increase package dimensions or reorganize the tray rather than damaging, cropping, or deleting them.
- ══════════════════════════════════════════════════
- PACKAGE CONTENTS LOCK
- ══════════════════════════════════════════════════
- Declare one canonical retail contents set.
- Normally include only:
- - ONE Beyblade
- - ONE compatible launcher
- - ONE corresponding launch mechanism
- - packaging
- Add additional accessories only when the generated concept genuinely requires them.
- Every declared item must be:
- - represented in the package if package contents are visible
- - compatible with the central product
- - absent from the package if it was never declared
- Do not introduce duplicate tops, duplicate launchers, mystery parts, unrelated weapons, or random collectibles merely to fill the tray.
- ══════════════════════════════════════════════════
- PRODUCT NAME + BRANDING
- ══════════════════════════════════════════════════
- Invent one concise Beyblade product name that reflects the character's identity and battle concept.
- Use a naming structure appropriate to the selected system while avoiding accidental duplication of an existing official product unless explicitly requested.
- The product name must remain identical across all visible occurrences.
- Use restrained package text.
- Prioritize legibility for:
- - product name
- - type or performance designation if displayed
- - spin direction if displayed
- - one short signature-gimmick callout if useful
- Other tiny box copy may appear as decorative product-print texture and need not be individually readable.
- Do not fill the image with paragraphs of pseudo-technical writing.
- ══════════════════════════════════════════════════
- CHARACTER ART ON PACKAGING
- ══════════════════════════════════════════════════
- If character artwork appears on the box, preserve the supplied character's identity accurately.
- Packaging artwork is secondary to the physical Beyblade.
- Do not allow a large character portrait to overwhelm the product-development purpose of the image.
- The character depiction may use a dramatic action pose appropriate to their identity, but:
- - anatomy must remain canonical
- - distinctive features must remain recognizable
- - costume details should not arbitrarily drift
- - the package art must not introduce a contradictory alternate character design
- If the reference character has unusual anatomy or topology, preserve it rather than normalizing it to conventional human anatomy.
- ══════════════════════════════════════════════════
- MANUFACTURED-OBJECT REALISM
- ══════════════════════════════════════════════════
- The Beyblade and accessories must look like actual manufactured physical objects.
- Use believable materials such as:
- - injection-molded plastic
- - transparent or translucent plastic
- - painted or plated metal
- - rubber where mechanically useful
- - printed inserts
- - molded texture
- - recessed graphics
- - stickers or tampos when appropriate
- Maintain believable:
- - wall thickness
- - seam placement
- - attachment points
- - molded detail scale
- - material transitions
- - tolerances
- - surface finish
- - screw or fastening logic if visible
- Avoid impossible infinitely thin fins, unsupported floating decorations, ornamental spikes too fragile for a toy, or shapes that would obviously prevent spinning.
- Character specificity must operate within manufacturable geometry.
- ══════════════════════════════════════════════════
- BATTLE-CONTACT GEOMETRY
- ══════════════════════════════════════════════════
- Any perimeter feature intended to affect battle must physically reach the contact envelope.
- Do not create attack blades, defensive bumpers, rubber surfaces, or counterattack elements that are recessed so deeply they could never touch an opponent.
- At the same time, keep the outer geometry within believable toy-safe proportions unless a deliberately exaggerated fantasy product style is requested.
- Distinctive motifs should serve one or more functions:
- - contact
- - mass distribution
- - stability
- - recoil behavior
- - airflow
- - grip
- - alignment
- - visual identity
- Avoid meaningless mechanical-looking clutter.
- ══════════════════════════════════════════════════
- TIP / DRIVER LOGIC
- ══════════════════════════════════════════════════
- Design the lower contact system to support the performance identity.
- Consider:
- - point shape
- - surface area
- - friction
- - height
- - mobility
- - free rotation
- - material
- - mode switching
- - stabilization
- An attack-oriented design should not accidentally use a broad immobile high-friction tip unless a specific counterintuitive gimmick explains it.
- A stamina design should not use a geometry that would obviously create constant drag unless intentionally balanced by another mechanism.
- If the character-specific gimmick affects the driver or tip, make its operation visually understandable.
- ══════════════════════════════════════════════════
- SPIN DIRECTION + CHIRALITY
- ══════════════════════════════════════════════════
- Lock the chosen spin direction before building directional geometry.
- If the Beyblade uses directional attack blades, ramps, fins, or launcher tabs, orient them consistently with that spin.
- Do not mirror only one representation.
- The assembled hero, exploded parts, launcher interface, package diagrams, and visible directional iconography must all agree.
- If left-spin is selected, do not accidentally retain right-spin directional geometry from a conventional default.
- ══════════════════════════════════════════════════
- PRIMARY IMAGE FORMAT
- ══════════════════════════════════════════════════
- Create ONE cohesive premium PRODUCT-DEVELOPMENT BOARD.
- Recommended aspect ratio:
- 4:5 portrait or 5:4 landscape depending on which orientation gives the declared content enough readable space.
- Choose the orientation that protects clarity.
- The board should normally include:
- PRIMARY:
- 1. LARGE ASSEMBLED HERO BEYBLADE
- - dominant visual element
- - three-quarter product angle
- - complete and uncropped
- - enough size to read geometry, emblem, materials, and gimmick
- SECONDARY:
- 2. EXPLODED COMPONENT STACK
- - aligned to the real assembly axis
- - clearly subordinate to hero
- 3. DEDICATED LAUNCHER + RIPCORD / LAUNCH MECHANISM
- - same exact accessories used in packaging
- 4. SEALED RETAIL PACKAGE
- 5. UNFOLDED PACKAGE NET
- - same package, not a second design
- TERTIARY:
- 6. SMALL FUNCTIONAL DETAIL OR GIMMICK INSET
- - only when useful for understanding the character-specific mechanism
- Do not add redundant views merely because space remains.
- Every view must prove a different part of the product system.
- ══════════════════════════════════════════════════
- REPRESENTATIONAL INSTANCE CONTROL
- ══════════════════════════════════════════════════
- The board may show the SAME canonical Beyblade several times for explanatory purposes.
- These are not multiple products.
- Treat them as multiple views of ONE design.
- The hero view, exploded assembly, packaging depiction, and optional mechanism inset must all describe the same canonical unit.
- Do not interpret repeated representations as permission to create variant Beyblades.
- Unless explicitly requested, generate exactly ONE Beyblade design.
- ══════════════════════════════════════════════════
- VISUAL HIERARCHY
- ══════════════════════════════════════════════════
- The assembled Beyblade is the primary subject.
- Allocate the most area and highest clarity to it.
- The exploded view and launcher are secondary.
- Packaging views are supporting proof.
- Do not allow the box, text, character portrait, or diagrams to become larger or more visually dominant than the actual Beyblade.
- Maintain enough negative space for:
- - clean separation between views
- - visible exploded alignment
- - readable launcher silhouette
- - intact package views
- - complete ripcord routing
- - legible product name
- Avoid collisions, overlaps, or crowding that make separate components appear fused.
- ══════════════════════════════════════════════════
- BACKGROUND + RENDERING STYLE
- ══════════════════════════════════════════════════
- Use a clean professional product-design presentation.
- Preferred background:
- - white
- - light neutral
- - subtle studio gradient
- - restrained technical-board surface
- Use controlled studio lighting that reveals:
- - molded geometry
- - metal surfaces
- - translucent components
- - edge thickness
- - mechanical interfaces
- - embossed details
- Aim for high-end toy photography combined with precise industrial-design visualization.
- The product should feel tangible, manufacturable, collectible, and ready for retail.
- Do not turn the background into a cinematic battlefield that obscures product information unless the user explicitly requests a cinematic format.
- ══════════════════════════════════════════════════
- TEXT + LABEL DISCIPLINE
- ══════════════════════════════════════════════════
- Keep visible text concise.
- Mandatory readable text should normally be limited to:
- - generated Beyblade name
- - optional performance type
- - optional spin direction
- - optional short gimmick name
- Do not cover every component with dense labels.
- Component correspondence should be communicated primarily through alignment and visual identity.
- Never display:
- - internal prompt instructions
- - placeholders
- - brackets
- - DEFAULT
- - SURPRISE ME
- - AI commentary
- - validation checklists
- ══════════════════════════════════════════════════
- CROSS-FIELD PROPAGATION
- ══════════════════════════════════════════════════
- Treat all user fields as connected.
- Examples:
- A heavily armored reference character may influence:
- - defensive or balance performance
- - thicker perimeter construction
- - impact-dispersing contact forms
- - higher visible metal mass
- - robust launcher styling
- - reinforced packaging graphics
- A fast agile character may influence:
- - attack or mobile balance behavior
- - directional attack edges
- - aggressive tip geometry
- - lightweight visual rhythm
- - angular launcher design
- A shapeshifting character may inspire:
- - mode-changing geometry
- - reversible components
- - adjustable contact forms
- - controlled reconfiguration
- without making the solid manufactured Beyblade literally behave like unrestricted living matter.
- A character wielding a distinctive weapon may inspire:
- - contact-edge geometry
- - central emblem
- - directional motifs
- without simply attaching a tiny toy weapon to the top.
- Propagate user customization across every dependent system.
- Do not allow the hero design, launcher, package, and performance description to feel like four unrelated concepts.
- ══════════════════════════════════════════════════
- CONFLICT PRIORITY
- ══════════════════════════════════════════════════
- Resolve conflicts in this order:
- 1. explicit current-user instructions
- 2. supplied character identity
- 3. canonical Beyblade-system coherence
- 4. component and cross-view continuity
- 5. functional launch and battle logic
- 6. packaging-state continuity
- 7. user-selected performance type
- 8. character-specific creative translation
- 9. visual styling
- 10. optional decorative embellishment
- If a character trait cannot be translated literally without making the product nonfunctional, preserve its design PURPOSE through an abstracted physical equivalent.
- Do not sacrifice the Beyblade's usability merely to copy a reference shape literally.
- Do not sacrifice character identity merely to make the top generic.
- ══════════════════════════════════════════════════
- HIGH-RISK FAILURE PREVENTION
- ══════════════════════════════════════════════════
- Before final rendering, specifically guard against the most likely failures.
- 1. GENERIC RECOLOR FAILURE
- The Beyblade must not be a stock spinning top with the character's palette applied.
- Require character-derived:
- - silhouette logic
- - component geometry
- - performance identity
- - gimmick
- - emblem
- - contact design
- 2. EXPLODED-VIEW DRIFT
- Do not invent separate components after designing the assembled top.
- Every exploded component must visibly belong to the hero design.
- 3. PACKAGE MISMATCH
- Do not design sealed and unfolded packaging separately.
- Use one package net and derive the folded state from it.
- 4. BROKEN RIPCORD FAILURE
- A curved stored ripcord is not a broken ripcord.
- Preserve one continuous full-length object through storage and use states.
- 5. LAUNCHER MISMATCH
- The launcher shown beside the top must be the same launcher packed in the box.
- 6. DUPLICATED ACCESSORY FAILURE
- Do not add extra ripcords, extra launchers, extra tops, or unexplained spare parts unless explicitly part of the product.
- 7. MIRRORING FAILURE
- Keep directional geometry, spin direction, launcher tabs, and graphics internally consistent.
- 8. HERO CROPPING
- Do not crop the primary Beyblade.
- Do not crop critical portions of the launcher, exploded parts, sealed package, or package net.
- 9. DECORATIVE GIMMICK FAILURE
- The signature gimmick must have a believable relationship to actual battle performance.
- 10. PACKAGING CAPACITY FAILURE
- The package must physically accommodate the declared top, launcher, and intact launch mechanism.
- Resize or reorganize the package rather than damaging accessories.
- ══════════════════════════════════════════════════
- MASTER-FIRST GENERATION ORDER
- ══════════════════════════════════════════════════
- Internally construct the result in this order:
- CHARACTER IDENTITY
- → CHARACTER-TO-BEYBLADE DESIGN TRANSLATION
- → PERFORMANCE ARCHETYPE
- → SIGNATURE GIMMICK
- → CANONICAL COMPONENT INVENTORY
- → ASSEMBLY INTERFACES
- → SPIN DIRECTION
- → TIP / DRIVER
- → COMPLETE ASSEMBLED BEYBLADE
- → EXPLODED REPRESENTATION
- → LAUNCHER INTERFACE
- → LAUNCHER
- → RIPCORD OR LAUNCH MECHANISM
- → PACKAGE CONTENTS
- → MASTER PACKAGE NET
- → INTERIOR TRAY
- → SEALED PACKAGE
- → UNFOLDED PACKAGE VIEW
- → FINAL PRODUCT-BOARD COMPOSITION
- Do not reverse this chain by improvising major downstream objects first.
- ══════════════════════════════════════════════════
- REVERSE-VALIDATION TESTS
- ══════════════════════════════════════════════════
- Before rendering the final image, mentally perform these tests.
- ASSEMBLY TEST
- Take every exploded part in order.
- Move it along the assembly axis.
- The parts must form the displayed hero Beyblade exactly.
- DISASSEMBLY TEST
- Take the hero Beyblade apart.
- It must produce the displayed exploded components without generating or losing pieces.
- LAUNCH TEST
- Mount the displayed Beyblade onto the displayed launcher.
- The interface and spin direction must agree.
- Operate the displayed pull mechanism.
- Nothing important should intersect the user's hand path or require impossible motion.
- RIPCORD TEST
- Take the curved packaged ripcord.
- Remove it from its tray.
- Gently straighten it.
- It must become the displayed operational ripcord with no change in identity or length.
- PACKING TEST
- Place the canonical Beyblade, launcher, and full ripcord into the interior tray.
- They must physically fit without overlap or breakage.
- PACKAGE-FOLD TEST
- Take the unfolded package net.
- Fold each real seam.
- The result must become the sealed package shown elsewhere on the board.
- PACKAGE-UNFOLD TEST
- Unfold the sealed package along its actual seams.
- It must reproduce the displayed net.
- IDENTITY TEST
- Ignore the package portrait.
- The Beyblade itself should still feel derived from the supplied character through shape, structure, performance, emblem, and gimmick.
- If any test fails, correct the canonical design before final output.
- ══════════════════════════════════════════════════
- FINAL VALIDATION
- ══════════════════════════════════════════════════
- Before generation, confirm all of the following:
- - exactly one canonical Beyblade design exists
- - the reference character remains the clear design source
- - the design is not merely a recolor
- - the performance type is physically supported
- - the signature gimmick is character-specific
- - every component has one assembly location
- - exploded parts correspond exactly to the assembled hero
- - spin direction is consistent
- - directional geometry agrees with spin direction
- - launcher interface is plausible
- - launcher and Beyblade are compatible
- - the same launcher appears in all views
- - the ripcord or launch mechanism remains intact
- - packaged and operational launch states are reachable from one another
- - package contents match the declared inventory
- - tray geometry can hold the contents
- - sealed packaging derives from the same master net as the unfolded view
- - package graphics remain on their correct physical panels
- - repeated emblems and product names remain identical
- - no unexplained duplicate components exist
- - the primary hero remains dominant
- - all essential objects remain uncropped
- - visible text is concise
- - the final board remains readable rather than overcrowded
- ══════════════════════════════════════════════════
- FINAL IMAGE STANDARD
- ══════════════════════════════════════════════════
- The finished result should look like a premium official-quality product development reveal for a completely realized character-specific Beyblade.
- It should simultaneously communicate:
- CHARACTER IDENTITY
- +
- PHYSICAL BEYBLADE DESIGN
- +
- BATTLE PERFORMANCE
- +
- MECHANICAL GIMMICK
- +
- COMPONENT CONSTRUCTION
- +
- LAUNCH COMPATIBILITY
- +
- RETAIL PRODUCT COHERENCE
- +
- PACKAGING CONTINUITY
- The viewer should be able to examine the image and understand:
- what the Beyblade is,
- which character inspired it,
- how its parts fit together,
- what kind of battler it is,
- what makes it mechanically distinctive,
- how it launches,
- what comes in the package,
- and how every representation belongs to the same canonical physical product.
- Generate the finished image now.
Advertisement
Add Comment
Please, Sign In to add comment