Comment 1 for bug 1665927

Hmm... I think it might be better to be less magic here.

I would suggest going the other way, and having the 'snapcraft init'
skeleton yaml guide people to the correct outcome. For example, if the
skeleton yaml looked like this:

name: my-snap-name # you will need to 'snapcraft register <my-snap-name>'
version: '0.1' # just for humans, typically '1.2+git' or '1.3.2'
summary: Single-line 79-character elevator pitch for your amazing snap
description: |
  This is my-snap's description. You have a paragraph or two to tell the
  most important story about your snap. Keep it under 100 words though,
  we live in tweetspace and your description wants to look good in the snap
  store.

grade: devel # for edge/beta, becomes 'stable' for candidate/stable channels
confinement: classic # use 'devel' then 'strict' once you have plugs and
slots

#environment: # set env for all apps
# FOO: value
# BAR: value

#apps:
# my-app: # will be exported as snap.app in /snap/bin/
# command: path/to/binary # relative to root of $SNAP
# environment: # specific to this app
# BAZ: value
# my-daemon: # will start automatically
# daemon: simple # see http://snapcraft.io/docs/daemons/
# command: bin/daemon # again relative to root of snap

parts:
  my-part:
    # See 'snapcraft plugins'
    plugin: nil