← ClaudeAtlas

pokemon-champions-ui-sessionlisted

Work on the active Pokémon Champions UI build session — read its intent and artifacts through the pcui CLI, run the normal UEP team-building flow, and submit each gate artifact back so the local web panel renders progress live. Trigger when the user asks to handle/process the current Pokémon UI session. Chinese examples include "处理当前 Pokémon UI 会话", "继续 UI 会话", "看看 UI 会话的决策". English examples include "work on the current Pokémon UI session", "continue the UI session", "pick up my UI session". Japanese examples include "現在の Pokémon UI セッションを処理して", "UI セッションを続けて". Requires the pokemon-champions-team skill (and its sibling data skills) — this skill only adds the session I/O, never replaces the UEP discipline.
pmwl0128/pokemon_champion_agent · ★ 27 · Web & Frontend · score 72
Install: claude install-skill pmwl0128/pokemon_champion_agent
# Pokémon Champions UI Session The local web panel (`pcui serve`) and you collaborate through ONE shared session store: the panel is the session's eyes and hands, you are the decision participant. This skill adds exactly one thing to your normal workflow — reading session context and submitting gate artifacts through `pcui`. The team-building discipline itself is unchanged: follow `pokemon-champions-team`'s assisted workflow (UEP) exactly as you always do. ## CLI The pcui command for this machine: `{{PCUI_CMD}}` (bridge directory: `{{BRIDGE_DIR}}`) ``` {{PCUI_CMD}} session list # newest first {{PCUI_CMD}} session show --id <S> # meta.intent + heads + ledger {{PCUI_CMD}} artifact get --session <S> --kind <kind> # latest artifact of that kind (verbatim) {{PCUI_CMD}} artifact put --session <S> --kind <kind> --file out.json # or pipe via stdin {{PCUI_CMD}} run <op> [--file team.json] [--context ctx.json] [--args '<json>'] # one whitelisted team operator in the daemon ``` ## Workflow 1. **Find the session**: `session list`, pick the one the user means (usually the newest, or the id they name). `session show --id <S>` gives `meta.intent` (the user's build intent typed in the panel), `heads` (latest artifact per kind), and the ledger. 2. **Read what exists**: `artifact get` every kind in `heads` that matters — `context`, `decision` if present (the user's checkpoi