navigation-topology-decision-contract

Select game navigation topologies based on movement semantics and determinism requirements.

2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/DubDev720/gdref --skill navigation-topology-decision-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: navigation-topology-decision-contract
Source: https://github.com/DubDev720/gdref/tree/main/godot-skills/godot-tertiary/navigation-topology-decision-contract
Command: npx skills add https://github.com/DubDev720/gdref --skill navigation-topology-decision-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you select the most appropriate navigation topology (e.g., grid, graph, navmesh) for your game or application, ensuring optimal performance and correctness based on movement semantics and determinism needs.

Core Features & Use Cases

  • Topology Selection: Guides the decision-making process for choosing between different pathfinding structures.
  • Policy Decoupling: Ensures path cost and traversal logic are separate from the topology representation.
  • Use Case: When starting a new project that requires complex character movement, use this Skill to determine whether a square grid, hex grid, or navigation mesh is the best fit for the game's movement rules and desired level of detail.

Quick Start

Use the navigation-topology-decision-contract skill to select the best navigation topology for a discrete-rule based movement system.

Frequently Asked Questions about navigation-topology-decision-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right pathfinding topology for my game's movement rules?

Use a navigation topology decision contract to evaluate movement semantics, determinism requirements, and cost policies. It guides selecting between square grids, hex grids, generic graphs, or navmeshes based on your specific movement rules and level of detail.

What is the difference between discrete-rule and continuous free-form navigation?

Discrete-rule navigation restricts movement to structured topology representations like grids or graphs, while free-form continuous navigation allows fluid movement across navmeshes. This decision contract evaluates your game scenarios to determine which approach fits your needs.

When should I use a navmesh instead of a square grid for pathfinding?

Use a navmesh instead of a square grid when your game requires free-form continuous navigation rather than discrete-rule based movement. The decision contract evaluates your movement semantics and determinism needs to recommend the correct architecture.

Does path cost logic need to be coupled to the navigation topology representation?

Path cost logic does not need to be coupled to the navigation topology. This decision contract ensures policy decoupling, keeping path cost and traversal logic separate from the underlying topology representation for better architectural flexibility.

Can I use this navigation topology contract for complex character movement systems?

You can use this navigation topology contract for complex character movement systems. It evaluates determinism requirements and cost policies to determine whether a square grid, hex grid, generic graph, or navmesh best fits your project's desired level of detail.