start
Skill432 starsChanged 11 days agoMITView on GitHub
Answers setup questions and walks through the open Getting started steps, with a link to each page.
135 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- 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
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
Used with
Projects with it also use setup-engine, team-audio and 10 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
- +5 more from CoralGame
- +3 more from lilangMax
Other versions135 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- ansvisor/ansvisor★ 23399% same
Wrote their own version · 134
- 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
- dsifry/metaswarm★ 432same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- alexeykrol/claude-code-starter★ 194same name
- romarayt/raytsystem-public-os★ 140same name
- striderZA/OpenCodeGameStudios★ 118same name
124 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 repository29 other files it gives its agents.
- analyzeSkill
- answerfirstSkill
- audit-fixSkill
- auditSkill
- beatSkill
- compareSkill
- createSkill
- factsSkill
- faqSkill
- featuresSkill
- gapsSkill
- getcito-aeo-coachSkill
- getcito-aeo-coach-standaloneSkill
- listingsSkill
- marketsSkill
- new-reportSkill
- opportunitiesSkill
- optimizeSkill
- publishSkill
- qualitySkill
- questionsSkill
- refreshSkill
- reportSkill
- rivalsSkill
- shoppingSkill
- tasksSkill
- translateSkill
- winbackSkill
- wrongclaimSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read only these, for the chat's brand:
- Distinctive: line 27
When the workspace has two brands or more and none is selected, ask which brand to set up first.
- Distinctive: line 35
When every step is done, say so and point to the brand's first results instead.
- Distinctive: line 47
Never mark a Getting started step done or skip one: it completes through its own check.
- Distinctive: line 48
Add competitors, topics or prompts only with the tools that do it, and the app asks the person first.
“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
Get started
The playbook of the /start shortcut ("Help me get started. What should I set up first?"): what to set up next in GetCito, from where the brand stands today.
Data plan
Read only these, for the chat's brand:
get_onboarding_progress: the Getting started steps, done and open, in stage order.list_competitors,list_topicsandlist_prompts: how many competitors, topics and prompts the brand has.list_connections: whether Google Search Console and Analytics are connected for the brand.get_plan_facts, only when an open step depends on what the plan includes.list_brandsonly when no brand is selected, andopen_pageto link each step's page.
Questions
- When the workspace has two brands or more and none is selected, ask which brand to set up first.
- Nothing else: the progress answers the rest.
Steps
- Say where the brand stands in one line: how many steps are done, out of how many.
- List the open steps in stage order, five at most. For each: what it needs, why it matters for AI answers, and its page, linked with
open_page. - For anything the person connects themselves (Search Console, Analytics, the AI Traffic snippet), give the short steps they take.
- When every step is done, say so and point to the brand's first results instead.
Output
Text: the one-line status, then the open steps as a numbered list.
Next moves
The next open steps, such as "Add 3 competitors" or "Connect Google Search Console".
Don't
- Never mark a Getting started step done or skip one: it completes through its own check.
- Add competitors, topics or prompts only with the tools that do it, and the app asks the person first.
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.

