Rails Architecture
ThibautBaissac/rails_ai_agents
Guides modern Rails 8 code architecture decisions and patterns.
Apply core Ruby on Rails best practices for architecture, naming, safety, and maintainability.
Install Rails Best Practices Core
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-core --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rails-best-practices-core .claude/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .claude/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-coreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-core --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rails-best-practices-core .agents/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .agents/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-core --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rails-best-practices-core .cursor/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .cursor/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/marckohlbrugge/37signals-skills.git --path skills/rails-best-practices-core--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-core --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rails-best-practices-core .gemini/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .gemini/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-coreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rails-best-practices-core .github/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .github/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install marckohlbrugge/37signals-skills rails-best-practices-core --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marckohlbrugge/37signals-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rails-best-practices-core .opencode/skills/rails-best-practices-core && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rails-best-practices-core" agent skill from https://github.com/marckohlbrugge/37signals-skills/tree/main/skills/rails-best-practices-core into .opencode/skills/rails-best-practices-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rails-best-practices-core", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rails-best-practices-core- GitHub stars
- 724
- Token cost
- ~1.7k tokens
- SKILL.md length
- 762 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- None found
At a glance
Apply core Ruby on Rails best practices for architecture, naming, safety, and maintainability.
- Works in 5 steps: Correctness and data safety. → Multi-tenant/security boundaries. → Maintainability and readability. → …
- Most Rails coding
- SKILL.md covers Core Defaults, Modeling Patterns, Naming and REST & Routing, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rails Best Practices Core is an agent skill from marckohlbrugge/37signals-skills. Apply core Ruby on Rails best practices for architecture, naming, safety, and maintainability. Use for most Rails coding, refactoring, and code review tasks so baseline standards stay consistent.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Backend development. It works with Ruby on Rails. The repository describes itself as: Unofficial agent skills + reference guide that teach AI coding assistants to write Rails the 37signals way — extracted from Fizzy, Campfire, and DHH's code reviews.
When your agent uses it
- Most Rails coding
- Code review tasks so baseline standards stay consistent
Example prompts
- “/rails-best-practices-core”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Correctness and data safety.
- Multi-tenant/security boundaries.
- Maintainability and readability.
- Performance hot spots.
- Style and polish.
What it can do on your machine
Read from SKILL.md and the folder at commit c58e7d5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are ruby).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rails Best Practices Core loads about 1.7k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 762 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 762 words (~1,742 tokens).
“Use this as the default baseline for Rails work. Distilled from 37signals codebases (Campfire, Fizzy) and DHH's review patterns.”
- name
- rails-best-practices-core
Files
Just SKILL.md in skills/rails-best-practices-core of marckohlbrugge/37signals-skills.
Open the folder on GitHubat commit c58e7d5
Compare with similar skills
Rails Best Practices Core next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rails Best Practices Core this skillmarckohlbrugge/37signals-skills | 724 | — | ~1.7k | Automated safety check: Pass | None | |
| Rails ArchitectureThibautBaissac/rails_ai_agents | 665 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Ruby Prodavila7/claude-code-templates | 33k | 8 repos | ~445 | Automated safety check: Pass | MIT | |
| Rubyericrisco/rsc-harness | 180 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Antipattern Preventiondoorkeeper-gem/doorkeeper | 5.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Layered Railsevilmartians/redprints-cfp | 108 | 1 repos | ~4.1k | Automated safety check: Pass | None |
Similar skills
Ruby Pro
davila7/claude-code-templates
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization.
Ruby
ericrisco/rsc-harness
A skill your agent uses when writing or refactoring plain Ruby outside Rails — scripts, CLIs, gems, libraries: Enumerable chains and blocks, module mixins and value objects, Bundler/gemspec…
Antipattern Prevention
doorkeeper-gem/doorkeeper
Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.
Layered Rails
evilmartians/redprints-cfp
Write, refactor, and review Rails code using layered architecture principles from "Layered Design for Ruby on Rails Applications".
Rails Expert
Jeffallan/claude-skills
Builds Rails 7+ apps with Hotwire Turbo Frames and Streams, Active Record tuning, Action Cable, Sidekiq jobs and RSpec specs, with migration and N+1 checks.
More from marckohlbrugge/37signals-skills
All 8 skills in this repoRails Jobs
marckohlbrugge/37signals-skills
Apply best practices for Rails background jobs using simple orchestration, idempotency, and safe retries.
Rails Security Multitenancy
marckohlbrugge/37signals-skills
Apply Rails security and multi-tenant safety practices including scoped queries, SSRF defenses, rate limiting, and tenant-scoped realtime updates.
Dhh
marckohlbrugge/37signals-skills
Review Ruby/Rails code like DHH would - direct, opinionated, allergic to over-engineering.
Rails Hotwire Realtime
marckohlbrugge/37signals-skills
Apply Hotwire, Turbo, Stimulus, and ActionCable best practices for real-time Rails interfaces.
Rails Migrations
marckohlbrugge/37signals-skills
Write and review Rails database migrations safely, including reversible changes, lock-aware operations, and rollout sequencing.
Rails Testing
marckohlbrugge/37signals-skills
Apply Rails testing standards with Minitest, fixtures, and pragmatic coverage boundaries.
Related
Works with
Categories
Questions about Rails Best Practices Core
What does Rails Best Practices Core do?
Apply core Ruby on Rails best practices for architecture, naming, safety, and maintainability. Rails Best Practices Core is an agent skill from marckohlbrugge/37signals-skills. Apply core Ruby on Rails best practices for architecture, naming, safety, and maintainability.
When should I use Rails Best Practices Core?
Rails Best Practices Core fits situations like: most Rails coding; code review tasks so baseline standards stay consistent.
How do I install Rails Best Practices Core in Claude Code?
Run `npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a claude-code`. Or copy the skill folder (skills/rails-best-practices-core in marckohlbrugge/37signals-skills) into .claude/skills/rails-best-practices-core in your project. Claude Code loads it when a task matches its description.
How do I install Rails Best Practices Core in Codex?
Run `npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a codex`. Or copy the skill folder (skills/rails-best-practices-core in marckohlbrugge/37signals-skills) into .agents/skills/rails-best-practices-core in your project. Codex loads it when a task matches its description.
Can I use Rails Best Practices Core in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add marckohlbrugge/37signals-skills --skill rails-best-practices-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rails-best-practices-core, .gemini/skills/rails-best-practices-core, .github/skills/rails-best-practices-core and .opencode/skills/rails-best-practices-core in your project.
What does Rails Best Practices Core need to run?
SKILL.md names no scripts, command-line tools or credentials: Rails Best Practices Core is instructions for the agent only.
Does Rails Best Practices Core access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rails Best Practices Core safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rails Best Practices Core use?
No licence was found for Rails Best Practices Core or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Rails Best Practices Core use?
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rails Best Practices Core?
Skills that share tags, products or a category with Rails Best Practices Core: Rails Architecture (ThibautBaissac/rails_ai_agents, 665 stars), Ruby Pro (davila7/claude-code-templates, 33k stars), Ruby (ericrisco/rsc-harness, 180 stars) and Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rails Best Practices Core?
marckohlbrugge (a GitHub user) maintains it in marckohlbrugge/37signals-skills, which has 724 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on June 9, 2026.
Source: marckohlbrugge/37signals-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.