agentleFS
Sign inStart free
ROCmROCm/AMDMIGraphX/.cursor/rules/split-sym-dim-pass-tests.mdc

AMDMIGraphX / rules

Cursor rule337 starsChanged 2 months agoMITView on GitHub

Enforce structural testing for the split_sym_dim transformation pass

We split this split-sym-dim-pass-tests.mdc into the rules it gives an agent

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

  • 3

    Very specific

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

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

    Test the pass by constructing the input program, running split_sym_dim plus required cleanup, constructing the complete expected program …

    line 9
  2. Very specific:

    Never call program::compile, program::eval, or create runtime parameter maps in this file.

    line 12
  3. Distinctive:

    Do not replace the explicit expected graph with property checks or numerical assertions.

    line 13
  4. Very specific:

    Put numerical execution coverage in an appropriate test/verify/ or target behavior test.

    line 14

≈ “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
split-sym-dim-pass-tests.mdc
---
description: Enforce structural testing for the split_sym_dim transformation pass
globs: test/split_sym_dim_test.cpp
alwaysApply: false
---

# split_sym_dim Pass Tests

- Test the pass by constructing the input program, running `split_sym_dim` plus required cleanup,
  constructing the complete expected program explicitly, and comparing them with
  `EXPECT(actual.sort() == expected.sort())`.
- Never call `program::compile`, `program::eval`, or create runtime parameter maps in this file.
- Do not replace the explicit expected graph with property checks or numerical assertions.
- Put numerical execution coverage in an appropriate `test/verify/` or target behavior test; it
  supplements but does not replace the structural pass test.
- Reuse the existing `add_clones` helper when expected split modules require it, while keeping each
  test's graph construction visible in the test case.

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 repository3 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