mcpField
U
unity-blueprints

unity-blueprints

github.com/besty0728Development1.9k85 installsUpdated today
Repository

About unity-blueprints

unity-blueprints is a design skill for planning lightweight Unity mini-games and vertical slices. It organizes a blueprint around the core loop, scenes, modules, scripts, data, and UI responsibilities, with guidance to keep the scope minimal.

Key features

  1. 01Supports seven game blueprint styles
  2. 02Plans core loops and scenes
  3. 03Recommends modules, scripts, and data
  4. 04Defines UI roles and limits scope

Use cases

  1. 01Plan a mini-game from scratch
  2. 02Structure a genre-specific gameplay prototype
  3. 03Prepare an initial script list for a vertical slice

MCP support

This is a documentation-only skill module and defines no REST skills; the input does not describe its relationship to MCP.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/besty0728/unity-skills --skill unity-blueprints

After installing, type/unity-blueprintsin Claude Code to confirm it loaded.

Details

From the project README

Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.

Triggers

  • Starting a small game from scratch
  • Scaffolding a genre core structure
  • Organizing a specific game type
  • 从零开始做小游戏、搭建某类型核心结构、组织特定玩法

Unity Gameplay Blueprints

Use this skill when starting a new mini-game or vertical slice and a lightweight architecture skeleton is more useful than raw code volume.

Supported Blueprint Styles

  • 2D platformer
  • top-down shooter
  • endless runner
  • puzzle / interaction game
  • tower defense
  • clicker / incremental
  • card / turn-based prototype

Output Format

  • Core loop
  • Recommended scenes
  • Recommended modules
  • Initial script list
  • Data/config assets
  • UI responsibilities
  • What to deliberately keep simple

Guardrails

Mode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).

  • Provide the smallest viable blueprint, not a giant reusable framework.
  • Prefer a short script inventory over “future-proof” template sprawl.

Comments

Markdown supported