agentleFS
infeniainfenia/yukta/plugin-api/CLAUDE.md

yukta / plugin-api

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 31

≈ “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

Plugin API Module CLAUDE.md

Overview

Plugin abstraction interfaces and base classes.

Build & Development Commands

# Run tests
yk gradle :plugin-api:test

Plugin Categories

  1. TriggerPlugin: Initiates workflows.
  2. ProcessorPlugin: Transforms or validates data.
  3. TerminalPlugin: Finalizes workflows.

Key Files

  • com.infenia.yukta.plugin.core.Plugin: Base interface for all workflow plugins.
  • com.infenia.yukta.plugin.type.TriggerPlugin, .type.ProcessorPlugin, .type.TerminalPlugin: Category-specific plugin interfaces.
  • com.infenia.yukta.plugin.core.WorkflowContext, .core.PluginCategory, .core.PluginDescriptor: Shared plugin-execution types.
  • com.infenia.yukta.plugin.core.ConfigField and Plugin#getConfigSchema(): optional per-plugin config parameters (name, type, required, default, options) that the UI renders as a form. Default is empty, in which case the UI shows a raw JSON editor. Keep names in step with the keys the plugin reads from config.
  • com.infenia.yukta.plugin.core.PluginLogSink: live log lines. A plugin takes it from the Reactor context (WorkflowContext.LOG_SINK_KEY, absent outside a run) and calls line("stdout"|"stderr", text) as output appears; the engine writes each line whole to the execution log (split only above 16,000 chars), counts it as node activity, and then does not echo the node's output message again.
  • com.infenia.yukta.plugin.store: NodeCheckpointStore, SecretProvider.
  • Module guide: ../docs/contributing/modules/plugin-api.mdx (module guide); open risks, bugs and review findings: GitHub issues labelled plugin-api (gh issue list -l plugin-api; risks also carry risk); evolution path and quality lenses: ../design/assessments/plugin-api.md.

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 :plugin-api: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.