Community call: shared skills for the Rails community - #151
Open
AFornio wants to merge 1 commit into
Open
Conversation
delbetu
reviewed
Aug 14, 2026
Skills are markdown documents that coding agents (Claude Code and friends) load as instructions. This adds a place to publish the ones the community agrees on, so nobody has to rewrite them per project. Each skill is a single file in _skills/, rendered at /skills/<name>/ with a markdown viewer, a raw view and a copy button. Skills are grouped by category and are not attributed to an author: they belong to the community. Entries can be tagged as a skill or a rule via the type field, shown as a badge on the card. Seeded with one rule for writing RSpec specs.
AFornio
force-pushed
the
skills-para-rails
branch
from
August 17, 2026 12:16
41738e3 to
644f246
Compare
AFornio
marked this pull request as ready for review
August 17, 2026 12:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Most of us already have a CLAUDE.md, a .cursorrules or something similar sitting in a project, with our rules for specs, for security, for performance. They are roughly the same rules, written many times over, each copy slightly different and none of them reviewed by anyone else.
This proposes keeping the good ones in one place instead.
What it adds
A
/skills/section linked from the home page: one page per skill, grouped by category, with a raw view and a copy button. No author attribution, skills belong to the community. Seeded withrspec-tests-for-rails.The call
Draft on purpose, the interesting part is which skills we want and what goes in them, not the code. To add one: drop the document in
_skills/<name>.mdand add its entry to_data/skills.yml. Categories are open too.Screenshots
QA steps
/skills/, check the search filters the cards