القائمة
Follow CampusOS branching and PR process. Use when starting new work, creating pull requests, reviewing code, merging to main, or resolving merge conflicts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build React components in Next.js using CampusOS patterns. Use when implementing UI components, working with the App Router, styling with Tailwind CSS v4, or managing forms with react-hook-form and Zod.
Comprehensive frontend development hub — UI/UX design, React/Next.js patterns, Tailwind CSS v4, shadcn/ui components, Three.js 3D graphics, creative web experiences, data visualization, diagramming, Figma integration, accessibility, game development, scroll animations, and design systems. Use for ANY frontend task: building components, designing interfaces, styling, theming, animations, charts, responsive layouts, mobile design, or implementing design patterns.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.
Generate PR titles and descriptions from commit history. Use when the user asks to generate a PR description, wants help writing a pull request, provides commit titles/messages, or says 'PR', 'pull request', 'PR description', or similar.
| name | git-workflow |
| description | Follow CampusOS branching and PR process. Use when starting new work, creating pull requests, reviewing code, merging to main, or resolving merge conflicts. |
<type>/<issue>-<description>
git checkout -b feature/123-enrollment-api
git checkout -b fix/456-login-crash
git checkout -b chore/789-update-deps
# Types: feature, fix, chore, docs, test, perf, refactor
Conventional Commits: <type>(<scope>): <subject>
git commit -m "feat(api): add vendor assignment endpoint"
git commit -m "fix(auth): handle expired token gracefully"
git commit -m "docs: update API standards guide"
Types: feat, fix, chore, docs, refactor, perf, test
git fetch origin
git rebase origin/main
# If conflicts: edit files → git add . → git rebase --continue
git push origin feature/123-task
gh pr create --title "feat: add enrollment" --body "Closes #123"
# PR Checklist:
# - [ ] pnpm lint passes
# - [ ] pnpm -C apps/<module> test -- --run passes
# - [ ] pnpm build succeeds
# - [ ] Docs updated if needed
Squash merge for clean history:
gh pr merge --squash 123
# Auto-deletes feature branch
git checkout -b feature/<issue>-<desc> # Create branch
git commit -m "type: message" # Commit
git push origin feature/<issue>-<desc> # Push
git fetch && git rebase origin/main # Update
| Issue | Solution |
|---|---|
| Merge conflict | Edit conflicted files, git add ., git rebase --continue |
| Committed to main | git revert <hash> — never force-push main |
| Need to reset | git reset --hard origin/main (loses local changes) |