메뉴
Deploy the Hebrew Codenames co-pilot to its HF Space (shmulc/hebrew-codenames-copilot) by uploading changed files from hf_space/, and report the build stage. Use when asked to "deploy", "push to HF", "ship the Space", or "release the co-pilot".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | codenames-deploy |
| description | Deploy the Hebrew Codenames co-pilot to its HF Space (shmulc/hebrew-codenames-copilot) by uploading changed files from hf_space/, and report the build stage. Use when asked to "deploy", "push to HF", "ship the Space", or "release the co-pilot". |
The hf_space/ directory is the deploy bundle for the Space
shmulc/hebrew-codenames-copilot. It is not its own git repo — deployment uploads files to
the Space via huggingface_hub. Upload only the files that changed and leave the large fastText
binaries (data/cc.he.300.*, hundreds of MB) already in the Space untouched.
hf_space/ is in sync with any dev-tree change (the dev probe.py differs
structurally from hf_space/probe.py; app.py/morph.py are kept identical — apply edits to
both). Run the codenames-qa legality regression first.~/.cache/huggingface/token).# default: upload the app/engine files most changes touch
python .agents/skills/codenames-deploy/scripts/deploy.py
# or name the changed files explicitly (paths relative to hf_space/)
python .agents/skills/codenames-deploy/scripts/deploy.py probe.py app.py data/word2root.json
It uploads the given files from hf_space/ in one commit, prints the commit URL, and reports the
build stage. The stage goes RUNNING_BUILDING → RUNNING; the old build keeps serving until the
new image is up.
Once the stage is RUNNING, verify live with the codenames-qa skill:
python .agents/skills/codenames-qa/scripts/verify_live.py
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Apply vertical slice architecture to organize code by feature instead of by technical layer. Use when adding a new feature, endpoint, command, query, or use case. Use when deciding whether to create new files or edit existing ones. Use when implementing CQRS, mediator pattern, plugin architecture, event-driven patterns, or auto-discovery registration. Use when the user asks about additive architecture, feature folders, or minimizing edit surface. Also trigger when you notice yourself about to add a new method to an existing controller or service — that is the moment this skill is most needed.
Use when the user wants a hands-free loop where grabbing UI elements in the browser with React Grab feeds tasks to the agent automatically, with no copy-paste or manual handoff. Triggers: "watch react grab", "monitor my grabs", "auto-process react grab", "watch my clipboard for grabs". Not for a one-off paste of a single grab; this is the continuous, always-on loop.
Pull and summarize user feedback (👍/👎 on clues) for the Hebrew Codenames co-pilot from the private HF dataset shmulc/codenames-feedback. Use when asked to "check feedback", "any new feedback", "grab feedback", review clue thumbs-up/down, or see what users complained about.
QA the Hebrew Codenames engine — run the clue-legality regression, the clue-quality benchmark against the feedback set, and optionally verify the live HF Space. Use before committing engine changes, after tuning scoring or legality, or when asked to "run QA", "run the tests", "run the benchmark", or "check the engine still works".
Use this skill for playing, teaching, or moderating the Hebrew version of Codenames (שם-קוד). Triggers include requests to explain rules, generate clues, validate guesses, simulate games, or clarify legal/illegal actions. Especially for generating high-quality Spymaster clues that avoid opponent and assassin words.