start
Skill9 starsChanged 7 months agoMITView on GitHub
Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".
135 other projects use a version of this.
Adopted by
Most recently taken up by
- flavien-ia/hypervibe-harnesstheir own version, first seen Nov 15, 2026
- srinator22/agent-kerneltheir own version, first seen Nov 15, 2026
- librosdeia/builder-method-claude-plugintheir own version, first seen Nov 15, 2026
- willink-oss/willink-claude-kittheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- relai-ai/agent-eval-looptheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-engine, team-audio and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +3 more from CoralGame
- +3 more from lilangMax
Other versions135 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 135
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- openai/plugins★ 7.8ksame name
- SterlingChin/marvin-template★ 1ksame name
- educlopez/ui-craft★ 441same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- dsifry/metaswarm★ 432same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- ansvisor/ansvisor★ 241same name
- alexeykrol/claude-code-starter★ 194same name
125 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 10 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run /brainstorm to explore game ideas
- Distinctive: line 28
Ask them to describe their idea in 2-3 sentences
- Distinctive: line 29
Ask: What Roblox games inspire this?
- Distinctive: line 35
Ask them to share or describe their existing design docs
- Very specific: line 37
Run /project-stage-detect to assess readiness
- Distinctive: line 42
Ask them to describe the project and share the codebase location
- Very specific: line 43
Run /reverse-document to generate docs from existing code
- Very specific: line 44
Run /project-stage-detect to assess current stage
- Distinctive: line 46
Create a plan for what's next
- Distinctive: line 52
After the starting-point question, ask:
- Distinctive: line 84
When a genre is selected, provide the following recommendations:
- Very specific: line 122
No preset guidance. Start from scratch with /gdd.
- Distinctive: line 128
After the genre step (or skip), confirm:
- Very specific: line 139
After the user answers all questions, write the configuration to persistent files.
- Very specific: line 143
Write the file to the repo root at project.config.json:
- Distinctive: line 179
Use the project name with spaces replaced by hyphens.
- Very specific: line 183
Write the chosen review mode to production/review-mode.txt.
- Distinctive: line 195
If a genre was selected, show the recommended wiki pages, skills, and agents
“Common” is measured: kept by at least 6 in 10 of the 122 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/start — Project Onboarding
Welcome the user and determine their starting point by asking:
"Where are you with this project?"
- No idea — I don't even have a game concept yet
- Vague concept — I have a rough idea but nothing documented
- Clear design — I have a GDD or design docs ready
- Existing code — I have a Roblox project with code already
Based on their answer:
If "No idea":
- Run
/brainstormto explore game ideas - Guide through genre selection, target audience, core loop definition
- Help define creative pillars (3-5 words each that describe the experience)
- Draft a 1-page game concept document
- Proceed to
/gddfor the master GDD
If "Vague concept":
- Ask them to describe their idea in 2-3 sentences
- Ask: What Roblox games inspire this? What's the core loop?
- Help crystallize: genre, setting, core mechanic, target audience
- Define creative pillars
- Proceed to
/gdd
If "Clear design":
- Ask them to share or describe their existing design docs
- Review for completeness against GDD standards
- Run
/project-stage-detectto assess readiness - Identify gaps and create a plan to fill them
- Set up the project structure if not already done
If "Existing code":
- Ask them to describe the project and share the codebase location
- Run
/reverse-documentto generate docs from existing code - Run
/project-stage-detectto assess current stage - Identify technical debt with
/tech-debt - Create a plan for what's next
Team Size Preset
After the starting-point question, ask:
"What's your team size?"
- Solo — just me. Streamlined review, fewer agent interactions.
- Small team (2-5) — lean review, key specialists involved.
- Studio (5+) — full review pipeline, all agents active.
Based on the answer, set review_mode automatically:
- Solo ->
solo - Small team ->
lean - Studio ->
full
Genre Preset (optional)
Ask:
"What genre?" (Tell the user they can skip this if they don't know yet.)
- Simulator — sets up simulator-specific patterns
- RPG — sets up RPG progression, combat, equipment
- FPS — sets up first-person framework, weapons, viewmodel
- Obby — sets up checkpoint system, kill bricks
- Tycoon — sets up dropper pipeline, buttons, upgrades
- Social / Hangout — sets up social features, housing
- Tower Defense — sets up tower placement, wave spawning, targeting
- Custom — no preset, start from scratch
Genre-specific guidance
When a genre is selected, provide the following recommendations:
Simulator
- Wiki pages:
wiki/patterns/simulator-loop.md,wiki/services/DataStoreService.md,wiki/concepts/server-authority.md - Skills to run first:
/gdd,/datastore-design - Key agents:
economy-designer,datastore-architect,luau-systems-programmer
RPG
- Wiki pages:
wiki/patterns/rpg-progression.md,wiki/services/DataStoreService.md,wiki/concepts/session-locking.md - Skills to run first:
/gdd,/datastore-design,/combat-design - Key agents:
game-designer,systems-designer,economy-designer,luau-gameplay-programmer
FPS
- Wiki pages:
wiki/patterns/fps-framework.md,wiki/concepts/server-authority.md,wiki/performance/heartbeat-budget.md - Skills to run first:
/gdd,/combat-design - Key agents:
luau-gameplay-programmer,remotes-networking-specialist,exploit-security-specialist,performance-analyst
Obby
- Wiki pages:
wiki/patterns/obby-checkpoints.md,wiki/services/DataStoreService.md - Skills to run first:
/gdd,/level-design - Key agents:
level-designer,luau-gameplay-programmer
Tycoon
- Wiki pages:
wiki/patterns/tycoon-dropper.md,wiki/services/DataStoreService.md,wiki/concepts/server-authority.md - Skills to run first:
/gdd,/datastore-design,/economy-design - Key agents:
economy-designer,datastore-architect,luau-systems-programmer
Social / Hangout
- Wiki pages:
wiki/patterns/social-features.md,wiki/patterns/housing-system.md - Skills to run first:
/gdd,/ui-design - Key agents:
ui-programmer,ux-designer,game-designer
Tower Defense
- Wiki pages:
wiki/patterns/tower-defense.md,wiki/concepts/object-pooling.md,wiki/performance/heartbeat-budget.md - Skills to run first:
/gdd,/combat-design,/economy-design - Key agents:
luau-gameplay-programmer,systems-designer,performance-analyst,economy-designer
Custom
- No preset guidance. Start from scratch with
/gdd.
Configuration Questions
After the genre step (or skip), confirm:
- Sync tool: Rojo / Argon / Manual Studio (default: Rojo)
- UI framework: Native ScreenGui / Roact / Fusion (default: Native)
- Project name: What should the game be called? (used in
default.project.jsonand config) - Max players: How many players per server? (default: 20)
Write Configuration
After the user answers all questions, write the configuration to persistent files. This is the critical step that makes /start durable across sessions.
Step 1: Create project.config.json
Write the file to the repo root at project.config.json:
{
"project_name": "<user's game name>",
"sync_tool": "<rojo | argon | manual>",
"ui_framework": "<native | roact | fusion>",
"review_mode": "<solo | lean | full>",
"genre": "<simulator | rpg | fps | obby | tycoon | social | tower-defense | custom | none>",
"max_players": <number>,
"configured_at": "<YYYY-MM-DD>"
}genreshould be"none"if the user skipped the genre question.configured_atshould be today's date.
Step 2: Update CLAUDE.md
In the ## Technology Stack section of CLAUDE.md, replace the placeholder lines with the actual choices:
- Replace
- **Sync Tool**: [CHOOSE: Rojo / Argon / Manual Studio]with the chosen tool, e.g.- **Sync Tool**: Rojo - Replace
- **UI Framework**: [CHOOSE: Native ScreenGui / Roact / Fusion]with the chosen framework, e.g.- **UI Framework**: Native ScreenGui
Step 3: Update default.project.json
Set the "name" field in default.project.json to the project name the user provided.
For example, if the user named their game "Dragon Quest Obby":
{
"name": "Dragon-Quest-Obby",
...
}Use the project name with spaces replaced by hyphens.
Step 4: Create production/review-mode.txt
Write the chosen review mode to production/review-mode.txt. The file should contain just the mode string on a single line:
soloor lean or full, depending on the team size preset.
After onboarding, always:
- Confirm the configuration was written by listing the files created/updated
- If a genre was selected, show the recommended wiki pages, skills, and agents
- Suggest next steps based on the starting point and genre
- Remind the user they can re-run
/startto change configuration
Review Mode Reference
- Full (
full): Every change gets reviewed by relevant agents before implementation. Best for production work with a studio team. - Lean (
lean): Critical changes reviewed; minor changes proceed with a single approval. Best for small teams moving fast. - Solo (
solo): Minimum review. User makes most decisions directly. Best for prototyping or solo development.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

