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
- Very specific: line 36
Use multiple and unmatched arguments for quality control:
- Very specific: line 48
Use {{}} (embrace) for function arguments
- Very specific: line 49
Use .data[[]] for character vectors
- Very specific: line 50
Use across() for multiple columns
- Very specific: line 87
Avoid: DayOne, calculate.mean, userData
- Distinctive: line 95
Use snake_case for variables and functions
≈ “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.
Files
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
- Use modern tidyverse patterns - Prioritize dplyr 1.1+ features, native pipe, and current APIs
- Write readable code first - Optimize only when necessary
- 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 matchesmultiple = "all"- Allow multiple matches explicitlyunmatched = "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 functionsacross()- Apply functions to multiple columnsreframe()- 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
| Avoid | Use 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, usemap_*()instead
See anti-patterns.md for examples of what to avoid and correct alternatives.
Migration Reference
Base R to Modern Tidyverse
| Base R | Modern 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 Pattern | New 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
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- jeremy-allen/claude-skills★ 63100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- Data Engineering Cloud InfrastructureSkill
- data-eng-data-qualitySkill
- data-eng-streaming-patternsSkill
- data-eng-testing-patternsSkill
- data-eng-warehouse-patternsSkill
- DevOps CI/CD PatternsSkill
- devops-docker-patternsSkill
- devops-monitoring-observabilitySkill
- devops-terraform-patternsSkill
- git-advanced-operationsSkill
- git-workflow-patternsSkill
- modern-python-patternsSkill
- python-api-developmentSkill
- python-async-patternsSkill
- python-data-pipelinesSkill
- python-data-wranglingSkill
- python-devops-automationSkill
- python-error-handlingSkill
- python-package-developmentSkill
- python-performanceSkill
- python-testingSkill
- customizing-vectors-rSkill
- designing-oop-rSkill
- developing-packages-rSkill
- metaprogramming-rlangSkill
- optimizing-rSkill
- sql-advanced-featuresSkill
- sql-analytics-patternsSkill
- sql-data-modelingSkill
- SQL Integration PatternsSkill
- sql-query-fundamentalsSkill
- sql-query-optimizationSkill
- sql-transformationsSkill
- API DesignSkill
- webdev-html-css-patternsSkill
- webdev-javascript-fundamentalsSkill
- webdev-react-patternsSkill
- webdev-typescript-patternsSkill
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.

