What problem does it solve? Packaging an application as a snap requires knowing its language, build system, entry points, system resource usage, interfaces, hooks, and confinement needs — information that is tedious and error-prone to gather manually from a codebase. ## Core Features & Use Cases - Systematic Codebase Scanning: Works through a structured checklist covering language/runtime, build system, entry points, daemons, GUI, network, filesystem, hardware, D-Bus, and audio usage. - Packaging Decisions: Selects the snapcraft plugin, determines strict vs classic confinement (with store-review caveats), maps system resources to snap interfaces with auto-connect status, and identifies required lifecycle hooks and layouts. - Structured Output: Writes a schema-versioned snap-analysis.json to /tmp that the snap-packager skill consumes to generate snapcraft.yaml. - Use Case: Point it at a Go daemon project and receive a complete packaging specification including the go plugin, network-bind plug, daemon mode, and an install hook for config seeding. ## Quick Start Analyze this project directory and produce the snap packaging specification file for it.