agentleFS
Sign inStart free
fusebase-devfusebase-dev/fusebase-flow/CLAUDE.md

fusebase-flow

CLAUDE.md9 starsChanged 27 days agoMITView on GitHub

This repo runs Fusebase Flow v5.11. Read AGENTS.md (unless its Flow overlay section is already in context), FLOW_RULES.md through ## Amendment log, both mandatory skill bodies, flow-skills/role-discipline/references/<role>.md, and the active workflow/ticket artifacts. Canonical provider details are in the recovery-owned adapter below. For maintenance work in this repository, also read docs/maintainer-execution.md. It is not copied into consumers. Read AGENTS.md unless its FuseBase Flow — workflow lifecycle overlay section is already in context, then FLOW_RULES.md through ## Amendment log. Claude Code supplies…

The file

Create a free account to mount
Files
CLAUDE.md

CLAUDE.md — Claude Code adapter for Fusebase Flow

This repo runs Fusebase Flow v5.11. Read AGENTS.md (unless its Flow overlay section is already in context), FLOW_RULES.md through ## Amendment log, both mandatory skill bodies, flow-skills/role-discipline/references/<role>.md, and the active workflow/ticket artifacts. Canonical provider details are in the recovery-owned adapter below.

For maintenance work in this repository, also read docs/maintainer-execution.md. It is not copied into consumers.

<!-- CUSTOM:SKILL:BEGIN -->

FuseBase Flow — Claude Code adapter

Read AGENTS.md unless its FuseBase Flow — workflow lifecycle overlay section is already in context, then FLOW_RULES.md through ## Amendment log. Claude Code supplies skill descriptions/metadata, not skill bodies. Read flow-skills/communication/SKILL.md, flow-skills/role-discipline/SKILL.md, and the attested role's reference once unless each exact body is already in context. Read the active workflow and ticket/handoff. Use the attestation and state footer from FLOW_RULES.md.

Claude surfaceCanonical owner
lifecycle skillsflow-skills/ mirrored to .claude/skills/
role agentsagents/ mirrored to .claude/agents/
commands (/fusebase-health, /onboard, /product-owner, /handoff, /token-waste-audit, /find-wasted-effort, /find-wasted-code, /step-out)hooks/local/fusebase-flow-overlays/commands/ mirrored to .claude/commands/
lifecycle hookshooks/handlers/ via .claude/settings.json.example
CLI runtime/quality guidanceCLI-owned .claude/skills/, .claude/agents/, .claude/hooks/

Hooks are opt-in until .claude/settings.json.example is merged into .claude/settings.json; Git hooks remain the fallback. Existing Fusebase CLI runtime/MCP/SDK rules override generic Flow guidance; Flow owns the lifecycle. For active context, commands, install/update recovery, and mixed-fleet behavior, use AGENTS.md; do not reprint those procedures here.

<!-- CUSTOM:SKILL:END -->

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