mihoyo-perspective

Assess decisions for long-term world-building alignment across product, content, and rollout.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Lumine2024/miHoYo.skill --skill mihoyo-perspective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mihoyo-perspective
Source: https://github.com/Lumine2024/miHoYo.skill/tree/main
Command: npx skills add https://github.com/Lumine2024/miHoYo.skill --skill mihoyo-perspective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires VideoWorkflow.psm1, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a Mihoyo-inspired, structured framework for high-level product and organizational decision-making, helping teams align on long-term world-building, IP cohesion, and cross-team execution.

Core Features & Use Cases

  • Long-term vision anchoring: ensures decisions reinforce immersive virtual worlds and IP-based value.
  • Team-of-Teams collaboration: clarifies interfaces and governance for cross-functional work.
  • Context not Control principle: prioritizes context and boundary-setting before tactical steps.
  • Global operation framing: supports multi-region rollout with consistent brand and experience.

Quick Start

Ask the AI to evaluate the Mihoyo perspective: outlining how a proposed game feature would affect long-term world-building, cross-team coordination, and potential risks.

Frequently Asked Questions about mihoyo-perspective

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

FAQPage Schema
How do I align game feature decisions with long-term world-building and IP cohesion?

To align game feature decisions with long-term world-building, you need a structured framework that evaluates proposals against immersive virtual world visions and IP-based value. This approach clarifies cross-team interfaces and ensures tactical steps reinforce the overarching narrative.

What is the "Context not Control" principle in cross-team product governance?

The "Context not Control" principle in cross-team product governance prioritizes establishing shared context and clear boundary-setting before defining tactical execution steps. This method enables autonomous team-of-teams collaboration without rigid top-down micromanagement.

How do I structure cross-functional collaboration for multi-region global game rollout?

Structuring cross-functional collaboration for multi-region global game rollout requires outlining scope across content production, organizational interfaces, and risk management. This ensures consistent brand experience and synchronized execution across all targeted regions.

Can I use a Mihoyo-inspired framework for high-level organizational decision-making?

Yes, you can use a Mihoyo-inspired framework for high-level organizational decision-making. It assesses decisions to determine long-term world-building alignment while specifying requirements for cross-team interfaces and context-first governance.

How to assess long-term vision anchoring for a proposed game feature?

Assessing long-term vision anchoring for a proposed game feature involves evaluating its scope across product design, content production, and risk management. This ensures the feature satisfies immersive virtual world requirements and reinforces IP cohesion.

What are the limitations of using a world-building perspective for product decision-making?

Using a world-building perspective for product decision-making focuses heavily on long-term IP alignment and cross-team governance, which may introduce overhead for rapid, short-term tactical iterations that do not require strict narrative or organizational interface validation.