Skip to content

feat: add new-unity-project orchestrator skill#26

Merged
andresbayon merged 1 commit into
unity-cli/add-new-project-workflowfrom
new-unity-project
Jul 8, 2026
Merged

feat: add new-unity-project orchestrator skill#26
andresbayon merged 1 commit into
unity-cli/add-new-project-workflowfrom
new-unity-project

Conversation

@andresbayon

Copy link
Copy Markdown
Collaborator

What

Adds a new-unity-project skill — a thin, slash-invocable orchestrator that gives the guided "idea → running project" experience.

Stacked on #25 (unity-cli/add-new-project-workflow). Review/merge #25 first; GitHub will retarget this to main automatically.

Why

Review feedback (@ewhittom) surfaced two things a standalone skill does that a workflow buried in unity-cli can't:

  1. Explicit /new-unity-project invocation — a clean, discoverable entry point for "I want to make a game," instead of only /unity-cli.
  2. Parallelism — the guided questions let us kick off the multi-minute unity install <editor> + modules in the background while the user answers concept questions, so setup overlaps the conversation.

Neither lives naturally in a command reference. So this skill owns the flow and nothing else.

Design: delegate, don't duplicate

This is what keeps it from overlapping unity-cli (the original concern):

  • Owns: the AskUserQuestion flow, question ordering, the background-install timing, and the handoffs.
  • Delegates all mechanics — commands to unity-cli (its "Bootstrap a new project from scratch" workflow is the backbone), package installs to unity-package-management, and monetization/backend integration to implement-in-app-purchases / levelplay-unity-integration / build-live-game.
  • Contains no command reference.

Deliberately out of scope

  • Gameplay scaffolding — the weak, throwaway-mocked-primitive step. The skill stops at a clean, running, empty-but-wired project and points the user to iterate from there.

Security

--git-token-stdin only, no secret literals, no curl | sh, no internal references; diff scanned clean of emoji/zero-width/variation-selector characters.

🤖 Generated with Claude Code

A thin, slash-invocable composer that gives the guided "idea -> running
project" experience without duplicating the reference skills. It owns the flow
only — questions, ordering, and handoffs — and delegates all mechanics:

- Guided AskUserQuestion flow (concept -> platforms/monetization).
- Backgrounds the multi-minute Editor install while it keeps asking questions,
  so setup overlaps the conversation (the key win over a raw recipe).
- Delegates commands to unity-cli and package installs to
  unity-package-management; hands off monetization to implement-in-app-purchases
  / levelplay-unity-integration / build-live-game.
- Deliberately NO gameplay scaffolding (the weak, throwaway-primitive step) and
  NO command reference (lives in the delegated skills).

Addresses the standalone-skill benefits raised in review (explicit /invocation
+ guided questions + parallel installs) while avoiding the overlap that
motivated folding the recipe into unity-cli.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@andresbayon andresbayon requested a review from a team as a code owner July 8, 2026 14:11
@andresbayon andresbayon merged commit e2e17b9 into unity-cli/add-new-project-workflow Jul 8, 2026
3 checks passed
@andresbayon andresbayon deleted the new-unity-project branch July 8, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant