vanilla-rails-style

Included with Lifetime

$97 forever

Use when writing Ruby/Rails code - enforces expanded conditionals over guard clauses, private indentation, invocation-order methods, and bang method restrictions that contradict standard Ruby guides

Writing & Docs

What this skill does


# Vanilla Rails Style

**These conventions CONTRADICT standard Ruby style guides.** They reflect production 37signals code.

## Counter-Intuitive Patterns

| Pattern | 37signals Way | Standard Ruby Way |
|---------|---------------|-------------------|
| Conditionals | `if/else` | Guard clauses |
| Private indent | 2 spaces under `private` | No indentation |
| Bang methods | Only with counterpart | Flag "dangerous" actions |
| Method order | Invocation sequence | Alphabetical |

## Expanded Conditionals (NOT Guard Clauses)

**Prefer `if/else`.** Guard clauses allowed ONLY at method start with 5+ line body.

```ruby
# Good
def todos_for_new_group
  if ids = params.require(:todolist)[:todo_ids]
    @bucket.recordings.todos.find(ids.split(","))
  else
    []
  end
end

# Bad
def todos_for_new_group
  ids = params.require(:todolist)[:todo_ids]
  return [] unless ids
  @bucket.recordings.todos.find(ids.split(","))
end
```

**Multiple guards → nested if/else.** Convert `return unless` chains to nested conditionals that show complete logic flow.

**Allowed exception:**
```ruby
def after_recorded_as_commit(recording)
  return if recording.parent.was_created?  # Guard at START, complex body below

  if recording.was_created?
    broadcast_new_column(recording)
  else
    broadcast_column_change(recording)
  end
end
```

## Private Method Indentation

Indent 2 spaces under `private`. No newline after `private`.

```ruby
class SomeClass
  def public_method
    # ...
  end

  private
    def helper_one
      # indented
    end

    def helper_two
      # indented
    end
end
```

**Exception — module with ONLY private methods:** mark `private` at top, blank line, no indent.

## Method Ordering

Order by invocation sequence — callers before callees:

1. Class methods
2. `initialize` (first among instance methods)
3. Public methods
4. Private methods (ordered by call sequence)

```ruby
class Builder
  def build
    prepare
    format
    output
  end

  private
    def prepare; end   # called first
    def format; end    # called second
    def output; end    # called third
end
```

## Bang Methods

Only use `!` when non-bang counterpart exists: `save/save!`, `update/update!`.

No counterpart → no bang. `close` not `close!`. `archive` not `archive!`.

## Red Flags

| If you're about to... | Do this instead |
|-----------------------|-----------------|
| Add guard clauses | Use if/else |
| Remove private indentation | Indent under `private` |
| Add `!` to method without counterpart | Use plain name |
| Alphabetize private methods | Order by invocation |
| Create a service object | Move logic to model |

## Self-Check

- [ ] if/else instead of guard clauses (except single guard at start with complex body)
- [ ] Private methods indented under `private`
- [ ] Methods ordered by invocation sequence
- [ ] Bang only on methods with non-bang counterpart

Files: 1

Size: 3.1 KB

Complexity: 7/100

Category: Writing & Docs

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

Related in Writing & Docs

jax-development

Included

Use 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.

Writing & Docsscripts

nature-article-writer

Included

Drafts, 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.

Writing & Docsscripts

deckrd

Included

Document-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.

Writing & Docsscripts

clinical-decision-support

Included

Generate 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.

Writing & Docsscripts

handling-sf-data

Included

Salesforce 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).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert 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.

Writing & Docsscripts