Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

R best practices: folders, renv and Quarto v1.0.0

Use this resource to organize a reproducible R project

New

  • 33 downloads
  • 21 likes
  • 34 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install r-programming-best-practices-rule

First time: connect the CLI with

npx --yes palatekit@latest login

Cursor applies these guidelines to R projects: R/, data/ and output/ folders, raw data kept unchanged, snake_case file names and Git. It favors base R, recommends renv to lock dependencies and Quarto for reports, and asks for version numbers in the DESCRIPTION file of packages.

Mostly picked by

Updated November 2, 2026

Card for “R best practices: folders, renv and Quarto”

Details

Works in
Install guides
Generates with
Your agent's model
Licence
CC0-1.0

Similar resources

View all

What you get

  • The .mdc file (in English): rules on R project structure, dependencies and reports
  • Guidance on R package structure and the DESCRIPTION file

Good fit for

  • A data analysis project in R shared by a team
  • An R repository whose folders and dependencies change from one session to the next

Not for

    Tags

    • r
    • renv
    • quarto
    • reproducibility

    About

    You say

    “Create the cleaning script in the R/ folder and save the output to data/processed/.”

    Card for “R best practices: folders, renv and Quarto”

    Rule published by PatrickJS under the CC0-1.0 license, delivered in its original version.

    Show more

    How to use it

    1. Copy the .mdc file into your project's .cursor/rules/ folder
    2. Ask Cursor to organize a reproducible R project
    3. Adjust the rule to your conventions

    Content preview

    Files

    • LICENSE6.5 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • r-programming-best-practices-rule.mdc7.8 KB

    Origin and licence

    Listed unmodified

    Author
    PatrickJS
    Source
    github.com/PatrickJS/awesome-cursorrules/blob/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/r-cursorrules-prompt-file-best-practices.mdc
    Licence
    CC0-1.0

    Notice

    « r-cursorrules-prompt-file-best-practices » (PatrickJS, CC0-1.0) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.