vanilla-rails-naming

Included with Lifetime

$97 forever

Use when naming classes, methods, routes in vanilla Rails codebases - enforces concern adjectives (-able/-ible only), no bangs for state, resource naming cascade, and commit message format

General

What this skill does


# Vanilla Rails Naming

37signals naming conventions from production Basecamp codebases.

## The Naming Cascade

Every state change flows through this cascade:

| Layer | Pattern | Example |
|-------|---------|---------|
| Concern | Adjective (-able/-ible) | `Card::Closeable` |
| State model | Noun | `Closure` |
| Controller | Plural noun | `ClosuresController` |
| Route | Singular resource | `resource :closure` |
| Method | Plain verb (no !) | `card.close` |
| Async enqueue | `*_later` | `notify_watchers_later` |
| Sync execute | `*_now` or plain | `notify_watchers_now` |

**If the cascade doesn't flow, the naming is wrong.**

## Concern Names: -able/-ible ONLY

```ruby
# Wrong
Card::Closing        # verb
Card::PinManager     # Manager/Handler/Service
Card::Closed         # past participle

# Right
Card::Closeable
Card::Pinnable
Card::Assignable
```

**If concern name doesn't end in -able/-ible, STOP and rename immediately.** No -ing, -er, -ish, Logic, Management, Handler, Service.

## State Methods: No Bangs

Plain verbs for state changes. `!` only when non-bang counterpart exists.

```ruby
# Wrong                    # Right
card.close!                card.close
card.pin!                  card.pin_by(user)
card.archive!              card.archive
```

## Async: _later/_now

`_later` always at the end of compound verbs:

```ruby
notify_watchers_later      # enqueues job
notify_watchers_now        # actual logic (called by job)
pin_and_notify_later       # compound verb
```

## File Locations

```
app/models/card/closeable.rb           # Model-specific concern
app/models/concerns/eventable.rb       # Shared concern
app/models/closure.rb                  # State record
app/controllers/cards/closures_controller.rb
```

## Commit Messages

Present tense, lowercase, no type prefixes:

```
add pin feature to cards
extract closeable concern
fix closure validation
```

Not: `feat:`, `fix:`, `[FEATURE]`, past tense, title case.

## Red Flags

| Red flag | Fix |
|----------|-----|
| Concern not -able/-ible | Rename immediately |
| State method with `!` | Remove bang |
| `post :close` in routes | `resource :closure` |
| Async without `_later` | Add suffix |
| `ClosureController` (singular) | `ClosuresController` (plural) |
| Commit with `feat:` prefix | Present tense, no prefix |

Files: 1

Size: 2.5 KB

Complexity: 6/100

Category: General

Source: https://github.com/zemptime/zemptime-marketplace/tree/main/vanilla-rails/skills/naming

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts