vanilla-rails-controllers
Use when writing Rails controllers or implementing state changes - enforces resource extraction, thin controllers delegating to models, params.expect, and controller concerns for scoping
What this skill does
# Vanilla Rails Controllers
**State changes are resources.** Every state change becomes its own resource controller with CRUD operations.
## Resource Extraction
```ruby
# Bad - custom actions
resources :cards do
post :close
post :archive
end
# Good - state as resource
resources :cards do
resource :closure, only: [:create, :destroy]
resource :archival, only: [:create, :destroy]
end
```
**See vanilla-rails-routing for route structure, nesting, and directory mapping.**
## Common State Resources
| State Change | Resource | create = | destroy = |
|--------------|----------|----------|-----------|
| Close/Reopen | `closure` | close | reopen |
| Archive/Unarchive | `archival` | archive | unarchive |
| Pin/Unpin | `pin` | pin | unpin |
| Publish/Unpublish | `publication` | publish | unpublish |
| Assign/Unassign | `assignment` | assign | unassign |
| Follow/Unfollow | `subscription` | subscribe | unsubscribe |
## Thin Controllers, Rich Models
Controllers delegate to intention-revealing model methods. No business logic in controllers.
```ruby
# Bad - logic in controller
class Cards::ArchivalsController < ApplicationController
def create
@card.update(archived: true)
end
end
# Good - delegate to model
class Cards::ArchivalsController < ApplicationController
include CardScoped
def create
@card.archive
respond_to do |format|
format.turbo_stream
format.json { head :no_content }
end
end
def destroy
@card.unarchive
respond_to do |format|
format.turbo_stream
format.json { head :no_content }
end
end
end
```
## Controller Concerns (Scoping)
Extract parent-finding into concerns. Name describes what's scoped:
```ruby
# app/controllers/concerns/card_scoped.rb
module CardScoped
extend ActiveSupport::Concern
included do
before_action :set_card
end
private
def set_card
@card = Card.find(params[:card_id])
end
end
# app/controllers/concerns/board_scoped.rb
module BoardScoped
extend ActiveSupport::Concern
included do
before_action :set_board
end
private
def set_board
@board = Current.account.boards.find(params[:board_id])
end
end
```
**Common concerns:**
| Concern | Sets | Used by |
|---------|------|---------|
| `BoardScoped` | `@board` | All controllers under `boards/` |
| `CardScoped` | `@card` | All controllers under `cards/` |
| `Authenticated` | session check | All controllers needing auth |
## params.expect()
Use `params.expect()` instead of `params.require().permit()`:
```ruby
# Bad
def card_params
params.require(:card).permit(:title, :description)
end
# Good
def card_params
params.expect(card: [:title, :description])
end
```
## Migration Pattern
State resources need a table tracking who/when:
```ruby
create_table :closures, id: :uuid do |t|
t.uuid :card_id, null: false
t.uuid :user_id
t.timestamps
end
add_index :closures, :card_id, unique: true
```
## Red Flags
| Red flag | Fix |
|----------|-----|
| `post :close`, `patch :activate` | Extract resource |
| Business logic in controller | Move to model |
| `params.require().permit()` | Use `params.expect()` |
| `before_action` duplicated across controllers | Extract scoping concern |
| Controller > 30 lines per action | Delegate more to model |
## Self-Check
- [ ] State changes modeled as resources (create/destroy)
- [ ] Controller actions delegate to model methods
- [ ] Parent-finding extracted to scoping concerns
- [ ] `params.expect()` for strong parameters
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.