Image Maker

@rules/natural-image-workflow.md @references/gpt-image-2-research.md @references/json-prompt-best-practices.md @references/prompt-schema.md

Image Maker

Respond in the user's language for planning notes, clarifying questions, and final reports. Keep all image-model-facing JSON prompt values in English, except exact visible text requested by the user, which must remain verbatim in image_prompt.text.verbatim.

Create situation-appropriate bitmap images that feel photographed, designed, or illustrated for the actual HyperB context rather than obviously AI-generated. The skill turns a vague visual request into a researched image brief, converts it into an English JSON prompt, reviews the prompt, generates or edits with gpt-image-2, and validates the result before it is used in the project.

Use this skill when the user wants Codex to create, edit, or prepare a raster image asset and the result must be believable, brand-usable, or tailored to a concrete business/content situation.

Prefer this skill over generic image generation when the request mentions any of these:

• "AI 티 안 나게", "realistic", "natural", "authentic", "not stock", "not AI-looking"
• HyperB marketing, business, product, landing page, social, article, deck, ad, or UI imagery
• research-backed visual direction before image generation
• using gpt-image-2 specifically

Do not use this skill when:

• the desired output is SVG/vector/code-native UI, not a raster image
• the deliverable is primarily a logo, favicon, app icon, or transparent-background brand mark; route to logo-maker instead
• the user wants a quick generic image-generation run without HyperB research, JSON review, archive, or preview discipline; use image-generation or the plain imagegen path instead
• the user only wants prompt writing and explicitly says not to generate
• a deterministic edit to an existing local SVG, HTML/CSS, or design-token asset is clearly better
• the request is only generic web research with no raster-image deliverable

1. Read references/gpt-image-2-research.md when model behavior, supported generation settings, quality/size choices, or provider-sensitive claims affect the task.
2. Read references/prompt-schema.md and references/json-prompt-best-practices.md before creating or changing the English JSON prompt structure.
3. Read rules/natural-image-workflow.md before adding naturalism, realism, or anti-AI-looking capture details.
4. Use scripts/archive-generated-images.mjs after generation/editing when local generated image paths or a latest-output count are available; inspect its output and archive listing before final response.
5. Rely on assets/image-preview-template.html only through the archive helper unless debugging preview rendering.
6. Use .hypercore/research/2026-04-29-image-maker-naturalism.md and .hypercore/research/2026-04-29-json-prompt-best-practices-for-image-maker.md when deeper rationale or source context is needed beyond the concise references.

• Codex only: use the Codex image generation capability or the project-approved imagegen path.
• Model requirement: every API/CLI image generation or image editing call must use gpt-image-2 unless the user explicitly changes the requirement in a later instruction.
• Prompt pipeline requirement: do not generate immediately from raw user wording. Always pass through user requirements → English JSON prompt → prompt review → image generation.
• JSON prompt language: all generated prompt values intended for the image model must be written in English, while notes to the user may be Korean or the user's language.
• Do not silently downgrade to another image model for convenience, transparency, cost, or compatibility.
• If transparent background is needed and gpt-image-2 cannot provide native transparency in the available path, use an opaque/chroma-key workflow or ask for a requirement change before using another model.
• Treat the system imagegen skill as the execution helper when available; this skill owns the higher-level HyperB research, art direction, and naturalism checks.
• Artifact archive requirement: after every generation/edit, create .hypercore/image-maker/<topic-slug>/, write the reviewed prompt as prompt.json, and copy generated outputs from ~/.codex/generated-images or the returned image path into that folder as image1.png, image2.png, image3.png, ... before reporting completion.
• Preview requirement: every completed archive must include .hypercore/image-maker/<topic-slug>/preview.html generated from the local preview template. When the user wants to inspect the result, or when the task asks to show the result, open that preview in a fresh Google Chrome window/tab with the local helper. If Chrome cannot be opened in the current environment, report the preview.html path and the open command instead of hiding the failure.

Positive examples:

• "HyperB 랜딩 페이지 히어로 이미지를 AI 티 안 나게 만들어줘."
• "gpt-image-2로 B2B SaaS 고객 사례용 자연스러운 사무실 사진 느낌 이미지를 생성해줘."
• "이 제품 설명을 읽고 상황에 맞는 블로그 대표 이미지를 리서치 기반으로 만들어줘."
• "광고용 이미지를 만들되 스톡 사진처럼 과장되지 않고 실제 촬영한 느낌이 나게 해줘."
• "이미지를 생성한 다음 preview.html로 저장하고 크롬에서 바로 보여줘."

Negative examples:

