agentleFS
Sign inStart free
MigoXLabMigoXLab/dingo/.cursor/rules/project-architecture.mdc

dingo / rules

Cursor rule757 starsChanged 7 months agoApache-2.0View on GitHub

Dingo project architecture — references AGENTS.md for full context

  • Reads credentials

We split this project-architecture.mdc into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Plugin architecture: All evaluators use @Model.rule_register() or @Model.llm_register() decorators.

    line 13
  2. Very specific:

    Evaluator contract: Every evaluator eval() method must return EvalDetail with metric, status (bool), label (list), and reason (list).

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
project-architecture.mdc
---
description: Dingo project architecture — references AGENTS.md for full context
globs:
alwaysApply: true
---

# Dingo — Quick Reference

**Full agent instructions**: see `AGENTS.md` at project root (tech stack, directory structure, core concepts, development conventions, config maintenance rules).

## Key Rules (always apply)

1. **Plugin architecture**: All evaluators use `@Model.rule_register()` or `@Model.llm_register()` decorators. Never modify the registration system.
2. **Data model**: `Data` uses `extra = "allow"` — do not add fixed fields unless absolutely necessary. Access optional fields with `getattr(data, 'field', default)`.
3. **Lazy imports**: Optional heavy dependencies (`pyarrow`, `transformers`, `sqlalchemy`, `boto3`, etc.) must use lazy imports inside methods, not top-level imports.
4. **Evaluator contract**: Every evaluator `eval()` method must return `EvalDetail` with `metric`, `status` (bool), `label` (list), and `reason` (list).
5. **Dependencies**: Core deps in `requirements/runtime.txt`, optional in `requirements/datasource.txt`. New optional deps → add to `setup.py` extras_require.
6. **MCP Server**: Entry point is `mcp_server.py`, uses FastMCP + SSE. Environment variables for LLM config (`OPENAI_API_KEY`, etc.).
7. **Three interfaces**: SDK (Python API), CLI (`dingo eval`), MCP Server. All share the same `InputArgs` → `Executor` pipeline.
8. **Testing**: `pytest test/scripts --ignore=test/scripts/data`. Integration tests via CLI with configs in `.github/env/`.

Download now (ZIP)

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

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