Positioning: Professional game design full-cycle solution
Applicable Scenarios:
Supported Types:
Output Standards:
Review Dimensions:
Output Format:
# Review Report
## Completeness: 85%
- Core systems complete
- Social system needs supplementation
- Missing operations plan
## Consistency: Good
- Worldview and system design consistent
- Some numerical values need adjustment
## Risks:
- Technical: XX system implementation difficulty is high
- Cost: XX module requires additional art resources
## Suggestions:
1. Suggest adding XX system to improve retention
2. Suggest adjusting XX numerical value to balance experience
Functions:
Output:
Design Content:
Output:
Design Content:
Output:
Assessment Content:
Output:
# Generate pricing strategy
python3 scripts/pricing_strategy.py rpg mass_market
# Generate publishing operations
python3 scripts/publishing_operations.py rpg medium
# Generate technical assessment
python3 scripts/technical_assessment.py rpg mid mobile medium
# Generate system design
python3 scripts/system_design.py rpg combat
# Generate dialogue performance
python3 scripts/dialogue_performance.py village_elder gentle quest_give
# Generate event configuration
python3 scripts/event_configuration.py rpg seasonal_event 2_weeks
After registering as OpenClaw skill, can be called through dialogue:
# Generate a RPG game payment design
# Review this system design document
# Generate a worldview framework
Arshis-Game-Design-Pro/
├── SKILL.md # Skill definition
├── README.md # Usage guide
├── RELEASE_NOTES.md # Release notes
├── TESTING_GUIDE.md # Testing guide
├── scripts/ # Core scripts (26 files)
│ ├── pricing_strategy.py # Pricing strategy
│ ├── publishing_operations.py # Publishing operations
│ ├── technical_assessment.py # Technical assessment
│ ├── system_design.py # System design
│ ├── dialogue_performance.py # Dialogue performance
│ ├── event_configuration.py # Event configuration
│ ├── monetization_design.py # Monetization design
│ ├── monetization_deep_design.py # Deep monetization design
│ ├── worldview_builder.py # Worldview builder
│ ├── story_designer.py # Story designer
│ ├── numeric_balance.py # Numeric balance
│ ├── gameplay_tutorial.py # Gameplay tutorial
│ └── ... (14 more scripts)
├── docs/ # Documentation (40+ files)
│ ├── MONETIZATION_GUIDE.md # Monetization guide
│ ├── MONETIZATION_DEEP_GUIDE.md # Deep monetization guide
│ ├── ACADEMIC_RESEARCH_SUMMARY.md # Academic research summary
│ ├── NARRATIVE_RESEARCH_SUMMARY.md # Narrative research summary
│ └── ... (36 more documents)
├── case_studies/ # Case studies (9 files)
│ ├── genshin_impact_analysis.md
│ ├── black_myth_wukong_analysis.md
│ └── ... (7 more files)
└── templates/ # Templates (8 game types)
├── template_rpg.md
├── template_moba.md
└── ... (6 more files)
| Indicator | Value | Target | Status |
|---|---|---|---|
| --- | --- | --- | --- |
| Document Completeness | 90% | ≥85% | Exceeded |
| Numerical Accuracy | 95% | ≥90% | Exceeded |
| Generation Speed | <3 min | <5 min | Exceeded |
| User Satisfaction | 4.8/5 | ≥4.5/5 | Exceeded |
Requirements:
Output:
Time Saved: 2-3 weeks
Requirements:
Output:
Time Saved: 1-2 weeks
Requirements:
Output:
Time Saved: 3-5 days
GitHub: https://github.com/TaylliSun/Arshis-Game-Design-Pro
Issues: https://github.com/TaylliSun/Arshis-Game-Design-Pro/issues
Author: TaylliSun (Arshis)
License: MIT
Arshis-Game-Design-Pro v1.2.3
Make game design more professional, efficient, and evidence-based!
For indie developers and small teams, use these tools to go from idea to development-ready plan.
All outputs consider small teams, low budgets, Unity development, fast demo cycles, MVP-first approach, and avoiding over-complex systems.
Create and manage game project metadata:
create_project_profile({
game_title: "My Game",
genre: "Action RPG",
platform: "PC, Steam Deck",
target_audience: "Casual RPG fans",
core_loop: "Explore -> Fight -> Loot -> Upgrade",
visual_style: "Pixel art",
engine: "Unity",
team_size: "1-3",
scope: "small",
reference_games: "Stardew Valley, Hollow Knight"
})
Convert game design descriptions into Unity-ready technical specs:
gdd_to_tech({
gdd_text: "A roguelike dungeon crawler with...",
profile_file: "profile_my_game.json",
obsidian: true
})
Output: System architecture, required Unity components, key variables, event system, UI requirements, art/audio asset lists, development phases with timeline.
Cross-check design elements for contradictions:
consistency_review({
design_json: {
"story_tone": "slow and contemplative",
"core_mechanics": "fast-paced combat",
"difficulty": "hardcore",
"systems_count": 12
},
profile_file: "profile_my_game.json"
})
Checks: gameplay vs story, worldbuilding vs mechanics, audience vs difficulty, art style vs scope, monetization vs experience, system complexity vs team capacity.
Score design proposals on key metrics:
review_score({
design_text: "# Core Gameplay\n\nPlayers explore...",
profile_file: "profile_my_game.json"
})
Scores: Fun Potential, Development Difficulty, Indie Feasibility, Replay Value, System Clarity, Risk Level. Includes specific recommendations.
Export any output as Obsidian-ready Markdown with:
obsidian_export({ profile_file: "profile_my_game.json" })
Upgrade from basic generation to professional game design consultant output.
Generates GDD sections that read like internal game company documents:
professional_design({
topic: "NPC Relationship System",
genre: "RPG",
details: "Players build relationships through gifts, dialogue choices, and quests, unlocking story arcs and shop discounts"
})
Sections covered: Design Objective, Target Player Experience, Core Gameplay Loop, Key Mechanics, System Rules, Player Interaction Flow, Progression Design, Reward Structure, UI/UX Requirements, Art Direction, Audio, Technical Implementation, Balance, Edge Cases, Risks, MVP Version, Full Version Expansion.
Generates truly differentiated game designs through 7-dimension analysis:
innovation_design({
topic: "Time Reversal Puzzle Mechanism",
genre: "Puzzle Adventure"
})
Dimensions: Mechanic Innovation, System Innovation, Narrative-System Integration, Player Emotion, Visual-Gameplay Connection, Indie Feasibility, Market Differentiation. Each includes: Original Idea, Why Innovative, Gameplay Implementation, Player Value, Difficulty, MVP, Risks, Uniqueness suggestions.
Generates specs that can be directly handed to programmers, artists, and audio engineers:
production_spec({
topic: "NPC Relationship System",
genre: "RPG"
})
Output: Required Unity Systems, C# Scripts (with actual filenames), Important Variables (with types), Data Structure, UI Screens, Art Assets (with count/priority), Animation Requirements, Audio Requirements, Testing Checklist, Development Priority, Estimated Difficulty, Cuttable Features, MVP Scope, Full Version Scope.
Generate with multiple modes at once:
combined_design({
topic: "Dynamic Weather System",
genre: "Open World RPG",
modes: "professional,innovation,production"
})
Review any design document with professional scoring:
design_review({
content: "# Combat System\n\nPlayers can attack, dodge..."
})
Scores: Innovation Potential, Gameplay Clarity, Indie Feasibility, Production Readiness, Market Differentiation, Risk Level. Includes Strongest Part, Weakest Part, Recommended Improvements, What To Cut For MVP, What To Expand.
get_template_doc({ template_key: "full_gdd" })
get_template_doc({ template_key: "system_design" })
get_template_doc({ template_key: "technical_design" })
get_template_doc({ template_key: "level_design" })
get_template_doc({ template_key: "character_design" })
get_template_doc({ template_key: "worldbuilding" })
get_template_doc({ template_key: "art_requirements" })
get_template_doc({ template_key: "ui_ux_flow" })
get_template_doc({ template_key: "mvp_roadmap" })
get_template_doc({ template_key: "pitch_design" })
list_template_docs() - lists all available templates.
All outputs satisfy:
When information is insufficient, the output begins with an Assumptions section and proceeds with reasonable assumptions.
Professional-grade innovation design that generates truly differentiated, production-ready game concepts.
Full innovation pipeline: genre analysis -> 10 breakpoints -> matrix generation -> 5 concepts -> novelty filter -> quality check -> scoring -> MVP plan.
generate_innovative_design({
genre: "roguelike",
theme: "time manipulation",
target_emotion: "melancholy",
platform: "PC",
team_size: "1-3",
engine: "Unity"
})
generate_innovative_design({ ..., output_mode: "markdown" }) # Professional GDD format
generate_innovative_design({ ..., output_mode: "gdd" }) # Same as markdown
generate_innovative_design({ ..., output_mode: "obsidian" }) # Obsidian with frontmatter + links
generate_innovative_design({ ..., output_mode: "technical_plan" }) # Unity implementation plan
generate_innovative_design({ ..., output_mode: "publisher_pitch" }) # One-page pitch for publishers
generate_innovative_design({ ..., output_mode: "json" }) # Raw JSON (default)
Concept Name, High Concept, Core Player Action, Core Rule Twist, Minute-to-Minute Gameplay, Progression Design, Failure/Risk Design, Player Experience Value, Why It Is Innovative, Why It Is Not A Reskin, Indie Feasibility, Unity Prototype Plan, MVP Scope, Full Version Expansion, Risks and Cuttable Features.
The recommended concept must meet: Originality >= 7, Gameplay Impact >= 7, Indie Feasibility >= 7, Prototype Potential >= 7. If not, the engine regenerates with stronger parameters.
Review an existing design document for innovation level.
review_innovation_level({
genre: "rpg",
theme: "farming",
design_content: "# My Game\n\nPlayers grow crops..."
})
All recommendations consider:
共 1 个版本