• "이 아이콘을 기존 SVG 스타일에 맞게 수정해줘." → edit SVG directly.
• "이미지 생성은 하지 말고 Midjourney 프롬프트만 써줘." → prompt-writing task only.
• "투명 배경 로고 PNG를 만들어줘." → use logo-maker for logo/favicons/brand marks.
• "빠르게 아무 이미지나 하나 생성해줘." → use generic image-generation/imagegen unless HyperB-grade research, archive, and preview are required.

Boundary example:

• "상품 페이지 이미지를 개선하고 싶어." If the user needs image asset generation or editing, use this skill; if they only need UX advice, use research/design guidance instead.

1. Clarify by inference first. Identify audience, placement, aspect ratio, brand tone, subject, required copy, and whether the asset is preview-only or project-bound. Ask only when a missing detail would cause a materially wrong image.
2. Research the situation. For unfamiliar domains, current products, visual references, markets, cultures, places, or factual scenes, run focused research before writing the prompt. Prefer official/product sources and recent visual references; record sources in the final note.
3. Pick the image job. Classify as generate, edit, reference-guided generate, or batch/variants.
4. Write an art-direction brief. Define job-to-be-done, viewer belief, scene, subject, camera/composition, lighting, material/texture truth, constraints, and avoid list.
5. Convert requirements into an English JSON prompt. Use references/prompt-schema.md and references/json-prompt-best-practices.md. Treat the JSON as an inspectable planning artifact, not just an API payload. Keep prompt-facing values in English, preserve exact requested visible text verbatim, and encode assumptions explicitly.
6. Review the JSON prompt before generation. Parse the JSON, check required fields, confirm source/reference roles and edit invariants when relevant, and verify that it is situation-specific, coherent, non-contradictory, safe, and compatible with gpt-image-2. Fix the JSON before generation if any review item fails.
7. Apply naturalism rules. Load rules/natural-image-workflow.md and add only the imperfections that fit the chosen capture story.
8. Generate/edit with gpt-image-2. Use the reviewed JSON prompt as the source of truth. Use quality: low for drafts and medium or high for final assets. Keep sizes valid for gpt-image-2; prefer 1024x1024, 1536x1024, 1024x1536, or a placement-specific multiple-of-16 size.
9. Validate visually before shipping. Check physical plausibility, lighting, anatomy, material behavior, text, brand fit, artifacts, and whether it looks generic/stock/AI.
10. Iterate narrowly. Change one failure dimension at a time: geometry, lighting, material, capture artifact, text, or composition. Update and re-review the JSON prompt before the next generation.
11. Archive deliberately. For each image job, choose a descriptive topic slug and create .hypercore/image-maker/<topic-slug>/. Save the final reviewed JSON prompt as .hypercore/image-maker/<topic-slug>/prompt.json, then copy every generated/edited output from ~/.codex/generated-images or the image generation return path into the same folder as image1.png, image2.png, image3.png, ... in generation order. Use scripts/archive-generated-images.mjs when local file paths are available. If the returned format is truly jpeg or webp, keep the real extension instead of lying with .png. If the asset must also be used by app code or committed, copy it separately to the project asset path after preserving the .hypercore/image-maker/<topic-slug>/ archive. Do not leave a referenced asset only in a Codex/global generated-images location.
12. Create and show the preview. Ensure the archive contains preview.html rendered from assets/image-preview-template.html. Use --open-preview when the user asked to see the finished result, so a fresh Google Chrome window opens to the local preview. If opening Chrome fails, keep the preview file and include the exact path plus command to open it.
13. Verify the archive and preview. Before reporting completion, list the archive directory and confirm prompt.json, preview.html, and every expected imageN.* file exists.
14. Report the prompt and evidence. Include final archive path(s), preview path, whether Chrome was opened, model (gpt-image-2), quality/size if known, final reviewed JSON prompt/brief, sources used, and any app/public asset copies.

When the image generation path saves files under ~/.codex/generated-images, archive them immediately with the local helper instead of manually renaming files:

node skills/image-maker/scripts/archive-generated-images.mjs \
  --topic "descriptive topic" \
  --prompt /path/to/reviewed-prompt.json \
  --images ~/.codex/generated-images/generated-1.png ~/.codex/generated-images/generated-2.png \
  --open-preview

The helper writes preview.html by default from assets/image-preview-template.html. Use --open-preview when the finished image should be shown immediately in a fresh Google Chrome window/tab; omit it for non-visual batch runs, CI, or environments without Chrome. If the exact generated file paths are not printed but the number of outputs is known, use --latest <n> right after generation so the newest generated files are copied into .hypercore/image-maker/<topic-slug>/ as image1.*, image2.*, ... . Always inspect the helper output and directory listing before final response.

