start
Skill0 starsChanged 7 months agoMITView on GitHub
Detect current project state and route to the appropriate workflow. Silently scan the project to determine its state. Do NOT list what you're checking — just analyze and present the result. Check these locations (silently): - briefs/ — any .md files? - deliverables/ — any subdirectories with files? - src/ — any source code files? - production/sprints/ — any sprint plans? - production/session-state/active.md — exists and has content beyond the template? - .claude/docs/brand-guidelines.md — has real content (not just TBD…
130 other projects use a version of this.
Adopted by
Most recently taken up by
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- paulocsb/worldcup-fifa-pooltheir own version, first seen Nov 8, 2026
- srinator22/New-Projecttheir own version, first seen Nov 8, 2026
- Memolok/Claude-plugintheir own version, first seen Nov 6, 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
- CoralGameSkill
team-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
- lilangMaxSkill
story-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 versions130 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 130
- anthropics/knowledge-work-plugins★ 35ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame 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★ 426same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- ansvisor/ansvisor★ 233same name
- alexeykrol/claude-code-starter★ 194same name
120 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 repository32 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architectSkill
- auditSkill
- brandSkill
- campaignSkill
- code-reviewSkill
- content-planSkill
- deploySkill
- design-reviewSkill
- design-systemSkill
- discoverSkill
- handoverSkill
- implementSkill
- intakeSkill
- kickoffSkill
- proposalSkill
- qaSkill
- reportSkill
- retroSkill
- reviewSkill
- seo-auditSkill
- sitemapSkill
- sprint-planSkill
- standupSkill
- strategySkill
- team-brandSkill
- team-contentSkill
- team-launchSkill
- team-marketingSkill
- team-websiteSkill
- wireframeSkill
- write-contentSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 117 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Check these locations (silently):
- Distinctive: line 28
Read the brief. Present options:
- Very specific: line 36
No design files? → suggest /brand or /wireframe
- Very specific: line 37
No source code? → suggest /architect or /implement
- Very specific: line 38
No content? → suggest /content-plan or /write-content
- Very specific: line 39
No tests? → suggest /qa
- Very specific: line 50
After routing, update production/session-state/active.md with session start timestamp.
“Common” is measured: kept by at least 6 in 10 of the 117 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 — Smart Project Router
Detect current project state and route to the appropriate workflow.
Instructions
Silently scan the project to determine its state. Do NOT list what you're checking — just analyze and present the result.
Step 1: Scan Project State
Check these locations (silently):
briefs/— any.mdfiles?deliverables/— any subdirectories with files?src/— any source code files?production/sprints/— any sprint plans?production/session-state/active.md— exists and has content beyond the template?.claude/docs/brand-guidelines.md— has real content (not just TBD placeholders)?
Step 2: Determine State & Route
State A — New Project (no briefs): Present via AskUserQuestion:
- "Start new client project" → suggest
/intake - "Resume previous work" → ask for context
- "Explore the agency" → explain available workflows
State B — Brief Exists, No Deliverables: Read the brief. Present options:
- "Run discovery research" →
/discover - "Create project proposal" →
/proposal - "Develop strategy" →
/strategy - "Skip to kickoff" →
/kickoff
State C — Project In Progress (has some deliverables): Analyze what exists and what's missing. Present the most logical next step:
- No design files? → suggest
/brandor/wireframe - No source code? → suggest
/architector/implement - No content? → suggest
/content-planor/write-content - No tests? → suggest
/qa - Everything present? → suggest
/team-launch
State D — Returning Session (active.md has real content): Read active.md. Present:
- Summary of last session state
- Option to continue where you left off
- Option to start something new
- Option to run
/standupfor status check
Step 3: Update State
After routing, update production/session-state/active.md with session start timestamp.
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.