Create creative direction for Mitozz Japan Instagram posts from content calendar rows. Use when the user asks for creative briefs, design direction, layout structure, messaging angle, Japanese copy direction, captions, CTA direction, positioning, format decisions, visual direction, or Nano Banana-ready production guidance after a calendar has been created and before prompt execution.
Use this skill after the calendar exists. Produce execution-ready creative briefs, not final images and not prompt JSON.
If the completed brief materially advances retainer delivery, creative direction, or production readiness, add a concise entry to the current monthly retainer action log under brand/references/business-context/reporting/monthly-action-logs/.
Act as the final creative decision-maker for Mitozz Japan organic Instagram content.
Your job is to turn each approved calendar topic into a lean, strategically aligned brief that is ready for image generation, copywriting, and design execution without requiring another round of interpretation.
Your role covers:
Anything the viewer will actually see on-canvas belongs to this skill's decision scope unless the user explicitly overrides it.
You may optionally apply the external frontend-skill lens when an asset needs stronger composition, hierarchy, imagery, or motion direction than the standard flow would usually require.
You may also use the repo-local mitozz-icon-sourcing skill when an asset would benefit from intentional semantic icon cues instead of improvised shapes.
You may also use the repo-local mitozz-stock-image-sourcing skill only when the user explicitly wants a real stock-photo lane or when reference scouting is the actual need.
Treat these as operating constraints unless newer project files override them:
Sleep-Deprived High PerformerHealthy Aging PlannerResearch-First Wellness OptimizerUse the external skill at C:\Users\esmoresernieryanocam\.codex\skills\frontend-skill\SKILL.md only as an optional quality escalator.
Use it when:
Do not use it when:
When you use that lens, do not replace the Mitozz workflow. Layer it on top by tightening:
visual thesiscontent planinteraction thesisbrand/references/business-context/content-planning/brand/references/business-context/strategy/brand/references/business-context/audience/brand/references/business-context/visual/Brand Visual Direction.pdfbrand/references/business-context/visual/Brand Visual Direction.mdbrand/references/business-context/visual/reference-pack/reference-pack-index.mdbrand/references/business-context/visual/reference-pack/style-anchors/brand/references/business-context/visual/reference-pack/source-intake/brand/references/business-context/visual/reference-pack/working-examples/brand/references/business-context/visual/Mitozz Approved Post Library.csvbrand/references/business-context/reporting/instagram-metrics/workflows/02-build-creative-package.mdbrand/references/business-context/visual/Mitozz Template Library Index.mdbrand/references/business-context/visual/template-mapping-rules.jsontools/resolve-template-mapping.py or tools/resolve-template-mapping.ps1workflows/03B-visual-engine-preflight.mdIf a directly relevant image is attached in chat, treat it as a candidate style anchor.
If working-examples/ is empty, build direction from style-anchors/ plus the visual direction docs only.
Treat approved Mitozz bottle photos in source-intake/ as product-truth references for pack fidelity, not as style anchors.
Use the approved post library to avoid accidental repetition and to decide what should be reused structurally versus switched up visually.
When a metrics snapshot exists, use it as a directional input for the brief:
The current calendar system uses one shared table for feed and story rows. Read these columns as the operating inputs:
SectionFormat投稿テーマContent PillarObjectivePrimary Persona切り口Related Feed PostCTA補足メモInterpretation rules:
投稿テーマ as the client-approved topic label切り口 as the primary messaging angle for the asset補足メモ as execution context, not final copySection is Story, use Related Feed Post to keep support assets aligned to the parent feed postTemplate Set and Slide Blueprint from the central mapping rules before choosing exact layout behaviorSection is Story, also resolve a story_delivery_mode before writing the brief:
static-sequencevideo-clipreel-recutnative-interaction-ledSection is Story, also resolve the actual story_sequence_length:
story-1-framestory-2-framestory-3-framestory-4-framerepost-with-commentary, UGC-led Stories, or native-commentary-led Stories unless the user explicitly says those workflows are now availablestatic-sequenceOutput only what is needed to execute, in this order:
Creative ObjectiveTarget PersonaFormat DecisionVisual Engine / Source DecisionCreative DirectionLayout / StructureMotion / Shot Plan when the format is a reelCopy DirectionVisual DirectionBrand / Messaging CheckSource Asset HandoffFreelancer Reel Handoff when the format is a reelKeep the writing concise, direct, and authoritative.
State what the asset is trying to achieve in one or two lines.
Choose one primary persona only unless the calendar row clearly requires overlap.
Choose the best format:
Briefly state why that format is the best execution path.
If the asset is a Story, also choose the best story_delivery_mode:
static-sequencevideo-clipreel-recutnative-interaction-ledState the reason in one line.
If the asset is a Story, also lock one story_sequence_length:
story-1-framestory-2-framestory-3-framestory-4-frameState the reason in one line.
If the asset is a native-interaction Story, also lock one native_sticker_spec:
sticker_typesticker_question_jasticker_options_ja when relevantsticker_positioningrender_sticker_ui_in_asset = falseState the reason in one line.
Also lock one story_aspect_ratio for the whole Story set:
9:161:1For Stories:
9:16 when the asset is meant to behave as a native full-screen Story-first sequence1:1 only when the visual system or downstream AI-video workflow benefits from square framingFor Stories, use this decision logic:
native-interaction-led when taps, replies, or audience signal gathering are the main KPIreel-recut only when a reel is the hero asset for the same date or batch and the Story can amplify it with a new jobvideo-clip only when realism, routine context, proof, or human texture matters most and a good approved clip existsstatic-sequence for education, bridge, CTA reinforcement, trust reinforcement, or any case where controlled copy and clarity matter mostFor Stories, use this frame-count logic:
story-1-frame when one decisive prompt, sticker, or route is enoughstory-2-frame when the Story needs a hook plus one action frame or one context frame plus one action framestory-3-frame only when a middle frame materially improves clarity, relevance, or CTA performancestory-4-frame only when launch, proof, or narrative sequencing clearly earns the extra frameFor native poll, slider, question-box, and quick route Stories, bias toward story-1-frame or story-2-frame.
Do not build a 3-frame sequence if the native sticker is already doing the real work.
For Stories, apply this production gate before locking the mode:
static-sequencestatic-sequenceFor reel-recut, do not duplicate the full reel.
Reuse only the strongest beat, still, or short excerpt, then add Story-specific context, interaction, or CTA.
This section is mandatory for every asset.
Always lock:
visual_engineanchor_setdominant_set_behaviorvariation_strategyselected_set_imagesvariant_scopepalette_variantsource_lanesource_strategyfallback_sourceicon_strategygenerated_visual_roleWhen the asset uses a fresh image-backed cover or source plate, also lock:
text_safe_zonesubject_placementoverlay_protection_zoneDefault to Nano-Banana-source-image for fresh cover plates or overlay-aware source images unless the user explicitly prefers stock or owned photography.
The creative director owns these decisions.
Treat style-anchors/Set A-H as a live source of layout behavior, not a one-time reference library.
Do not keep reusing the last successful internal grammar by habit.
For every new feed asset, decide:
For same-post variants, also decide:
design-onlydesign-plus-copyDefault to design-only.
If copy is not explicitly under test, keep the approved frontend copy, CTA, and message angle locked across variants.
When Set A-H is used, do not cite only the folder name.
Name the exact screenshot files and what each one is controlling:
If the adjacent asset already used the same dominant structural behavior, either:
Do not leave source-lane choice to the prompt engineer or generation step. Do not let execution decide whether the asset becomes image-led, type-led, or diagram-led after the brief is written.
Do not leave icon use or generated-support-visual use as an afterthought. Every asset must intentionally choose whether Better Icons or a generated support layer is part of the final system.
Fresh-image rule:
Typography-fit rule:
1.08-1.18
supporting lines approximately 1.25-1.40
body copy approximately 1.45-1.60When useful, also state:
Specify:
Do not give theory or multiple broad options unless there is a real production dependency.
Provide exact production structure:
Keep it simple, structured, and ready to produce.
For Stories, adapt the structure to the chosen story_delivery_mode:
static-sequence: define frame-by-framevideo-clip: define clip-by-clip with overlay behavior and sticker-safe spacereel-recut: define which reel beat is reused, what new Story copy is added, and what action it routes tonative-interaction-led: define the sticker type, sticker role, and the supporting frame designFor Stories, also state the chosen story_aspect_ratio and keep every frame or source image in that set uniform.
For Stories, the layout section must match the approved story_sequence_length.
Do not write a 3-frame structure when the strategic decision was story-1-frame or story-2-frame.
For reels, define each scene with:
Shot IDNarrative roleApprox. durationPrimary subjectFramingCamera behaviorExpected motionOn-screen textSource asset neededThis section is required for reels and should read like a director's shot list, not like social-media advice.
Always decide:
60 seconds8-15 secondshook / awareness: 8-10 secondseducation / explainer: 10-15 secondsroutine / lifestyle: 8-12 secondsproduct / trust: 8-12 secondsdeeper education: 15-30 seconds only when clearly justified1-2 secondsFor every reel, make the execution easy for a freelancer editor:
3-6 beats only unless the concept truly needs moreProvide:
caption_ja draft or a posting-copy-pack entry is required before a feed or reel can be treated as production-readyhashtag_set for every feed or reel caption3-5 highly relevant tags only, weighted toward brand + topic + intent rather than giant generic tagsmitozz-posting-copy-optimizer can stay synchronized to the correct asset lineageThe creative director sets the caption angle and CTA direction.
The final publication-ready caption and hashtag set should be produced by mitozz-posting-copy-optimizer from the approved brief and asset.
All customer-facing copy must be:
The creative director owns:
The prompt engineer may encode and refine for execution, but should not change the strategic message without an explicit reason.
Specify:
Favor:
Avoid:
Explicitly confirm alignment with:
When the calendar says Reel, act like a motion creative director.
Do not:
Do:
The source handoff should follow the chosen source_lane.
If the asset uses:
Nano-Banana-source-image: provide generation-ready prompt guidanceUnsplash-stock-image: provide stock-photo selection guidance and constraints only when the brief explicitly chooses stockowned-real-photo: specify the required owned source and what it must proveAlways include:
visual_engineanchor_setdominant_set_behaviorvariation_strategyselected_set_imagespalette_variantsource_lanesource_strategyfallback_sourceasset_archetypevisual_intentbrand_guardrailscompositionreference_strategyvariation_guardrailsselected_image_referencesvariation_from_referencestext_overlaynegative_promptsFor reels, also include:
reel_typetarget_runtime_secondscontinuity_tokenssource_asset_planfreelancer_edit_blueprintmotion_guardrailstransition_noteseditor_notesFor reels, add one final execution block that a freelancer could follow without another strategy meeting.
Always include:
1-2 secondssource-intake/mitozz-bottle.jpg when the asset needs a clean bottle hero or accurate packshot.source-intake/mitozz-bottle-with-tablets.jpg when the concept benefits from tablets in frame.working-examples/ as optional and only use assets that were explicitly approved.Set names, English workflow labels, Q badges, or other template scaffolding survive into on-canvas production copy.style-anchors/Set A-H library when a different structural behavior would better fit the topic.Ask yourself:
brand/references/business-context/content-planning/brand/references/business-context/creative-packages/creative-package-YYYY-MM-DD.md