agentleFS
pdparchitectpdparchitect/noodle/Applet/AGENTS.md

noodle / Applet

AGENTS.md259 starsChanged 35 days agoApache-2.0View on GitHub

Keep the companion application, runners and package handling in this folder. Integration compatibility uses the versioned Protocol package. Keep Applet release notes in CHANGELOG.md here and Noodle integration notes in the root changelog. Do not publish releases without the user's explicit request. The guidance bots read about noodlets lives in Protocol/Sources/AppletBridge/AppletGuidance.swift. Noodle's applet tool gives it to bots; do not copy it anywhere else. Test package validation, single-instance ownership, and runtime diagnostics. Verify the signed sandboxed bundle before claiming a…

The file

We split this AGENTS.md 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
  1. Very specific:

    Keep the companion application, runners and package handling in this folder.

    line 3
  2. Distinctive:

    Do not publish releases without the user's explicit request.

    line 6

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

Noodle Applet

Keep the companion application, runners and package handling in this folder. Integration compatibility uses the versioned Protocol package. Keep Applet release notes in CHANGELOG.md here and Noodle integration notes in the root changelog. Do not publish releases without the user's explicit request.

The guidance bots read about noodlets lives in Protocol/Sources/AppletBridge/AppletGuidance.swift. Noodle's applet tool gives it to bots; do not copy it anywhere else. Test package validation, single-instance ownership, and runtime diagnostics. Verify the signed sandboxed bundle before claiming a runtime or capability works.

The Xcode project is generated by Tuist from Project.swift; change that, never the generated project.

Launch arguments for verification runs are matched by digest, so no name appears in the binary. Only one the release checks run against the packaged app ships in every build; any other goes under #if NOODLE_DEV_HOOKS.

README.md is for people using Applet; do not document code in it. Follow the no-code-docs skill.

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.