تشغيل أي مهارة في Manus بنقرة واحدة

asset-pipeline-propshaft

النجوم٢١

التفرعات٢

آخر تحديث١ يونيو ٢٠٢٦ في ١٨:٠٣

Asset pipeline for Rails 8 — Propshaft as the new default (replacing Sprockets), Importmap-rails for JS without bundling, jsbundling-rails for esbuild/rollup/webpack, cssbundling-rails for Tailwind/Sass/PostCSS, the Sprockets-to-Propshaft migration, asset host for CDN, digest stamping, far-future expiry headers. Use when the user mentions Propshaft, Sprockets migration, importmap, jsbundling, cssbundling, asset_host, asset pipeline, .css.erb, manifest.js, or asks about Rails 8 assets.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

sandeepmvl

sandeepmvl/rails-skills

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

2 ملفات

SKILL.md

readonly

المزيد من هذا المستودع

نفس المستودع

rails-project-discovery

sandeepmvl/rails-skills

Interview the developer about their Ruby on Rails project (app type, database, frontend stack, background jobs, deployment target, traffic profile, compliance, current Rails version) and then route to the right downstream rails-skills. Use at the start of any new Rails work session, when the user says they want to "start a new Rails app", "set up a Rails project", "scaffold Rails", "build a Rails API", "build a Rails monolith", "build a Rails 8 app", or anytime they reference rails-skills without specifying which skill they want. Also use when reviewing or auditing an existing Rails codebase to determine which skills apply. This is the entry point of the rails-skills pack — almost every Rails task should start here.

2026-06-0521

scaffold-project-skills

sandeepmvl/rails-skills

Generate project-specific Claude Skills for THIS Rails app — interview the codebase (domain models, workflows, multi-tenancy, auth, test + verification loop, branch rules, deploy) and emit starter SKILL.md files under the user's own .claude/skills/ that encode their product's conventions. Use when the user says "create skills for my app", "make project-specific skills", "scaffold local skills", "the generic rails-skills don't know my domain", "teach the agent my codebase conventions", "generate a skill for my <feature>", or wants the agent to learn their app's tenant rules / domain workflows / test gates rather than generic Rails advice.

2026-06-0521

activerecord-patterns

sandeepmvl/rails-skills

