agentleFS
Sign inStart free
joshuadavidthomasjoshuadavidthomas/django-language-server/.agents/skills/djls-workspace-conventions/SKILL.md

djls-workspace-conventions

Skill207 starsChanged yesterdayApache-2.0View on GitHub

Use when adding or editing crates, Cargo.toml files, workspace dependencies, crate manifests, lints, versions, or project structure in django-language-server. Handles Rust workspace layout, dependency grouping, and new crate setup.

We split this skill into the rules it gives an agent

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

  • 7

    Very specific

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

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

    Use this before changing Cargo.toml, adding crates, or reorganizing workspace structure.

    line 8
  2. Very specific:

    Put all dependency versions in root [workspace.dependencies].

    line 13
  3. Very specific:

    Every crate uses [lints] workspace = true.

    line 21
  4. Very specific:

    Only djls carries the release version.

    line 22
  5. Very specific:

    Add the crate under crates/<name>/.

    line 26
  6. Very specific:

    Add it to root [workspace.dependencies] as an internal path dependency.

    line 27
  7. Very specific:

    Keep module files as folder.rs, not folder/mod.rs.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill 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
SKILL.md

DJLS Workspace Conventions

Use this before changing Cargo.toml, adding crates, or reorganizing workspace structure.

Rules

  • Crates live in crates/ and are auto-discovered by members = ["crates/*"].
  • Put all dependency versions in root [workspace.dependencies]; crates use dep.workspace = true.
  • Root dependency groups, in order:
    1. internal path crates
    2. pinned core deps: salsa, tower-lsp-server
    3. crates.io deps
    4. git deps: ruff_*
  • Alphabetize within each root dependency group.
  • In crate manifests, list internal deps before third-party deps, separated by a blank line.
  • Every crate uses [lints] workspace = true.
  • Only djls carries the release version. Library crates use version = "0.0.0".

Adding a crate

  1. Add the crate under crates/<name>/.
  2. Add it to root [workspace.dependencies] as an internal path dependency.
  3. In crates/<name>/Cargo.toml, use workspace dependencies and [lints] workspace = true.
  4. Keep module files as folder.rs, not folder/mod.rs.

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