Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

forge-world-release

Étoiles0

Forks0

Mis à jour20 juillet 2026 à 08:49

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

DrHepa

DrHepa/rpg-world-forge

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Autres occupations informatiquesProfessions informatiques et mathématiques·SOC 15-1299

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	forge-world-release
description	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.

Forge a world release

Operate with explicit FORGE_ROOT, external WORLD_ROOT, and new BUNDLE_ROOT. No game path is in scope.

Release sequence

Read ADR-0009, docs/CONTENT_PIPELINE.md, and docs/ASSET_PIPELINE.md.
Require a release-valid, canon-locked world source.
Compile the worldpack and run narrative analysis.
Require a complete v3 asset manifest in production, bound to that exact worldpack and containing no self-declared deliverable.
Build the runtime-only renderpack under assets/release/; the builder must pass the internal build profile against the exact worldpack.
Run worldforge finalize-asset-release with the production-manifest hash, then require worldforge validate-assets --profile release to pass.
Export a new release ID with worldforge export-bundle.
Run worldforge verify-bundle against the completed directory.
Record the verified output path and bundle hash for the import phase.

Release invariants

The bundle contains only its manifest, worldpack, renderpack, processed assets, and runtime license files.
Every file is declared by relative POSIX path, size, and SHA-256.
A byte change creates a new bundle hash and release; never patch an imported release in place.
World ID, release ID, content hashes, schema versions, and required runtime features agree at every layer.
Prompts, provider/model metadata, references, candidates, phase state, and production manifests never cross the bundle boundary.
This skill releases the current 2D/2.5D renderpack bundle only. A sealed 3D assetpack is an engine-neutral implementation handoff and is not accepted by export-bundle or the generated pyray game.

Do not modify a game repository in this phase. $import-world-bundle owns the separate compatibility, copy, catalog-update, and game-load gate.

Completion

Return bundle/world/release hashes, capability result, license inventory, and verification evidence.

Plus depuis ce dépôt

même dépôt

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

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

operate-modly-asset

DrHepa/rpg-world-forge

Run one reviewed Modly extension for one approved M5 asset specification through modly-cli-mcp under GPT orchestration. Use for the optional local route only after capability research, not direct model calls, selection, refinement, or QA.

2026-07-200

Forge a world release

Operate with explicit FORGE_ROOT, external WORLD_ROOT, and new BUNDLE_ROOT. No game path is in scope.

Release sequence

Read ADR-0009, docs/CONTENT_PIPELINE.md, and docs/ASSET_PIPELINE.md.

Require a release-valid, canon-locked world source.

Compile the worldpack and run narrative analysis.

Require a complete v3 asset manifest in production, bound to that exact worldpack and containing no self-declared deliverable.

Build the runtime-only renderpack under assets/release/; the builder must pass the internal build profile against the exact worldpack.

Run worldforge finalize-asset-release with the production-manifest hash, then require worldforge validate-assets --profile release to pass.

Export a new release ID with worldforge export-bundle.

Run worldforge verify-bundle against the completed directory.

Record the verified output path and bundle hash for the import phase.

Release invariants

The bundle contains only its manifest, worldpack, renderpack, processed assets, and runtime license files.

Every file is declared by relative POSIX path, size, and SHA-256.

A byte change creates a new bundle hash and release; never patch an imported release in place.

World ID, release ID, content hashes, schema versions, and required runtime features agree at every layer.

Prompts, provider/model metadata, references, candidates, phase state, and production manifests never cross the bundle boundary.

This skill releases the current 2D/2.5D renderpack bundle only. A sealed 3D assetpack is an engine-neutral implementation handoff and is not accepted by export-bundle or the generated pyray game.

Do not modify a game repository in this phase. $import-world-bundle owns the separate compatibility, copy, catalog-update, and game-load gate.

Completion

Return bundle/world/release hashes, capability result, license inventory, and verification evidence.