mrcbrbn5361mrcbrbn5361/SyncytiumMD/llms.txt

SyncytiumMD

llms.txt6 starsChanged 7 days agoMITView on GitHub

One canonical .syncytium/ context transpiled into every AI coding tool, with a multi-agent handoff baton and a lease-based workspace lock. Every input is validated with zod before it reaches the engine, every tool declares MCP safety annotations, and all calls are rate limited in-process.

In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/adapter-standards.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/release-criteria.mdcCursor rule
- .cursor/rules/security.mdcCursor rule
- .cursor/rules/syncytium-architecture.mdcCursor rule
- .cursor/rules/syncytium-handoff.mdcCursor rule
- .cursor/rules/testing-standards.mdcCursor rule
- llms-full.txtllms.txt

The file

We split this llms.txt 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

Distinctive:
Every input is validated with zod before it reaches the engine, every tool declares MCP safety annotations, and all calls are rate limited …
line 37

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt 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

llms.txt

# SyncytiumMD

> One canonical `.syncytium/` context transpiled into every AI coding tool,
> with a multi-agent handoff baton and a lease-based workspace lock.

- Version: 0.3.1
- npm: https://www.npmjs.com/package/syncytium-md
- Repository: https://github.com/mrcbrbn5361/SyncytiumMD
- MCP Registry name: io.github.mrcbrbn5361/syncytiummd
- License: MIT

## Run the MCP server

```json
{
  "mcpServers": {
    "syncytium": {
      "command": "npx",
      "args": [
        "--ignore-scripts",
        "-y",
        "-p",
        "syncytium-md@0.3.1",
        "syncytium-mcp"
      ]
    }
  }
}
```

```bash
npx -y -p syncytium-md@0.3.1 syncytium-mcp
```

## Tools (23)

Every input is validated with zod before it reaches the engine, every tool
declares MCP safety annotations, and all calls are rate limited in-process.

- `syncytium_create_rule` — Create a canonical rule (write)
- `syncytium_diff` — Check context drift (read)
- `syncytium_doctor` — Read-only workspace health check (read)
- `syncytium_get_context` — Get canonical context (read)
- `syncytium_get_graph` — Get the knowledge graph (read)
- `syncytium_get_history` — Get handoff history (read)
- `syncytium_handoff` — Record agent handoff (write)
- `syncytium_import` — Import unmanaged rule files (write)
- `syncytium_lint` — Lint canonical content (read)
- `syncytium_list_decisions` — List ADRs (read)
- `syncytium_list_rules` — List canonical rules (read)
- `syncytium_list_trash` — List recoverable deletions (read)
- `syncytium_lock_acquire` — Acquire the workspace lease (write)
- `syncytium_lock_release` — Release the workspace lease (write)
- `syncytium_lock_status` — Read lease status (read)
- `syncytium_record_decision` — Record an ADR (write)
- `syncytium_remove_decision` — Archive and remove an ADR (destructive)
- `syncytium_remove_rule` — Archive and remove a canonical rule (destructive)
- `syncytium_restore` — Restore an archived rule or ADR (write)
- `syncytium_sync` — Regenerate bridge files and prune orphans (destructive)
- `syncytium_update_rule` — Update a canonical rule (write)
- `syncytium_validate` — Validate config and rule frontmatter (read)
- `syncytium_validate_fix` — Repair invalid config or frontmatter (write)

## Canonical workspace

- `.syncytium/rules/` — stack-aware rules with zod-validated frontmatter
- `.syncytium/memory/decisions.md` — architectural decision records
- `.syncytium/HANDOFF.md` — live agent handoff baton
- `.syncytium/memory/lock.json` — machine-local workspace lease
- `syncytium sync` — regenerate bridge files; `syncytium diff --check` — drift gate

## More

- `llms-full.txt` — full rule and ADR text
- `server.json` — MCP Registry manifest
- `README.md` — setup and CLI reference

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