game-brief
Skill0 starsChanged 39 days agoNo licenceView on GitHub
Author the full game-contract set (GAME_BRIEF, HOW_TO, EXPECT_GAMEPLAY_VISUAL, ASSET_MANIFEST, SCOPE, ARCHITECTURE, FOLLOWUPS, PLAYTEST, CONTEXT, ADR) plus the release plan (MILESTONES.md, numbered slice files, RELEASE_CHECKLIST.md) for an existing Cocos Creator project by spawning a configurable agent (default Fable 5.1) via Orca. Works from any source: an App Store reference pack (store-game-clone, optionally with a merged unity-apk-rip pack and mandatory rip-port-analysis forensic maps for rip-backed ports), a user-supplied media folder (screenshots / video / GDD / GLB), a gameplay video file or URL (measured with gameplay-video), or a text-only idea, with optional director gameplay notes and amendments to existing contracts. Sits between store-game-clone / new-cocos-game and game-producer. Use when the user says "game-brief", "game brief", "fable brief", "brief sâu", "contracts", "HOW_TO/EXPECT", or wants deep contracts for a game that was NOT cloned from a store.
In this repository24 other files it gives its agents.
- char-animSkill
- cocos-asset-genSkill
- cocos-orca-fleetSkill
- codex-image-genSkill
- computer-useSkill
- figma-flow-designSkill
- figma-game-cloneSkill
- find-skillsSkill
- gameplay-videoSkill
- game-producerSkill
- game-ui-kitSkill
- gpt-image-2-style-librarySkill
- new-cocos-gameSkill
- orca-agent-fleetSkill
- orca-cliSkill
- orca-gpt-image-genSkill
- orca-hermes-fleetSkill
- orchestrationSkill
- rip-port-analysisSkill
- store-game-cloneSkill
- typesafe-aiSkill
- unity-apk-ripSkill
- workflow-pilotSkill
- writing-great-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 6 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.