Comparison

A · Cursor rules · imazen/imageflow B · Cursor rules · imazen/imageflow

What each file covers, counted
Dimension	Only in A	Overlap
Sections	0	—
Commands	0	—
Section tags	1	0%

What each file covers

Sections

neither file has any

Commands

neither file has any

Section tags

0 shared · 1 only in A · 0 only in B

− git-pr

Line diff

+24 added−63 removed12 unchanged16.0% identical

imazen/imageflow · .cursor/rules/git-commits.mdc

@@ −1 @@

1---

2description: Git Conventional Commits

3globs:

4---

5Rule for automatically committing changes made by CursorAI using conventional commits format.

7<rule>

8name: conventional_commits

9description: Automatically commit changes made by CursorAI using conventional commits format

10filters:

11 - type: event

12 pattern: "build_success"

13 - type: file_change

14 pattern: "*"

16actions:

17 - type: execute

18 command: |

19 # Extract the change type and scope from the changes

20 CHANGE_TYPE=""

21 case "$CHANGE_DESCRIPTION" in

22 *"add"*|*"create"*|*"implement"*) CHANGE_TYPE="feat";;

23 *"fix"*|*"correct"*|*"resolve"*) CHANGE_TYPE="fix";;

24 *"refactor"*|*"restructure"*) CHANGE_TYPE="refactor";;

25 *"test"*) CHANGE_TYPE="test";;

26 *"doc"*|*"comment"*) CHANGE_TYPE="docs";;

27 *"style"*|*"format"*) CHANGE_TYPE="style";;

28 *"perf"*|*"optimize"*) CHANGE_TYPE="perf";;

29 *) CHANGE_TYPE="chore";;

30 esac

32 # Extract scope from file path

33 SCOPE=$(dirname "$FILE" | tr '/' '-')W

35 # Commit the changes

36 git add "$FILE"

37 git commit -m "$CHANGE_TYPE($SCOPE): $CHANGE_DESCRIPTION"

39 - type: suggest

40 message: |

41 Changes should be committed using conventional commits format:

43 Format: <type>(<scope>): <description>

45 Types:

46 - feat: A new feature

47 - fix: A bug fix

48 - docs: Documentation only changes

49 - style: Changes that do not affect the meaning of the code

50 - refactor: A code change that neither fixes a bug nor adds a feature

51 - perf: A code change that improves performance

52 - test: Adding missing tests or correcting existing tests

53 - chore: Changes to the build process or auxiliary tools

55 The scope should be derived from the file path or affected component.

56 The description should be clear and concise, written in imperative mood.

57 For anything in .github or ci folders, (ci) is the correct scope.

59examples:

60 - input: |

61 # After adding a new function

62 CHANGE_DESCRIPTION="add user authentication function"

63 FILE="src/auth/login.ts"

64 output: "feat(src-auth): add user authentication function"

66 - input: |

67 # After fixing a bug

68 CHANGE_DESCRIPTION="fix incorrect date parsing"

69 FILE="lib/utils/date.js"

70 output: "fix(lib-utils): fix incorrect date parsing"

72metadata:

73 priority: high

74 version: 1.0

75</rule>

imazen/imageflow · .cursor/rules/riapi.mdc

@@ +1 @@

1---

2description:

3globs: *.rs,*.md

4alwaysApply: false

5---

6It's important to reference the files below when touching anything to do with the Imageflow API, Instructions, querystring commands, RIAPI, or Ir4Commands.

8To work effectively with Imageflow, you should understand that Imageflow's main (98%) usage path is via querystring commands, like ?w=20&h=20.

10This syntax is backwards compatible with ImageResizer 1,2,3,4. There are around 100 commands, defined in @/imageflow_riapi/src/ir4/parsing.rs and @/imageflow_riapi/src/srcset.rs, and are transformed to JSON with the logic in @/imageflow_riapi/src/encoder.rs, @/imageflow_riapi/src/layout.rs, @/imageflow_riapi/src/mod.rs, and @/imageflow_riapi/sizing.rs. The query is not expanded to JSON all at once, part happens before the image is decoded, and part happens afterwards.

12These commands are partially documented in @/docs/src/querystring/encoding.md, @/docs/src/querystring/examples.md, @/docs/src/querystring/filters.md, @/docs/src/querystring/introduction.md, @/docs/src/querystring/transforms.md, and @/docs/src/querystring/rfc-qp.md, and we need to keep them up-to-date.

