agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/AGENTS.md

agents-arwaky

AGENTS.md0 starsChanged 26 days agoMITView on GitHub

agents-arwaky operational guide.

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

    Every command must match the exact CI gate.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

agents-arwaky

Runtime

  • Language: Python 3.10+, Rust (cargo), Node.js 18+ (pnpm), Bun, C.
  • Environment: host bare-metal; XDG base directories. No Docker. Anytype is the only Podman-containerized service. OmniRoute runs host-native.
  • Artifacts: XDG prefixes. Data in ${XDG_DATA_HOME:-$HOME/.local/share}/, config in ${XDG_CONFIG_HOME:-$HOME/.config}/, cache in ${XDG_CACHE_HOME:-$HOME/.cache}/, launchers in ${XDG_BIN_HOME:-$HOME/.local/bin}/.
python3 --version
uv sync

Project Quick Facts

INPUT = config/manifest.json (tool registry, SSOT) OUTPUT = XDG-compliant host binaries plus MCP server configs plus launchers

Pipeline

manifest, adapter, capability, orchestrator, surface CLI

Project Structure

agents-arwaky/
├── config/manifest.json   # tool registry (SSOT)
├── modules/               # AES features (vertical slices)
├── internal/              # sibling repos (submodules)
└── vendor/                # upstream tools (submodules)

Commands

Every command must match the exact CI gate.

# Tests
python3 -m pytest modules/ -q                            # whole-workspace Python tests
python3 -m pytest modules/<feat>/tests -q                # one feature
python3 -m pytest modules/<feat>/tests/unit_<feat>.py -q # one file

# Lint / types / architecture
python3 -m ruff check modules/ --fix                     # matches ci.yml ruff job
python3 -m mypy modules/ --strict                        # type checker
lac scan . --format json                                  # architecture scanner (lint-arwaky)
lac scan . --fix                                           # dry-run variant, fixer is destructive

Related Documents

  • ARCHITECTURE.md - the 7-layer AES vertical-slicing system.
  • ROADMAP.md - cross-cutting feature roll-up and status.
  • CONTRIBUTING.md - how to add, update, or remove a vendor tool.
  • README.md - quickstart and operator workflow.

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