Add additional console commands to Readme (#83)

Author: justinwhite15

README.md

@@ -8,6 +8,7 @@ Watch a quick [demo of Blueprint](https://www.youtube.com/watch?v=A_gUCwni_6c) i
 - [Requirements](#requirements)
 - [Basic Usage](#basic-usage)
 - [Defining Components](#defining-components)
+- [Additional Console Commands](#additional-console-commands)
 - [Contributing](#contributing)
 
 
@@ -26,7 +27,7 @@ Blueprint requires a Laravel application running version 6.0 or higher.
 While Blueprint may be more flexible in a future version, it currently assumes a standard project structure using the default `App` namespace.
 
 ## Basic Usage
-Blueprint adds an artisan command.
+Blueprint adds multiple artisan commands. The most commonly used command is the `blueprint:build` command to generate the Laravel components:
 
 ```sh
 php artisan blueprint:build [draft]
@@ -313,6 +314,23 @@ controllers:
 
 While these references will often be used within _Eloquent_ and `query` statements, they may be used in other statements as well. When necessary, Blueprint will convert these into variable references using an arrow (`->`) syntax.
 
+## Additional Console Commands
+Beyond the `blueprint:build` command, Blueprint provides additional commands:
+
+<dl>
+  <dt>blueprint:erase</dt>
+  <dd>
+
+  Erases the components created by the last _build_ and warns about any updated components.
+  
+  While this command is helpful, it's better to run the `blueprint:build` command from a clean working state and use Git commands like `reset` and `clean` to _undo_ the last _build_.</dd>
+  <dt>blueprint:trace</dt>
+  <dd>
+
+  Loads definitions for existing models into the Blueprint cache file (`.blueprint`) so you may reference them in your _draft_ file.</dd>
+</dl>
+
+
 ## Contributing
 Contributions may be made by submitting a Pull Request against the `master` branch. Any submissions should be complete with tests and adhere to the [PSR-2 code style](https://www.php-fig.org/psr/psr-2/).