Persistent verification mode. Use when the user explicitly says `/test` or clearly wants exhaustive test, QA, and fix loops before signoff, especially when they want you to keep grinding while they are away. Bias Codex toward running the relevant existing test stack, browser or desktop verification, and diagnosis repeatedly until the requested surface is verified or a real blocker remains.
์ฝ๋ ๋ฆฌ๋ทฐ. ์์ ํ ๋ณ๊ฒฝ์ฌํญ์ Z.AI ๋ชจ๋ธ๋ก ๊ฒํ ํ๊ณ , Codex๊ฐ ๊ฒฐ๊ณผ๋ฅผ ๋ค์ ๊ฒ์ฆํด ์ ํจํ ์ด์๋ง ์ ๋ฆฌํ๋ค. /rr ๋๋ 'GLM ๋ฆฌ๋ทฐ' ์์ฒญ ์ ์ฌ์ฉ.
GLM-5 ์ฝ๋ ๋ฆฌ๋ทฐ. /rr์ ์์ ๋ฒ์ ์ผ๋ก ๋ ๊ฐํ ๋ชจ๋ธ๋ก ๋ณ๊ฒฝ์ฌํญ์ ๊ฒํ ํ๊ณ , Codex๊ฐ ๊ฒฐ๊ณผ๋ฅผ ๋ค์ ๊ฒ์ฆํด ์ ํจํ ์ด์๋ง ์ ๋ฆฌํ๋ค.
Local verify-commit-push wrapper for Codex. Use only when the user explicitly says `/cp` or clearly asks to finish the current work by running the relevant local checks, staging intended files explicitly, committing on the current branch, and pushing. This workflow may commit directly to `main` or `master` when that is the repo's chosen operating model.
Frontend design mode for strong visual direction, UI polish, redesigns, landing pages, and production-grade interface work, including shadcn-based surfaces. Use when the user says `/fd` or explicitly asks for better design, styling, layout, visual quality, or UX polish.
Persistent completion mode. Use when the user explicitly says `/ralph` or clearly wants you to keep iterating until the task is actually finished, repeating implement-verify-fix loops instead of stopping at partial progress.
Explicit extra-research mode. Use only when the user says `/re` or clearly asks for a research-heavy pass before coding. This skill should bias Codex toward more source-checking and justification without replacing its normal orchestration.