2025-03-16 Sun

• AI Coding

  • CursorAI/v0.47

    • #Updated CursorAI/Project Rule/Test/Agent/✅/Find MDC/in Subfolder after testing it
    • • Rules: Allow nested .cursor/rules directories and improved UX to make it clearer when rules are being applied.
        • Awesome, I asked for this in CursorAI/Forum/25/03/Scan for Project Rules in Subdirectories of .cursor rules
    • #Filed
      • CursorAI Project Rule Types
        • This update has introduced new UI constraints and help strings. I've updated my descriptions of the different cursor project rule types in this page and its sub-pages.
      • Person/Deniz Gokcin

        • • My Notes

            • helped me gain some awareness of how FabricAI could be used in CursorAI and gh to create a Pull Request with a review in CursorAI/Forum/24/10/Generate PR description from PR diff

  • Person/Ryoichi Izumita/Blog/25/03/Mimicking Windsurf Memory in Cursor

    • • My Notes

        • describes a CursorAI/Project Rule that, like CursorAI/Project Rule/cursor-project-rule-editor.mdc, can create a new project rule. Goes into a bit more detail than other examples I've seen about how to explain to cursor the various CursorAI Project Rule Types and when to use them, presumably because memories should have different activation properties that the user should control.
        • It seems to me that storing memories in cursor project rules may be functional but inefficient. I'd prefer to have Cursor store its memories in Logseq, as described in CursorAI/Idea/Using Logseq with Project Rules. Of course, in that context, the memories would be shared across instances, so it may not make sense to use a symlinked common directory, but instead use a project memory logseq garden.

  • CursorAI/Idea/Using Logseq with Project Rules

    • If one keeps a Knowledge Garden filled with all technical knowledge that cursor needs to know about, it may make sense to symlink that into a each repository and to make it available to CursorAI Agent Mode to draw upon. CursorAI/Project Rules could then even be written that reference a well-known spot where the documentation is stored, so the same information could be utilized across projects.

• Documentation

  • It seems like uv's documentation page is using the word Guides to be either Diataxis/Tutorial or Diataxis/How To or the union of the two. I like this word. I have a feeling that they are using it to refer to How To guides, because How-to guides - Diátaxis actually uses the word "guide" and also because the articles don't seem to adhere to the stle of Tutorials - Diátaxis.

• LangChain/Ecosystem

  • langgraph/Studio/issue/24/11/Dynamic AWS Creds in LangGraph Studio

• Knowledge Gardener

  • Person/Nicole van der Hoeven

• Package Management

  • uv
    • uv/How To/Use uv in GitHub Actions
  • PyPoetry/Concept/Misconception - Disadvantages of Pip vs Poetry

    • • Misconception - There's no easy way to use Py/pyproject.toml to do Py/Editable Installs with uv pip as there is with PyPoetry

        • WRONG - see PyPoetry/Concept/How to handle Monorepos in Poetry vs uv for an updated understandingPoetry/Concept/How to handle Monorepos in Poetry vs uv

          • In poetry, it's possible to have a python Monorepo with poetry by specifying editable installs. With uv pip, the recommended approach would be to specify requirements-dev.txt with -e path/to/package alongside pyproject.toml, which seems like a strange mixture of old and new package management techniques.

          • Feature	Poetry (poetry install)	pip / uv pip install
            Editable installs in pyproject.toml	✅ {path = "path/to/package", develop = true}	❌ Not supported
            -e flag in requirements.txt	❌ Not needed	✅ -e path/to/package works
            Installing local editable packages automatically	✅ Done via pyproject.toml	❌ Must be installed manually