Skip to main content
Run any Skill in Manus
with one click
GitHub repository

godot-sight

godot-sight contains 3 collected skills from Lanc3, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
3
Stars
3
updated
2026-05-28
Forks
0
Occupation coverage
2 occupation categories · 100% classified
repository explorer

Skills in this repository

godot-sight
software-developers

Drive the Godot Sight MCP server as the agent's eyes and hands during Godot 4 development. Use proactively whenever code, scenes, shaders, UI, or game logic are being authored, refactored, debugged, or reviewed — not only when the user explicitly asks. Triggers: writing or editing GDScript, modifying .tscn scenes, adjusting shaders, building UI/menus, implementing a story or feature, fixing a visual bug, fixing a script or logic bug, suspected regression, before marking work done, before code review, generating test evidence for a story, reproducing a user-reported bug, or any phrase like 'this looks wrong', 'it crashes', 'doesn't work', 'broken', 'verify', 'check the game', 'show me what happens', 'screenshot', 'test the menu', 'does this run', 'did I break anything'. Wraps the 12 MCP tools (doctor, project_info, verify_project, run_scene, stop, get_logs, get_runtime_state, get_scene_tree, screenshot, input_action, run_playtest, latest_report) into the development inner loop so Cursor verifies before editing

2026-05-28
player-writer
software-quality-assurance-analysts-and-testers

Guides users through Playwrite Capture, Replay, and optional Promotion for Godot Sight. Use when the user invokes /player-writer or asks to record gameplay, create a Playwrite, replay a recorded path, or promote a Playwrite into a Wrapper Playtest.

2026-05-28
godot-master
software-developers

Master Godot 4 development skill — the agent's brain for any Godot work in this project. Use proactively whenever Godot code, scenes, shaders, resources, or settings are being authored, refactored, debugged, reviewed, or planned — not only when the user explicitly asks. Triggers: writing or editing .gd / GDScript, modifying .tscn / .scn scenes, editing .gdshader / .gdshaderinc shaders, editing .tres / .res resources, changing project.godot or autoload list, working with input map / themes / .import files, suggesting any Godot API or class, designing a Godot system, picking GDScript vs C# vs GDExtension, optimizing a hot path, profiling, choosing physics / rendering / input / UI patterns, hooking up signals, building autoloads, anything that mentions Godot, GDScript, Forward+ / Mobile / Compatibility renderer, Jolt, AnimationMixer, NavigationServer, MultiplayerSynchronizer, Control nodes, or any Godot subsystem. Routes the agent to the right engine reference doc, the right specialist agent brief, the right pat

2026-05-25