Watt 3
These instructions ship with the installed Watt 3 release. The wattpm skill [FILE]
command is available starting with 3.74.0. Prefer writing application files directly
when assisting an agent-driven workflow. Watt 3 still supports its existing generators,
including create, init, add, and import workflows.
Inspect the project
- Read project instructions, manifests, lockfiles, configuration, entrypoints, and deployment files.
- Require Node.js 22.19.0 or newer in development, CI, and production.
- Identify the installed Watt version and capability versions. Keep dependencies on major 3;
do not silently upgrade to Watt 4. Check external capabilities' compatibility separately.
- Preserve the package manager, module system, workspace boundaries, scripts, and existing topology.
- Identify public listeners, application IDs, environment variable names, and the requested goal.
- Preserve unrelated code and secrets. Explain substantial changes and obtain authorization
before installing dependencies, running migrations, deploying, or executing project code.
Use the project's local Watt installation for CLI checks. Do not fall back to a global
installation or let npx download the latest version. If no installation exists, agree
on the target version and installation first. If the version predates 3.74.0 or has no
skill command, stop the skill workflow and report the requirement; do not upgrade automatically.
Configuration contract
- Prefer
watt.json for new Watt 3 projects. Existing JSON5, YAML, and TOML configurations
remain supported. Do not rewrite them into Watt 4 watt.config.* modules.
- Identify capabilities with
module or a matching $schema. Use the exact installed
package version for schema URLs rather than copying an old example's version.
- A multi-application root declares
applications and/or autoload; Watt also supports
the services and web directory shortcuts. Keep root runtime options at the root.
- A standalone capability can embed orchestration options under
runtime. Do not add a
nested runtime block to a runtime root merely because a capability example has one.
- Watt 3 uses
entrypoint and root server for the public application. Check the capability
and custom-command contract before changing listener addresses or ports.
- Environment placeholders such as
{PORT} are valid. Preserve their required/default
behavior and document variable names in .env.example without exposing secret values.
- Watt 3 tracing configuration is named
telemetry. Inspect installed schemas before
borrowing options from another release.
- Native TypeScript stripping does not replace framework builds or type checking and
does not support every TypeScript language feature.
Installed schemas and source take precedence over generic examples. A requested upgrade
to Watt 4 is a separate migration: obtain destination-version guidance explicitly rather
than applying v4 API or configuration changes during ordinary v3 maintenance.
Workflow router
| Request |
References |
init, setup, integrate, port an existing app |
Frameworks, integration |
create, scaffold, add an application |
Scaffolding |
| Service, gateway, database |
Services |
| Enterprise, multi-service |
Enterprise |
| POC |
POC checklist |
| Logs, traces, metrics |
Observability |
| Profiling, CPU, heap, flamegraphs |
Performance |
| Cron, scheduled jobs |
Scheduler |
| CMS, content webhooks |
CMS integration |
| Docker |
Docker |
| Kubernetes |
Kubernetes |
| Cloud |
Cloud deployment |
| Commands, import, resolve, admin |
CLI |
| Operations |
Operations |
| Diagnosis |
Troubleshooting |
| Status |
Status check below |
Read only the references relevant to the task. Reference examples illustrate individual
concerns; merge them with existing configuration instead of replacing whole files.
Reading bundled references
wattpm skill prints this file verbatim. All relative Markdown links refer to documents
inside the same release's bundle, not files in the user's application or the discovery skill.
Resolve a link relative to the document currently being read, remove its fragment, and
pass the resulting bundle-relative path to the same local wattpm skill command.
wattpm skill references/frameworks.md
wattpm skill references/frameworks/nextjs.md
For example, frameworks/nextjs.md in references/frameworks.md resolves to
references/frameworks/nextjs.md. All bundled references are available offline. External
web links provide optional further reading; they are not paths accepted by this command.
Status check
- Identify installed versions and report mixed Watt majors or incompatible capabilities.
- Check Node.js against the installed release's requirement.
- Inspect recognized configuration files, scripts, build output, application IDs, and listeners.
- Inspect environment variable names, not values. Deployment-supplied variables do not require
.env.
- Distinguish static inspection from schema validation and successful startup. Parsing JSON
or printing a CLI version does not establish that an application is ready.
- With authorization, check development startup, representative endpoints/internal calls,
framework build, production startup, and shutdown. Stop processes started for validation.
Report findings, changes, checks performed, and remaining decisions. The companion agents
and slash commands in platformatic/skills are distributed separately from this bundle.
1---2name: watt3description: |4 Scaffold, integrate, configure, diagnose, profile, and deploy Platformatic Watt 3 applications.5 Use for watt.json, multi-application workspaces, gateways, services, databases, wattpm commands,6 observability, scheduled jobs, CMS integration, Docker, Kubernetes, and cloud deployments.7 Covers Next.js, Nuxt, Nitro, React Router, TanStack Start, Vite, Express, Fastify, Koa, Remix,8 Astro, NestJS, and external PHP capabilities.9argument-hint: "[init|create|deploy|status] [framework-hint]"10allowed-tools: Read, Glob, Grep, Bash, Write, Edit11metadata:12 source: https://skillmd.com/skills/tuyv/watt13---1415# Watt 31617These instructions ship with the installed Watt 3 release. The `wattpm skill [FILE]`18command is available starting with **3.74.0**. Prefer writing application files directly19when assisting an agent-driven workflow. Watt 3 still supports its existing generators,20including `create`, `init`, `add`, and import workflows.2122## Inspect the project23241. Read project instructions, manifests, lockfiles, configuration, entrypoints, and deployment files.252. Require Node.js **22.19.0 or newer** in development, CI, and production.263. Identify the installed Watt version and capability versions. Keep dependencies on major 3;27 do not silently upgrade to Watt 4. Check external capabilities' compatibility separately.284. Preserve the package manager, module system, workspace boundaries, scripts, and existing topology.295. Identify public listeners, application IDs, environment variable names, and the requested goal.306. Preserve unrelated code and secrets. Explain substantial changes and obtain authorization31 before installing dependencies, running migrations, deploying, or executing project code.3233Use the project's local Watt installation for CLI checks. Do not fall back to a global34installation or let `npx` download the latest version. If no installation exists, agree35on the target version and installation first. If the version predates 3.74.0 or has no36`skill` command, stop the skill workflow and report the requirement; do not upgrade automatically.3738## Configuration contract3940- Prefer `watt.json` for new Watt 3 projects. Existing JSON5, YAML, and TOML configurations41 remain supported. Do not rewrite them into Watt 4 `watt.config.*` modules.42- Identify capabilities with `module` or a matching `$schema`. Use the exact installed43 package version for schema URLs rather than copying an old example's version.44- A multi-application root declares `applications` and/or `autoload`; Watt also supports45 the `services` and `web` directory shortcuts. Keep root runtime options at the root.46- A standalone capability can embed orchestration options under `runtime`. Do not add a47 nested `runtime` block to a runtime root merely because a capability example has one.48- Watt 3 uses `entrypoint` and root `server` for the public application. Check the capability49 and custom-command contract before changing listener addresses or ports.50- Environment placeholders such as `{PORT}` are valid. Preserve their required/default51 behavior and document variable names in `.env.example` without exposing secret values.52- Watt 3 tracing configuration is named `telemetry`. Inspect installed schemas before53 borrowing options from another release.54- Native TypeScript stripping does not replace framework builds or type checking and55 does not support every TypeScript language feature.5657Installed schemas and source take precedence over generic examples. A requested upgrade58to Watt 4 is a separate migration: obtain destination-version guidance explicitly rather59than applying v4 API or configuration changes during ordinary v3 maintenance.6061## Workflow router6263| Request | References |64| --- | --- |65| `init`, setup, integrate, port an existing app | [Frameworks](references/frameworks.md), [integration](references/integration.md) |66| `create`, scaffold, add an application | [Scaffolding](references/scaffolding.md) |67| Service, gateway, database | [Services](references/services.md) |68| Enterprise, multi-service | [Enterprise](references/enterprise.md) |69| POC | [POC checklist](references/poc-checklist.md) |70| Logs, traces, metrics | [Observability](references/observability.md) |71| Profiling, CPU, heap, flamegraphs | [Performance](references/performance.md) |72| Cron, scheduled jobs | [Scheduler](references/scheduler.md) |73| CMS, content webhooks | [CMS integration](references/cms-integration.md) |74| Docker | [Docker](references/deployment/docker.md) |75| Kubernetes | [Kubernetes](references/deployment/kubernetes.md) |76| Cloud | [Cloud deployment](references/deployment/cloud.md) |77| Commands, import, resolve, admin | [CLI](references/wattpm-cli.md) |78| Operations | [Operations](references/operations.md) |79| Diagnosis | [Troubleshooting](references/troubleshooting.md) |80| Status | Status check below |8182Read only the references relevant to the task. Reference examples illustrate individual83concerns; merge them with existing configuration instead of replacing whole files.8485## Reading bundled references8687`wattpm skill` prints this file verbatim. All relative Markdown links refer to documents88inside the same release's bundle, not files in the user's application or the discovery skill.89Resolve a link relative to the document currently being read, remove its fragment, and90pass the resulting bundle-relative path to the same local `wattpm skill` command.9192```sh93wattpm skill references/frameworks.md94wattpm skill references/frameworks/nextjs.md95```9697For example, `frameworks/nextjs.md` in `references/frameworks.md` resolves to98`references/frameworks/nextjs.md`. All bundled references are available offline. External99web links provide optional further reading; they are not paths accepted by this command.100101## Status check1021031. Identify installed versions and report mixed Watt majors or incompatible capabilities.1042. Check Node.js against the installed release's requirement.1053. Inspect recognized configuration files, scripts, build output, application IDs, and listeners.1064. Inspect environment variable names, not values. Deployment-supplied variables do not require `.env`.1075. Distinguish static inspection from schema validation and successful startup. Parsing JSON108 or printing a CLI version does not establish that an application is ready.1096. With authorization, check development startup, representative endpoints/internal calls,110 framework build, production startup, and shutdown. Stop processes started for validation.111112Report findings, changes, checks performed, and remaining decisions. The companion agents113and slash commands in `platformatic/skills` are distributed separately from this bundle.