14We want to expand unit tests to cover common cases, so that we can prove our documented explanations are correct, and expand that documentation with concrete examples.

16Users typically interact via Imageflow.Net, a C# wrapper over the JSON FFI interface (see [ffi.mdc](mdc:.cursor/rules/ffi.mdc)), or via Imageflow Server (https://github.com/imazen/imageflow-server), which offers an HTTP API, and lets you map image sources to virtual paths and add querystrings to modify them on-the-fly (thus our focus on performance.) There are other bindings for go/node/elixr/etc.

18The current project also contains the imageflow_tool command-line tool, which can be used with JSON or like `imageflow_tool v1/querystring --command width=60&height=40&mode=max&format=jpg --in 100x100.jpg --out out4.jpg`, which is implemented in @/imageflow_tool/src/lib.rs, @/imageflow_tool/src/self_test.rs, and @/imageflow_tool/src/cmd_build.rs,

20NB: When working on @/imageflow_riapi/src/parsing.rs, make sure both serialization and deserialization are fully tested, and that new querystring keys are added to that allowlist array.

22When making examples for docs or schema, we try to use good, stunning photographs when we can, via our RIAPI compliant Imageflow Server deployment at https://i.zr.io/ri/i/glacier.jpg?w=300

24Here are some base URLs, with their intrinsic sizes and aspect ratios:

26https://i.zr.io/ri/i/above-trees.jpg 2400x3200 3:4

27https://i.zr.io/ri/i/above-trees_orig.jpg 6048x8064 3:4

28https://i.zr.io/ri/i/glacier.jpg 2400x3600 2:3

29https://i.zr.io/ri/i/horse.jpg 2400x3600 2:3

30https://i.zr.io/ri/i/komodo-island.jpg 2400x3226 1200:1613

31https://i.zr.io/ri/i/lake-town.jpg 2400x3598 1200:1799

32https://i.zr.io/ri/i/pearl-tower.jpg 2400x3600 2:3

33https://i.zr.io/ri/i/sahara.jpg 2400x1600 3:2

34https://i.zr.io/ri/i/santorini.jpg 2400x3600 2:3

35https://i.zr.io/ri/i/snowy-trees.jpg 2400x1797 800:599

36https://i.zr.io/ri/i/woman.jpg 2400x3600 2:3

@@ −1 +1 @@

11 ---

2−description: Git Conventional Commits

3−globs:

2+description:

3+globs: *.rs,*.md

4+alwaysApply: false

45 ---

5−Rule for automatically committing changes made by CursorAI using conventional commits format.

6+It's important to reference the files below when touching anything to do with the Imageflow API, Instructions, querystring commands, RIAPI, or Ir4Commands.

7−<rule>

8−name: conventional_commits

9−description: Automatically commit changes made by CursorAI using conventional commits format

10−filters:

11− - type: event

12− pattern: "build_success"

13− - type: file_change

14− pattern: "*"

8+To work effectively with Imageflow, you should understand that Imageflow's main (98%) usage path is via querystring commands, like ?w=20&h=20.

159

16−actions:

17− - type: execute

18− command: |

19− # Extract the change type and scope from the changes

20− CHANGE_TYPE=""

21− case "$CHANGE_DESCRIPTION" in

22− *"add"*|*"create"*|*"implement"*) CHANGE_TYPE="feat";;

23− *"fix"*|*"correct"*|*"resolve"*) CHANGE_TYPE="fix";;

24− *"refactor"*|*"restructure"*) CHANGE_TYPE="refactor";;

25− *"test"*) CHANGE_TYPE="test";;

26− *"doc"*|*"comment"*) CHANGE_TYPE="docs";;

27− *"style"*|*"format"*) CHANGE_TYPE="style";;

28− *"perf"*|*"optimize"*) CHANGE_TYPE="perf";;

29− *) CHANGE_TYPE="chore";;

30− esac

10+This syntax is backwards compatible with ImageResizer 1,2,3,4. There are around 100 commands, defined in @/imageflow_riapi/src/ir4/parsing.rs and @/imageflow_riapi/src/srcset.rs, and are transformed to JSON with the logic in @/imageflow_riapi/src/encoder.rs, @/imageflow_riapi/src/layout.rs, @/imageflow_riapi/src/mod.rs, and @/imageflow_riapi/sizing.rs. The query is not expanded to JSON all at once, part happens before the image is decoded, and part happens afterwards.

