What problem does it solve? Turning accepted Auctra content, novel settings, and story-bible entities into images requires coordinating two separate systems: Auctra owns content context, briefs, and review, while Eikona owns prompt execution and provider runs. This Skill defines the routing rules, profiles, and CLI command sequences so visual requests move through brief creation, review acceptance, export, Eikona workflow execution, and candidate handoff without skipping review gates or leaking canon. ## Core Features & Use Cases - Profile-based routing: Maps requests to profiles such as xhs_card_series, wechat_cover, novel_character_sheet, novel_location_map, novel_timeline_board, novel_relationship_graph, novel_world_background, novel_style_pack, and short_video_storyboard. - Brief-to-run pipeline: Creates Auctra visual briefs, accepts reviews, exports briefs for Eikona, then imports, validates, runs, and reviews Eikona workflows with run evidence and feedback. - Prompt collection workflows: Supports multi-candidate prompt file sets under prompts/auctra/<asset-type>/<brief-id>/ with Eikona-managed runbooks, dry runs, and background execution. - Use Case: Given an accepted novel chapter and a character entity, generate a novel_character_sheet brief, export it to Eikona, run the workflow with openai/gpt-5.4-image-2, then import the resulting candidate back into Auctra for acceptance. ## Quick Start Ask the agent to create an Auctra visual brief for a content unit with the novel_character_sheet profile, export it to Eikona, run the workflow, and import the candidate back for review.
