القائمة
Add a new announcement to all 5 JSON files with auto-translation, commit, and tag. Use when adding announcements, writing update notices, or posting new content.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a selectable planner keyword end-to-end across FE, BE, and i18n with the proper in-game translation. Use when adding a plan keyword, synergy keyword, faction keyword, or a value to the planner keyword filter.
Synchronize patterns from docs/**/findings.md to CLAUDE.md and skill documentation. Use when updating specs, consolidating learnings, preventing outdated documentation, or running /findings-sync command.
Full commit workflow — pre-commit validation, branch creation, commit message writing, staging, and checkout. Use this skill whenever the user asks to commit, create a commit, write a commit message, stage changes, finalize work, or prepare code for a PR. Also triggers on phrases like "commit the change", "ready to commit", "let's commit this", "wrap this up", or any git commit-related request.
Create and manage Claude Code skills. Use when creating skills, modifying skill-rules.json, or debugging activation.
Interview simulator that tests understanding of architectural decisions. Asks "why" questions, gives hints instead of answers, probes deeper on correct responses. Supports topic-based and random code quiz modes.
| name | announcement |
| description | Add a new announcement to all 5 JSON files with auto-translation, commit, and tag. Use when adding announcements, writing update notices, or posting new content. |
Ask the user for:
kr_title)kr_body)YYYY-MM-DD if not providedYYYY-MM-DD) — optional, skip if not providedboolean) — optional, skip if not providedFormat: {date}-{NN} where NN is a zero-padded 2-digit incremental counter.
The date used in the ID depends on announcement type:
1970-01-01To determine NN:
static/data/announcements.jsonid starts with the target date prefix01"1970-01-01-01" → new permanent ID is "1970-01-01-02"Before translating, refine the raw Korean input to match the tone and style of existing announcements:
static/i18n/KR/announcements.json to learn the established style.claude/skills/announcement/terms.csv and correct any game terms to their canonical Korean forms (e.g., EGO 기프트 → E.G.O 기프트)kr_title and kr_body to match that style (sentence structure, formality, formatting)Do NOT proceed to translation until the user approves the refined Korean text.
Read the term dictionary at .claude/skills/announcement/terms.csv (if not already read in Step 3).
It contains canonical translations for:
For in-game terms like identity names, EGO names, and EGO gift names — read the subsection.
Translate kr_title and kr_body into EN, CN, JP using the dictionaries above for all game-specific terms. Use natural-sounding language for surrounding prose.
In the input, [[{category}:{name}]] marks an in-game term. Find its id or internal representation in the KR i18n files, then use that key to look up translations in EN/JP/CN.
| Category | Lookup file (static/i18n/KR/) | Key format |
|---|---|---|
id | identityNameList.json | numeric id |
ego | egoNameList.json | numeric id |
gift | egoGiftNameList.json | numeric id |
keyword | battleKeywords.json | PascalCase id |
themepack | themePack.json | numeric id |
trait | plannerKeywords.json | PascalCase id (matched on label) |
Example: [[keyword:부하]] → search battleKeywords.json for entry with "name" containing 부하 → find key ChargeLoad → look up ChargeLoad in EN/JP/CN battleKeywords.json → 부하/Load/負荷/载荷
Trait example: [[trait:엄지]] → search plannerKeywords.json for entry whose "label" is 엄지 → find key AccelBullet → look up AccelBullet in EN/JP/CN plannerKeywords.json → 엄지/The Thumb/親指/拇指. (거미집 → SojiRyoshuEntangle → The House of Spiders/蜘蛛の巣/蜘蛛巢.)
Read each file before editing. JSON must remain valid (no trailing commas).
static/data/announcements.jsonRegular announcements: Prepend a new object at index 0 (newest-first):
{
"id": "<generated-id>",
"date": "<date>"
}
Permanent announcements: Append at the end of the array. Use date 1970-01-01.
{
"id": "<generated-id>",
"date": "1970-01-01",
"permanent": true
}
Include "expiresAt": "<date>" only if provided.
Include "permanent": true only if provided.
static/i18n/KR/announcements.jsonAdd key "<id>": { "title": "<kr_title>", "body": "<kr_body>" } alongside existing entries.
static/i18n/EN/announcements.jsonAdd key "<id>": { "title": "<en_title>", "body": "<en_body>" }.
static/i18n/CN/announcements.jsonAdd key "<id>": { "title": "<cn_title>", "body": "<cn_body>" }.
static/i18n/JP/announcements.jsonAdd key "<id>": { "title": "<jp_title>", "body": "<jp_body>" }.
main):cd static
git add data/announcements.json i18n/KR/announcements.json i18n/EN/announcements.json i18n/JP/announcements.json i18n/CN/announcements.json
git commit -m "data: add <date> announcement"
dev):cd ..
git add static
git commit -m "data: add <date> announcement"
v{YY}{MM}{DD}:git tag v<YYMMDD>
Example: date 2026-04-01 → tag v260401.
If the tag already exists (multiple announcements same day), append a sequential suffix: v260401-2.
Push the static submodule first, then the supermodule dev branch, then the tag. Submodule must go first so the pointer resolves for anyone pulling.
git -C static push origin main
git push origin dev
git push origin v<YYMMDD>
List all 5 files changed, display the generated ID and tag name.