agentleFS
scaleapiscaleapi/scale-agentex-python/.cursor/rules/20_codegen_boundaries.mdc

scale-agentex-python / rules

Cursor rule25 starsChanged 41 days agoApache-2.0View on GitHub

Keep manual code separate from generated SDK code

We split this 20_codegen_boundaries.mdc into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Avoid modifying auto-generated files in src/agentex/ except where explicitly intended.

    line 9
  2. Very specific:

    When adding features, prefer adding new modules under src/agentex/lib/ rather than changing generated files directly.

    line 10
  3. Distinctive:

    If a change to generated code is required, document the reason and ensure the generator configuration or upstream schema is updated to make …

    line 11

≈ “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
20_codegen_boundaries.mdc
---
description: Keep manual code separate from generated SDK code
globs: "src/agentex/**"
alwaysApply: true
---

Guideline:

- Avoid modifying auto-generated files in `src/agentex/` except where explicitly intended. Place custom logic, extensions, and higher-level abstractions in `src/agentex/lib/`.
- When adding features, prefer adding new modules under `src/agentex/lib/**` rather than changing generated files directly.
- If a change to generated code is required, document the reason and ensure the generator configuration or upstream schema is updated to make the change reproducible.

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.