3111

32− # Extract scope from file path

33− SCOPE=$(dirname "$FILE" | tr '/' '-')W

12+These commands are partially documented in @/docs/src/querystring/encoding.md, @/docs/src/querystring/examples.md, @/docs/src/querystring/filters.md, @/docs/src/querystring/introduction.md, @/docs/src/querystring/transforms.md, and @/docs/src/querystring/rfc-qp.md, and we need to keep them up-to-date.

3413

35− # Commit the changes

36− git add "$FILE"

37− git commit -m "$CHANGE_TYPE($SCOPE): $CHANGE_DESCRIPTION"

14+We want to expand unit tests to cover common cases, so that we can prove our documented explanations are correct, and expand that documentation with concrete examples.

3815

39− - type: suggest

40− message: |

41− Changes should be committed using conventional commits format:

16+Users typically interact via Imageflow.Net, a C# wrapper over the JSON FFI interface (see [ffi.mdc](mdc:.cursor/rules/ffi.mdc)), or via Imageflow Server (https://github.com/imazen/imageflow-server), which offers an HTTP API, and lets you map image sources to virtual paths and add querystrings to modify them on-the-fly (thus our focus on performance.) There are other bindings for go/node/elixr/etc.

4217

43− Format: <type>(<scope>): <description>

18+The current project also contains the imageflow_tool command-line tool, which can be used with JSON or like `imageflow_tool v1/querystring --command width=60&height=40&mode=max&format=jpg --in 100x100.jpg --out out4.jpg`, which is implemented in @/imageflow_tool/src/lib.rs, @/imageflow_tool/src/self_test.rs, and @/imageflow_tool/src/cmd_build.rs,

4419

45− Types:

46− - feat: A new feature

47− - fix: A bug fix

48− - docs: Documentation only changes

49− - style: Changes that do not affect the meaning of the code

50− - refactor: A code change that neither fixes a bug nor adds a feature

51− - perf: A code change that improves performance

52− - test: Adding missing tests or correcting existing tests

53− - chore: Changes to the build process or auxiliary tools

20+NB: When working on @/imageflow_riapi/src/parsing.rs, make sure both serialization and deserialization are fully tested, and that new querystring keys are added to that allowlist array.

5421

55− The scope should be derived from the file path or affected component.

56− The description should be clear and concise, written in imperative mood.

57− For anything in .github or ci folders, (ci) is the correct scope.

22+When making examples for docs or schema, we try to use good, stunning photographs when we can, via our RIAPI compliant Imageflow Server deployment at https://i.zr.io/ri/i/glacier.jpg?w=300

5823

59−examples:

60− - input: |

61− # After adding a new function

62− CHANGE_DESCRIPTION="add user authentication function"

63− FILE="src/auth/login.ts"

64− output: "feat(src-auth): add user authentication function"

24+Here are some base URLs, with their intrinsic sizes and aspect ratios:

6525

66− - input: |

67− # After fixing a bug

68− CHANGE_DESCRIPTION="fix incorrect date parsing"

69− FILE="lib/utils/date.js"

70− output: "fix(lib-utils): fix incorrect date parsing"

71−

72−metadata:

73− priority: high

74− version: 1.0

75−</rule>

26+https://i.zr.io/ri/i/above-trees.jpg 2400x3200 3:4

27+https://i.zr.io/ri/i/above-trees_orig.jpg 6048x8064 3:4

28+https://i.zr.io/ri/i/glacier.jpg 2400x3600 2:3

29+https://i.zr.io/ri/i/horse.jpg 2400x3600 2:3

30+https://i.zr.io/ri/i/komodo-island.jpg 2400x3226 1200:1613

31+https://i.zr.io/ri/i/lake-town.jpg 2400x3598 1200:1799

32+https://i.zr.io/ri/i/pearl-tower.jpg 2400x3600 2:3

33+https://i.zr.io/ri/i/sahara.jpg 2400x1600 3:2

34+https://i.zr.io/ri/i/santorini.jpg 2400x3600 2:3

35+https://i.zr.io/ri/i/snowy-trees.jpg 2400x1797 800:599

36+https://i.zr.io/ri/i/woman.jpg 2400x3600 2:3