valkor-ai/loom

valkor-ai/loom

Skill Claude CodeCodex

Use when the user invokes /loom deploy or /loom-deploy to prepare, run, inspect, validate, stop, bootstrap, or repair deployment through Loom MCP.

valkor-ai/loom

Skill Claude CodeCodex

Use when the user invokes /loom to route software delivery, knowledge, or deploy work through the Loom MCP server.

valkor-ai/loom

Skill Claude CodeCodex

Build, test, debug, and visually verify Godot projects through Loom. Use this skill for Godot project structure, GDScript or C# API questions, headless checks, input maps, runtime inspection through godot-mcp, gameplay tests, screenshots, and handoff evidence.

valkor-ai/loom

Skill Claude CodeCodex

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…

valkor-ai/loom

Skill Claude CodeCodex

Run gdUnit4 unit tests and parse results into structured output. Use this skill after writing or modifying code to verify correctness via unit tests, when diagnosing test failures, or when writing new test files. Triggers: "run tests", "test fails", "write a test", any gdUnit4/unit test mention. Supports both GDScript…

valkor-ai/loom

Skill Claude CodeCodex

Look up Godot engine class APIs — methods, properties, signals, enums. Use when you need to find which class to use or look up specific API details. Supports version-specific docs — reads the correct API for the project's Godot version.

valkor-ai/loom

Skill Claude CodeCodex

Write and run E2E (end-to-end) game tests using the godot-e2e framework. Python controls a live Godot game over TCP — Locator-based semantic queries, expect() auto-retry assertions, and engine log capture make failures self-diagnosing. Use this skill whenever you need to: Test actual gameplay: player movement…

valkor-ai/loom

Skill Claude CodeCodex

Compile-check a Godot project using headless mode. Use after writing or modifying any GDScript or C# code to verify it compiles. Triggers: after code changes, before running tests, when build errors need diagnosis. Also use this when the user says "check if it compiles", "build check", "does this parse", or after any…

valkor-ai/loom

Skill Claude CodeCodex

Manage Godot input action mappings in project.godot. Use when adding input actions, changing key bindings, setting up controls for a new genre, or validating that all referenced actions exist. Use it while implementing mechanics or changing the project's controls.

valkor-ai/loom

Skill Claude CodeCodex

Runtime debugging and live project inspection via godot-mcp. Use when headless tools cannot diagnose the problem: code compiles but runtime behavior is wrong, tests pass but the game does not work as expected, or you need to inspect live state (node tree, console output, rendering). Escalation trigger: a task has…

valkor-ai/loom

Skill Claude CodeCodex

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.

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot Animation implementation for known pitfalls. Triggers AFTER implementation, when code involves AnimationPlayer, AnimationTree, AnimatedSprite2D, SpriteFrames, AnimationNodeStateMachine, BlendSpace, OneShot, callbackmodeprocess, or animation playback control (play/travel/start). Do NOT use this skill for…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot Audio implementation for known pitfalls. Triggers AFTER implementation, when code involves AudioStreamPlayer, AudioStreamPlayer2D, AudioStreamPlayer3D, AudioServer, AudioBus, AudioEffect, AudioStream, or .finished signal on audio players. Do NOT use this skill for planning or teaching — only for…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot navigation implementation for known pitfalls. Triggers AFTER implementation, when code involves NavigationAgent2D, NavigationAgent3D, NavigationRegion2D, NavigationRegion3D, NavigationLink2D, NavigationLink3D, NavigationObstacle2D, NavigationObstacle3D, targetposition, TargetPosition, avoidanceenabled…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot Particles implementation for known pitfalls. Triggers AFTER implementation, when code involves GPUParticles2D, GPUParticles3D, CPUParticles2D, CPUParticles3D, ParticleProcessMaterial, trailenabled, sub-emitters, GPUParticlesCollision, or particle amount/emission control. Do NOT use this skill for…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot physics implementation for known pitfalls. Triggers AFTER implementation, when code involves CollisionObject2D, RigidBody2D, CharacterBody2D, Area2D, collision layers, or physics callbacks. Do NOT use this skill for planning or teaching — only for post-implementation review.

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot Shader/Material implementation for known pitfalls. Triggers AFTER implementation, when code involves ShaderMaterial, setshaderparameter, .gdshader, VisualShader, hintscreentexture, BackBufferCopy, instance uniform, or uniform declarations. Do NOT use this skill for planning or teaching — only for…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot TileMap implementation for known pitfalls. Triggers AFTER implementation, when code involves TileMapLayer, TileSet, TileSetAtlasSource, TileSetScenesCollectionSource, terrain painting, setcell, erasecell, getcelltiledata, collision polygons on tiles, or NavigationRegion2D with tile-based navigation. Do…

valkor-ai/loom

Skill Claude CodeCodex

Reviews Godot UI/Control implementation for known pitfalls. Triggers AFTER implementation, when code involves Control, Container, HBoxContainer, VBoxContainer, GridContainer, MarginContainer, ScrollContainer, PanelContainer, Button, Label, LineEdit, TextEdit, OptionButton, TabContainer, CanvasLayer, Theme, StyleBox…

valkor-ai/loom

Skill Claude CodeCodex

Capture gameplay screenshots using godot-e2e for visual verification. Use when you need to: take a screenshot of the running game, capture multiple screenshots during an E2E scenario, generate reference.png, visually verify game state, or provide screenshots for VQA analysis. Triggers: "screenshot", "capture…

valkor-ai/loom

Skill Claude CodeCodex

Inspect Godot screenshots or short frame sequences for acceptance issues. Use after capturing a scene, when checking camera framing, missing assets, UI overlap, collision visualization, animation, or a black/empty viewport.