agentleFS
Sign inStart free
PhoenixNestPhoenixNest/AGENT-GLOBAL-BASE/studio/CLAUDE.md

AGENT-GLOBAL-BASE / studio

CLAUDE.md2 starsChanged 2 months agoApache-2.0View on GitHub

Entry point for the Studio system. Contains all active and future creative game development studios. No other studios have been instantiated yet. Future studios will be added as sibling folders to casual-games/ following the conventions below. New studios follow this structure: Each studio defines its own pipeline independently. Do not assume future studios will inherit the Casual Games Studio's 11-stage pipeline. Studio identity, pipeline, and crew structure are entirely self-contained per studio. Studio folder names use kebab-case (e.g., casual-games, narrative-studio,…

The file

We split this CLAUDE.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No other studios have been instantiated yet.

    line 23
  2. Distinctive:

    Each studio defines its own pipeline independently: Do not assume future studios will inherit the Casual Games Studio's 11-stage pipeline.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

studio/ — The Studio

Entry point for the Studio system. Contains all active and future creative game development studios.

What Lives Here

studio/
├── README.md          ← Studio index + naming conventions for future studios
└── casual-games/      ← Only active studio

Active Studios

StudioPathStatusEngine
Casual Games Studiocasual-games/Active — Stage 0-readyUnity 6.3 LTS

No other studios have been instantiated yet. Future studios will be added as sibling folders to casual-games/ following the conventions below.

Future Studio Conventions

New studios follow this structure:

studio/<studio-name>/
├── library/       ← Studio knowledge hub
├── pipeline/      ← Studio-specific pipeline definition
├── projects/      ← Per-game project folders (kebab-case slugs)
└── team/crew/     ← Studio crew by division

Each studio defines its own pipeline independently. Do not assume future studios will inherit the Casual Games Studio's 11-stage pipeline. Studio identity, pipeline, and crew structure are entirely self-contained per studio.

Studio folder names use kebab-case (e.g., casual-games, narrative-studio, puzzle-lab).

Architecture Principle

Studios are architecturally independent of The Company. They share governance through the ASGF framework and report through the authority hierarchy, but their pipelines, crew structures, and project conventions are self-contained. Do not import company pipeline stage numbers or department structures into studio work.

Where to Start

For the Casual Games Studio — the only active studio — start at:

studio/casual-games/library/overview/casual-games-studio.md

For studio-level conventions and the index of all studios:

studio/README.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free