Pawbytes Creative Suites Setup

Overview

Installs and configures the Pawbytes Creative Suites module into a project. Module identity (name, code, version) comes from ./assets/module.yaml. Collects user preferences and writes them to the Pawbytes ecosystem config:

• {project-root}/.pawbytes/config/config.yaml — shared project config: core settings at root plus a cra: section with module-specific values.
• {project-root}/.pawbytes/config/config.user.yaml — personal settings intended to be gitignored: API keys and any variable marked user_setting: true in ./assets/module.yaml. These values live exclusively here.
• {project-root}/.pawbytes/config/module-help.csv — registers module capabilities for the help system.

Both config scripts use an anti-zombie pattern — existing entries for this module are removed before writing fresh ones, so stale values never persist.

{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root, not the skill root.

On Activation

1. Read ./assets/module.yaml for module metadata and variable definitions (the code field cra is the module identifier)
2. Check if {project-root}/.pawbytes/config/config.yaml exists — if a cra: section is already present, inform the user this is an update
3. Check for existing config at {project-root}/_bmad/config.yaml (legacy BMad format). If found, inform the user that legacy config can be migrated to the new Pawbytes ecosystem format.