Nick Tassone

Discussing offline, we decided that we will rely on formatting options more than color, though color should be used where appropriate. For color, we should stick to the default 16...

Word wrap, yes! @jeffandersen > No newline after command This one is pretty inconsistent in our current version, agreed it should be no newline.

I prefer the latter, new line after output. But that's just because I like whitespace and it distinguishes nicely between the last command.

> I'm against vertical whitespace immediately following... @jbowes I'll defer to you and standard formatting on this one. We should adhere to the standards for this kind of stuff as...

Some inspiration and resources: - Our own @jeffandersen's [Designing for CLI post](https://blog.manifold.co/six-things-to-consider-when-designing-for-the-command-line-2b9b9d6ad009#.qdmbgeip0) - [Heroku CLI Style Guide](https://devcenter.heroku.com/articles/cli-style-guide) - [Angular style guide](https://angular.io/styleguide) has an interesting format with notes for `Do`, `Consider`,...

We had a good discussion about this IRL last week. Didn't get into specifics as much as general philosophy but a good kick off for discussion. To start the discussion...

### Command Naming/Describing The general guide to naming a command should be to make it as simple and relevant as possible. When writing a description of the command for help,...

+1 to utilizing context where possible. I'm in favor of having success states contain output but I'm coming at this from a non-programmer background. Are success messages considered extraneous to...

Another topic we talked about was empty states. I think we should utilize the hints ui in our empty states to suggest the user can perform an action in order...

@jeffandersen and @jbowes and I discussed the pointer offline and @jbowes followed through! https://github.com/manifoldco/torus-cli/pull/150