Skip to content

First meeting onboarding kit

Goal for the first team meeting: everyone leaves with repo access, the correct local toolchain, a working editor launch path, and one small assignment. Do not make standalone wiki/toolkit migration the meeting goal.

Pre-meeting install checklist

Ask everyone to start these before the meeting because UE and Visual Studio installs can take a long time.

  • GitHub access to Rephrased-Games/Rephrased-Game (the current daily repo)
  • Epic Games Launcher
  • Unreal Engine 5.8
  • Visual Studio 2026 Community, stable channel
  • Repo-root .vsconfig imported into Visual Studio Installer
  • GitHub Desktop or Git CLI
  • Optional for AI workflow: Cursor, Claude Code, Codex, or another MCP-capable coding agent
  • Optional for MCP: uv

60-90 minute agenda

0-10 min — Project and org orientation

  • Rephrased now lives under the Rephrased-Games organization.
  • Rephrased-Games/Rephrased-Game is the main source of truth for code, wiki, and MCP.
  • The old demo repo is history/reference, not the daily working repo.
  • Standalone Rephrased-Wiki and Rephrased-agent-toolkit are reference copies synced outward from the main repo.
  • The rule is branch -> PR -> review -> merge. No direct main edits.

10-25 min — Repo access and clone

  • Confirm each person can see the private repo.
  • Clone the repo to a simple writable Windows path.
  • Confirm the root contains Rephrased.uproject, Content/, Source/, and Config/.

25-45 min — UE/VS environment check

  • Confirm UE 5.8 is installed.
  • Confirm Visual Studio 2026 Community is installed from the stable channel.
  • Import the repo .vsconfig.
  • Explain: designers/artists do not open Visual Studio day to day; it is installed so Unreal can rebuild when C++ changes.

45-60 min — Build/open check

  • Run [OpenAfterPull]Build_Project.bat -check.
  • Expected checks: UE 5.8 found, VS 2026 C++ found, Windows SDK 10.0.22621 found.
  • Run [OpenAfterPull]Build_Project.bat normally.
  • Open Rune Showcase and press Play.
  • Record blockers by person instead of trying random fixes.

60-75 min — Rephrased MCP setup

Rephrased MCP is useful, but it should not block the first meeting. If it blocks, skip it and continue with repo/build onboarding.

  • Confirm the repo ships .cursor/mcp.json and .claude/mcp.json.
  • Install/run the local MCP package from tools/rephrased-mcp.
  • Run /onboard with the team review key from the lead.
  • Confirm the agent can see these tools: onboarding, convention_check, request_review, wiki_query, devlog.
  • Never commit the review key or paste it into shared chat.

75-90 min — First assignments

Assign tiny, low-risk tasks that prove each person can use the workflow.

  • Engineers: create a branch, build/open, inspect one small C++ area, make no main edits.
  • Designers: open Rune Showcase, inspect one level or DataAsset, write one question/blocker.
  • Artists: open content folders, inspect materials/assets, avoid renaming shared assets without lead approval.
  • Producer/lead: track who is blocked, what install step failed, and who needs follow-up.

Copy-paste team message

Tomorrow setup goal: get everyone into the same Rephrased repo and able to open the project.

Please install before meeting if possible:

  1. Epic Games Launcher + Unreal Engine 5.8
  2. Visual Studio 2026 Community, stable channel
  3. GitHub Desktop or Git CLI
  4. Access to Rephrased-Games/Rephrased-Game

After cloning, import the repo .vsconfig into Visual Studio Installer. You do not need to open Visual Studio day to day; it is installed so Unreal has the compiler toolchain when the build bat needs it.

Daily workflow after setup: pull latest, then double-click [OpenAfterPull]Build_Project.bat.

If the bat fails, do not randomly edit project files. Screenshot/copy the error and tell Gabriel/lead.

MCP talking points

  • Rephrased MCP is the team AI toolkit, not a replacement for Unreal.
  • It gives coding agents project-specific tools: onboarding, convention check, team review request, wiki search, and devlog.
  • The review key is private. It should be shared by a lead directly, never committed.
  • MCP setup is second priority after repo access and project launch.

Main risks tomorrow

  • UE 5.8 install is large and slow.
  • Visual Studio install can take a long time.
  • Some members may not yet have GitHub org access.
  • GitHub Education benefits/branch protection may still be pending.
  • Cloudflare wiki deployment may still point at the old demo repo until repointed to the org repo.
  • MCP setup may vary by IDE; do not let MCP block people from opening the project.

Success criteria

By the end of the meeting:

  • Everyone has repo access or a named access blocker.
  • Most members have UE 5.8 + VS 2026 installed or installing.
  • At least a few machines run the bat successfully.
  • At least one engineer verifies Rephrased MCP sees the five expected tools.
  • Everyone knows the daily workflow: pull, run the bat, work on a branch, ask before main-impact changes.

Change history

  • 2026-08-26 — Gabriel Li — Added Cloudflare live wiki source risk after org migration.
  • 2026-08-26 — Gabriel Li — Updated first-meeting kit with main-repo source-of-truth policy, standalone reference repos, VS-once workflow, and MCP setup order.
  • 2026-08-26 — Gabriel Li — Initial first-meeting kit for org repo onboarding and Rephrased MCP setup.