gameuniverse-framework

Translate GameUniverse feature requests into Root/GUV-compliant architecture plans.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill gameuniverse-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gameuniverse-framework
Source: https://github.com/imgamer/AILearn/tree/main/Game-Skills/game-framework-skill
Command: npx skills add https://github.com/imgamer/AILearn --skill gameuniverse-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GameUniverse gameplay work often stalls between vague requirements and correct Root/GUV-aligned technical execution; this Skill turns those inputs into a structured plan that matches the project’s ownership and authority rules.

Core Features & Use Cases

  • Full workflow master skill: covers requirement analysis, Root/GUV compliance review, evidence-driven design, and an implementation-ready plan in one place.
  • Architecture-correct ownership mapping: decides what belongs to Root GlobalState, GS Managers, GS Rules, PS/CH skills, subsystems, or world Actor/Components based on the feature type.
  • Specialized branches guidance: supports anomaly/map-zone/event/reward systems and networked tether/transport/rope actor systems with appropriate topology, network rules, and validation steps.
  • Evidence-first instruction: prioritizes workspace governance and root references, then read-only code/config exploration before making conclusions.

Quick Start

Use the gameuniverse-framework skill when you need to analyze a new gameplay feature for GameUniverse and produce a requirement-to-implementation report with Root/GUV ownership, concrete technical方案 options, and verification steps.

Frequently Asked Questions about gameuniverse-framework

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

FAQPage Schema
How do I plan GameUniverse gameplay architecture to ensure Root/GUV compliance?

To plan GameUniverse gameplay architecture with Root/GUV compliance, translate feature requests into structured technical plans that map ownership across Root GlobalState, GS Managers, Rules, PS/CH skills, and world Actors. This ensures correct authority delegation and architecture validation.

What is the best way to design networked tether and rope Actor systems for GameUniverse?

Designing networked tether and rope Actor systems requires applying appropriate topology and network rules. You must validate transport integrations by decomposing requirements into class and config layers, ensuring explicit risk assessment and networked actor validation steps.

How do I map ownership across GS Managers and Root GlobalState for a new gameplay feature?

Mapping ownership across GS Managers and Root GlobalState requires evidence-first governance checks. You analyze the feature type to decide authority delegation across Root/GS/PS/CH/subsystem/actor layers, ensuring implementation-ready plans match project ownership rules.

Can I use this approach to validate anomaly and map-zone event systems in GameUniverse?

Yes, you can validate anomaly and map-zone event systems by applying specialized branch guidance. This involves reviewing topology, network rules, and validation steps specific to anomaly systems, ensuring event and reward distributions comply with Root/GUV architecture.

How to decompose GameUniverse gameplay requirements into an implementation-ready technical plan?

To decompose gameplay requirements into an implementation-ready technical plan, perform evidence-first code and config exploration. Translate inputs into Root/GUV-compliant architecture analysis, outputting concrete technical options, class/config decomposition, and verification steps.

What are the limitations of designing GameUniverse gameplay features without explicit ownership mapping?

Designing GameUniverse gameplay without explicit ownership mapping risks stalling technical execution between vague requirements and incorrect Root/GUV alignment. Skipping evidence-first governance checks and subsystem authority mapping leads to non-compliant architecture and validation failures.