agentleFS
butterbase-aibutterbase-ai/butterbase-skills/skills/journey-durable/SKILL.md

journey-durable

Skill535 starsChanged 5 months agoMITView on GitHub

Use as the durable-objects build stage of the Butterbase journey. Implements the Durable section of 02-plan.md by delegating to durable-objects. Calls manage_durable_objects (deploy). Skipped if the plan has no per-key stateful actors (chat rooms, multiplayer, rate limiters).

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke …

    line 18
  2. Very specific:

    Refresh docs: Call butterbase_docs with topic: "functions".

    line 27
  3. Very specific:

    Verify with manage_durable_objects action: list and action: get.

    line 33
  4. Very specific:

    After all DOs are done, tick - [x] durable in 00-state.md, set current_stage: to the next unchecked stage.

    line 36

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

Journey: Durable Objects

Stage 3i of the guided journey. Deploy stateful per-key actors.

When to use

  • Dispatched by journey when current_stage: durable.
  • Directly via /butterbase-skills:journey-durable.
  • Skipped (annotated (n/a)) if the plan has no Durable section.

Preflight

If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke butterbase-skills:journey-preflight first. Wait for it to return successfully before proceeding.

Inputs

  • docs/butterbase/02-plan.md — the Durable section.
  • docs/butterbase/00-state.md — for app_id.

Procedure

  1. Refresh docs. Call butterbase_docs with topic: "functions". For Durable Object class structure, also WebFetch https://docs.butterbase.ai/durable-objects. Skip if cache is fresh.

For each Durable Object class in the plan:

  1. Print: "About to deploy Durable Object: <name>. Proceed?". Wait for yes.
  2. Invoke butterbase-skills:durable-objects via the Skill tool with the DO spec and app_id. The wrapped skill calls manage_durable_objects action: deploy, sets env via set_env if needed.
  3. Verify with manage_durable_objects action: list and action: get.
  4. Append one line per DO to docs/butterbase/04-build-log.md: <ISO timestamp> durable manage_durable_objects <do-name> ok
  5. After all DOs are done, tick - [x] durable in 00-state.md, set current_stage: to the next unchecked stage.
  6. Return to journey orchestrator (or ask "Continue to the next stage? (yes/no)").

Outputs

  • Deployed Durable Object classes.
  • One line per DO in 04-build-log.md.

Anti-patterns

  • ❌ Sharing state across users via a single DO key — keys should be naturally per-room / per-user / per-resource.

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.