ai-break-duel-card-addition

Estrelas7

Forks1

Atualizado9 de julho de 2026 às 11:02

Add or modify AI Break Duel cards end-to-end across the React/TypeScript game, headless simulation, decks, UI text, generated card art, documentation, tests, and commits. Use when the user asks to add a summon, command, relic, card effect, deck entry, card wording change, card image, or card-balance rule in the ai-break-duel repository.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

tegnike

tegnike/break-duel

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores webInformática e Matemática·SOC 15-1254

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	ai-break-duel-card-addition
description	Add or modify AI Break Duel cards end-to-end across the React/TypeScript game, headless simulation, decks, UI text, generated card art, documentation, tests, and commits. Use when the user asks to add a summon, command, relic, card effect, deck entry, card wording change, card image, or card-balance rule in the ai-break-duel repository.

AI Break Duel Card Addition

Workflow

Start from repository truth, not memory.
- Read docs/game-spec.md for current rules and naming conventions.
- Read references/file-map.md for the files that must stay synchronized.
- Inspect current code around similar card effects before editing.
Model the card once in the single TypeScript implementation.
- Add TypeScript effect unions, card pool entries, deck entries, rule helpers, action resolution, AI behavior, UI selection flow, and card text.
- The browser game and the headless simulation CLI (src/sim/) share the same engine, so one change covers both.
- Register every new or changed card effect in src/game/cardEffectCoverage.test.ts. The unit suite fails by design when an effect is unregistered, so skipping this breaks npm run check.
- Respect the deck construction rules when touching deck entries: 25 cards per deck, at most 2 copies per card name, and at most 5 summons of power 3 or higher.
Treat visible card text as player-facing rules text.
- Do not include internal implementation caps such as "maximum 3" on the card unless the user explicitly wants it on-card.
- Put internal details in docs/game-spec.md detailed rule sections when useful.
- Write draw text as 山札からカードをN枚引く.
- Avoid ただし; split drawbacks into separate short sentences, e.g. 消耗で出る。手札防御に使えない。
- Opponent draw logs must not reveal opponent card names.
Add generated art for every new card unless the user explicitly opts out.
- Under Codex: use the imagegen skill directly.
- Under Claude Code: imagegen cannot be executed directly. Delegate the generation to Codex CLI via the codex:rescue skill (or the codex:codex-rescue subagent), passing a self-contained task such as: imagegen スキルで「<カード名>」のカードアートを生成し、1600x900 (16:9) の WebP として src/assets/card-art/<card-id>.webp に保存して。アート方向性: <雰囲気・モチーフの指示> After the run, verify the file exists and is 16:9 (e.g. sips -g pixelWidth -g pixelHeight <file>) before registering it.
- Only if Codex is unavailable, procedural composition with PIL is an acceptable fallback (see src/assets/card-art/cmd-purge.webp for a precedent).
- Default card art should be 16:9 landscape WebP under src/assets/card-art/.
- Vary the art direction/style prompt for each card instead of reusing one fixed house style across a batch.
- Import the asset in src/components/cardPresentation.ts and map it in SUPPORT_CARD_ART or AI_CARD_ART.
Update docs and tests.
- Update docs/game-spec.md for authoritative current rules.
- Update design/planning docs only when they would become misleading.
- Add focused vitest cases in src/game/*.test.ts for rule behavior.
- Add or adjust UI tests only if the project already has a relevant harness or the UI change is high risk.
- Check the tutorial is not broken. src/tutorial.ts scripts a fixed playthrough that depends on specific card IDs, costs, effects, and draw order. Changing a card that appears in the tutorial decks can silently soft-lock the scripted flow. Run npx vitest run src/game/tutorial.test.ts, and for changes to tutorial-deck cards walk the scripted turns on paper (or in the browser) before calling the change done.
Verify before reporting or committing.
- Run npm run check (typecheck + vitest + build). If npm is not on PATH (Codex runtime), use PATH="/Users/user/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH" npm run check.
- If assets or text layout changed substantially, inspect the browser when practical.
- Card additions and effect changes shift the balance. For anything beyond cosmetic changes, follow the verification pipeline in .agents/skills/ai-break-duel-balance-tuning/SKILL.md (league on 2+ seeds, excitement metrics, docs/balance-history.md entry).
Commit in useful units.
- Separate mechanical wording/docs-only cleanup from new card implementation when both exist.
- Include generated assets in the implementation commit.
- Keep commit messages short and concrete.

Mais deste repositório

mesmo repositório

ai-break-duel-balance-tuning

tegnike/break-duel

ai-break-duel（Break Duel）のバランス調整を、検証つきで最初から最後まで実行するワークフロー。カード効果・デッキ構成・ルール数値・CPU（AIプロファイル）の強化/弱体化/調整、勝率やゲームバランスの検証、リーグ戦シミュレーション、盛り上がり（試合展開）の分析、バランス変更の採用判断と記録を頼まれたら必ずこのスキルを使うこと。「〜が強すぎる/弱すぎる」「ナーフして」「勝率を調べて」「バランスを見て」「デッキを調整して」「CPUを強くして」のような曖昧な依頼でも、ai-break-duel リポジトリでの作業ならこのスキルの対象。

2026-07-107

ai-break-duel-release

tegnike/break-duel

ai-break-duel（Break Duel）リポジトリでバージョンタグ付けとGitHubリリース作成を最初から最後まで実行するワークフロー。「リリースして」「タグを切って」「vX.Y.Z にして」「リリースノートを書いて」「バージョンを上げて」のような依頼が来たら必ずこのスキルを使うこと。タグだけ・ノートだけの部分的な依頼でも、リリースに関する作業ならこのスキルの対象。

2026-07-107

ai-break-duel-cpu-improvement

tegnike/break-duel

Break Duel の CPU（challenger / beginner）を改善・強化・修正するための専用ワークフロー。「CPUを強くして」「最強CPUを更新して」「CPUの悪手を直して」「beginnerの難易度を調整して」「fair-genの次世代を作って」「ビーム/評価関数/カウンティングを改善して」のような依頼が来たら必ずこのスキルを使うこと。カード・デッキ・ルール側の変更が主目的なら ai-break-duel-balance-tuning を使う（CPU改善の副作用でゲーム側の修正が必要になった場合もそちらに切り替える）。

2026-07-097

ai-break-duel-balance-regression

tegnike/break-duel

Run and interpret AI Break Duel preset-deck and biased-cost stress-deck balance regression checks. Use when you need to test existing deck round-robin balance, first-player win rate, one-sided game rate, resource-exhaustion pressure, or whether power-band stress decks such as p1, p2, p3 cap, p4 cap, p1-2, p2-3, or p3-4 cap outperform the existing six decks after card, rule, AI, or action-cost changes in the ai-break-duel repository.

2026-07-097

develop-pr-coderabbit

tegnike/break-duel

Use when creating or opening a GitHub pull request for a local repository where the PR should target develop, be ready for review, include a useful main PR body, and be checked for CodeRabbit feedback after creation.

2026-07-077

name	ai-break-duel-card-addition
description	Add or modify AI Break Duel cards end-to-end across the React/TypeScript game, headless simulation, decks, UI text, generated card art, documentation, tests, and commits. Use when the user asks to add a summon, command, relic, card effect, deck entry, card wording change, card image, or card-balance rule in the ai-break-duel repository.

AI Break Duel Card Addition

Workflow

Start from repository truth, not memory.
- Read docs/game-spec.md for current rules and naming conventions.
- Read references/file-map.md for the files that must stay synchronized.
- Inspect current code around similar card effects before editing.
Model the card once in the single TypeScript implementation.
- Add TypeScript effect unions, card pool entries, deck entries, rule helpers, action resolution, AI behavior, UI selection flow, and card text.
- The browser game and the headless simulation CLI (src/sim/) share the same engine, so one change covers both.
- Register every new or changed card effect in src/game/cardEffectCoverage.test.ts. The unit suite fails by design when an effect is unregistered, so skipping this breaks npm run check.
- Respect the deck construction rules when touching deck entries: 25 cards per deck, at most 2 copies per card name, and at most 5 summons of power 3 or higher.
Treat visible card text as player-facing rules text.
- Do not include internal implementation caps such as "maximum 3" on the card unless the user explicitly wants it on-card.
- Put internal details in docs/game-spec.md detailed rule sections when useful.
- Write draw text as 山札からカードをN枚引く.
- Avoid ただし; split drawbacks into separate short sentences, e.g. 消耗で出る。手札防御に使えない。
- Opponent draw logs must not reveal opponent card names.
Add generated art for every new card unless the user explicitly opts out.
- Under Codex: use the imagegen skill directly.
- Under Claude Code: imagegen cannot be executed directly. Delegate the generation to Codex CLI via the codex:rescue skill (or the codex:codex-rescue subagent), passing a self-contained task such as: imagegen スキルで「<カード名>」のカードアートを生成し、1600x900 (16:9) の WebP として src/assets/card-art/<card-id>.webp に保存して。アート方向性: <雰囲気・モチーフの指示> After the run, verify the file exists and is 16:9 (e.g. sips -g pixelWidth -g pixelHeight <file>) before registering it.
- Only if Codex is unavailable, procedural composition with PIL is an acceptable fallback (see src/assets/card-art/cmd-purge.webp for a precedent).
- Default card art should be 16:9 landscape WebP under src/assets/card-art/.
- Vary the art direction/style prompt for each card instead of reusing one fixed house style across a batch.
- Import the asset in src/components/cardPresentation.ts and map it in SUPPORT_CARD_ART or AI_CARD_ART.
Update docs and tests.
- Update docs/game-spec.md for authoritative current rules.
- Update design/planning docs only when they would become misleading.
- Add focused vitest cases in src/game/*.test.ts for rule behavior.
- Add or adjust UI tests only if the project already has a relevant harness or the UI change is high risk.
- Check the tutorial is not broken. src/tutorial.ts scripts a fixed playthrough that depends on specific card IDs, costs, effects, and draw order. Changing a card that appears in the tutorial decks can silently soft-lock the scripted flow. Run npx vitest run src/game/tutorial.test.ts, and for changes to tutorial-deck cards walk the scripted turns on paper (or in the browser) before calling the change done.
Verify before reporting or committing.
- Run npm run check (typecheck + vitest + build). If npm is not on PATH (Codex runtime), use PATH="/Users/user/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH" npm run check.
- If assets or text layout changed substantially, inspect the browser when practical.
- Card additions and effect changes shift the balance. For anything beyond cosmetic changes, follow the verification pipeline in .agents/skills/ai-break-duel-balance-tuning/SKILL.md (league on 2+ seeds, excitement metrics, docs/balance-history.md entry).
Commit in useful units.
- Separate mechanical wording/docs-only cleanup from new card implementation when both exist.
- Include generated assets in the implementation commit.
- Keep commit messages short and concrete.