メニュー
Issues, labels, contributor workflow, pull request process for CampusOS. Use when onboarding contributors, documenting issue labels, setting up contribution guidelines, or managing PR workflow.
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 | contribution-guide |
| description | Issues, labels, contributor workflow, pull request process for CampusOS. Use when onboarding contributors, documenting issue labels, setting up contribution guidelines, or managing PR workflow. |
type-bug, type-feature, type-documentation, type-questionpriority-critical, priority-high, priority-medium, priority-lowneeds-review, blocked, in-progress, help-wantedgood-first-issue (<2hr, self-contained), intermediate, advanced<type>/<issue>-<description> (e.g., feature/123-add-login)pnpm lint
pnpm -C apps/<module> test -- --run
pnpm build
feat:, fix:, chore:, docs:main| Level | Criteria | Privileges |
|---|---|---|
| Contributor | 1st PR | Listed in CONTRIBUTORS.md |
| Collaborator | 3+ quality PRs | Approve PRs, assign issues |
| Maintainer | Long-term | Merge, release management |
git checkout -b feature/<issue>-<desc> # Create branch
pnpm lint && pnpm test # Run checks
git commit -m "feat: description" # Conventional commit
gh pr create --fill # Create PR
See: docs/contributing/CONTRIBUTING.md, docs/contributing/CODING_GUIDELINES.md