메뉴
Ingest the local recipe-icons-improvement-for-esir companion mod, audit ESIR recipe icon and visibility drift, and generate non-mutating batch review reports plus patch-ready planning data for icon, sorting, hiding, and signal cleanup work.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | esir-recipe-icon-style |
| description | Ingest the local recipe-icons-improvement-for-esir companion mod, audit ESIR recipe icon and visibility drift, and generate non-mutating batch review reports plus patch-ready planning data for icon, sorting, hiding, and signal cleanup work. |
Use this skill when work touches ESIR recipe icon readability, subgroup or order drift, Factoriopedia visibility, player-crafting visibility, recipe signal cleanup, or batch review of companion-style changes outside the game.
This skill treats the locally installed recipe-icons-improvement-for-esir companion mod as the primary baseline and keeps the workflow non-mutating by default.
Read the sources in this order unless the user explicitly wants something else:
%APPDATA%\Factorio\mods\recipe-icons-improvement-for-esir*.zip.factorio-qc/dump-run-data-2/script-output/data-raw-dump.jsonexotic-space-industries-remembrance/Do not treat Mod Portal screenshots as the primary spec when the local companion mod is available.
Run the probe first so the skill starts from local truth instead of memory.
python .codex/skills/esir-recipe-icon-style/scripts/companion_mod_probe.py `
--output .codex/skills/esir-recipe-icon-style/output/companion-baseline.json
When you need drift detection against an older snapshot:
python .codex/skills/esir-recipe-icon-style/scripts/companion_mod_probe.py `
--compare .codex/skills/esir-recipe-icon-style/output/companion-baseline.json `
--diff-output .codex/skills/esir-recipe-icon-style/output/baseline-diff.json
The probe is expected to summarize:
0-config.luadata-final-fixes.luaesir-21* through esir-43*Use the audit script to build a best-effort static inventory before planning changes.
python .codex/skills/esir-recipe-icon-style/scripts/recipe_icon_audit.py `
--repo-root . `
--probe .codex/skills/esir-recipe-icon-style/output/companion-baseline.json `
--output .codex/skills/esir-recipe-icon-style/output/recipe-audit.json
The audit should stay conservative. If a prototype cannot be classified confidently, prefer manual-review-needed over guessing.
For direct companion icon-helper hits, the audit now tries to synthesize concrete proposed.icon_layers from the local companion rule expressions. If a helper expression stays dynamic or ambiguous, keep it strategy-only instead of fabricating layers.
By default, the audit keeps the report limited to ESIR-owned recipes plus recipes that resolve back to ESIR's declared dependency and touchpoint universe from .codex/esir/dependency-catalog.json. Use the wider mode only when you explicitly want companion spillover from unrelated active mods.
Common variants:
python .codex/skills/esir-recipe-icon-style/scripts/recipe_icon_audit.py `
--repo-root . `
--probe .codex/skills/esir-recipe-icon-style/output/companion-baseline.json `
--scope all-candidates `
--output .codex/skills/esir-recipe-icon-style/output/recipe-audit.json
--include-non-esir still works as a compatibility alias, but prefer the explicit --scope modes:
esir-and-dependencies (default)esir-onlyall-candidatesUse the batch normalizer when you want one manifest that can drive both review and patch planning.
python .codex/skills/esir-recipe-icon-style/scripts/recipe_icon_batch.py `
--audit .codex/skills/esir-recipe-icon-style/output/recipe-audit.json `
--output .codex/skills/esir-recipe-icon-style/output/recipe-batch.json
You can also merge explicit entries for prototypes that need manual notes, missing art, or stronger review tags.
Common variants:
python .codex/skills/esir-recipe-icon-style/scripts/recipe_icon_batch.py `
--audit .codex/skills/esir-recipe-icon-style/output/recipe-audit.json `
--extra-manifest .codex/skills/esir-recipe-icon-style/assets/examples/recipe-icon-manifest.example.json `
--output .codex/skills/esir-recipe-icon-style/output/recipe-batch.json
python .codex/skills/esir-recipe-icon-style/scripts/recipe_icon_batch.py `
--audit .codex/skills/esir-recipe-icon-style/output/recipe-audit.json `
--status manual-review-needed `
--family isotope-overlay `
--prototype ei-bio-oil-synthesis `
--output .codex/skills/esir-recipe-icon-style/output/recipe-batch.json
Generate the HTML report, machine-readable JSON, and PNG contact sheet from the batch manifest.
python .codex/skills/esir-recipe-icon-style/scripts/render_recipe_icon_report.py `
--manifest .codex/skills/esir-recipe-icon-style/output/recipe-batch.json `
--output-dir .codex/skills/esir-recipe-icon-style/output/report
The report is meant for sanity checking outside Factorio. It should always show before and after behavior data, not icon previews alone.
The renderer can resolve icon assets from:
base, core, and space-age%APPDATA%\Factorio\modsIf an icon still cannot be resolved after those sources are checked, keep the placeholder and call it out in notes instead of fabricating a preview.
Use preview.resolved_sources in report.json as the provenance trail when you need to confirm whether a preview came from repo-local art, Factorio data, or installed mod archives.
Use milestone monitoring by default:
Session-sidecar monitoring is also acceptable during long implementation sessions, but do not present it as an always-on watcher. This skill is meant to support bounded re-checks, not background daemon behavior.
scripts/companion_mod_probe.py: summarize the companion mod and emit baseline diffsscripts/recipe_icon_audit.py: statically inspect ESIR prototypes and classify driftscripts/recipe_icon_batch.py: normalize audit data plus manual entries into one manifestscripts/render_recipe_icon_report.py: build report.html, report.json, and report-sheet.pngassets/examples/recipe-icon-manifest.example.json: starter manifest for guided or batch reviewESIR-first repo-local development surface for Exotic Space Industries: Remembrance. Use when Codex should work faster inside this workspace by relying on checked-in manifests, the ESIR wrapper command, Factorio QC delegation, Mod Portal scouting, save catalog resolution, Lua/runtime/prototype helper routing, Meshy/Blender asset pipeline routing, Factorio asset export, item icon prep, recipe icon style audits, art/browser session handoff, cache diffing, packaging, or ESIR-specific runtime/prototype maps.
Use when Codex should create, inspect, or render Blender procedural animations for non-human assets, ESIR machines, crystals, gates, orbitals, props, Meshy GLBs, animation spritesheets, or Factorio-ready transparent frame sheets.
Use when Codex should orchestrate a full ESIR asset pipeline from Meshy prompts or existing models through Blender static/procedural rendering, Factorio-style shadows, staged Factorio export, previews, QA, manifests, and reproducible asset dossiers.
Use when Codex should stage Meshy/Blender spritesheets, animated sheets, shadow sheets, or source icon art as Factorio/ESIR-ready asset drafts with previews, manifests, and Lua prototype snippets without wiring them into the mod.
Use when ESIR item art needs to be turned into a transparent Factorio item icon strip, especially when source art has a baked light checkerboard or white background and must end up as a `128/64/32` mipmapped item icon under `exotic-space-industries-remembrance/graphics/items/`.
Prefer the shared `ei_lib` helper surface in `exotic-space-industries-remembrance/lib/lib.lua` before creating new Lua local functions. Use when Codex edits ESIR runtime, data-stage, prototype, migration, or support Lua files and might add utility helpers, table or string helpers, recipe or technology mutation helpers, notification helpers, color or formatting helpers, wrappers around `data.raw`, prototype `custom_tooltip_fields`, or runtime `LuaEntity.custom_status` combat readouts such as DPS/status rows for weapons, turrets, or vehicles. For runtime queue, delayed-bucket, telemetry-gate, counter, or status-snapshot plumbing, prefer `exotic-space-industries-remembrance/lib/runtime-scheduler.lua` instead. Inspect `ei_lib` first when the helper is general utility; if it almost fits, extend or harden the shared function instead of inventing a one-off local helper.