create-next-pro-cli 0.1.30 → 0.1.32

package/README.md

@@ -95,12 +95,12 @@ Run the following commands from the root of a generated project.
 
 ```bash
 # Simple or nested pages
-create-next-pro addpage profile
-create-next-pro addpage account.security
+create-next-pro addpage profile --area public
+create-next-pro addpage account.security --area user
 
 # Global components or components attached to a page
 create-next-pro addcomponent Alert
-create-next-pro addcomponent PasswordForm --page account.security
+create-next-pro addcomponent PasswordForm --page account.security --area user
 
 # Libraries and modules
 create-next-pro addlib analytics
@@ -114,17 +114,19 @@ create-next-pro addlanguage de
 create-next-pro addtext dashboard.welcome "Welcome"
 
 # Direct removal
-create-next-pro rmpage account.security
+create-next-pro rmpage account.security --area user
 
 # Tree-based autocomplete menu with confirmation
 create-next-pro rmpage
 ```
 
+Every page belongs to an explicit route area. Use `--area public` for routes rendered by the public layout and `--area user` for authenticated routes rendered by the user layout. There is no default area. Direct `addpage` and `rmpage` commands require it, as does `addcomponent --page`; interactive `addpage` asks for it and the `rmpage` menu groups pages by area. Route groups do not alter the public URL.
+
 `addlanguage` copies every message file from the configured default locale. The command reports each copied path and emits a required `translate` next step: the copied source-language text must be translated before the locale is ready to ship.
 
 `addpage` creates `layout`, `page`, and `loading` files by default. Available long options are `--layout`, `--page`, `--loading`, `--not-found`, `--error`, `--global-error`, `--route`, `--template`, and `--default`. The historical short forms remain available.
 
-`rmpage` only lists routes that contain an actual `page.tsx`. Next.js route groups and technical directories are hidden. Removal is confined to the project and preserves shared parent directories and unrelated files.
+`rmpage` only lists routes that contain an actual `page.tsx` in the `(public)` or `(user)` route group. Technical directories remain hidden. Removal is confined to the selected area and project, and it preserves shared parent directories and unrelated files.
 
 ## Generated project architecture
 
@@ -132,9 +134,15 @@ The Next.js route and its interface are separate: `src/app` owns routing while `
 
 ```text
 my-app/
+├── .agents/
+│   └── skills/
+│       ├── create-next-pro-create-project/
+│       ├── create-next-pro-addpage/
+│       └── ...
 ├── .env.example
 ├── .gitignore
 ├── .prettierignore
+├── AGENTS.md
 ├── bun.lock
 ├── cnp.config.json
 ├── messages/
@@ -202,6 +210,8 @@ my-app/
 
 Template working files (`.env`, the nested Git repository, caches, screenshots, and test results) are not copied into generated projects. The CLI creates `cnp.config.json` with the project name and selected alias.
 
+Generated projects also include concise root guidance in `AGENTS.md` and eight instruction-only command skills under `.agents/skills`. Agents should prefer the deterministic `--json` contract and read the matching skill before invoking a project mutation.
+
 ## CLI architecture
 
 ```text
@@ -326,7 +336,7 @@ The versioned document has stable status, event, next-step, and error fields:
 
 Paths inside events and next steps are relative to their named scope. Applicable absolute roots are exposed as `projectRoot`, `configRoot`, and `homeRoot`. Events never contain file contents, environment values, credentials, or secrets.
 
-Command statuses are `success`, `unchanged`, `cancelled`, and `failed`. Successful mutations, idempotent no-op results, and user cancellations exit with code `0`; only `failed` exits with code `1`. Stable error codes include `INVALID_ARGUMENT`, `CONFIG_NOT_FOUND`, `I18N_DISABLED`, `TARGET_EXISTS`, `TARGET_NOT_FOUND`, `TEMPLATE_MISSING`, `UNSAFE_PATH`, `INCONSISTENT_LOCALE`, `FILESYSTEM_ERROR`, `INTERACTIVE_INPUT_REQUIRED`, and `ONBOARDING_REQUIRED`.
+Command statuses are `success`, `unchanged`, `cancelled`, and `failed`. Successful mutations, idempotent no-op results, and user cancellations exit with code `0`; only `failed` exits with code `1`. Stable error codes include `INVALID_ARGUMENT`, `CONFIG_NOT_FOUND`, `I18N_DISABLED`, `TARGET_EXISTS`, `TARGET_NOT_FOUND`, `TEMPLATE_MISSING`, `UNSAFE_PATH`, `INCONSISTENT_ROUTE`, `INCONSISTENT_LOCALE`, `FILESYSTEM_ERROR`, `INTERACTIVE_INPUT_REQUIRED`, and `ONBOARDING_REQUIRED`.
 
 Interactive input is never attempted in JSON mode. Pass every required argument explicitly. On a new machine, run the CLI once without `--json` to complete onboarding; `--reconfigure --json` is intentionally rejected.
 

package/create-next-pro-completion.sh

@@ -1,13 +1,14 @@
 # Bash completion for create-next-pro.
 _create_next_pro_complete() {
-  local cur command candidates
+  local cur candidates
+  local -a prior
   COMPREPLY=()
   cur="${COMP_WORDS[COMP_CWORD]}"
-  command="${COMP_WORDS[1]}"
   if [[ ${COMP_CWORD} -eq 1 ]]; then
     candidates="$(create-next-pro __complete 2>/dev/null)"
   else
-    candidates="$(create-next-pro __complete "${command}" 2>/dev/null)"
+    prior=("${COMP_WORDS[@]:1:$((COMP_CWORD - 1))}")
+    candidates="$(create-next-pro __complete "${prior[@]}" 2>/dev/null)"
   fi
   mapfile -t COMPREPLY < <(compgen -W "${candidates}" -- "${cur}")
 }

package/create-next-pro-completion.zsh

@@ -1,12 +1,12 @@
 #compdef create-next-pro
 
 _create_next_pro() {
-  local command
-  command="${words[2]}"
+  local -a prior
   if (( CURRENT == 2 )); then
     compadd -- ${(f)"$(create-next-pro __complete 2>/dev/null)"}
   else
-    compadd -- ${(f)"$(create-next-pro __complete "${command}" 2>/dev/null)"}
+    prior=("${(@)words[2,$((CURRENT - 1))]}")
+    compadd -- ${(f)"$(create-next-pro __complete "${prior[@]}" 2>/dev/null)"}
   fi
 }