Tim Kevin Oxley

Great idea. Creating magical file seems bad though. Should probably go in [datadir](https://github.com/substack/adventure/blob/d6f9d53e925f3cddcfda4d36efecf0081837a5ab/index.js#L31-L34) and also include direction to some command that will disable it. Maybe also provide an "always". If...

Note it should only be asking this if the user is missing files that exist in the boilerplate. Can you elaborate on the scenario where you want to have files...

Sounds good. I suggest passing the "adventure" instance to `setup`.

@hustcer good idea, you can get it from reading the name property of the second argument to the `dataTransform`. This isn't documented though, so my bad. If you get this...

e.g. https://github.com/zeke/package-json-to-readme/blob/27b2129a5aeb0c04ae497fd635910220bd66b351/test/index.js#L38-L47

What would api look like do you think?

Having a a .not() in the chain makes it a little unclear whether it should be before or after the expectation: ``` js nixt() .cwd(path.join(__dirname, 'node_modules', '.bin')) .run('mocha --version') .stdout('1.13.0')...

+1 sucks when you have a bunch of junk in the prototype… or nested prototypes, Typology currently won't validate unless you add all of the methods.

minor point but the `@` sign will make make imports look like a syntax shitshow when combined with npm's [scoped packages syntax](https://docs.npmjs.com/misc/scope): ``` js import express from "@strongloop/express@2" ```

Being able to specify aliases/mappings up in the `package.json` could solve this, along with a bunch of other issues related to being tied directly to filesystem for dependency lookups: ```...