Individual skill
rails-design-system
Ruby on Rails design system guidelines for building consistent, maintainable UI with minimal abstraction. This skill should be used when creating or refactoring Rails views, partials, components, form builders, helpers, Stimulus controllers, Turbo Frames, Turbo Streams, or design tokens. Triggers on tasks involving ERB partials, Turbo navigation, Turbo Streams, ViewComponent, Phlex, Tailwind design tokens, custom form builders, view helpers, Stimulus behaviors, Import Maps, Lookbook previews, or design system consistency audits.
skills/.experimental/rails-design-system/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 221
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,520 bytesassets/templates/_template.mddoc · 919 bytesmetadata.jsonasset · 1,289 bytesreferences/_sections.mddoc · 2,674 bytesreferences/comp-explicit-args.mddoc · 2,801 bytesreferences/comp-slots-for-markup.mddoc · 3,120 bytesreferences/comp-test-rendered-output.mddoc · 4,110 bytesreferences/comp-when-to-use.mddoc · 3,727 bytesreferences/decide-avoid-wrapper-components.mddoc · 2,303 bytesreferences/decide-design-system-scope.mddoc · 3,260 bytesreferences/decide-helper-vs-partial.mddoc · 2,138 bytesreferences/decide-partial-vs-component.mddoc · 2,845 bytesreferences/decide-prove-then-extract.mddoc · 2,944 bytesreferences/decide-three-uses-rule.mddoc · 2,400 bytesreferences/form-accessible-labels.mddoc · 3,546 bytesreferences/form-button-consistency.mddoc · 3,425 bytesreferences/form-custom-builder.mddoc · 3,239 bytesreferences/form-error-display.mddoc · 2,993 bytesreferences/form-group-wrapper.mddoc · 4,354 bytesreferences/form-set-default-builder.mddoc · 1,917 bytesreferences/helper-badge-pattern.mddoc · 3,960 bytesreferences/helper-conditional-classes.mddoc · 2,832 bytesreferences/helper-icon-helper.mddoc · 3,155 bytesreferences/helper-scope-to-domain.mddoc · 3,277 bytesreferences/helper-tag-helpers.mddoc · 2,465 bytesreferences/org-deduplication-audit.mddoc · 4,259 bytesreferences/org-document-design-decisions.mddoc · 3,381 bytesreferences/org-file-structure.mddoc · 3,961 bytesreferences/org-import-maps.mddoc · 2,827 bytesreferences/org-naming-conventions.mddoc · 3,276 bytesreferences/org-preview-with-lookbook.mddoc · 3,280 bytesreferences/partial-collection-with-spacer.mddoc · 2,914 bytesreferences/partial-explicit-locals.mddoc · 1,934 bytesreferences/partial-naming-conventions.mddoc · 2,529 bytesreferences/partial-presenter-objects.mddoc · 2,937 bytesreferences/partial-shared-directory.mddoc · 2,742 bytesreferences/partial-yield-blocks.mddoc · 2,803 bytesreferences/stim-composable-controllers.mddoc · 3,972 bytesreferences/stim-data-attribute-config.mddoc · 3,820 bytesreferences/stim-general-purpose.mddoc · 3,188 bytesreferences/stim-leverage-library.mddoc · 4,084 bytesreferences/stim-small-controllers.mddoc · 4,168 bytesreferences/stim-use-outlets.mddoc · 4,202 bytesreferences/token-component-tokens.mddoc · 2,888 bytesreferences/token-semantic-color-names.mddoc · 2,985 bytesreferences/token-share-tokens-with-ruby.mddoc · 3,586 bytesreferences/token-spacing-scale.mddoc · 2,615 bytesreferences/token-tailwind-theme.mddoc · 2,337 bytesreferences/token-typography-scale.mddoc · 3,416 bytesreferences/turbo-drive-defaults.mddoc · 3,237 bytesreferences/turbo-frame-decompose.mddoc · 2,788 bytesreferences/turbo-frame-naming.mddoc · 2,973 bytesreferences/turbo-frame-vs-stream.mddoc · 3,008 bytesreferences/turbo-stimulus-coordination.mddoc · 3,439 bytesreferences/turbo-stream-crud.mddoc · 3,690 bytes
Read excerpt
# Community Ruby on Rails Design System Best Practices
Comprehensive design system guide for Ruby on Rails applications, maintained by Community. Contains 51 rules across 9 categories, prioritized by impact to guide automated refactoring and code generation. Covers the full Rails frontend stack: Turbo (Drive, Frames, Streams), Stimulus, ERB partials, design tokens, form builders, and view helpers. Complements `rails-dev` (controllers, models, queries) and `tailwind` (CSS patterns) by covering the systematic UI component architecture layer.
## When to Apply
Reference these guidelines when:
- Deciding whether to extract a partial, component, or helper
- Defining design tokens with Tailwind CSS `@theme`
- Creating or refactoring ERB partials with explicit locals
- Decomposing pages into Turbo Frames for targeted updates
- Using Turbo Streams for multi-element CRUD updates
- Coordinating Turbo navigation with Stimulus controllers
- Building ViewComponent or Phlex components for complex UI