Initialize a Puppet Master project. Checks dependencies, reads pmMode from config, and guides through setup (develop or build mode). Optionally starts the dev server.

Manage the PM development server. Start, stop, restart, or check status. The dev server runs on port 3000 by default.

Display full Puppet Master project status: config mode, database state, dev server, enabled modules, features, and sections.

Push Drizzle ORM schema to SQLite database. Creates the database file and applies schema changes.

Seed the database with initial data (users, roles, sample content). Requires an existing database.

Reset the database: delete the SQLite file, re-run migrations, and seed with initial data.

Run Drizzle migrations against the database.

Open Drizzle Studio (web UI for browsing the database).

Deploy the Puppet Master project to its configured VPS. Builds Docker image, pushes via SSH, runs Ansible deploy playbook, regenerates Traefik config, and health checks.

Roll back the deployment to the previous Docker image.

View deployment logs from the VPS.

Provision the VPS with Docker, Dockge, Traefik, and SSH setup.

Run a production build of the Puppet Master project. Creates optimized output in .output/ directory. Only use when explicitly requested for deployment or testing.

Run linting on the project. Supports ESLint and formatting checks. Can auto-fix issues with the fix option.

Run tests for the Puppet Master project. Supports unit tests, API tests, E2E tests (Playwright), and the full staged suite.

Read Puppet Master configuration values. Returns pmMode, entities, features, modules, sections, locales, colors, admin settings.

Modify a Puppet Master configuration value directly in project/puppet-master.config.ts. Supports dot-notation keys. WARNING: rewrites the config file as JavaScript.

Load the Puppet Master framework knowledge base. Returns CSS system, component architecture, composables, database schema, API patterns, config system, and RTL reference.

Load greenfield or brownfield entrypoint documentation. Greenfield = new project from PM baseline. Brownfield = migrating existing codebase into PM.

List or read PM contribution documents. Contributions are fixes/features exported from client projects for application back into the PM framework. Stored in docs/contributing/.

List all existing contribution documents in docs/contributing/. These are fixes/features exported from client projects that can be applied to the PM framework.

Read a specific contribution document. Returns the full content for review or application.

Export current git changes as a PM contribution document. Generates a .pm-contribution.md file with diffs, descriptions, and testing instructions. Use this when you fix a bug or add a feature in a client project that should be contributed back to the PM framework.

Read a .pm-contribution.md file and display its contents for manual application. Lists changed files, affected domains, dependencies, and testing instructions. Does NOT auto-apply — the AI agent reviews and applies.

Get the review checklist for a given PM specialty. Returns a structured checklist of items reviewers should verify.

Run automated checks relevant to a given specialty domain. Executes lint, typecheck, or test commands to validate code quality.