agentleFS
infeniainfenia/yukta/messaging/CLAUDE.md

yukta / messaging

CLAUDE.md1 starsChanged 20 days agoApache-2.0View on GitHub

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md 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
CLAUDE.md

Messaging Module CLAUDE.md

Overview

Shared messaging abstractions and implementations.

Architecture

Message-based inter-node communication framework:

  • Message: Generic interface for an atomic data packet (header + payload).
  • NodeMessageChannel: Transport abstraction between workflow nodes — DirectNodeMessageChannel (in-memory pass-through) is the only implementation. Register your own NodeMessageChannelProvider bean to override it.

Key Files

  • src/main/java/com/infenia/yukta/message/Message.java
  • src/main/java/com/infenia/yukta/message/channel/NodeMessageChannel.java (+ DirectNodeMessageChannel)
  • Module guide: ../docs/contributing/modules/messaging.mdx (module guide); open risks, bugs and review findings: GitHub issues labelled messaging (gh issue list -l messaging; risks also carry risk); evolution path and quality lenses: ../design/assessments/messaging.md

Build & Development Commands

# Run messaging tests
yk gradle :messaging:test

Imports

@.claude/rules/coding-standards.md @.claude/rules/git-workflow.md

Testing speed

Follow the tiered "Test Execution Policy (speed)" in the root CLAUDE.md: run --tests for the classes you changed first; full :messaging:test only when many files changed.

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.