agentleFS
docxologydocxology/codomyrmex/.devcontainer/AGENTS.md

codomyrmex

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Dev Container definition for reproducible VS Code / GitHub Codespaces environments: a Python 3.11 image with uv, just, and Node LTS, the repository's lint and type-check extensions, and forwarded ports for the local docs and dashboard servers. - devcontainer.json — the whole definition: - image: mcr.microsoft.com/devcontainers/python:3.11, the requires-python floor and the pull-request CI interpreter; - features: just and Node LTS; - postCreateCommand: installs uv with the upstream installer, then runs uv sync --all-groups (dev, docs, lint, and test groups; no…

The file

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

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Keep the image at the supported Python floor unless requires-python and the CI matrix move with it.

    line 38
  2. Very specific:

    When a server's default port changes in code, update forwardPorts and portsAttributes together.

    line 43
  3. Very specific:

    Keep editor settings aligned with repository tooling (Ruff for format and lint, ty for type checks).

    line 45

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

AGENTS.md — codomyrmex/.devcontainer

Purpose

Dev Container definition for reproducible VS Code / GitHub Codespaces environments: a Python 3.11 image with uv, just, and Node LTS, the repository's lint and type-check extensions, and forwarded ports for the local docs and dashboard servers.

Key Files

  • devcontainer.json — the whole definition:
    • image: mcr.microsoft.com/devcontainers/python:3.11, the requires-python floor and the pull-request CI interpreter;
    • features: just and Node LTS;
    • postCreateCommand: installs uv with the upstream installer, then runs uv sync --all-groups (dev, docs, lint, and test groups; no optional extras);
    • VS Code settings: Ruff as formatter and fixer from .venv/bin/ruff, the ty extension, interpreter .venv/bin/python;
    • forwardPorts: 8000 (docs server), 8787 (admin dashboard), 8888 (PAI dashboard);
    • remoteUser: vscode.
  • README.md — human signpost.

Dependencies

  • pyproject.toml — requires-python and the [dependency-groups] that uv sync --all-groups installs.
  • justfile — recipes available through the just feature.
  • Port owners: mkdocs serve (make serve-docs / just docs-serve, port 8000), codomyrmex dashboard (default 8787 in src/codomyrmex/cli/core.py), and the PAI PM server (PAI_PM_PORT, default 8888 in src/codomyrmex/website/pai_mixin.py).
  • The production image is built separately from Dockerfile (Python 3.13, uv sync --frozen --no-dev); neither file is derived from the other.
  • Parent: ../README.md · Root contract: ../AGENTS.md

Development Guidelines

  • Keep the image at the supported Python floor unless requires-python and the CI matrix move with it; drift here produces environments where the test suite fails for dependency reasons rather than code reasons.
  • Optional module extras are not installed; add them explicitly (uv sync --all-groups --extra <module>) before running that module's tests.
  • When a server's default port changes in code, update forwardPorts and portsAttributes together.
  • Keep editor settings aligned with repository tooling (Ruff for format and lint, ty for type checks); do not add a second formatter.

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.