Run any Skill in Manus with one click

update-pyray-platform

Stars0

Forks0

UpdatedJuly 20, 2026 at 04:48

Change the locked pyray binding version, raylib backend, native API, Python range, and matching CI configuration in a standalone game. Use only for an explicit platform-baseline migration.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DrHepa

DrHepa/rpg-world-forge

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	update-pyray-platform
description	Change the locked pyray binding version, raylib backend, native API, Python range, and matching CI configuration in a standalone game. Use only for an explicit platform-baseline migration.

Update the pyray platform baseline

Scope

Change one locked Python/pyray/raylib/backend baseline in G02. Do not change the runtime API, gameplay, content, or presentation features.

Inputs

Absolute FORGE_ROOT and external GAME_ROOT.
Current platform lock, proposed exact baseline, migration reason, and target OS/architecture matrix.
Current source-tree, runtime-lock, and catalog hashes plus previous gate.
Official binding/backend support evidence for every declared target.

Outputs

Matching platform.lock.json, CI-consumed requirements.lock, direct/build dependency declarations, CI, notices, and focused platform tests.
Forge-owned native evidence and G20-G32 invalidation record.

Invariants

Keep src/isoworld, runtime.lock.json, bundles, and gameplay immutable.
Pin the complete supported dependency closure and keep native API, backend, Python range, pyproject.toml, both locks, CI, and notices consistent.
Never copy AGENTS.md, .agents, Forge skills, or phase evidence into GAME_ROOT.
Return runtime changes to G01 and adapter changes to their G20-G25 phase.

Workflow

Read the G02 gate in docs/GAME_IMPLEMENTATION_PHASES.md.
Record the current platform lock and the reason for the candidate baseline.
Verify official binding/backend support on every declared target platform.
Update platform.lock.json, requirements.lock, and direct/build dependency declarations together; never leave a floating or alternate dependency surface.
Run headless tests plus native window, input, DPI, graphics, and audio profiles.
Invalidate G20-G32 evidence and rerun affected presentation phases and G30.

Completion

Complete only when the lock, dependency graph, CI, and notices agree and every required native matrix row passes. Record unsupported or skipped rows as missing evidence, never as passes.

More from this repository

same repository

animate-3d-asset-with-blender

DrHepa/rpg-world-forge

Animate one reviewed rig through bounded Blender MCP operations under GPT orchestration. Use for specified clips and loop evidence only, not rig changes, final GLB export, refinement, or QA approval.

2026-07-200

define-asset-bibles

DrHepa/rpg-world-forge

Define and approve target-scoped visual and audio bibles from a locked worldpack. Use for M5 art direction only, not inventory derivation, asset generation, processing, or QA.

2026-07-200

derive-asset-inventory

DrHepa/rpg-world-forge

Derive a complete target-scoped M5 asset inventory from locked canon and approved bibles. Use for requirements and semantic slots only, not specifications, generation, or processing.

2026-07-200

design-3d-asset-references

DrHepa/rpg-world-forge

Produce a coherent reference-image set for one approved 3D asset specification through OpenAI Image. Use for 3D design evidence only, not modeling, rigging, animation, GLB export, or QA.

2026-07-200

forge-world-release

DrHepa/rpg-world-forge

Compile, package, and verify one immutable runtime bundle from an approved world-authoring repository. Use only for the world-release phase; game import is a separate skill.

2026-07-200

model-3d-asset-with-blender

DrHepa/rpg-world-forge

Model one specified 3D asset through bounded Blender MCP operations under GPT orchestration. Use for geometry, UVs, and material slots only, not rigging, animation, final export, or QA approval.

2026-07-200

name	update-pyray-platform
description	Change the locked pyray binding version, raylib backend, native API, Python range, and matching CI configuration in a standalone game. Use only for an explicit platform-baseline migration.

Update the pyray platform baseline

Scope

Change one locked Python/pyray/raylib/backend baseline in G02. Do not change the runtime API, gameplay, content, or presentation features.

Inputs

Absolute FORGE_ROOT and external GAME_ROOT.
Current platform lock, proposed exact baseline, migration reason, and target OS/architecture matrix.
Current source-tree, runtime-lock, and catalog hashes plus previous gate.
Official binding/backend support evidence for every declared target.

Outputs

Matching platform.lock.json, CI-consumed requirements.lock, direct/build dependency declarations, CI, notices, and focused platform tests.
Forge-owned native evidence and G20-G32 invalidation record.

Invariants

Keep src/isoworld, runtime.lock.json, bundles, and gameplay immutable.
Pin the complete supported dependency closure and keep native API, backend, Python range, pyproject.toml, both locks, CI, and notices consistent.
Never copy AGENTS.md, .agents, Forge skills, or phase evidence into GAME_ROOT.
Return runtime changes to G01 and adapter changes to their G20-G25 phase.

Workflow

Read the G02 gate in docs/GAME_IMPLEMENTATION_PHASES.md.
Record the current platform lock and the reason for the candidate baseline.
Verify official binding/backend support on every declared target platform.
Update platform.lock.json, requirements.lock, and direct/build dependency declarations together; never leave a floating or alternate dependency surface.
Run headless tests plus native window, input, DPI, graphics, and audio profiles.
Invalidate G20-G32 evidence and rerun affected presentation phases and G30.

Completion

Complete only when the lock, dependency graph, CI, and notices agree and every required native matrix row passes. Record unsupported or skipped rows as missing evidence, never as passes.