Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From lumina
Create or prepare a Unity project for Lumina — folder structure, .gitignore, Git LFS for binary assets, and the unity-mcp bridge package so the engine MCP can connect. Use before building anything in Unity.
npx claudepluginhub tapascodespace/claude-plugin --plugin luminaHow this skill is triggered — by the user, by Claude, or both
Slash command
/lumina:scaffold-unityThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Prepare a Unity project so Lumina can drive it. Unity projects must be created by the Unity
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
Prepare a Unity project so Lumina can drive it. Unity projects must be created by the Unity Editor/Hub itself (the binary layout isn't ours to fabricate), so this skill verifies, wires, and standardizes rather than inventing a project from nothing.
Project path (default = current directory): $ARGUMENTS
Locate or create the project.
ProjectSettings/ProjectVersion.txt and an
Assets/ folder (use Glob).Unity.exe/unity CLI is available,
create it headlessly:
Unity -batchmode -quit -createProject "<path>" (then confirm the version).ProjectSettings/ProjectVersion.txt — later skills
and the engine MCP need it (version drift is a known risk).Standardize folders. Ensure these exist under Assets/:
Scripts/, Models/, Textures/, Audio/, Prefabs/, Scenes/, Materials/.
Create any missing ones with Write (an empty .gitkeep is fine).
Install version control hygiene. Copy the bundled templates into the project root if absent:
.gitignore ← ${CLAUDE_PLUGIN_ROOT}/templates/unity/gitignore.txt.gitattributes (Git LFS for *.glb *.fbx *.png *.wav *.mp3 *.tga *.psd)
← ${CLAUDE_PLUGIN_ROOT}/templates/unity/gitattributes.txt
Run git lfs install if git-lfs is present; warn (don't fail) if it isn't.Wire the unity-mcp bridge. The engine MCP (CoplayDev/unity-mcp) needs its companion Unity
package installed in the project so the Editor exposes the control endpoint. Add it via
Packages/manifest.json (git URL) or the package's documented install, then tell the user to
open the project in the Unity Editor — the MCP only connects while the Editor is running.
Verify the bridge. Once the Editor is open, confirm mcp__unity responds (e.g. a ping /
list-scenes call). If it doesn't, point the user at the doctor output from the SessionStart hook.
Report: project path, detected Unity version, folders ensured, VCS files added, and whether the engine MCP connected.