agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/map-systems/SKILL.md

map-systems

Skill9 starsChanged 7 months agoMITView on GitHub

Enumerate and categorize all game systems. Create design/gdd/systems-index.md. Identify dependencies between systems.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use asset-spec, create-control-manifest 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.
  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 8 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 8 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Read design/gdd/ for existing GDDs

    line 16
  2. Very specific:

    Read src/ for code organization hints

    line 17
  3. Very specific:

    Check production/sprints/ for recently worked-on systems

    line 18

“Common” is measured: kept by at least 6 in 10 of the 15 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.

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

/map-systems — System Inventory

Delegate to: game-designer

Purpose

A "system" is a cohesive gameplay feature with its own rules, data, and player interaction (e.g., Combat, Inventory, Shop, Quests, Friends). The systems index is the source of truth for "what does this game have."

Steps

1. Scan Existing State

  • Read design/gdd/ for existing GDDs
  • Read src/ for code organization hints
  • Check production/sprints/ for recently worked-on systems

2. Identify Systems

List every system, planned or implemented:

Common Roblox game systems:

  • Core Loop: the primary gameplay action
  • Combat: damage, abilities, weapons
  • Inventory: items, equipment, storage
  • Progression: XP, levels, skills
  • Economy: currencies, shops, trading
  • Quests: missions, objectives, rewards
  • Social: friends, parties, guilds, chat
  • UI/HUD: menus, notifications
  • Onboarding: tutorial, FTUE
  • Daily Rewards: login streaks
  • Codes: redemption system
  • Settings: audio, graphics, controls
  • Monetization: GamePasses, DevProducts
  • Leaderboards: global rankings
  • Events: seasonal content
  • Cosmetics: skins, pets, accessories

3. Categorize by Status

For each system:

  • Not started — exists only as an idea
  • In design — GDD being written
  • In implementation — code being written
  • Implemented — feature in code, not yet polished
  • Polished — feature complete and tested
  • Live — shipped to players

4. Identify Dependencies

Which systems depend on which?

Example:

Shop
├── depends on: Inventory (to place bought items)
├── depends on: Economy (to charge currency)
└── depends on: UI (to display items)

Trading
├── depends on: Inventory
├── depends on: Economy (for trade tax)
├── depends on: Friends (to choose trade partner)
└── depends on: DataStore (for atomic swap)

5. Priority Scoring

For each system, assess:

  • Player value (1-5): How important for the player experience?
  • Effort (1-5): How much work to build?
  • Risk (L/M/H): How uncertain is the implementation?
  • Monetization impact (1-5): Does this drive revenue?

High player value + low effort = do first High player value + high effort = plan carefully Low value + low effort = defer Low value + high effort = consider cutting

6. Generate Index

Save to design/gdd/systems-index.md:

# Systems Index

**Last Updated**: YYYY-MM-DD

## Summary
- Total systems: X
- Not started: X
- In design: X
- In implementation: X
- Implemented: X
- Polished: X
- Live: X

## Systems

### Core Loop
- **Status**: Implemented
- **Priority**: P0 (critical)
- **Value**: 5 | **Effort**: 4 | **Risk**: Medium
- **GDD**: `design/gdd/core-loop-gdd.md`
- **Depends On**: (none — core)
- **Depended On By**: Combat, Progression, Economy
- **Notes**: [any context]

### Combat
- **Status**: In implementation
- **Priority**: P0
- **Value**: 5 | **Effort**: 4 | **Risk**: Medium
- **GDD**: `design/gdd/combat-gdd.md`
- **Depends On**: Core Loop, Inventory
- **Depended On By**: Quests
- **Notes**: Hit detection in progress

...

## Dependency Graph
[ASCII or mermaid diagram showing system dependencies]

## Priority List (recommended build order)
1. Core Loop
2. Combat
3. Inventory
4. Progression
5. ...

7. Present to User

Present the index for review. On approval, save to disk. Offer to update individual GDD statuses or add missing system GDDs.

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.