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

djls-salsa

Skill207 starsChanged yesterdayApache-2.0View on GitHub

Use when editing Salsa inputs, tracked functions, database traits, setters, SemanticDb, crate::Db, invalidation behavior, or incremental computation in django-language-server. Handles project-specific Salsa conventions and required impl updates.

We split this skill into the rules it gives an agent

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

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before changing Salsa inputs, tracked functions, database traits, or query plumbing.

    line 8
  2. Very specific:

    Use #[returns(ref)] on fields returning owned types.

    line 14
  3. Very specific:

    When adding SemanticDb methods, update impls in:

    line 20
  4. Very specific:

    When adding crate::Db methods in djls-semantic, update all test database impls.

    line 23
  5. Very specific:

    Search with rg, not grep:

    line 27

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

Use this before changing Salsa inputs, tracked functions, database traits, or query plumbing.

Setter and invalidation rules

  • Setter API is project.set_field(db).to(value), not .set_field(db, value).
  • Compare before setting because setters always invalidate.
  • Use #[returns(ref)] on fields returning owned types.
  • Salsa returns &T for #[returns(ref)], so compare with &new_value.
  • Tracked return types need PartialEq for backdate optimization.

Required updates

  • When adding SemanticDb methods, update impls in:
    • djls-db/src/db.rs
    • djls-bench/src/db.rs
  • When adding crate::Db methods in djls-semantic, update all test database impls. Missing impls produce E0046.

Checks

Search with rg, not grep:

rg "impl crate::Db" crates/djls-semantic/ -g '*.rs'
rg "trait SemanticDb|impl SemanticDb" crates/ -g '*.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