How do I install the Pocketjs Gba Imagegen skill?

Run npx skillmds@latest add pocket-stack/pocketjs-gba-imagegen in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pocketjs Gba Imagegen safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pocketjs Gba Imagegen?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pocketjs Gba Imagegen free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pocketjs Gba Imagegen?

pocket-stack (@pocket-stack) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pocketjs Gba Imagegen by pocket-stack

Name: Pocketjs Gba Imagegen
Author: pocket-stack

Pocketjs Gba Imagegen

Generate original GBA-friendly pixel-art asset source sheets through Codex app-server and ImageGen, then save PNGs for PocketJS AOT asset baking. Use when a local coding agent needs reusable tiles, 16x16 character sprites, RPG item icons, or generic Game Boy Advance-style pixel art through the shared Codex image generation path.

pocket-stack f4853ee 2.5 KB Updated Sep 17, 2026

File contents

PocketJS GBA ImageGen

Overview

Use this skill when a PocketJS or local Codex agent needs GBA-class pixel-art source images without hand-driving the built-in ImageGen tool. The standard entrypoint is bun imagegen; it starts a temporary Codex app-server on localhost, sends a single ImageGen turn, captures the image_generation result from the app-server event stream, and writes the PNG requested by --out.

The prompt is intentionally generic to the platform category. It must not ask for a specific existing game, franchise, creature, character, logo, or visual style clone.

Standard Workflow

Confirm the target branch and local changes:

git status --short --branch

Generate a source sheet with the Bun TypeScript CLI:

bun imagegen --out aot/demo/imagegen/gba-source.png

Add an art-direction seed only when the user asks for one:

bun imagegen --out aot/demo/imagegen/rainy-port-source.png --theme "rainy port town with stone quays and lanterns"

Use --json when another coding agent needs machine-readable output:

bun imagegen --out /tmp/gba-sheet.png --json

If replacing the AOT demo source sheet, rerun the deterministic extractor:

bun aot/demo/imagegen/build-assets.ts

Prompt Profiles

Use --kind sprite-sheet for the default mixed source sheet: terrain cells plus one generic four-direction walking character.

Use --kind tileset for top-down background terrain and props.

Use --kind character for one 16x16-style walking sprite with down/up/left/right facings and two walk frames per facing.

Use --kind items for small RPG item icons that remain readable as 16x16 sprites.

Constraints

Keep all command wrappers in Bun TypeScript. Do not add native shell scripts for this workflow.
Generate original assets only; avoid franchise terms and existing character references.
Keep the output as a source sheet on a neutral background with gutters so later scripts can crop or quantize it.
Treat the generated PNG as source art. The AOT runtime still requires deterministic 4bpp extraction before the image can ship as cartridge data.

---name: pocketjs-gba-imagegendescription: Generate original GBA-friendly pixel-art asset source sheets through Codex app-server and ImageGen, then save PNGs for PocketJS AOT asset baking. Use when a local coding agent needs reusable tiles, 16x16 character sprites, RPG item icons, or generic Game Boy Advance-style pixel art through the shared Codex image generation path.---# PocketJS GBA ImageGen## OverviewUse this skill when a PocketJS or local Codex agent needs GBA-class pixel-art source images without hand-driving the built-in ImageGen tool. The standard entrypoint is `bun imagegen`; it starts a temporary Codex app-server on localhost, sends a single ImageGen turn, captures the `image_generation` result from the app-server event stream, and writes the PNG requested by `--out`.The prompt is intentionally generic to the platform category. It must not ask for a specific existing game, franchise, creature, character, logo, or visual style clone.## Standard Workflow1. Confirm the target branch and local changes:```textgit status --short --branch```2. Generate a source sheet with the Bun TypeScript CLI:```textbun imagegen --out aot/demo/imagegen/gba-source.png```3. Add an art-direction seed only when the user asks for one:```textbun imagegen --out aot/demo/imagegen/rainy-port-source.png --theme "rainy port town with stone quays and lanterns"```4. Use `--json` when another coding agent needs machine-readable output:```textbun imagegen --out /tmp/gba-sheet.png --json```5. If replacing the AOT demo source sheet, rerun the deterministic extractor:```textbun aot/demo/imagegen/build-assets.ts```## Prompt ProfilesUse `--kind sprite-sheet` for the default mixed source sheet: terrain cells plus one generic four-direction walking character.Use `--kind tileset` for top-down background terrain and props.Use `--kind character` for one 16x16-style walking sprite with down/up/left/right facings and two walk frames per facing.Use `--kind items` for small RPG item icons that remain readable as 16x16 sprites.## Constraints- Keep all command wrappers in Bun TypeScript. Do not add native shell scripts for this workflow.- Generate original assets only; avoid franchise terms and existing character references.- Keep the output as a source sheet on a neutral background with gutters so later scripts can crop or quantize it.- Treat the generated PNG as source art. The AOT runtime still requires deterministic 4bpp extraction before the image can ship as cartridge data.

Frequently asked questions