LuckyMouse420

Untitled

Sep 3rd, 2026
50
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 42.08 KB | None | 0 0
  1. CHARACTER-SPECIFIC BEYBLADE GENERATOR
  2. VERSION 1.0 — REFERENCE-IDENTITY TRANSLATION + CANONICAL PART STACK + PERFORMANCE LOGIC + LAUNCH SYSTEM + PACKAGING CONTINUITY
  3.  
  4. ══════════════════════════════════════════════════
  5. CORE PURPOSE
  6. ══════════════════════════════════════════════════
  7.  
  8. Create ONE polished, professional product-development image that transforms a supplied CHARACTER REFERENCE into a complete, believable, character-specific BEYBLADE product system.
  9.  
  10. The reference character is the PRIMARY DESIGN AUTHORITY.
  11.  
  12. Do not merely place the character's colors, face, logo, or silhouette onto a generic spinning top.
  13.  
  14. Design a Beyblade that feels as though its:
  15.  
  16. - visual construction
  17. - part geometry
  18. - attack/defense/stamina/balance behavior
  19. - weight distribution
  20. - gimmick
  21. - contact points
  22. - launcher
  23. - ripcord or launch interface
  24. - performance identity
  25. - emblem
  26. - packaging
  27. - product graphics
  28. - accessory treatment
  29.  
  30. were all purpose-designed from the specific character.
  31.  
  32. The finished result should communicate:
  33.  
  34. THIS CHARACTER
  35. → TRANSLATED INTO A BEYBLADE DESIGN LANGUAGE
  36. → AS A FUNCTIONAL PHYSICAL TOY
  37. → WITH A COHERENT PART SYSTEM
  38. → WITH A CHARACTER-APPROPRIATE BATTLE IDENTITY
  39. → WITH ITS OWN LAUNCH EQUIPMENT
  40. → PRESENTED AS A COMPLETE RETAIL PRODUCT
  41.  
  42. Generate the FINISHED IMAGE immediately after interpreting the supplied inputs.
  43.  
  44. Do not return an explanation, design proposal, or text-only specification.
  45.  
  46. ══════════════════════════════════════════════════
  47. CUSTOMIZABLE INPUTS
  48. ══════════════════════════════════════════════════
  49.  
  50. CHARACTER REFERENCE:
  51. [ATTACH ONE OR MORE REFERENCE IMAGES]
  52.  
  53. BEYBLADE ERA / SYSTEM:
  54. [SURPRISE ME / ORIGINAL CHARACTER-SPECIFIC SYSTEM / SPECIFY]
  55.  
  56. PERFORMANCE ARCHETYPE:
  57. [SURPRISE ME / ATTACK / DEFENSE / STAMINA / BALANCE / HYBRID / SPECIFY]
  58.  
  59. SIGNATURE GIMMICK:
  60. [SURPRISE ME / INFER FROM CHARACTER / SPECIFY]
  61.  
  62. PRIMARY MOTIF OR POWER:
  63. [INFER FROM CHARACTER / SPECIFY]
  64.  
  65. SPIN DIRECTION:
  66. [SURPRISE ME / RIGHT / LEFT]
  67.  
  68. PRODUCT TIER:
  69. [STANDARD RETAIL RELEASE / PREMIUM RELEASE / SPECIAL EDITION / SURPRISE ME]
  70.  
  71. PACKAGING STYLE:
  72. [ERA-APPROPRIATE RETAIL BOX / BLISTER / WINDOW BOX / PREMIUM COLLECTOR BOX / SURPRISE ME]
  73.  
  74. CUSTOM NOTES:
  75. [OPTIONAL NATURAL-LANGUAGE INSTRUCTIONS]
  76.  
  77. 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.
  78.  
  79. Do not display placeholders such as DEFAULT, SURPRISE ME, or INFER in the final image.
  80.  
  81. ══════════════════════════════════════════════════
  82. REFERENCE IDENTITY LOCK
  83. ══════════════════════════════════════════════════
  84.  
  85. Before designing the Beyblade, establish one canonical interpretation of the referenced character.
  86.  
  87. Preserve and analyze all identity-bearing traits that materially distinguish the character, including when applicable:
  88.  
  89. - species
  90. - anatomy
  91. - body proportions
  92. - silhouette
  93. - head shape
  94. - face
  95. - eyes
  96. - ears
  97. - horns
  98. - hair
  99. - fur
  100. - skin
  101. - armor
  102. - clothing
  103. - major equipment
  104. - asymmetry
  105. - markings
  106. - scars
  107. - symbols
  108. - palette
  109. - material cues
  110. - powers
  111. - occupation
  112. - personality
  113. - movement style
  114. - combat style
  115. - recurring motifs
  116. - elemental or thematic associations
  117.  
  118. Do not preserve every trait literally.
  119.  
  120. Translate them intelligently into product design.
  121.  
  122. The Beyblade must feel recognizably derived from the reference even when the character itself is not physically depicted on the top.
  123.  
  124. Use the character as a GENERATIVE DESIGN SYSTEM.
  125.  
  126. Examples of translation logic include:
  127.  
  128. character silhouette
  129. → major outer-ring geometry
  130.  
  131. signature weapon
  132. → impact blades, protrusions, contact geometry, or emblem structure
  133.  
  134. armor
  135. → layered mechanical surfacing
  136.  
  137. body markings
  138. → controlled graphics or molded relief
  139.  
  140. power or element
  141. → performance gimmick, material treatment, or symbolic geometry
  142.  
  143. movement style
  144. → attack pattern or stability behavior
  145.  
  146. personality
  147. → aggressive, technical, elegant, deceptive, defensive, chaotic, precise, or endurance-oriented performance identity
  148.  
  149. asymmetry
  150. → intentional asymmetric mass or visual structure when mechanically plausible
  151.  
  152. species traits
  153. → abstracted structural motifs rather than pasted animal faces
  154.  
  155. Do not reduce character translation to palette matching.
  156.  
  157. ══════════════════════════════════════════════════
  158. BEYBLADE SYSTEM SELECTION
  159. ══════════════════════════════════════════════════
  160.  
  161. If the user specifies a recognizable Beyblade era or mechanical system, respect that system's defining construction vocabulary.
  162.  
  163. 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.
  164.  
  165. The chosen system must establish:
  166.  
  167. - one clear top architecture
  168. - identifiable separable components
  169. - a defined assembly axis
  170. - locking interfaces
  171. - a tip or driver
  172. - a central rotational body
  173. - one dominant contact layer or attack ring
  174. - a launcher interface
  175. - intended spin direction
  176. - battle-performance logic
  177.  
  178. Do not mix mutually incompatible parts from unrelated Beyblade generations merely because they are visually recognizable.
  179.  
  180. If hybridization is intentionally selected, redesign the interfaces so the result behaves as one coherent system.
  181.  
  182. ══════════════════════════════════════════════════
  183. MASTER PRODUCT LEDGER
  184. ══════════════════════════════════════════════════
  185.  
  186. Before producing any view, establish ONE canonical Beyblade design.
  187.  
  188. Lock:
  189.  
  190. - total component count
  191. - component names or identities
  192. - component order
  193. - upper and lower orientation
  194. - assembly axis
  195. - spin direction
  196. - locking method
  197. - outer silhouette
  198. - contact points
  199. - major dimensions
  200. - color placement
  201. - translucent versus opaque materials
  202. - metal versus plastic distribution
  203. - emblem placement
  204. - graphics
  205. - molded motifs
  206. - gimmick mechanism
  207. - performance role
  208. - launcher compatibility
  209. - launcher type
  210. - ripcord or pull mechanism
  211. - package contents
  212. - package dimensions and panel layout
  213.  
  214. Every representation must derive from this single master.
  215.  
  216. Never independently redesign:
  217.  
  218. - the assembled Beyblade
  219. - exploded parts
  220. - launcher
  221. - packaged contents
  222. - packaging artwork
  223. - instruction diagrams
  224.  
  225. between views.
  226.  
  227. ══════════════════════════════════════════════════
  228. PERFORMANCE IDENTITY ENGINE
  229. ══════════════════════════════════════════════════
  230.  
  231. Translate the character into a believable battle-performance concept.
  232.  
  233. Select one coherent primary archetype:
  234.  
  235. ATTACK
  236. DEFENSE
  237. STAMINA
  238. BALANCE
  239. or an explicitly justified HYBRID.
  240.  
  241. Then define the Beyblade's behavior through actual geometry and mass logic.
  242.  
  243. ATTACK may emphasize:
  244.  
  245. - aggressive perimeter contact points
  246. - uneven or directional geometry
  247. - high-impact protrusions
  248. - rapid movement
  249. - lower or more mobile tip behavior
  250. - strong recoil accepted as part of the design
  251.  
  252. DEFENSE may emphasize:
  253.  
  254. - compact mass
  255. - guarded perimeter geometry
  256. - recoil deflection
  257. - stable center of gravity
  258. - low movement
  259. - shock-dispersing structures
  260.  
  261. STAMINA may emphasize:
  262.  
  263. - smooth aerodynamic perimeter
  264. - low friction
  265. - rotational symmetry
  266. - efficient mass placement
  267. - long-spin tip geometry
  268. - reduced collision drag
  269.  
  270. BALANCE may combine traits deliberately without becoming mechanically incoherent.
  271.  
  272. The physical form must support the claimed performance identity.
  273.  
  274. Do not label a generic symmetric top "attack type" while giving it no meaningful attack geometry.
  275.  
  276. ══════════════════════════════════════════════════
  277. SIGNATURE CHARACTER GIMMICK
  278. ══════════════════════════════════════════════════
  279.  
  280. Every generated Beyblade should possess ONE principal signature gimmick derived from the reference character.
  281.  
  282. The gimmick must be:
  283.  
  284. - visually understandable
  285. - mechanically plausible within toy-scale logic
  286. - materially compatible with the chosen system
  287. - relevant to the character
  288. - visible enough to distinguish the design
  289. - integrated into battle behavior rather than attached as decorative clutter
  290.  
  291. Possible categories include:
  292.  
  293. - directional contact geometry
  294. - free-spinning sub-ring
  295. - rubberized contact section
  296. - spring-loaded or flexing component
  297. - shifting mass
  298. - reversible component
  299. - mode change
  300. - adjustable tip
  301. - deployable contact geometry
  302. - spin-direction interaction
  303. - counterattack surface
  304. - destabilizing attack pattern
  305. - defensive shock absorption
  306. - stamina-preserving bearing
  307. - controlled asymmetry
  308.  
  309. Do not automatically use any particular gimmick.
  310.  
  311. Invent the one that best expresses the supplied character.
  312.  
  313. 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.
  314.  
  315. ══════════════════════════════════════════════════
  316. CANONICAL COMPONENT STACK
  317. ══════════════════════════════════════════════════
  318.  
  319. Construct the Beyblade from a clear vertical stack.
  320.  
  321. Every major visible component must have:
  322.  
  323. - a distinct structural role
  324. - one position in the assembled product
  325. - one corresponding exploded representation
  326. - one stable color/material identity
  327. - one connection to neighboring components
  328. - no duplicate counterpart unless duplication is physically intentional
  329.  
  330. The exact number of parts may vary by selected system.
  331.  
  332. However, the finished product must remain understandable as a real assembled spinning top rather than a pile of arbitrary decorative layers.
  333.  
  334. Build the canonical stack FIRST.
  335.  
  336. Then derive the assembled top from it.
  337.  
  338. Then derive the exploded view from the same exact components.
  339.  
  340. Do not create the hero Beyblade first and improvise unrelated exploded pieces afterward.
  341.  
  342. ══════════════════════════════════════════════════
  343. COMPONENT BIJECTION LOCK
  344. ══════════════════════════════════════════════════
  345.  
  346. Every canonical component must satisfy:
  347.  
  348. ONE COMPONENT
  349. ↔ ONE ASSEMBLED LOCATION
  350. ↔ ONE EXPLODED COMPONENT
  351. ↔ ONE PACKAGE LOCATION if included
  352. ↔ ONE INSTRUCTIONAL IDENTITY if diagrammed
  353.  
  354. No component may:
  355.  
  356. - disappear between views
  357. - change shape between views
  358. - change major colors between views
  359. - split into several unexplained pieces
  360. - merge with another component without a designed mechanism
  361. - appear in packaging without belonging to the declared product
  362. - exist in an exploded diagram without an assembly location
  363.  
  364. Hidden interior pieces remain part of the canonical inventory even when occluded in the assembled view.
  365.  
  366. ══════════════════════════════════════════════════
  367. EXPLODED PARTS VIEW
  368. ══════════════════════════════════════════════════
  369.  
  370. Include a clear exploded assembly view of the SAME Beyblade shown in the hero presentation.
  371.  
  372. Arrange components along the actual assembly axis.
  373.  
  374. Maintain:
  375.  
  376. - correct top-to-bottom order
  377. - stable orientation
  378. - one-to-one correspondence
  379. - proportional scale
  380. - matching geometry
  381. - matching materials
  382. - matching colors
  383. - matching markings
  384. - matching locking surfaces
  385.  
  386. Exploded means DISASSEMBLED FOR EXPLANATION.
  387.  
  388. It does not mean:
  389.  
  390. - shattered
  391. - broken
  392. - damaged
  393. - blown apart
  394. - debris
  395. - cracked
  396. - battle-destroyed
  397.  
  398. Provide enough separation for each component to be legible while preserving obvious alignment.
  399.  
  400. The viewer should be able to mentally slide the parts together and reproduce the assembled hero exactly.
  401.  
  402. ══════════════════════════════════════════════════
  403. EMBLEM + CHARACTER ICONOGRAPHY
  404. ══════════════════════════════════════════════════
  405.  
  406. Create one central emblem or avatar mark derived from the reference character.
  407.  
  408. This emblem should be visually simplified enough to function at toy scale.
  409.  
  410. It may abstract:
  411.  
  412. - face
  413. - species
  414. - helmet
  415. - eye motif
  416. - insignia
  417. - weapon symbol
  418. - power symbol
  419. - signature mark
  420.  
  421. Do not paste a full photographic portrait into the center unless the requested product style specifically supports printed character portraits.
  422.  
  423. The emblem must remain the SAME design wherever repeated:
  424.  
  425. - Beyblade center
  426. - package front
  427. - launcher insignia
  428. - instruction graphics
  429. - optional product badge
  430.  
  431. Do not allow alternate versions of the emblem to appear accidentally.
  432.  
  433. ══════════════════════════════════════════════════
  434. LAUNCHER SYSTEM
  435. ══════════════════════════════════════════════════
  436.  
  437. Design one dedicated launcher compatible with the canonical Beyblade.
  438.  
  439. Its interface must correspond to the top's chosen spin direction and locking geometry.
  440.  
  441. Character-specific styling may influence:
  442.  
  443. - grip silhouette
  444. - molded paneling
  445. - accent colors
  446. - emblem
  447. - ergonomic form
  448. - surface detailing
  449.  
  450. but the launcher must remain recognizably functional.
  451.  
  452. It must include:
  453.  
  454. - launcher body
  455. - Beyblade coupling interface
  456. - grip area
  457. - pull mechanism or equivalent launching mechanism
  458. - coherent orientation for use
  459.  
  460. If a ripcord system is used, the ripcord must be one continuous physical object.
  461.  
  462. If a string launcher is used, show a plausible reel or retracting mechanism.
  463.  
  464. Do not combine mutually incompatible launch mechanisms unless specifically designed as a dual-mode launcher.
  465.  
  466. ══════════════════════════════════════════════════
  467. RIPCORD CONTINUITY + STORAGE LOCK
  468. ══════════════════════════════════════════════════
  469.  
  470. If the launcher uses a plastic ripcord, establish ONE canonical ripcord before depicting any storage or operational state.
  471.  
  472. The ripcord must have:
  473.  
  474. - one continuous strip
  475. - continuous molded teeth where appropriate
  476. - one handle end
  477. - one insertion end
  478. - consistent width and thickness
  479. - flexible plastic behavior
  480.  
  481. DEPLOYED STATE:
  482.  
  483. The ripcord may be largely straight or naturally slightly bowed.
  484.  
  485. PACKAGED STATE:
  486.  
  487. Route the SAME full-length intact ripcord through a broad, gentle tray curve or loop so it fits within the package.
  488.  
  489. Treat the material as resilient flexible plastic.
  490.  
  491. Do not represent storage by:
  492.  
  493. - snapping it
  494. - cutting it
  495. - separating it into segments
  496. - sharply folding it back on itself
  497. - giving it broken teeth
  498. - melting it
  499. - replacing part of it with another piece
  500.  
  501. The curved packaged state and straightened operating state are two configurations of the same object.
  502.  
  503. Mentally straighten the stored ripcord and confirm it becomes the operational ripcord without changing length, geometry, teeth, or handle.
  504.  
  505. ══════════════════════════════════════════════════
  506. LAUNCH COMPATIBILITY VALIDATION
  507. ══════════════════════════════════════════════════
  508.  
  509. The Beyblade, launcher, and pull mechanism must form one working interface system.
  510.  
  511. Verify:
  512.  
  513. - the top connects at the correct central launch point
  514. - the launcher is oriented consistently with the selected spin direction
  515. - the coupling is mechanically reachable
  516. - the ripcord or launch mechanism enters the correct region
  517. - the user's hand could plausibly hold the launcher without blocking operation
  518. - the launcher shown in packaging is the same launcher shown separately
  519.  
  520. Do not create a decorative launcher that could not physically engage the Beyblade.
  521.  
  522. ══════════════════════════════════════════════════
  523. MASTER PACKAGE SYSTEM
  524. ══════════════════════════════════════════════════
  525.  
  526. If packaging is included, design ONE master package structure before showing any package state.
  527.  
  528. Establish:
  529.  
  530. - package dimensions
  531. - front panel
  532. - back panel
  533. - left panel
  534. - right panel
  535. - top
  536. - bottom
  537. - flaps
  538. - tabs
  539. - windows
  540. - hang tab if appropriate
  541. - interior tray footprint
  542. - location of Beyblade
  543. - location of launcher
  544. - ripcord route
  545. - accessory locations
  546. - major graphics
  547. - logos
  548. - character emblem
  549. - product name
  550. - visual hierarchy
  551.  
  552. Use this master package as the source of every packaging representation.
  553.  
  554. Do not independently design a sealed box and a flattened box.
  555.  
  556. ══════════════════════════════════════════════════
  557. SEALED ↔ UNFOLDED PACKAGE CONTRACT
  558. ══════════════════════════════════════════════════
  559.  
  560. When both a sealed package and an unfolded package net are shown, they must depict THE SAME PHYSICAL PACKAGE.
  561.  
  562. Construct the flat package net first with stable:
  563.  
  564. - panel dimensions
  565. - adjacency
  566. - fold lines
  567. - flap geometry
  568. - graphics
  569. - windows
  570. - logos
  571. - product name
  572. - character artwork
  573. - color fields
  574. - legal or decorative microtext regions
  575.  
  576. Then mentally fold that same net into the sealed package.
  577.  
  578. The resulting box must reproduce the displayed sealed package.
  579.  
  580. Panel relationships must remain physically possible.
  581.  
  582. For example:
  583.  
  584. - front graphics remain on the front
  585. - side-panel artwork moves only according to the fold
  586. - windows retain the same dimensions and location
  587. - top and bottom flaps correspond
  588. - no artwork teleports between panels
  589. - no panel changes proportion
  590. - no extra panel appears
  591. - no required panel disappears
  592.  
  593. Reverse-check the result:
  594.  
  595. SEALED BOX
  596. → UNFOLD ALONG REAL SEAMS
  597. → SAME DISPLAYED NET
  598.  
  599. If this reverse transformation would fail, correct the packaging before generation.
  600.  
  601. ══════════════════════════════════════════════════
  602. INTERIOR TRAY + CONTENT PLACEMENT
  603. ══════════════════════════════════════════════════
  604.  
  605. Design one package tray capable of physically holding the declared contents.
  606.  
  607. Provide shaped recesses or channels for:
  608.  
  609. - assembled Beyblade
  610. - launcher
  611. - ripcord or launch mechanism
  612. - optional accessory if explicitly generated
  613.  
  614. The tray must respect each object's actual dimensions.
  615.  
  616. Do not place objects through one another.
  617.  
  618. Do not shrink or stretch accessories simply to make them fit.
  619.  
  620. The stored ripcord route must preserve the entire continuous object.
  621.  
  622. If the contents cannot plausibly fit, increase package dimensions or reorganize the tray rather than damaging, cropping, or deleting them.
  623.  
  624. ══════════════════════════════════════════════════
  625. PACKAGE CONTENTS LOCK
  626. ══════════════════════════════════════════════════
  627.  
  628. Declare one canonical retail contents set.
  629.  
  630. Normally include only:
  631.  
  632. - ONE Beyblade
  633. - ONE compatible launcher
  634. - ONE corresponding launch mechanism
  635. - packaging
  636.  
  637. Add additional accessories only when the generated concept genuinely requires them.
  638.  
  639. Every declared item must be:
  640.  
  641. - represented in the package if package contents are visible
  642. - compatible with the central product
  643. - absent from the package if it was never declared
  644.  
  645. Do not introduce duplicate tops, duplicate launchers, mystery parts, unrelated weapons, or random collectibles merely to fill the tray.
  646.  
  647. ══════════════════════════════════════════════════
  648. PRODUCT NAME + BRANDING
  649. ══════════════════════════════════════════════════
  650.  
  651. Invent one concise Beyblade product name that reflects the character's identity and battle concept.
  652.  
  653. Use a naming structure appropriate to the selected system while avoiding accidental duplication of an existing official product unless explicitly requested.
  654.  
  655. The product name must remain identical across all visible occurrences.
  656.  
  657. Use restrained package text.
  658.  
  659. Prioritize legibility for:
  660.  
  661. - product name
  662. - type or performance designation if displayed
  663. - spin direction if displayed
  664. - one short signature-gimmick callout if useful
  665.  
  666. Other tiny box copy may appear as decorative product-print texture and need not be individually readable.
  667.  
  668. Do not fill the image with paragraphs of pseudo-technical writing.
  669.  
  670. ══════════════════════════════════════════════════
  671. CHARACTER ART ON PACKAGING
  672. ══════════════════════════════════════════════════
  673.  
  674. If character artwork appears on the box, preserve the supplied character's identity accurately.
  675.  
  676. Packaging artwork is secondary to the physical Beyblade.
  677.  
  678. Do not allow a large character portrait to overwhelm the product-development purpose of the image.
  679.  
  680. The character depiction may use a dramatic action pose appropriate to their identity, but:
  681.  
  682. - anatomy must remain canonical
  683. - distinctive features must remain recognizable
  684. - costume details should not arbitrarily drift
  685. - the package art must not introduce a contradictory alternate character design
  686.  
  687. If the reference character has unusual anatomy or topology, preserve it rather than normalizing it to conventional human anatomy.
  688.  
  689. ══════════════════════════════════════════════════
  690. MANUFACTURED-OBJECT REALISM
  691. ══════════════════════════════════════════════════
  692.  
  693. The Beyblade and accessories must look like actual manufactured physical objects.
  694.  
  695. Use believable materials such as:
  696.  
  697. - injection-molded plastic
  698. - transparent or translucent plastic
  699. - painted or plated metal
  700. - rubber where mechanically useful
  701. - printed inserts
  702. - molded texture
  703. - recessed graphics
  704. - stickers or tampos when appropriate
  705.  
  706. Maintain believable:
  707.  
  708. - wall thickness
  709. - seam placement
  710. - attachment points
  711. - molded detail scale
  712. - material transitions
  713. - tolerances
  714. - surface finish
  715. - screw or fastening logic if visible
  716.  
  717. Avoid impossible infinitely thin fins, unsupported floating decorations, ornamental spikes too fragile for a toy, or shapes that would obviously prevent spinning.
  718.  
  719. Character specificity must operate within manufacturable geometry.
  720.  
  721. ══════════════════════════════════════════════════
  722. BATTLE-CONTACT GEOMETRY
  723. ══════════════════════════════════════════════════
  724.  
  725. Any perimeter feature intended to affect battle must physically reach the contact envelope.
  726.  
  727. Do not create attack blades, defensive bumpers, rubber surfaces, or counterattack elements that are recessed so deeply they could never touch an opponent.
  728.  
  729. At the same time, keep the outer geometry within believable toy-safe proportions unless a deliberately exaggerated fantasy product style is requested.
  730.  
  731. Distinctive motifs should serve one or more functions:
  732.  
  733. - contact
  734. - mass distribution
  735. - stability
  736. - recoil behavior
  737. - airflow
  738. - grip
  739. - alignment
  740. - visual identity
  741.  
  742. Avoid meaningless mechanical-looking clutter.
  743.  
  744. ══════════════════════════════════════════════════
  745. TIP / DRIVER LOGIC
  746. ══════════════════════════════════════════════════
  747.  
  748. Design the lower contact system to support the performance identity.
  749.  
  750. Consider:
  751.  
  752. - point shape
  753. - surface area
  754. - friction
  755. - height
  756. - mobility
  757. - free rotation
  758. - material
  759. - mode switching
  760. - stabilization
  761.  
  762. An attack-oriented design should not accidentally use a broad immobile high-friction tip unless a specific counterintuitive gimmick explains it.
  763.  
  764. A stamina design should not use a geometry that would obviously create constant drag unless intentionally balanced by another mechanism.
  765.  
  766. If the character-specific gimmick affects the driver or tip, make its operation visually understandable.
  767.  
  768. ══════════════════════════════════════════════════
  769. SPIN DIRECTION + CHIRALITY
  770. ══════════════════════════════════════════════════
  771.  
  772. Lock the chosen spin direction before building directional geometry.
  773.  
  774. If the Beyblade uses directional attack blades, ramps, fins, or launcher tabs, orient them consistently with that spin.
  775.  
  776. Do not mirror only one representation.
  777.  
  778. The assembled hero, exploded parts, launcher interface, package diagrams, and visible directional iconography must all agree.
  779.  
  780. If left-spin is selected, do not accidentally retain right-spin directional geometry from a conventional default.
  781.  
  782. ══════════════════════════════════════════════════
  783. PRIMARY IMAGE FORMAT
  784. ══════════════════════════════════════════════════
  785.  
  786. Create ONE cohesive premium PRODUCT-DEVELOPMENT BOARD.
  787.  
  788. Recommended aspect ratio:
  789.  
  790. 4:5 portrait or 5:4 landscape depending on which orientation gives the declared content enough readable space.
  791.  
  792. Choose the orientation that protects clarity.
  793.  
  794. The board should normally include:
  795.  
  796. PRIMARY:
  797.  
  798. 1. LARGE ASSEMBLED HERO BEYBLADE
  799. - dominant visual element
  800. - three-quarter product angle
  801. - complete and uncropped
  802. - enough size to read geometry, emblem, materials, and gimmick
  803.  
  804. SECONDARY:
  805.  
  806. 2. EXPLODED COMPONENT STACK
  807. - aligned to the real assembly axis
  808. - clearly subordinate to hero
  809.  
  810. 3. DEDICATED LAUNCHER + RIPCORD / LAUNCH MECHANISM
  811. - same exact accessories used in packaging
  812.  
  813. 4. SEALED RETAIL PACKAGE
  814.  
  815. 5. UNFOLDED PACKAGE NET
  816. - same package, not a second design
  817.  
  818. TERTIARY:
  819.  
  820. 6. SMALL FUNCTIONAL DETAIL OR GIMMICK INSET
  821. - only when useful for understanding the character-specific mechanism
  822.  
  823. Do not add redundant views merely because space remains.
  824.  
  825. Every view must prove a different part of the product system.
  826.  
  827. ══════════════════════════════════════════════════
  828. REPRESENTATIONAL INSTANCE CONTROL
  829. ══════════════════════════════════════════════════
  830.  
  831. The board may show the SAME canonical Beyblade several times for explanatory purposes.
  832.  
  833. These are not multiple products.
  834.  
  835. Treat them as multiple views of ONE design.
  836.  
  837. The hero view, exploded assembly, packaging depiction, and optional mechanism inset must all describe the same canonical unit.
  838.  
  839. Do not interpret repeated representations as permission to create variant Beyblades.
  840.  
  841. Unless explicitly requested, generate exactly ONE Beyblade design.
  842.  
  843. ══════════════════════════════════════════════════
  844. VISUAL HIERARCHY
  845. ══════════════════════════════════════════════════
  846.  
  847. The assembled Beyblade is the primary subject.
  848.  
  849. Allocate the most area and highest clarity to it.
  850.  
  851. The exploded view and launcher are secondary.
  852.  
  853. Packaging views are supporting proof.
  854.  
  855. Do not allow the box, text, character portrait, or diagrams to become larger or more visually dominant than the actual Beyblade.
  856.  
  857. Maintain enough negative space for:
  858.  
  859. - clean separation between views
  860. - visible exploded alignment
  861. - readable launcher silhouette
  862. - intact package views
  863. - complete ripcord routing
  864. - legible product name
  865.  
  866. Avoid collisions, overlaps, or crowding that make separate components appear fused.
  867.  
  868. ══════════════════════════════════════════════════
  869. BACKGROUND + RENDERING STYLE
  870. ══════════════════════════════════════════════════
  871.  
  872. Use a clean professional product-design presentation.
  873.  
  874. Preferred background:
  875.  
  876. - white
  877. - light neutral
  878. - subtle studio gradient
  879. - restrained technical-board surface
  880.  
  881. Use controlled studio lighting that reveals:
  882.  
  883. - molded geometry
  884. - metal surfaces
  885. - translucent components
  886. - edge thickness
  887. - mechanical interfaces
  888. - embossed details
  889.  
  890. Aim for high-end toy photography combined with precise industrial-design visualization.
  891.  
  892. The product should feel tangible, manufacturable, collectible, and ready for retail.
  893.  
  894. Do not turn the background into a cinematic battlefield that obscures product information unless the user explicitly requests a cinematic format.
  895.  
  896. ══════════════════════════════════════════════════
  897. TEXT + LABEL DISCIPLINE
  898. ══════════════════════════════════════════════════
  899.  
  900. Keep visible text concise.
  901.  
  902. Mandatory readable text should normally be limited to:
  903.  
  904. - generated Beyblade name
  905. - optional performance type
  906. - optional spin direction
  907. - optional short gimmick name
  908.  
  909. Do not cover every component with dense labels.
  910.  
  911. Component correspondence should be communicated primarily through alignment and visual identity.
  912.  
  913. Never display:
  914.  
  915. - internal prompt instructions
  916. - placeholders
  917. - brackets
  918. - DEFAULT
  919. - SURPRISE ME
  920. - AI commentary
  921. - validation checklists
  922.  
  923. ══════════════════════════════════════════════════
  924. CROSS-FIELD PROPAGATION
  925. ══════════════════════════════════════════════════
  926.  
  927. Treat all user fields as connected.
  928.  
  929. Examples:
  930.  
  931. A heavily armored reference character may influence:
  932.  
  933. - defensive or balance performance
  934. - thicker perimeter construction
  935. - impact-dispersing contact forms
  936. - higher visible metal mass
  937. - robust launcher styling
  938. - reinforced packaging graphics
  939.  
  940. A fast agile character may influence:
  941.  
  942. - attack or mobile balance behavior
  943. - directional attack edges
  944. - aggressive tip geometry
  945. - lightweight visual rhythm
  946. - angular launcher design
  947.  
  948. A shapeshifting character may inspire:
  949.  
  950. - mode-changing geometry
  951. - reversible components
  952. - adjustable contact forms
  953. - controlled reconfiguration
  954.  
  955. without making the solid manufactured Beyblade literally behave like unrestricted living matter.
  956.  
  957. A character wielding a distinctive weapon may inspire:
  958.  
  959. - contact-edge geometry
  960. - central emblem
  961. - directional motifs
  962.  
  963. without simply attaching a tiny toy weapon to the top.
  964.  
  965. Propagate user customization across every dependent system.
  966.  
  967. Do not allow the hero design, launcher, package, and performance description to feel like four unrelated concepts.
  968.  
  969. ══════════════════════════════════════════════════
  970. CONFLICT PRIORITY
  971. ══════════════════════════════════════════════════
  972.  
  973. Resolve conflicts in this order:
  974.  
  975. 1. explicit current-user instructions
  976. 2. supplied character identity
  977. 3. canonical Beyblade-system coherence
  978. 4. component and cross-view continuity
  979. 5. functional launch and battle logic
  980. 6. packaging-state continuity
  981. 7. user-selected performance type
  982. 8. character-specific creative translation
  983. 9. visual styling
  984. 10. optional decorative embellishment
  985.  
  986. If a character trait cannot be translated literally without making the product nonfunctional, preserve its design PURPOSE through an abstracted physical equivalent.
  987.  
  988. Do not sacrifice the Beyblade's usability merely to copy a reference shape literally.
  989.  
  990. Do not sacrifice character identity merely to make the top generic.
  991.  
  992. ══════════════════════════════════════════════════
  993. HIGH-RISK FAILURE PREVENTION
  994. ══════════════════════════════════════════════════
  995.  
  996. Before final rendering, specifically guard against the most likely failures.
  997.  
  998. 1. GENERIC RECOLOR FAILURE
  999.  
  1000. The Beyblade must not be a stock spinning top with the character's palette applied.
  1001.  
  1002. Require character-derived:
  1003. - silhouette logic
  1004. - component geometry
  1005. - performance identity
  1006. - gimmick
  1007. - emblem
  1008. - contact design
  1009.  
  1010. 2. EXPLODED-VIEW DRIFT
  1011.  
  1012. Do not invent separate components after designing the assembled top.
  1013.  
  1014. Every exploded component must visibly belong to the hero design.
  1015.  
  1016. 3. PACKAGE MISMATCH
  1017.  
  1018. Do not design sealed and unfolded packaging separately.
  1019.  
  1020. Use one package net and derive the folded state from it.
  1021.  
  1022. 4. BROKEN RIPCORD FAILURE
  1023.  
  1024. A curved stored ripcord is not a broken ripcord.
  1025.  
  1026. Preserve one continuous full-length object through storage and use states.
  1027.  
  1028. 5. LAUNCHER MISMATCH
  1029.  
  1030. The launcher shown beside the top must be the same launcher packed in the box.
  1031.  
  1032. 6. DUPLICATED ACCESSORY FAILURE
  1033.  
  1034. Do not add extra ripcords, extra launchers, extra tops, or unexplained spare parts unless explicitly part of the product.
  1035.  
  1036. 7. MIRRORING FAILURE
  1037.  
  1038. Keep directional geometry, spin direction, launcher tabs, and graphics internally consistent.
  1039.  
  1040. 8. HERO CROPPING
  1041.  
  1042. Do not crop the primary Beyblade.
  1043.  
  1044. Do not crop critical portions of the launcher, exploded parts, sealed package, or package net.
  1045.  
  1046. 9. DECORATIVE GIMMICK FAILURE
  1047.  
  1048. The signature gimmick must have a believable relationship to actual battle performance.
  1049.  
  1050. 10. PACKAGING CAPACITY FAILURE
  1051.  
  1052. The package must physically accommodate the declared top, launcher, and intact launch mechanism.
  1053.  
  1054. Resize or reorganize the package rather than damaging accessories.
  1055.  
  1056. ══════════════════════════════════════════════════
  1057. MASTER-FIRST GENERATION ORDER
  1058. ══════════════════════════════════════════════════
  1059.  
  1060. Internally construct the result in this order:
  1061.  
  1062. CHARACTER IDENTITY
  1063. → CHARACTER-TO-BEYBLADE DESIGN TRANSLATION
  1064. → PERFORMANCE ARCHETYPE
  1065. → SIGNATURE GIMMICK
  1066. → CANONICAL COMPONENT INVENTORY
  1067. → ASSEMBLY INTERFACES
  1068. → SPIN DIRECTION
  1069. → TIP / DRIVER
  1070. → COMPLETE ASSEMBLED BEYBLADE
  1071. → EXPLODED REPRESENTATION
  1072. → LAUNCHER INTERFACE
  1073. → LAUNCHER
  1074. → RIPCORD OR LAUNCH MECHANISM
  1075. → PACKAGE CONTENTS
  1076. → MASTER PACKAGE NET
  1077. → INTERIOR TRAY
  1078. → SEALED PACKAGE
  1079. → UNFOLDED PACKAGE VIEW
  1080. → FINAL PRODUCT-BOARD COMPOSITION
  1081.  
  1082. Do not reverse this chain by improvising major downstream objects first.
  1083.  
  1084. ══════════════════════════════════════════════════
  1085. REVERSE-VALIDATION TESTS
  1086. ══════════════════════════════════════════════════
  1087.  
  1088. Before rendering the final image, mentally perform these tests.
  1089.  
  1090. ASSEMBLY TEST
  1091.  
  1092. Take every exploded part in order.
  1093.  
  1094. Move it along the assembly axis.
  1095.  
  1096. The parts must form the displayed hero Beyblade exactly.
  1097.  
  1098. DISASSEMBLY TEST
  1099.  
  1100. Take the hero Beyblade apart.
  1101.  
  1102. It must produce the displayed exploded components without generating or losing pieces.
  1103.  
  1104. LAUNCH TEST
  1105.  
  1106. Mount the displayed Beyblade onto the displayed launcher.
  1107.  
  1108. The interface and spin direction must agree.
  1109.  
  1110. Operate the displayed pull mechanism.
  1111.  
  1112. Nothing important should intersect the user's hand path or require impossible motion.
  1113.  
  1114. RIPCORD TEST
  1115.  
  1116. Take the curved packaged ripcord.
  1117.  
  1118. Remove it from its tray.
  1119.  
  1120. Gently straighten it.
  1121.  
  1122. It must become the displayed operational ripcord with no change in identity or length.
  1123.  
  1124. PACKING TEST
  1125.  
  1126. Place the canonical Beyblade, launcher, and full ripcord into the interior tray.
  1127.  
  1128. They must physically fit without overlap or breakage.
  1129.  
  1130. PACKAGE-FOLD TEST
  1131.  
  1132. Take the unfolded package net.
  1133.  
  1134. Fold each real seam.
  1135.  
  1136. The result must become the sealed package shown elsewhere on the board.
  1137.  
  1138. PACKAGE-UNFOLD TEST
  1139.  
  1140. Unfold the sealed package along its actual seams.
  1141.  
  1142. It must reproduce the displayed net.
  1143.  
  1144. IDENTITY TEST
  1145.  
  1146. Ignore the package portrait.
  1147.  
  1148. The Beyblade itself should still feel derived from the supplied character through shape, structure, performance, emblem, and gimmick.
  1149.  
  1150. If any test fails, correct the canonical design before final output.
  1151.  
  1152. ══════════════════════════════════════════════════
  1153. FINAL VALIDATION
  1154. ══════════════════════════════════════════════════
  1155.  
  1156. Before generation, confirm all of the following:
  1157.  
  1158. - exactly one canonical Beyblade design exists
  1159. - the reference character remains the clear design source
  1160. - the design is not merely a recolor
  1161. - the performance type is physically supported
  1162. - the signature gimmick is character-specific
  1163. - every component has one assembly location
  1164. - exploded parts correspond exactly to the assembled hero
  1165. - spin direction is consistent
  1166. - directional geometry agrees with spin direction
  1167. - launcher interface is plausible
  1168. - launcher and Beyblade are compatible
  1169. - the same launcher appears in all views
  1170. - the ripcord or launch mechanism remains intact
  1171. - packaged and operational launch states are reachable from one another
  1172. - package contents match the declared inventory
  1173. - tray geometry can hold the contents
  1174. - sealed packaging derives from the same master net as the unfolded view
  1175. - package graphics remain on their correct physical panels
  1176. - repeated emblems and product names remain identical
  1177. - no unexplained duplicate components exist
  1178. - the primary hero remains dominant
  1179. - all essential objects remain uncropped
  1180. - visible text is concise
  1181. - the final board remains readable rather than overcrowded
  1182.  
  1183. ══════════════════════════════════════════════════
  1184. FINAL IMAGE STANDARD
  1185. ══════════════════════════════════════════════════
  1186.  
  1187. The finished result should look like a premium official-quality product development reveal for a completely realized character-specific Beyblade.
  1188.  
  1189. It should simultaneously communicate:
  1190.  
  1191. CHARACTER IDENTITY
  1192. +
  1193. PHYSICAL BEYBLADE DESIGN
  1194. +
  1195. BATTLE PERFORMANCE
  1196. +
  1197. MECHANICAL GIMMICK
  1198. +
  1199. COMPONENT CONSTRUCTION
  1200. +
  1201. LAUNCH COMPATIBILITY
  1202. +
  1203. RETAIL PRODUCT COHERENCE
  1204. +
  1205. PACKAGING CONTINUITY
  1206.  
  1207. The viewer should be able to examine the image and understand:
  1208.  
  1209. what the Beyblade is,
  1210.  
  1211. which character inspired it,
  1212.  
  1213. how its parts fit together,
  1214.  
  1215. what kind of battler it is,
  1216.  
  1217. what makes it mechanically distinctive,
  1218.  
  1219. how it launches,
  1220.  
  1221. what comes in the package,
  1222.  
  1223. and how every representation belongs to the same canonical physical product.
  1224.  
  1225. Generate the finished image now.
Advertisement
Add Comment
Please, Sign In to add comment