agentsclimarketplace

Inventory equipment

Skill Firzus/agent-skills/skills/game/inventory-equipment

Architecture blueprint for inventory and equipment systems across gacha, ARPG/looter, and online/MMO games: instance-vs-count items, stable IDs, caps, gear RNG, affixes, crafting, enhancement, lock invariants, inventory UI, loadouts, transmog, trades, and dupe-safe persistence. Use when designing inventories, gear generation, crafting, equipment screens, trade flows, or when players destroy rare items, sets double-apply, sorts jump, or items dupe.From its SKILL.md

Install
npx -y skills add Firzus/agent-skills --skill inventory-equipment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

6.8 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it

Inventory & Equipment

Build the inventory/equipment layer of a game — data model, gear generation, crafting, enhancement, UI, equipment, and (for online games) dupe-safe networked persistence. The skill spans three traditions and tells you which patterns are shared and which are mode-specific:

  • Gacha / live-service (Genshin via the Grasscutter GameItem schema + leaked-server RNG RE — the best public source on a AAA loot generator).
  • ARPG / looter (Diablo II/III/IV, Path of Exile 1/2, Last Epoch, Grim Dawn, Borderlands — affix systems, the deterministic↔random crafting dial).
  • Online / MMO (WoW, EVE, Albion, Lost Ark — server-authoritative ownership and the duplication-prevention playbook).

The architecture rule

One item model, two families: instances carry state, materials carry counts — and every protection is a model invariant, not a UI rule. In online games, add a third: the server owns item state; the client sends intent, never state.

definition (static table)  type, rarity, stack limit, equip type, curves
instance (equipment)       stable GUID + level/exp/lock/rolled-affix state
count (materials)          itemId + count, clamped to stackLimit
tabs                       ItemType -> polymorphic tab (lists vs id->stack maps)
the invariant example      isDestroyable() = !locked && !equipped

Reference map

FileCovers
data-model.mdInstance/count split, stable GUIDs, polymorphic tabs, caps as policy (warehouse vs scarcity), the BotW counterpoint, definition-vs-instance, persistence integration
gear-generation.mdThe Genshin 4-draw RNG pipeline (weighted pools, roll tiers, affix-ID encoding), ARPG affix systems (prefix/suffix, ilvl-gated tiers, weights, mutual exclusion), the deterministic↔random crafting spectrum (PoE orbs, D4 tempering/masterworking, LE forging potential, runewords, smart-loot), the constrained-guarantee funnel
enhancement.mdThe unified enhancement service, per-type tables, 80% recycling, exp-overflow refunds, batch QoL, dissolve/salvage loops, recycle-into-value
inventory-ui.mdLayouts (grid/list/Tetris-weight), loot-filter DSLs (PoE/Last Epoch), search syntax (DIM), stable sorts + filters + lock plans, compare tooltips, loadouts/transmog/wardrobe, controller vs mouse, mass-salvage safety
networking.mdServer-authoritative ownership, the duplication root-cause catalog with real incidents, 2-phase-commit trades + escrow + row locks + idempotency, append-only ledgers / event sourcing, reconciliation, anti-cheat, sharding/account-stash consistency
pitfalls.md16 failure modes (symptom → cause → prevention) with real incidents (D4 trade dupe, D3 integer-overflow gold dupe, D2 SoJ economy), debugging order, ship checklist

Build order (4 shippable tiers)

Tier 1 — Model and tabs
- [ ] Definition/instance/count split; stable GUIDs (never engine object IDs)
- [ ] Polymorphic tabs with per-tab caps; the new-item flag
- [ ] The lock invariant (isDestroyable = !locked && !equipped)
- [ ] Online: server-authoritative mutation path; client sends intent only
Tier 2 — Generation and enhancement
- [ ] Generation as weighted data tables (gacha 4-draw, or ARPG affix pools
      with ilvl gating); affix-ID encoding (stat+tier per ID)
- [ ] The crafting layer placed on the determinism dial (chosen deliberately)
- [ ] Unified enhancement service: per-type tables, recycling, batch with
      locked-excluded + high-value confirmation
Tier 3 — UI
- [ ] Virtualized grid/list + detail panel; async icons with placeholders
- [ ] Stable sort with instance-ID tiebreakers; filter + lock-plan rule engine
- [ ] Loot filter (drop-time) if acquisition outpaces curation
- [ ] Equip flows + compare panel (full before/after stats); mass-salvage
      gated by favorite/lock
Tier 4 — Equipment depth & online
- [ ] Set counting: equipped-only, per-character; bonuses as data affixes
- [ ] Loadouts: pin-by-instance vs clone-by-rule (choose + document fallback)
- [ ] Trade: 2-phase commit + escrow + row locks + idempotency + hash-chained
      log; soulbound gating on the most valuable items
- [ ] Persistence: ACID over an append-only ledger; reconciliation job

Key numbers (starting points — sourced anchors)

ParameterValueAnchor
Genshin main-stat poolssands 1334/1333/1333/500/500 weights; substat weights flat 6 / %·EM·ER 4 / crit 3leaked server datamine
Genshin roll tiers4 equiprobable: 70/80/90/100% of max; upgrade every +4datamine
PoE rare mod cap3 prefix + 3 suffix = 6; T1–T2 need ilvl ~82–86poewiki
D2 gamble oddsUnique 0.05% / Set 0.10% / Rare 10% / Magic ~89.85%; ilvl clvl−5..+4Arreat Summit
D3 smart loot~85% class-tailored / ~15% randomD3 2.0.1 notes
D4 (post-2.5)4 base affixes; tempering deterministic pick; masterwork max Quality 20Blizzard 2.5.0
Last Epochforging potential ~20–40 (rare→exalted); craftable cap T5community
Enhancement5★ +20 = 270,475 EXP; fodder recycling = base + 80% investedGenshin wiki
BotW pouchesweapons 8→19(+1), bows 5→13(+1), shields 4→20 (slot caps AS progression)wiki

Full sourced tables (with flagged "do-not-invent" gaps) live in each reference file.

Engine mapping (summary)

Generic blockUnity 6UE5 (5.4+) — Lyra is the first-party reference
ModelSO definitions + serializable instances linked by custom GUID (never GetInstanceID())ItemDefinition (const) + ItemInstance (runtime) + ItemFragments (composition)
Equipment statshand-rolled recompute pipelineequip = infinite GameplayEffect (handle-guaranteed removal); set bonuses via tag-count
ReplicationMirror/NGO ownershipregistered subobject lists + FFastArraySerializer (order NOT guaranteed → stable UI sorts)
UI gridUITK ListView virtualization (no native GridView → rows-of-cells)UMG ListView/TileView (pooled); CommonUI for controller nav
BackendUGS Cloud Code rolls + Economy writes (deny client Write)custom/PlayFab v2 (per-instance StackId, IdempotencyId)

Full detail in networking.md and the reference files.

What ships with it: 6 files

44.4 KB alongside SKILL.md

Gives 0 of the 12 instructions most operations skills give in ~1.7k tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • use one item model with two families
  • make every protection a model invariant
  • never use engine object IDs
  • enforce per-tab inventory caps
  • implement the lock invariant for item destruction
  • use server-authoritative item state for online games

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.