Idiomatic ActiveRecord patterns for Ruby on Rails — associations (belongs_to/has_many/has_one/has_many :through), counter_cache, polymorphic, STI vs delegated_type, scopes vs class methods, callbacks vs after_commit, find vs find_by vs where.first, includes vs preload vs eager_load, pluck vs select, exists? vs any?, batch processing with find_each, and fat-models-with-concerns. Use whenever the user writes or reviews ActiveRecord models, asks why a Rails query is slow or wrong, mentions includes/preload/eager_load, says "callback", references scopes, or is generating model code. Also use proactively when reading any Rails model file (app/models/*.rb).

2026-06-0121

n-plus-one-killer

sandeepmvl/rails-skills

Detect, diagnose, and eliminate N+1 queries in Ruby on Rails. Use when the user mentions slow Rails endpoints, slow queries, "N+1", Bullet, prosopite, includes/preload/eager_load, eager loading, query count is high, page is slow to render, or asks why a Rails controller is slow. Also use proactively when reviewing any controller action that iterates a collection and accesses associations, or any view that loops and calls `.author`, `.comments.count`, etc. Bundles a Bullet config script and an EXPLAIN ANALYZE reference for Rails devs.

2026-06-0121

service-objects-vs-fat-models

sandeepmvl/rails-skills

Decide when Rails logic stays in the model and when it earns a service object. Use when the user asks about service objects, fat models, "where does this logic go", refactoring a controller, extracting business logic, the Result pattern, interactor gem, dry-monads, command objects, or is about to write a class ending in Service / Manager / Handler / Processor. Also use proactively when reviewing any controller action with more than ~10 lines of business logic, or any model file exceeding ~200 lines.

2026-06-0121

rspec-testing-pyramid

sandeepmvl/rails-skills

RSpec testing for Ruby on Rails — pyramid shape (lots of model + request specs, fewer system specs), FactoryBot patterns, let vs let! vs before, shared examples, VCR for external HTTP, system specs with Capybara + Cuprite, transactional vs truncation strategy, parallel testing, SimpleCov coverage. Use when writing or reviewing Rails tests, the user mentions RSpec, FactoryBot, Capybara, Cuprite, VCR, system specs, request specs, model specs, fixtures, factories, flaky tests, slow test suite, parallel_rspec, or asks for help with rails_helper / spec_helper. Bundles drop-in spec_helper.rb + rails_helper.rb + .rspec templates.

2026-06-0121

name

asset-pipeline-propshaft

description

Asset Pipeline (Propshaft)

Rails 8 ships Propshaft. It does two things: maintain a load path for assets, and digest-stamp filenames for cache-busting. That's it. Sprockets did much more (preprocessing, transpilation, concatenation). Most of that moved to dedicated bundlers (esbuild, vite, sass).

The opinion

Greenfield Rails 8: Propshaft + Importmap (no Node) for simple apps. Propshaft + jsbundling-rails (esbuild) for richer apps. Propshaft + cssbundling-rails (Tailwind / Dart Sass) for Tailwind apps. Don't migrate an existing Sprockets app to Propshaft unless you audit for Sprockets-specific features (.scss.erb, manifest directives, asset processors) — those don't translate.

What Propshaft does NOT do

No preprocessing. No .scss.erb. No ERB inside CSS / JS.
No transpilation. No CoffeeScript, no Babel built-in.
No concatenation. No //= require directives. Bundle with esbuild / vite if you need.
No source maps. Bundlers handle.

What it does: serve app/assets/, stamp filenames with content digests, set Cache-Control headers.

Decision matrix — JS bundler

App	Pick
Rails 8 monolith, server-rendered, minor JS	Importmap-rails (no Node)
Mixed React/Vue islands	jsbundling-rails + esbuild
Heavy SPA mixed in	vite_ruby (HMR, TypeScript)
Legacy Webpacker	Shakapacker (community fork) — migrate later

Decision matrix — CSS

App	Pick
Tailwind CSS	cssbundling-rails + Tailwind
Dart Sass	cssbundling-rails + Dart Sass
Vanilla CSS	Propshaft directly (no bundler)
Plain CSS via Sprockets (was sass-rails)	Migrate to Dart Sass via cssbundling-rails

Core patterns

Pattern 1: Greenfield — Importmap + Propshaft

rails new myapp --asset-pipeline=propshaft --javascript=importmap

# config/importmap.rb
pin "application", preload: true
pin "@hotwired/turbo-rails", to: "turbo.min.js", preload: true
pin "@hotwired/stimulus", to: "stimulus.min.js", preload: true
pin_all_from "app/javascript/controllers", under: "controllers"

Browser fetches each module separately. No bundling. No Node required. Modern browsers handle the parallel fetches efficiently.

Trade-off: initial page load issues N small fetches instead of one bundle. With HTTP/2 + browser cache, this is usually fine.

Pattern 2: Greenfield — jsbundling-rails + esbuild

rails new myapp --asset-pipeline=propshaft --javascript=esbuild

// package.json (generated)
{
  "scripts": {
    "build": "esbuild app/javascript/*.* --bundle --sourcemap --outdir=app/assets/builds --public-path=/assets"
  }
}

# Procfile.dev
web: bin/rails server
js: yarn build --watch

bin/dev starts both. Output goes to app/assets/builds/, Propshaft serves digest-stamped versions.

Pattern 3: Tailwind via cssbundling-rails

rails new myapp --asset-pipeline=propshaft --javascript=importmap --css=tailwind

// package.json
{
  "scripts": {
    "build:css": "tailwindcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css --minify"
  }
}

bin/dev runs yarn build:css --watch alongside the server.

Pattern 4: Migrating from Sprockets to Propshaft

Audit first:

# Find Sprockets-specific features
grep -rE "//= require|\\.scss\\.erb|\\.coffee|sprockets" app/

If you find any:

Found	Migrate to
`//= require foo`	Use a bundler (jsbundling or vite)
`.scss.erb` (ERB in SCSS)	Move dynamic values to CSS variables; SCSS via cssbundling-rails
`.coffee`	Transpile to JS, then bundle with esbuild
`app/assets/javascripts/manifest.js` directives	Bundler config
`Sprockets.register_*` processors	No equivalent; either drop or run as a build step

Migration steps:

Add Propshaft + bundlers to Gemfile alongside Sprockets.
Move asset compilation off Sprockets piece by piece.
Once nothing references Sprockets, remove the gem.
Test in staging — first cache flush often surfaces missing files.

For non-trivial apps: 2-5 days. Don't combine with the Rails version bump.

Pattern 5: Asset host (CDN)

# config/environments/production.rb
config.asset_host = "https://cdn.example.com"

Propshaft generates URLs like https://cdn.example.com/assets/application-abc123.css. Point CloudFront / Cloudflare / Fastly at the Rails origin; cache assets at the edge.

Far-future expiry is automatic — digest in the filename means a new content version = new URL = no stale cache.

Pattern 6: Importmap pin from CDN

# config/importmap.rb
pin "react", to: "https://ga.jspm.io/npm:react@18/index.js"
pin "react-dom", to: "https://ga.jspm.io/npm:react-dom@18/index.js"

CDN-hosted modules. Skip yarn entirely for these. Useful when you want one or two npm libraries without a bundler.

Pattern 7: Vendoring importmap pins

bin/importmap pin react
# Downloads react to vendor/javascript/ and pins to it

When you want predictable behavior (CDN downtime resilience, deterministic builds), vendor the pinned modules.

Pattern 8: Removing Sprockets entirely

# Gemfile — remove
# gem "sprockets-rails"
# gem "sass-rails"
# gem "coffee-rails"

# config/application.rb — remove
# require "sprockets/railtie"

# Replace with
gem "propshaft"

# config/manifest.js — DELETE if you used it
# config/assets.rb — DELETE

# config/initializers/assets.rb (or config/application.rb)
config.assets.paths << Rails.root.join("app/assets/builds")  # if using bundlers

Common mistakes to refuse

Don't try to use .scss.erb with Propshaft. Move dynamic values to CSS variables.
Don't migrate from Sprockets to Propshaft in the same PR as the Rails version bump.
Don't disable digest stamping. The whole cache-bust mechanism depends on it.
Don't put hashed file references in code — Rails' asset helpers (asset_path, image_tag) resolve them.
Don't ship sourcemaps to production publicly. They reveal your unminified source.

When NOT to use this skill

Pre-Rails 7 app — Sprockets is still your default. Wait for v0.2 / v0.3 backport content.
The user is asking about a specific bundler (esbuild config) — touch lightly, defer to bundler docs.

asset-pipeline-propshaft

Asset Pipeline (Propshaft)

The opinion

What Propshaft does NOT do

Decision matrix — JS bundler

Decision matrix — CSS

Core patterns

Pattern 1: Greenfield — Importmap + Propshaft

Pattern 2: Greenfield — jsbundling-rails + esbuild

Pattern 3: Tailwind via cssbundling-rails

Pattern 4: Migrating from Sprockets to Propshaft

Pattern 5: Asset host (CDN)

Pattern 6: Importmap pin from CDN

Pattern 7: Vendoring importmap pins

Pattern 8: Removing Sprockets entirely

Common mistakes to refuse

When NOT to use this skill

See also

Sources

Asset Pipeline (Propshaft)

The opinion

What Propshaft does NOT do

Decision matrix — JS bundler

Decision matrix — CSS

Core patterns

Pattern 1: Greenfield — Importmap + Propshaft

Pattern 2: Greenfield — jsbundling-rails + esbuild

Pattern 3: Tailwind via cssbundling-rails

Pattern 4: Migrating from Sprockets to Propshaft

Pattern 5: Asset host (CDN)

Pattern 6: Importmap pin from CDN

Pattern 7: Vendoring importmap pins

Pattern 8: Removing Sprockets entirely

Common mistakes to refuse

When NOT to use this skill

See also

Sources