The prompt must be created as JSON first. Use valid JSON only: double-quoted keys/strings, no comments, no trailing commas. The JSON is the reviewed source of truth for the final model-facing prompt; it is not merely a raw Image API request body.

Load references/json-prompt-best-practices.md when creating or changing this structure. Best-practice gates:

• Keep API/output settings separate from creative direction.
• Use a stable schema_version and preserve key order for reviewability.
• Record assumptions, unknowns, source inputs, and research anchors explicitly.
• For edits/reference-guided generation, name each input by role and state what must not change.
• Put exact visible text only in image_prompt.text.verbatim; preserve the user's requested language there.
• Assemble generation_prompt only after the review checklist passes.

Use references/prompt-schema.md as the canonical prompt schema. The core review contract is:

• Required field groups: schema_version, model, task, use_case, generation_settings, artifact_archive, user_requirements_summary, assumptions, source_inputs, placement, research_anchors, image_prompt, edit_plan, review_checklist, review_notes, and generation_prompt.
• Fresh generation may set edit_plan to null; edit/reference-guided jobs must fill edit_plan.change_only, edit_plan.preserve, edit_plan.allowed_drift, and mask/selection notes when relevant.
• source_inputs must name each reference by role and invariant before generation.
• generation_prompt is assembled only after the review checklist passes.

Prompt review rules:

• If review_checklist.valid_json is false, repair the JSON before doing anything else.
• If required fields are empty, fill them with a concrete assumption or mark why the gap is non-blocking.
• If any prompt-facing value is not English, translate it while preserving exact user-requested visible text in image_prompt.text.verbatim.
• If the JSON mixes multiple capture/design stories, split into variants or choose the strongest single story before generation.
• If factual/current/specialized scenes lack research_anchors, research first or mark why research was unnecessary.
• If source images are present but source_inputs lacks roles/invariants, add them before generation.
• Generate only after every review checklist value is true or the unresolved risk is explicitly accepted by the user.

Before completion, pass all checks:

• The model requirement is satisfied: gpt-image-2 used or explicitly specified for the generation path.
• User requirements were converted into a valid English JSON prompt before generation.
• The JSON prompt was parsed successfully and follows the stable schema from references/json-prompt-best-practices.md.
• The JSON prompt was reviewed and corrected before image generation.
• Reference-guided or edit jobs include source-input roles, edit invariants, and explicit preserve/change-only constraints.
• The image brief is situation-specific, not generic style-word soup.
• Research was performed or consciously skipped because the scene was simple and non-factual.
• The prompt uses one coherent capture/design story without contradictory lighting or lens cues.
• Naturalism uses physical evidence: lens, exposure, lighting, material texture, or context continuity.
• The output is checked for common AI tells: anatomy, hands, teeth, eyes, text, repeated patterns, impossible shadows, warped product details, excess symmetry, and stock-photo posing.
• Every generation/edit job has a stable archive directory under .hypercore/image-maker/<topic-slug>/.
• The archive contains the reviewed prompt at .hypercore/image-maker/<topic-slug>/prompt.json.
• Every generated/edited image has a stable copy in the archive as image1.png, image2.png, image3.png, ... or the matching real extension for non-PNG outputs.
• The archive contains preview.html generated from assets/image-preview-template.html, and it renders the archived images using local relative paths.
• If the user asked to see the result, preview.html was opened in a fresh Google Chrome window/tab, or the failure and exact open command were reported.
• No generated image remains only in ~/.codex/generated-images or another global/temp Codex location.
• Project-bound images that app code must reference are additionally copied to the appropriate tracked/public asset path if needed.
• Final response includes saved paths, reviewed JSON prompt or concise prompt summary, sources, and remaining risks if any.

• rules/natural-image-workflow.md: practical rules for non-AI-looking, context-aware image direction.
• references/gpt-image-2-research.md: source-backed gpt-image-2 model facts and links.
• references/json-prompt-best-practices.md: researched JSON prompt schema, review gates, and source maps.
• references/prompt-schema.md: canonical full JSON prompt example and edit/reference-guided edit_plan shape.
• scripts/archive-generated-images.mjs: deterministic helper that copies reviewed prompts and generated image files into .hypercore/image-maker/<topic-slug>/prompt.json and imageN.*.
• assets/image-preview-template.html: local, self-contained preview template rendered as .hypercore/image-maker/<topic-slug>/preview.html by the archive helper.
• .hypercore/research/2026-04-29-image-maker-naturalism.md: full naturalism/model research report saved for reuse.
• .hypercore/research/2026-04-29-json-prompt-best-practices-for-image-maker.md: JSON prompt best-practice research report.