agentleFS
Sign inStart free
jammyfujammyfu/open-game-skills/skills/disciplines/deck-build/SKILL.md

deck-build

Skill12 starsChanged 23 days agoMITView on GitHub

Use when cards or card-like actions move through a deck/hand/discard/exhaust system and the project needs stable card identity, zone transactions, draw/shuffle rules and replayable RNG ownership.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the deck model: fixed, constructed, draft, run-builder, rotating-pool, hybrid, or existing.

    line 8

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

Deck build

Ask the deck model: fixed, constructed, draft, run-builder, rotating-pool, hybrid, or existing.

Contract

Publish:

  • stable deck_ruleset_id and revision
  • stable card_id plus card-definition revision
  • legal deck constraints
  • canonical zone IDs and move rules
  • draw/shuffle/mulligan policy
  • cost/resource owner references
  • rng-seed stream reference for stochastic ordering
  • persistence/reset behavior

Ownership

This skill owns deck composition rules and card movement between canonical zones. Card effects route to their gameplay owners; resources route to their own meter/economy skill; RNG algorithm/state stays in rng-seed.

Rules

  1. Each zone transition has transaction/request identity so duplicate callbacks cannot draw, discard or exhaust the same card twice.
  2. Shuffle/draw order is reproducible from declared stream state when determinism is required.
  3. Starter viability, encounter order and required content are project policies, not deck-system invariants.
  4. Card display order/animation is not canonical zone order unless explicitly authored.
  5. Ruleset changes increment revision and define migration for persisted decks/runs.

Acceptance

Given the same ruleset revision, canonical zones and RNG stream state, the same draw/shuffle/move results occur. A reviewer can distinguish deck ownership from card effects, resource costs and presentation.

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