create-next-pro-cli 0.1.30 → 0.1.32

package/templates/Projects/default/AGENTS.md

@@ -0,0 +1,91 @@
+# Project Agent Instructions
+
+This repository was generated by `create-next-pro`. Follow these instructions when an agent creates or evolves project resources with the CLI.
+
+## Work from the correct directory
+
+- Run project creation from the parent directory that will contain the new project.
+- Run every `add*` command and `rmpage` from the generated project root, where `cnp.config.json` is located.
+- Prefer the installed `create-next-pro` executable. If it is unavailable, use `bunx create-next-pro-cli`, `npx create-next-pro-cli`, or `pnpm dlx create-next-pro-cli` with the same arguments.
+- Read the linked command skill before invoking a mutation.
+
+## Choose one package manager
+
+Bun is the primary example in this project. A Bun workflow does not require a separate Node.js installation. npm and pnpm remain supported alternatives for generated projects.
+
+Use one command family consistently in a working copy:
+
+```bash
+bun install
+bun run check
+bun run dev
+```
+
+```bash
+npm install
+npm run check
+npm run dev
+```
+
+```bash
+pnpm install
+pnpm run check
+pnpm run dev
+```
+
+Do not commit an additional lockfile unless the project has intentionally changed its package manager policy.
+
+## Use the agentic output contract
+
+- Add `--json` to non-interactive agent commands.
+- Pass every required argument in JSON mode. The CLI never opens prompts in that mode.
+- Parse the single JSON document from standard output. Do not scrape the human renderer.
+- Check `status`, `events`, `nextSteps`, and `error`, not only `exitCode`.
+- Treat `success`, `unchanged`, and `cancelled` as exit code `0`. Treat `failed` as exit code `1`.
+- Verify every `created`, `copied`, or `updated` path and confirm every `deleted` path is absent.
+- Complete all required `nextSteps` before considering the task finished.
+
+## Protect project data
+
+- Never print, commit, or include `.env` values in prompts, logs, events, or reports.
+- Use `.env.example` as the public development contract. Create a local file with `cp .env.example .env`, then replace credentials for production.
+- Use `--force` only after resolving and inspecting the exact destination. It deletes the existing child destination before scaffolding.
+- Pass logical names, not filesystem paths. Names use safe dot-separated segments such as `account.security`; never pass absolute paths, slashes, empty segments, or `..`.
+- Select `--area public` or `--area user` explicitly for page creation, direct page removal, and page-scoped components. A route area controls the layout and authorization boundary without changing the public URL.
+- Preserve existing source files. The add commands report existing resources as `unchanged` instead of overwriting them.
+- Use `rmpage` only for a page returned by the area-aware CLI page catalog, and inspect deletion events before making follow-up edits.
+
+## CLI operations
+
+| Operation        | Purpose                                                         | Skill                                                                                       |
+| ---------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| Create a project | Scaffold the complete Next.js project in a new child directory. | [`$create-next-pro-create-project`](.agents/skills/create-next-pro-create-project/SKILL.md) |
+| `addpage`        | Add an explicitly zoned route, page UI, and localized messages. | [`$create-next-pro-addpage`](.agents/skills/create-next-pro-addpage/SKILL.md)               |
+| `addcomponent`   | Add a global or area-qualified page component and messages.     | [`$create-next-pro-addcomponent`](.agents/skills/create-next-pro-addcomponent/SKILL.md)     |
+| `addlib`         | Add a library directory or a library module and export.         | [`$create-next-pro-addlib`](.agents/skills/create-next-pro-addlib/SKILL.md)                 |
+| `addapi`         | Add an App Router API route handler.                            | [`$create-next-pro-addapi`](.agents/skills/create-next-pro-addapi/SKILL.md)                 |
+| `addlanguage`    | Copy and register a new locale that must then be translated.    | [`$create-next-pro-addlanguage`](.agents/skills/create-next-pro-addlanguage/SKILL.md)       |
+| `addtext`        | Set one translation path across all configured locales.         | [`$create-next-pro-addtext`](.agents/skills/create-next-pro-addtext/SKILL.md)               |
+| `rmpage`         | Remove one area-qualified page and its resources safely.        | [`$create-next-pro-rmpage`](.agents/skills/create-next-pro-rmpage/SKILL.md)                 |
+
+## Global options
+
+- `--json`: emit one deterministic JSON document without prompts or decorative output.
+- `--force`: replace an existing project destination during project creation only.
+- `--reconfigure`: rerun the interactive CLI configuration assistant.
+- `--help`: display public command help.
+- `--version` or `-v`: display the CLI version.
+
+## Page-area option
+
+- `--area public`: target the public route group and layout.
+- `--area user`: target the authenticated user route group and layout.
+- The option is required for direct `addpage`, direct `rmpage`, and `addcomponent --page` commands. It is rejected for global components.
+- Do not infer an area from a page name or persist one as a project-wide default.
+
+## Finish every mutation
+
+1. Inspect the CLI result and all changed paths.
+2. Complete required review or translation steps.
+3. Run `bun run check`, `npm run check`, or `pnpm run check` with the selected package manager.
+4. Report the command, status, affected paths, and any remaining required work.

package/templates/Projects/default/README.md

@@ -4,21 +4,27 @@ Next.js App Router template for `create-next-pro-cli`.
 
 ## Runtime
 
-Choose Bun, npm, or pnpm for dependency installation and project scripts. The
-repository keeps `bun.lock` as its reproducible source lockfile, while npm and
-pnpm consumers create their own lockfiles in their working copies.
+Choose one runtime and package-manager path for dependency installation and
+project scripts. The repository keeps `bun.lock` as its reproducible source
+lockfile, while npm and pnpm consumers create their own lockfiles in their
+working copies.
 
-Required:
+Bun-only path:
+
+```bash
+bun --version
+```
+
+Node.js path:
 
 ```bash
 node --version
-bun --version # optional
-npm --version # optional
-pnpm --version # optional
+npm --version # or: pnpm --version
 ```
 
-Node must satisfy `>=24.0.0`. Bun must satisfy `>=1.3.14` when selected, and
-pnpm 11 or later is supported.
+Bun must satisfy `>=1.3.14` when selected and does not require a separate
+Node.js installation. The Node.js path requires Node.js `>=24.0.0`; pnpm 11 or
+later is supported.
 
 The npm `allowScripts` policy and pnpm `allowBuilds` policy approve only the
 native build steps required by Next.js and the file-watcher toolchain. Security
@@ -87,6 +93,20 @@ Replace `bun run` with `npm run` or `pnpm run` for the selected manager. The
 `audit` and `test:consumer` scripts detect the invoking manager without shell
 commands, including on Windows.
 
+## Agent workflows
+
+Codex-compatible project guidance is available in `AGENTS.md`. Focused command
+skills under `.agents/skills` document project creation and every public
+`add*`/`rmpage` operation. Agents should read the matching skill, invoke the CLI
+with `--json`, inspect all reported events and complete every required next
+step before running the project checks.
+
+Page operations use explicit route areas. Pass `--area public` or `--area user`
+to direct `addpage` and `rmpage` commands and to `addcomponent --page`. The
+interactive page flows expose the same area-aware catalog. Areas select a route
+layout without changing the public URL; see the linked command skills for the
+complete contract.
+
 ## Template Features
 
 - Next.js 16 App Router