Rexboard Visibility And Routes
Developmentrexboard-visibility-and-routesRexboard Visibility And Routes is an Agent Skill for development published in the rexrainbow/phaser3-rex-notes repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use this skill when working with RexBoard fieldOfView, FieldOfView, board visibility, line of sight, LOS, blockers, cone mode, visible tiles, RexBoard Monopoly, board route traversal, route cost, or directional board paths. Triggers on: RexBoard fieldOfView, FieldOfView, board visibility, line of sight, LOS, RexBoard Monopoly, board route.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/rexrainbow/phaser3-rex-notes/blob/HEAD/skills/rexboard/rexboard-visibility-and-routes/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rexboard-visibility-and-routes, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
RexBoard Visibility And Routes
Use this skill for board algorithms that answer visibility and route traversal questions.
Use This First
Choose the helper:
| Need | Use |
|---|---|
| Visible tiles around a chess piece | FieldOfView.findFOV(...) |
| Can a piece see a target | FieldOfView.isInLOS(...) or LOS(...) |
| Filter visible targets | FieldOfView.LOS(targets, ...) |
| Directional route traversal | Monopoly.getPath(...) |
| Route stop/blocker rules | Monopoly.costCallback |
Required Setup
This skill assumes pieces are already registered as RexBoard chess. If not, use rexboard-board-and-chess.
References
Read these only when needed:
references/fieldofview-config.md: FOV config, callbacks, costs, blockers, LOS, and cone options.references/monopoly-config.md: route traversal config, callbacks, and sentinels.references/visibility-route-recipes.md: reduced recipes for visible tiles, LOS, target filtering, and route paths.
Core Rules
- Use
FieldOfViewfor visibility; usePathFinderfor shortest/reachable paths. - Use
Monopolyfor directional route traversal, not general A* pathfinding. - Keep occupied tests, blocker tests, pre-test callbacks, and cost callbacks separate.
- Use instance sentinels (
fov.BLOCKER,fov.INFINITY,monopoly.STOP,monopoly.BLOCKER) in callbacks. - Choose
coneMode: 'direction'for grid-direction cones andconeMode: 'angle'for angular cones.
Source File Map
plugins/board/fieldofview/FieldOfView.d.ts: visibility config, callbacks, LOS, and FOV methods.plugins/board/monopoly/Monopoly.d.ts: route config, cost callback, and path methods.plugins/board/fieldofview/Factory.js:fieldOfViewfactory signature.plugins/board/monopoly/Factory.js:monopolyfactory signature.
Related Skills
rexboard-board-and-chess: board chess and blockers.rexboard-grids-and-coordinates: directions, cones, distances, and line tile queries.rexboard-movement-and-pathfinding: PathFinder and MoveTo workflows.
Gotchas
FieldOfView.BLOCKERisnull;FieldOfView.INFINITYisundefined.Monopoly.STOPis-1;Monopoly.BLOCKERisnull.LOShas several overloads; keep argument order explicit in generated code.