메뉴
Prepare a BrainRot repository work session on a new task branch created from the latest remote main branch. Use when starting a new task, initializing a fresh coding session, or when the user asks to create a branch before implementation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Inspect, triage, implement, test, and reply to unresolved BrainRot pull request review comments while preserving exact model ownership for game files. Use for human, Copilot, or automated PR feedback and requested changes.
Prepare and publish a compliant BrainRot pull request by checking scope, metadata, documentation, tests, commit conventions, branch safety, push state, and PR content. Use when the user asks to commit, push, publish, open, or create a pull request for completed work.
Create, improve, or fix BrainRot game implementations while enforcing exact AI model ownership, standalone-file architecture, quality requirements, desktop-first gameplay, metadata maintenance, and documentation updates. Use for any change under public/games or any new game/version request.
Build, substantially revise, or visually review BrainRot Three.js games. Use for any game implementation that imports Three.js or creates a THREE.WebGLRenderer, including art direction, authored 3D forms, local GLB/image assets, rendering budgets, test hooks, diagnostics, and active-play visual verification.
Validate BrainRot repository changes with process-safe, change-scoped local checks while leaving the complete lint, build, and Playwright gate to required pull request CI. Use after implementation, before committing or opening a PR, or when diagnosing test and build failures.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
| name | start-session |
| description | Prepare a BrainRot repository work session on a new task branch created from the latest remote main branch. Use when starting a new task, initializing a fresh coding session, or when the user asks to create a branch before implementation. |
This workflow is mandatory before every task that may modify repository files, create commits, or push changes. Create the task branch before changing files. Never commit or push task work directly to main or another default branch.
Use <type>/<task-slug> with a short lowercase hyphenated slug:
feat/ for new behaviorfix/ for bug fixesdocs/ for documentation-only workchore/ for tooling or repository maintenancerefactor/ for behavior-preserving restructuringtest/ for test-only changesgit status --short --branch and git status --porcelain.origin remote and origin/main are expected for this repository.git fetch origin main. If it fails, stop; do not claim a branch is based on latest main or fall back to stale local state.origin. If it already exists, stop and request a different name.git switch --create <branch> origin/main.<branch> and that HEAD equals the fetched origin/main commit before implementation begins.Do not run this workflow when the user explicitly asks to continue an existing branch.