القائمة
Esposter git workflow conventions — commit message format, safety rules, and branch hygiene. Apply when running git operations or advising on source control workflows.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Esposter TypeScript conventions — banned patterns (Omit over Except, forEach, parameter properties, the void operator), as unknown as treated like any (model the type instead; the rare mock and library-seam exceptions), declare over ! on class fields, arrow functions and overloads, neverthrow promise style, InvalidOperationError, guard clauses, exhaustive switch guards, enum naming/refs/values arrays, discriminant-keyed maps for polymorphic dispatch, and the string "" sentinel with the null-vs-undefined rules. Apply when writing any TypeScript in this project.
Esposter vue-phaserjs integration patterns — component inventory, markRaw for Phaser objects in Pinia stores, configuration Pick pattern, all-configuration-keys-present-at-setup. Apply when writing Phaser game objects, stores, or vue-phaserjs components.
Esposter pnpm script reference — packages/app scripts (lint, typecheck, test, format, dev, build) and the root scripts (test, coverage, depcruise:graph, outdated:dependencies). Apply whenever running or recommending package scripts.
Esposter Vitest testing conventions — describe with function refs, canonical test values, takeOne for unsafe index access, destructuring from stores/composables, mock session patterns (getMockSession/mockSessionOnce/replayMockSession), mock cleanup by creation style, toThrowErrorMatchingInlineSnapshot as the only error assertion, the node-default test environment (nuxt only via per-file directive; stub window for client/server paths), bundle-size snapshot tests, and type-level conventions for .test-d.ts files. Apply when writing .test.ts or .test-d.ts files.
Esposter responsive/mobile UI conventions — command bars collapse into a single overflow dropdown of icon+text list items on narrow viewports, which controls never collapse, and when flex-wrap is the allowed exception. Apply when adding or editing any toolbar, action row, or button group that must work on mobile.
Esposter Vue 3 component architecture — the shared Styled/App shell primitives, same level of abstraction, the wrapper + pure-child pattern for async data, generic SFCs, per-variant type correctness, is-prefixed boolean props typed as the non-default literal, present-tense emit names, component folder naming and Nuxt auto-import name collapse, defineSlots and conditional slot forwarding, slot extraction, array + v-for over hardcoded list items, shared list-item shells with action slots, permission-filtered action items, one affordance per action, singleton dialogs over per-item dialogs, page decomposition, and maximal component granularity. Apply when designing, decomposing, naming, or refactoring Vue components.
| name | git |
| description | Esposter git workflow conventions — commit message format, safety rules, and branch hygiene. Apply when running git operations or advising on source control workflows. |
Conventional-commits format and the type list are in ~/.claude/rules/git-workflow.md.
Commit attribution is enabled. ~/.claude/settings.json sets no includeCoAuthoredBy key, so it defaults on — recent commits carry the Co-Authored-By trailer. Expect it; don't strip it. (The global rules file claims attribution is disabled — it is not.)
The Bash tool is POSIX sh, NOT PowerShell. Never use PowerShell here-string syntax (@'...'@) in the Bash tool — it is taken literally and leaves stray @ lines in the commit message. Pick the form matching the tool:
Bash tool → heredoc piped to -F -:
git commit -F - <<'EOF'
fix: short subject
Body line.
EOF
PowerShell tool → single-quoted here-string with @' / '@ at column 0:
git commit -m @'
fix: short subject
Body line.
'@
After committing, verify with git log -1 --format='%B' before pushing.
Never use git stash — a failed/forgotten pop loses in-progress changes. To inspect prior committed state, use git show HEAD:path/to/file or git diff HEAD. To set work aside, make a WIP commit.
Never push into a running CodeRabbit review — if the branch has an open PR, check the review state first; pushing mid-review cancels it, burns a rate-limit slot, and loses the in-progress findings for good (CodeRabbit won't re-review commits it has already seen):
gh pr checks --json name,state,description --jq '.[] | select(.name=="CodeRabbit")'
Push only on SUCCESS; otherwise wait for it to settle. Full rationale and symptoms in the coderabbit skill.
Batch commits and push once per coherent chunk of work. Several pushes in quick succession each retrigger review, so the later ones reliably land mid-review — the exact case the rule above exists to prevent.
develop, not maindevelop; develop merges to main for releasesThe local check suite runs once, on develop, after the merge — never iteratively on the feature branch:
develop into the branch first if it has drifted (resolve conflicts there), then merge the PR into develop.develop — run the check suite (see the package-scripts skill) once, post-merge, and fix forward directly on develop.Rationale: branch-side local checks duplicate PR CI and get invalidated by the merge anyway — the merged state on develop is the only state worth verifying locally.