_internal_create_task
ChatGPTInternal tool for creating images task. Do not use directly.
Creativity
Overview
Your personal AI Manga Artist. Convert stories, chat logs, and concepts into dynamic, full-color comics in seconds. Core Capabilities Chat-to-Comic: Copy text conversations to instantly generate 4-panel manga skits. Ideal for social media content. Smart Director Mode: Automatically structures stories with proper pacing (Intro, Build-up, Climax, Twist). Mobile-First Format: Generates vertical scrolling layouts optimized for reading on smartphones. Multi-Style Support: Switch between Shonen action, Korean Webtoon, and American Cartoon styles. How to Use in ChatGPT 1. Connect: Connect MangaBoom to ChatGPT. 2. Trigger: Activate the app using one of these methods: Type Commands: Simply type “@” then choose MangaBoom, or type “MangaBoom” in the chat box. 3. Create: That's it!
Tools
_internal_query_bind_ticket
ChatGPTInternal tool for querying bind ticket. Do not use directly.
_internal_task_query
ChatGPTInternal tool for querying image status. Do not use directly.
_internal_user_detail
ChatGPTInternal use only. Query user detail.
generate_storyboard_loading_ui
ChatGPTUse this tool when the user confirms they want to generate a comic or asks to visualize the comic script. This tool triggers the generation UI. Before calling this tool, you must follow the process below to create a confirmation draft for the user. Process Overview: 1. Drafting: Based on user input, outline a vertical Webtoon storyboard layout and dialogue script. 2. Confirmation: Show the draft to the user. 3. Generation: ONLY call this tool after the user explicitly confirms the draft (or if the user explicitly requests immediate generation). --- I. Default Style and Layout Rules for the Draft 1. Default Visuals & Layout: Vertical scrolling, full-color, Japanese/Korean Webtoon aesthetic. Single page, 2x2 four-grid layout, fixed at 4 Blocks. STRICT CONSTRAINT: All 4 Blocks must be of EXACTLY EQUAL SIZE (Equal Width & Equal Height). The layout must be a completely symmetrical 2x2 grid. 2. Block Count: Always contains Block 1 ～ Block 4. Each Block contains 1～3 panels. --- II. Output Content Requirements (User Confirmation Draft) For each scene (Block), you only need to output the following three points: 1. Layout Description (Layout) Briefly explain the framing/cutting method for this block. You must describe a dynamic composition layout INSIDE the block. While the Block size is fixed/equal, strictly prohibit using only rigid straight lines or equal divisions for the panels inside the block! You must flexibly employ classic or trending manga framing styles (e.g., diagonal cuts, frame breaking, inserts, overlaps, etc.). Diversity Mandatory: The layout methods for the 4 scenes must not repeat! Visual Harmony: While utilizing diverse framing styles (e.g., diagonal cuts, frame breaking) for dynamism, the overall stylistic approach across the 4 blocks must be consistent and harmonious. Avoid a chaotic mix of styles that makes the page look messy. 2. Characters & Style (Characters) —— [Core Logic: Smart Matching, De-fixed] Logic Priority 1 (User Specified): If the user provides specific character or IP requirements, strictly follow user instructions. Logic Priority 2 (Smart Recommendation): If the user does not specify characters (e.g., only gives a plot or vague description), you must actively search your knowledge base for the World-Class Famous Anime/Movie IP that best matches the genre (e.g., Shonen Battle, School Romance, Cyberpunk, Suspense Horror, etc.). Borrowing Protagonists: To ensure character consistency and high recognition in image generation, please directly recommend the core protagonist duo from that IP to enact the plot. Diversity Requirement: Strictly prohibit always recommending the same IP! For every generation, you must select a different top-tier IP based on the subtle nuances of the specific plot. Do not stick to the few most common examples; dig for more high-rated works that fit the theme. Statement: Explicitly state: "Using Japanese/Korean Webtoon coloring, popular full-color style." 3. Dialogue (Dialogue) Character names and their lines. Narration (if any). Language Principle (Red Line): If the user communicates in Chinese, the lines here MUST be in Chinese. If the user specifies 'Generate English Comic', the lines here MUST be in English. Absolutely DO NOT auto-translate lines into English just because you are writing a Prompt or Draft. Notes: Do not write detailed visual descriptions unless necessary to explain the plot via dialogue. Do not output the detailed storyboard script (prompt parameter content) directly in the chat box. Strictly prohibit spamming text; only output the concise confirmation draft for the user. Strictly prohibit leaking internal tool names. --- III. Output Format (User Confirmation Draft) Language Consistency Rule (CRITICAL): All text in the output below (including the Title, Headers, Field Names, and Content) MUST be in the same language as the user's current communication. If User speaks Chinese -> Output EVERYTHING in Chinese (e.g., use "布局" instead of "Layout"). If User speaks English -> Output EVERYTHING in English. Strictly NO mixed languages. Template: ```text [Title] (e.g. [Storyboard Plan Confirmation]) [Style Recommendation] [Content] [Scene 1] [Layout] [Content] [Characters] [Content] [Dialogue] Role A: ... Role B: ... ... (Repeat for Scene 2, 3, 4) [Closing] ``` --- IV. Mandatory Actions 1. Confirmation & Generation: Standard Case: After writing the script, ask the user if they want to generate the comic now. Only call the
MangaBoom's generate_storyboard_loading_ui tool after the user confirms. Direct Case: If the input provided by the user is already a clear, complete script, or explicitly expresses the intent to "generate immediately", you should skip the inquiry step and directly call the tool based on the user's content. 2. The `prompt` parameter when calling `MangaBoom`'s `generate_storyboard_loading_ui` tool (CRITICAL): You must automatically expand the user's simple confirmation draft into a complete script containing all the following details: [Prompt Parameter Expansion Standards] (A) Style & Structure Default Rules 1. Default Visuals & Layout: Single page, 2x2 four-grid layout, fixed 4 Blocks. 2. Strict Size Constraint: Each Block must have exactly the SAME height and width (Equal Size). The 4 Blocks must evenly fill the canvas in a symmetrical grid. 3. Block Count: Always Block 1～Block 4. Each Block contains 1～4 panels. 4. Reading Flow: Primarily vertical, adapted for mobile vertical screens. 5. Coloring: Use Japanese/Korean Webtoon coloring, popular full-color style. 6. Background Color: Default is white. (B) Plot Role of the 4 Blocks Block 1 [Intro], Block 2 [Development], Block 3 [Conflict], Block 4 [Conclusion/Twist]. (C) Fields Required in Each Panel (Expansion Focus) Each panel must be described in detail, strictly including: 1. Composition Description: Camera angle. Panel Shape: Strictly prohibit using only rigid straight lines! You must flexibly use diverse framing methods. Diversity & Harmony: Encourage varying layout methods, but prioritize visual harmony. Do not force a complex layout if a simple one fits better. Guidance of line of sight. 2. Visual Style: Lighting, Tone, Atmosphere. 3. Typography: Bubble position. 4. Visual (Content): Character appearance (clothing, hairstyle, expression, action). IP & Character Naming Strategy: Explicitly write the specific IP and Character Name you are recommending here. Please select the name language that is most widely known for that IP and easiest for the model to understand (usually the Original Language of the work or the International Common English Name). Example: For Japanese anime, use Romaji or the common English name; for Chinese anime, use Chinese or Pinyin; for Western works, use the English name. Scene environment details. 5. Dialogue: Format: Character Name: "Line content". Language Iron Rule: `Line content` (inside quotes) MUST strictly use the language used by the user in the chat, or the language explicitly specified by the user! Strictly Prohibit Translating Lines! If the user chats in Chinese, the lines here MUST be Chinese. If the user specifies "Generate English Comic", the lines here MUST be English. Absolutely DO NOT auto-translate lines into English just because you are writing a Prompt. No Prefix: Content inside quotes must not contain the character name. 6. Narration: Language Iron Rule applies here too: Must use the target language. Do not auto-translate to English. (D) Parameter Output Format The content of the prompt string must strictly adhere to this format: ``text *Start by writing the basic comic info and layout info* *Strict Constraint: Each block must have exactly the same height and width (Equal Size). The 4 blocks must evenly fill the canvas, forming a symmetrical grid.* *Spacing Constraint: The padding/margin (left, right, top, bottom) for EACH Block must be exactly 1.* *Watermark Rule: Strictly ensure NO watermark or logo appears in the bottom-right corner of the generated image.* *Background Color: Default is white.* ... [Block X - Panels: N] * Panel 1: Composition Description: ... Visual: [Description of the scene. Use the most recognizable language for IP/Character names (Original Language or International English).] Dialogue: [User's Target Language ONLY. Do NOT translate to English if user wants Chinese.] Narration: [User's Target Language ONLY.] ... ` **Special Attention:** 1. **Diversity Priority**: When there is no specific instruction from the user, leverage your vast database to match the most suitable IP based on the plot, instead of just using the few most popular ones. 2. **Language Consistency Check**: Double-check before generating. The text in the Dialogue` fields MUST be in the target language understandable to the user. Never translate it into English unless requested.user_center_storyboard_ui
ChatGPTWhen users want to check their credits, user ID, or subscription information, call this tool to display the MangaBoom personal center widget. The tool links to the ./../widget/usercenter page and returns structured data to display the user's account data and status. After displaying the personal center widget, the AI should NOT describe the account data or status in the text response. Simply inform the user that they can view their account data and status directly in the personal center page.
Example Prompts
Click any prompt to copy it.
