Emoji Forge
Run uv run forge --help from this skill folder, or pass its path with uv run --project SKILL_DIR forge from the working folder. Use individual commands on files and folders or forge all with an optional repeatable pack manifest. The tool reference covers both paths, including timing and Python hooks.
Explore ideas with the user. Sketch or discuss a storyboard when it helps, try poses or graphic treatments, and adapt to their feedback. If the harness has native image generation and editing, such as Codex's built-in image tool or an image MCP, use it for characters, poses, expressions, props and in-betweens. For character packs, sketch a distinctive model and check its name and silhouette for resemblance to existing characters. Model the parts that recur, then thread each cel through the previous frame, nearest key, and relevant character, asset and integration sheets. Frame-edit workflow
Use forge new, sheets, stage and review-pack for production scaffolds and reviewer hand-offs. If there is no native image tool, use a user-provided image API, hand-made art or a Python drawing hook.
One-shot requests
Treat make <idea> after the skill name, or an equivalent request for a finished pack, as a one-shot request. Run forge make "<idea>" --project <pack-dir> --json yourself. Use a project directory in the user's workspace. Pass request details as CLI options. Use --refs for attached images, --count for pack size, --target for the platform preset, --static or --animated for the requested format, and --emoji for each explicitly named emoji.
Handle needs-image with the available image tool and continue with forge make --resume --project <pack-dir> --json. Use the same project's make.json on follow-ups. Review stage outputs yourself, fix issues, and continue through the final checks. By default, return only the finished overview GIF or PNG and the ZIP.
Add --checkpoints only when the user asks to see intermediate work. For “show me the storyboard before animating,” set --checkpoints storyboard. Share the requested materials on needs-review and continue with --resume --approve once the user approves. One-shot workflow
Design effects around each emoji’s story. Use the custom effect walkthrough to test an idea at the target size. For a hit, comparing timings on the same pose can show where the contact reads best. Treat the recipes and helpers as a toolbox. Write your own shader and passes whenever the action needs them, using any technique and skipping helpers that get in the way.
Review individual assets, how they interact in motion, and the whole pack side by side with forge lineup. Use forge check with a model mask and a drift tolerance to catch unintended changes of scale or position. Use forge snapshot before a revision and forge compare to show the difference. Read the review tips or the Slack export reference when relevant. For ideas, see the optional craft notes on timing, expressions, and common problems.