* This rule is flagging compound logical statements with parenthesis,
and I feel like the pare...

* I am not a fan of single-line empty methods:

```ruby
def foo; end
```

* This rule is not aware of when keyword arguments are vertically
aligned with the first keywo...

* It's useful to use STDOUT directly in specs, but otherwise use
`$stdout` in `lib/` code.

* I prefer `has_foo?` style method names.

* This conflicts with methods where a required keyword argument is at
the very end of the keyw...

* I use a space before the comma to indicate that a keyword argument
requires a value:

```r...

* I prefer to use double quotes for english text, URLs, RSpec descriptions.

* I use sole-nested conditions frequently instead of safe-navigation or
to breakup complex if ...

* If the programmer uses `rescue => error` without an exception class,
then they most likely w...

* I prefer to escape the `.` within regexp `[ ]` character sets, even
though it's apparently n...

* I always use double quotes when created quoted Symbols.

* I prefer `has_key?`/`has_value?` to `key?`/`value?`.

* Let the programmer group conditions using parentheses as they see fit.

* I often prefer to use explicit `return`s to indicate the return value.

* This rule cannot detect when blocks are aligned after an `=`
assignment:

```ruby
foo = ...

* Sometimes I prefer using `%w[]` word arrays, and sometimes I prefer to
use explicit `[]` Str...

* I am not a fan of the new safe-navigation operator (`&.`).

* Configure it to prefer stabby lambdas.

* I prefer to define accessors one per-line. Sometimes I will group them
in the specs.

* Exclude specific files that do not need to call `super()` because the
superclass does not de...

* We are adult programmers here, we can compare values to `0` or greater
than `0` without usin...

* Sometimes it might be necessary to leave constants mutable.

* It is valid to put optional arguments at the beginning or in the
middle of a method's argume...

* Exclude the `spec/` directory though.

* Exclude files which need to define empty place holder methods.

* I prefer to define keyword arguments in the order they will typically
be given to a method-c...

* I prefer to sometimes compress `if`/`else` statements to three lines:

```ruby
if conditio...

* The `$/` global variable, which represents the Operating System's
new-line deliminator, is u...

* I prefer to use explicit multi-line `if`/`unless` when raising
exceptions or returning value...

* Not a fan of *always* using guard clauses (ex: `return unless var`)
over explicit `if`/`unle...

* Exclude the `spec/` directory though.

* This clashes with Ronin's overall style of not adding a space after
`{` or before `}`.

* Variable names should be descriptive. Shortening `error` to `e` makes
the code *less* readable.

* I am a fan of `.kind_of?(ClassName)` over `.is_a?(ClassName)`.

* The defacto rule is to use `{` `}` blocks when chaining together
multiple method calls. This...

* This rule is not configurable and we use spaces after the comma for
Hashes and method-calls ...

* It's unaware of different alignments of groupings of keys/values,
and tries to validate alig...