菜单
Inspect or initialize a Godot project without imposing a game architecture. Use when starting a project, checking project.godot, adding a main scene, or deciding which optional Godot addons are needed.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/valkor-ai/loom --skill project-scaffold命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when the user invokes /loom to route software delivery, knowledge, or deploy work through the Loom MCP server.
Mandatory routing skill. When the user explicitly invokes @loom, call the matching Loom MCP route before any repository work; plain delivery requests must start with loom.plan.
Lint and format GDScript files using gdtoolkit (gdlint + gdformat). Use after writing or modifying .gd files, when asked to check code style, fix lint errors, format code, or set up linting configuration. Also use when gdlint/gdformat errors appear in output and need diagnosis. Does NOT require Godot — runs as a standalone Python tool.
正在显示 SKILL.md
基于 SOC 职业分类
| name | project-scaffold |
| description | Inspect or initialize a Godot project without imposing a game architecture. Use when starting a project, checking project.godot, adding a main scene, or deciding which optional Godot addons are needed. |
Loom does not prescribe an ECS, folder layout, asset pipeline, or game genre. Keep the existing project structure when one is already present. For a new project, use the smallest structure that matches the request and record the choice in the Loom architecture or task contract.
From the directory containing project.godot, check:
test -f project.godot
rg -n '^(config/features|run/main_scene|config/name|renderer/|environment/defaults)' project.godot
find . -maxdepth 2 -type f \( -name '*.tscn' -o -name '*.gd' -o -name '*.cs' \) | sort
Read the configured main scene before creating another entry point. Reuse existing autoloads, input actions, renderer settings, and naming conventions.
Godot's Project Manager can create the project. A small code-first project can start with:
project-root/
├── project.godot
├── scenes/
│ └── main.tscn
├── scripts/
├── assets/
└── tests/ # only when tests are part of the project
For a 3D project, use a Node3D root, a Camera3D, at least one light, and a
world environment or clear background. Add collision shapes alongside bodies;
do not rely on visual meshes alone for gameplay collision.
Use the exact ConfigFile syntax already present in the project. The common sections are:
[application]
config/name="Project Name"
run/main_scene="res://scenes/main.tscn"
[display]
window/size/viewport_width=1280
window/size/viewport_height=720
[rendering]
renderer/rendering_method="gl_compatibility"
Only add [input], [autoload], physics, or renderer settings when the task
needs them. Confirm every script-referenced input action exists before handing
off the task.
Treat addons as project dependencies, not as Loom features. Check the addon's
own compatibility table and pin a version that matches the installed Godot
version. Do not copy an entire addon repository into addons/; install only
the addon directory and verify that it contains plugin.cfg where applicable.
The references/project_settings.md file contains the detailed ConfigFile and
input serialization patterns carried over from the Godot reference material.
After scaffolding or changing scenes:
GODOT_BIN="${GODOT_PATH:-godot}"
"$GODOT_BIN" --headless --path . --editor --quit
Then run the project's tests, launch the main scene, and capture evidence when the task includes runtime or visual acceptance criteria.