agentleFS
Sign inStart free
lucasluslucaslus/dsh-desktop/examples/AGENTS.md

dsh-desktop / examples

AGENTS.md1 starsChanged 2 months agoMITView on GitHub

Runnable harness compositions. examples/ is one workspace member and the module-resolution root for runnable and test Cordis configs; it is not a build target. package.json declares the packages loaded by those configs, while each leaf's private package.json remains metadata only. Extract reusable logic into packages/, where per-file coverage and README gates apply. Examples keep only cordis.yml wiring, demo artifacts, and e2e/snapshot scenarios; app package bins own boot glue. Each example has both: Keyless process smokes use @deepseek-ai/dsh-loader-smoke for Loader launch…

  • Reads credentials

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

    Do not inventory example tests here.

    line 16

≈ “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.md — Examples

Runnable harness compositions. examples/ is one workspace member and the module-resolution root for runnable and test Cordis configs; it is not a build target. package.json declares the packages loaded by those configs, while each leaf's private package.json remains metadata only.

Extract reusable logic into packages/, where per-file coverage and README gates apply. Examples keep only cordis.yml wiring, demo artifacts, and e2e/snapshot scenarios; app package bins own boot glue.

E2E smokes

Each example has both:

  • Keyless: boot the real cordis.yml through the Loader, drive it, and assert output and clean exit. Catches invalid Loader exports that hand-mounted tests miss (postmortem).
  • With-key: send a live-model prompt and verify external state, not the model's claim. Self-skip without DEEPSEEK_API_KEY; see testing.md.

Keyless process smokes use @deepseek-ai/dsh-loader-smoke for Loader launch resolution; terminal tests wrap that launch in a pseudo-terminal. Tests supply paths, environment, input, and assertions. Every checked-in test Cordis config lives under its corresponding examples/<agent>/ leaf. Map a package-owned config to examples/<agent>/tests/fixtures/<group>/<package>/cordis.yml, keep its driver and assertions package-local, and declare every package it names in both root tsconfig.json references and examples/package.json.

Do not inventory example tests here; the tests/ trees and root scripts are authoritative.

In cordis.yml, comment only non-obvious wiring, load-order consequences, replay, security boundaries, and configuration scope. Do not narrate visible entries; use dsh-prose-standard for required coverage and editorial judgment.

See the root AGENTS.md for repo-wide conventions and docs/architecture.md for the design.

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.

Reviews can't be read right now.

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