[Discussion] How about a 'tool', rather than a boilerplate

- I'm not sure if something like this doesn't already exist \*

I liked this starting project a lot. But it's quite limited (as it should be, to be general enough...)

Wouldn't it be nice to have something like this:

```
mg init
# generates this boilerplate

mg create collection tasks
# generates:
# /imports/api/tasks/tasks.js
# /imports/api/tasks/server/publications.js
# adds the publications to the server file
# etc

mg create page tasks
# generates
# /imports/ui/pages/tasks/taskContainer.jsx
```

etc, completely following the Meteor Guide?

Start by reviewing the starter application's structure and the Meteor Guide conventions referenced in the discussion. The proposed commands would need defined behavior for generating collections, publications, server wiring, and React pages; done would require an agreed command design and working generated output, but the issue does not identify implementation files or tests.

Written by the indexing model from the issue text.