agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/context-shards/SKILL.md

context-shards

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Build and use per-sequence project context shards so an agent can work on a feature film without loading the whole project state.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the current durable project state before you make a decision.

    line 14
  2. Very specific:

    Use ../../scripts/context_shards.py for deterministic state changes or checks.

    line 16
  3. Distinctive:

    If the result blocks progress, keep the current Todo target blocked until the problem is fixed.

    line 18
  4. Very specific:

    Do not load the full feature-film state when a sequence shard is sufficient.

    line 22
  5. Distinctive:

    Do not treat a shard as a second canon.

    line 23
  6. Distinctive:

    Do not infer completion from file existence alone.

    line 24
  7. Distinctive:

    Do not hide an exception. Record the exception and the reason.

    line 25
  8. Distinctive:

    Use global checks only when the check needs global evidence.

    line 27

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

Context Shards

Use

  1. Read ../../references/CONTEXT_SHARDS.md.
  2. Read the current durable project state before you make a decision.
  3. Work on the smallest valid SEQ-###, job frontier, or global gate.
  4. Use ../../scripts/context_shards.py for deterministic state changes or checks.
  5. Save the result before you continue.
  6. If the result blocks progress, keep the current Todo target blocked until the problem is fixed.

Rules

  • Do not load the full feature-film state when a sequence shard is sufficient. A shard includes the relevant canon and current story-state subset needed for its related character/location/prop IDs.
  • Do not treat a shard as a second canon; authoritative project files still win.
  • Do not infer completion from file existence alone.
  • Do not hide an exception. Record the exception and the reason.
  • Preserve stable IDs and project-relative paths.
  • Use global checks only when the check needs global evidence.

Done

The requested feature-scale state is written, validated, and traceable from durable project files.

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