agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/design/liveops-design/SKILL.md

liveops-design

Skill105 starsChanged 8 months agoMITView on GitHub

Design seasonal, event, or post-launch content that extends engagement without destabilizing the core product.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  1. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  2. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

≈ “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.

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

Liveops Design

Purpose

Design seasonal, event, or post-launch content that extends engagement without destabilizing the core product.

Use When

  • the game has post-launch events, cadence, shops, or rotating content
  • retention needs event support
  • live content needs safer design rules

Inputs

  • economy model
  • retention goals
  • content cadence
  • telemetry signals

Process

  1. define the event or season purpose
  2. set entry requirements, rewards, and economy impact
  3. plan live tuning and rollback options
  4. coordinate messaging, store, and content dependencies
  5. specify analytics needed to judge success

Outputs

  • liveops brief
  • reward plan
  • operational guardrails
  • monitoring requirements

Quality Bar

  • supports the core fantasy and player goals
  • defines readable rules, edge cases, and feedback
  • creates concrete hooks for tuning, telemetry, and QA

Common Failure Modes

  • adding systems that do not serve the core loop
  • shipping vague rules that QA and engineering must guess at
  • tuning without instrumentation or hypotheses

Related Agents

  • liveops-manager
  • economy-designer
  • telemetry-analyst

Related Commands

  • liveops-brief
  • telemetry-plan
  • patch-notes

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

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