agentleFS
justanestajustanesta/claude-code-resources/skills/R/writing-tidyverse-r/SKILL.md

writing-tidyverse-r

Skill2 starsChanged 10 months agoMITView on GitHub

Modern tidyverse patterns, style guide, and migration guidance for R development. Use this skill when writing R code with dplyr, reviewing tidyverse code, updating legacy R code to modern patterns, or enforcing consistent style. Covers native pipe usage, join_by() syntax, .by grouping, pick/across/reframe operations, tidy selection, stringr patterns, naming conventions, spacing, and migration from base R or older tidyverse APIs.

We split this skill into the rules it gives an agent

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

  • 5

    Very specific

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

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

    Use multiple and unmatched arguments for quality control:

    line 36
  2. Very specific:

    Use {{}} (embrace) for function arguments

    line 48
  3. Very specific:

    Use .data[[]] for character vectors

    line 49
  4. Very specific:

    Use across() for multiple columns

    line 50
  5. Very specific:

    Avoid: DayOne, calculate.mean, userData

    line 87
  6. Distinctive:

    Use snake_case for variables and functions

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill 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
SKILL.md

Writing Tidyverse R

This skill covers modern tidyverse patterns for R 4.3+ and dplyr 1.1+, style guidelines, and migration from legacy patterns.

Core Principles

  1. Use modern tidyverse patterns - Prioritize dplyr 1.1+ features, native pipe, and current APIs
  2. Write readable code first - Optimize only when necessary
  3. Follow tidyverse style guide - Consistent naming, spacing, and structure

Pipe Usage

Always use native pipe |> instead of magrittr %>%

R 4.3+ provides all needed features. See pipe-examples.md for usage patterns.

Join Syntax (dplyr 1.1+)

Use join_by() instead of character vectors for joins

Modern join syntax supports:

  • Equality joins: join_by(company == id)
  • Inequality joins: join_by(company == id, year >= since)
  • Rolling joins: join_by(company == id, closest(year >= since))

See join-examples.md for complete patterns.

Multiple Match Handling

Use multiple and unmatched arguments for quality control:

  • multiple = "error" - Expect 1:1 matches
  • multiple = "all" - Allow multiple matches explicitly
  • unmatched = "error" - Ensure all rows match

Data Masking vs Tidy Selection

Understand the difference:

  • Data masking functions: arrange(), filter(), mutate(), summarise()
  • Tidy selection functions: select(), relocate(), across()

Key patterns:

  • Use {{}} (embrace) for function arguments
  • Use .data[[]] for character vectors
  • Use across() for multiple columns

See data-masking-examples.md for patterns.

Modern Grouping and Column Operations

Use .by for per-operation grouping (dplyr 1.1+)

This replaces the old group_by() |> ... |> ungroup() pattern.

Additional modern operations:

  • pick() - Column selection inside data-masking functions
  • across() - Apply functions to multiple columns
  • reframe() - Multi-row summaries

See grouping-examples.md for complete examples.

String Manipulation with stringr

Use stringr over base R string functions

Benefits:

  • Consistent str_ prefix
  • String-first argument order
  • Pipe-friendly and vectorized

See stringr-examples.md for common patterns and base R equivalents.

Style Guide Essentials

Object Names

  • Use snake_case for all names
  • Variable names = nouns, function names = verbs
  • Avoid dots except for S3 methods

Good: day_one, calculate_mean, user_data Avoid: DayOne, calculate.mean, userData

Spacing and Layout

See style-examples.md for proper spacing and pipe formatting.

Naming and Arguments

  • Use snake_case for variables and functions
  • Prefix non-standard arguments with . (e.g., .data, .by)

Anti-Patterns to Avoid

Legacy Patterns

AvoidUse Instead
%>%`>`
by = c("a" = "b")by = join_by(a == b)
sapply()map_*()
group_by() |> ... |> ungroup().by argument

Performance Anti-Patterns

  • Don't grow objects in loops - Pre-allocate or use purrr
  • Don't use sapply() - Type-unstable, use map_*() instead

See anti-patterns.md for examples of what to avoid and correct alternatives.

Migration Reference

Base R to Modern Tidyverse

Base RModern Tidyverse
subset(data, condition)filter(data, condition)
data[order(data$x), ]arrange(data, x)
aggregate(x ~ y, data, mean)summarise(data, mean(x), .by = y)
sapply(x, f)map(x, f)
grepl("pattern", text)str_detect(text, "pattern")
gsub("old", "new", text)str_replace_all(text, "old", "new")

Old to New Tidyverse Patterns

Old PatternNew Pattern
data %>% function()data |> function()
group_by(x) |> summarise() |> ungroup()summarise(..., .by = x)
by = c("a" = "b")by = join_by(a == b)
gather()/spread()pivot_longer()/pivot_wider()
map_dfr(x, f)map(x, f) |> list_rbind()
separate(col, into = ...)separate_wider_delim()

See migration-examples.md for complete migration patterns.

source: Sarah Johnson's gist https://gist.github.com/sj-io/3828d64d0969f2a0f05297e59e6c15ad

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.

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.