agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/day-night/SKILL.md

day-night

Skill13 starsChanged 24 days agoMITView on GitHub

Use when world time changes lighting, schedules, availability, stealth, spawning or other systems and the project needs one versioned clock contract with explicit consumers.

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 mode: cosmetic, scheduled-world, gameplay-linked, externally-driven, hybrid, or existing.

    line 8

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

Day night

Ask the mode: cosmetic, scheduled-world, gameplay-linked, externally-driven, hybrid, or existing.

Contract

Publish:

  • stable time_cycle_id and revision
  • clock source and time scale/pause policy
  • canonical time state and boundary definitions
  • stable transition identity for dawn/day/dusk/night or project equivalents
  • persistence/suspend behavior
  • list of authorized effect consumers

Ownership

day-night owns canonical world-time state and transition events. Lighting, spawn schedules, stealth, weather, quests and audio consume that state through their own skills. It does not rewrite combat clocks or save bytes.

Rules

  1. A transition is emitted once for a given state boundary/revision; resume or duplicate callbacks cannot replay it accidentally.
  2. Time skips, sleeps and scripted jumps declare source and resulting transition sequence.
  3. Save/load restores canonical time plus policy revision; presentation interpolations are not the source of truth.
  4. Systems may ignore world time or depend on it according to project policy; neither choice is universal.

Acceptance

Given the same time_cycle_id, revision, clock source and start state, the same canonical time and transition identities result. Consumers can change presentation or schedules without becoming a second time owner.

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.