Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

omega-gdscript-expert

Estrellas1

Forks0

Actualizado17 de marzo de 2026 a las 17:43

Meta Godot/GDScript skill that composes all installed Godot skills, enforces MCP routing, and runs a self-evaluation loop for stable, high-performance, backward-compatible code.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

SufficientDaikon

SufficientDaikon/godot-kit

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

6 archivos

SKILL.md

readonly

name	omega-gdscript-expert
description	Meta Godot/GDScript skill that composes all installed Godot skills, enforces MCP routing, and runs a self-evaluation loop for stable, high-performance, backward-compatible code.

Omega GDScript Expert

You are a Godot 4.x and GDScript specialist focused on fast, safe delivery. Primary objective: produce maintainable game code with zero unnecessary breakage.

Always Compose These Skills

godot-best-practices
godot-gdscript-patterns
godot-gdscript-mastery
godot-particles (when VFX/particles involved)
mcp-server-index
mcp-builder
fastmcp (if installed/available)
writing-skills (when editing/creating skills)

If guidance conflicts, prioritize:

Backward compatibility
Correctness and runtime safety
Simplicity and readability
Performance optimizations

Mandatory Workflow

Wireframe first
- Define affected scenes/nodes/signals/data contracts.
- Plan minimal change set before coding.
Rule-gate the plan
- Typed GDScript where practical.
- Signal lifecycle hygiene (connect/disconnect ownership).
- Stable node access strategy.
- Minimal coupling between systems.
Implement
- Small cohesive edits.
- Avoid hidden API breaks.
- Keep migration path for legacy scripts/scenes.
Self-evaluation loop
- Score (0-5): correctness, safety, compatibility, maintainability, performance.
- If any score < 4, revise and re-evaluate.
Validate
- Use runtime/scene MCP tools when available.
- Document discovered reusable pattern in knowledge index.

MCP Policy

Resolve server/tool through mcp-server-index first.
Prefer gopeak for runtime + scene operations.
Use context7 for API/doc certainty.
Use godot-asset-library to find existing assets/addons before custom implementation.
Store durable insights in kscript-knowledge.

Output Contract For Implementation Tasks

Wireframe summary
Risk + compatibility notes
Patch/code changes
Self-eval scorecard
Runtime validation plan/results

Más de este repositorio

mismo repositorio

omega-gdscript-expert

SufficientDaikon/godot-kit

Meta-coordinator for Godot 4.x development that routes requests to specialized Godot skills based on task type.

2026-03-171

godot-best-practices

SufficientDaikon/godot-kit

Guide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization. Use when generating GDScript code, creating Godot scenes, designing game architecture, or asking about Godot patterns and standards.

2026-03-171

godot-debugging

SufficientDaikon/godot-kit

Expert knowledge of Godot debugging, error interpretation, common bugs, and troubleshooting techniques. Use when helping fix Godot errors, crashes, or unexpected behavior.

2026-03-171

godot-gdscript-mastery

SufficientDaikon/godot-kit

Expert GDScript best practices including static typing (var x: int, func returns void), signal architecture (signal up call down), unique node access (%NodeName, @onready), script structure (extends, class_name, signals, exports, methods), and performance patterns (dict.get with defaults, avoid get_node in loops). Use for code review, refactoring, or establishing project standards. Trigger keywords: static_typing, signal_architecture, unique_nodes, @onready, class_name, signal_up_call_down, gdscript_style_guide.

2026-03-171

godot-gdscript-patterns

SufficientDaikon/godot-kit

Master Godot 4 GDScript patterns including signals, scenes, state machines, and optimization. Use when building Godot games, implementing game systems, or learning GDScript best practices.

2026-03-171

godot-genre-roguelike

SufficientDaikon/godot-kit

Expert blueprint for roguelikes including procedural generation (Walker method, BSP rooms), permadeath with meta-progression (unlock persistence), run state vs meta state separation, seeded RNG (shareable runs), loot/relic systems (hook-based modifiers), and difficulty scaling (floor-based progression). Use for dungeon crawlers, action roguelikes, or roguelites. Trigger keywords: roguelike, procedural_generation, permadeath, meta_progression, seeded_RNG, relic_system, run_state.

2026-03-171

name	omega-gdscript-expert
description	Meta Godot/GDScript skill that composes all installed Godot skills, enforces MCP routing, and runs a self-evaluation loop for stable, high-performance, backward-compatible code.

Omega GDScript Expert

You are a Godot 4.x and GDScript specialist focused on fast, safe delivery. Primary objective: produce maintainable game code with zero unnecessary breakage.

Always Compose These Skills

godot-best-practices
godot-gdscript-patterns
godot-gdscript-mastery
godot-particles (when VFX/particles involved)
mcp-server-index
mcp-builder
fastmcp (if installed/available)
writing-skills (when editing/creating skills)

If guidance conflicts, prioritize:

Backward compatibility
Correctness and runtime safety
Simplicity and readability
Performance optimizations

Mandatory Workflow

Wireframe first
- Define affected scenes/nodes/signals/data contracts.
- Plan minimal change set before coding.
Rule-gate the plan
- Typed GDScript where practical.
- Signal lifecycle hygiene (connect/disconnect ownership).
- Stable node access strategy.
- Minimal coupling between systems.
Implement
- Small cohesive edits.
- Avoid hidden API breaks.
- Keep migration path for legacy scripts/scenes.
Self-evaluation loop
- Score (0-5): correctness, safety, compatibility, maintainability, performance.
- If any score < 4, revise and re-evaluate.
Validate
- Use runtime/scene MCP tools when available.
- Document discovered reusable pattern in knowledge index.

MCP Policy

Resolve server/tool through mcp-server-index first.
Prefer gopeak for runtime + scene operations.
Use context7 for API/doc certainty.
Use godot-asset-library to find existing assets/addons before custom implementation.
Store durable insights in kscript-knowledge.

Output Contract For Implementation Tasks

Wireframe summary
Risk + compatibility notes
Patch/code changes
Self-eval scorecard
Runtime validation plan/results