SyncytiumMD / rules
Cursor rule6 starsChanged 8 days agoMITView on GitHub
Active Syncytium handoff and agent state
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,181 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
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/testing-standards.mdcCursor rule
- llms-full.txtllms.txt
- llms.txtllms.txt
The file
We split this syncytium-handoff.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Do not edit manually unless you plan to run reverse-sync.
- Distinctive: line 31
Notes: No npm credential exists locally or in GitHub secrets, so 0.3.1 cannot be published until the npm-side trusted publisher exists.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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.
Files
--- description: Active Syncytium handoff and agent state alwaysApply: true --- <!-- ⚠️ AUTO-GENERATED BY SYNCYTIUM-MD ⚠️ This file is automatically synchronized from .syncytium/ Do not edit manually unless you plan to run reverse-sync. Source of truth: .syncytium/ --> # 🤝 Syncytium Active Handoff ### 🤝 Live Handoff Status - **Active Agent:** `opencode` (Next: `Human`) - **Status:** `BLOCKED` - **Current Goal:** v0.3.1 npm publish and MCP Registry listing are blocked on npm OIDC trusted-publisher setup - **Pending Tasks:** - [ ] On npmjs.com add a Trusted Publisher for syncytium-md: GitHub Actions, owner mrcbrbn5361, repo SyncytiumMD, workflow release.yml - [ ] Re-run Release run 42053623967, then run the MCP Discovery workflow (or re-run 42053623576) - [ ] Rotate any credential that was pasted into chat earlier - **Recently Touched:** - `.gitattributes` - `src/core/storage.ts` - `server.json` - `src/mcp/safety.ts` - `.github/workflows/release.yml` - `.github/dependabot.yml` - `scripts/build-discovery.mjs` - `.github/workflows/discoverability.yml` - **Notes:** No npm credential exists locally or in GitHub secrets, so 0.3.1 cannot be published until the npm-side trusted publisher exists. After that, both workflows are idempotent and need no secrets. - **Last Updated:** 2026-11-05T15:24:48.885Z
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
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.