skills.rest
onemanking
onemankingCOMMUNITY
Explore all skills by this author →
GitHub

start

Guides new users through onboarding by detecting project state and routing to workflows.

Updated Apr 13, 2026
Search Tags:#game development#brainstorming#onboarding#workflow routing#project detection#guided setup
One-click install
npx skills add https://github.com/onemanking/the-operator --skill start-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/start
Command: npx skills add https://github.com/onemanking/the-operator --skill start-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New users of a game development workspace often don't know where to begin — whether to brainstorm a concept, configure an engine, or organize existing work. This Skill removes that uncertainty by asking where the user is starting from and routing them to the right workflow. ## Core Features & Use Cases - Silent Project Detection: Scans for engine configuration, game concept documents, source code, prototypes, and design docs before asking any questions. - Four-Path Routing: Presents four starting states (no idea, vague idea, clear concept, existing work) and recommends a tailored sequence of next skills for each. - Edge-Case Handling: Detects mismatches between the user's self-assessment and actual project state, such as picking "existing work" in an empty project. - Use Case: A user opens a fresh game studio template, runs the onboarding flow, answers "vague idea — something with space," and receives a recommended path starting with brainstorming, then engine setup, then prototyping. ## Quick Start Ask the assistant to start the guided onboarding and answer the question about where you are with your game idea.

Frequently Asked Questions about start

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

FAQPage Schema
How do I get started with a new game development project?▼

Run the onboarding flow, which first scans your project for engine configuration, design docs, and code, then asks where you are starting from. Based on your answer — no idea, vague idea, clear concept, or existing work — it recommends a tailored sequence of next steps.

How do I choose a game engine for my project?▼

The onboarding flow checks whether an engine is configured in the technical preferences file and routes you to the engine setup step if it is not. Engine selection typically comes after brainstorming, which recommends an engine based on your concept.

What if I already have design docs or code in my project?▼

Choose the existing work path during onboarding. The skill reports what it found — source files, design docs, prototypes, engine status — and recommends a full gap analysis to identify what is missing before continuing.

Does the onboarding skill run the next workflow automatically?▼

No. It follows a collaborative protocol: it presents recommended paths, asks which step you want to take first, and never auto-executes the next skill. You confirm before any handoff occurs.

What happens if my answer doesn't match my actual project state?▼

The skill detects mismatches, such as picking existing work in an empty project or claiming no idea when code already exists. It gently points out the discrepancy and suggests a better-fitting path instead of proceeding blindly.

Related Skills

Explore More Product & Management Skills→
VanLengsVanLengs
1

init

Initialize a git-tracked studio workspace with config and directories.

Community
Intermediate
WindXRanWindXRan

prototype

Test a game concept's core interaction loop with a throwaway prototype.

Community
Intermediate
HechaoYannetHechaoYannet

project-stage-detect

Scan repository artifacts to classify project stage and identify gaps.

Community
Intermediate
karolmckghkarolmckgh
2

onboarding

Assess learner's Copilot knowledge and customize tutorial lessons.

Community
Intermediate