@angular/cli 19.1.0-rc.0 → 19.1.0

package/lib/config/schema.json

@@ -908,15 +908,15 @@
     "SchematicsAngularApplicationSchema": {
       "title": "Angular Application Options Schema",
       "type": "object",
-      "description": "Generates a new basic application definition in the \"projects\" subfolder of the workspace.",
+      "description": "Generates a new Angular application within your workspace. This schematic sets up the foundational structure of your project, including the root component, module, and configuration files. You can customize various aspects of the application, such as routing, styling, and testing.",
       "additionalProperties": false,
       "properties": {
         "projectRoot": {
-          "description": "The root directory of the new application.",
+          "description": "The directory where the new application's files will be created, relative to the workspace root. If not specified, the application will be created in a subfolder within the `projects` directory, using the application's name.",
           "type": "string"
         },
         "name": {
-          "description": "The name of the new application.",
+          "description": "The name for the new application. This name will be used for the project directory and various identifiers throughout the application's code.",
           "type": "string",
           "pattern": "^(?:@[a-zA-Z0-9-*~][a-zA-Z0-9-*._~]*/)?[a-zA-Z0-9-~][a-zA-Z0-9-._~]*$",
           "$default": {
@@ -925,17 +925,17 @@
           }
         },
         "inlineStyle": {
-          "description": "Include styles inline in the root component.ts file. Only CSS styles can be included inline. Default is false, meaning that an external styles file is created and referenced in the root component.ts file.",
+          "description": "Include the styles for the root component directly within the `app.component.ts` file. Only CSS styles can be included inline. By default, a separate stylesheet file (e.g., `app.component.css`) is created.",
           "type": "boolean",
           "alias": "s"
         },
         "inlineTemplate": {
-          "description": "Include template inline in the root component.ts file. Default is false, meaning that an external template file is created and referenced in the root component.ts file. ",
+          "description": "Include the HTML template for the root component directly within the `app.component.ts` file. By default, a separate template file (e.g., `app.component.html`) is created.",
           "type": "boolean",
           "alias": "t"
         },
         "viewEncapsulation": {
-          "description": "The view encapsulation strategy to use in the new application.",
+          "description": "Sets the view encapsulation mode for the application's components. This determines how component styles are scoped and applied.",
           "enum": [
             "Emulated",
             "None",
@@ -945,18 +945,18 @@
         },
         "routing": {
           "type": "boolean",
-          "description": "Creates an application with routing enabled.",
+          "description": "Generate an application with routing already configured. This sets up the necessary files and modules for managing navigation between different views in your application.",
           "default": true
         },
         "prefix": {
           "type": "string",
           "format": "html-selector",
-          "description": "A prefix to apply to generated selectors.",
+          "description": "A prefix to be added to the selectors of components generated within this application. For example, if the prefix is `my-app` and you generate a component named `my-component`, the selector will be `my-app-my-component`.",
           "default": "app",
           "alias": "p"
         },
         "style": {
-          "description": "The file extension or preprocessor to use for style files.",
+          "description": "The type of stylesheet files to be created for components in the application.",
           "type": "string",
           "default": "css",
           "enum": [
@@ -967,7 +967,7 @@
           ]
         },
         "skipTests": {
-          "description": "Do not create \"spec.ts\" test files for the application.",
+          "description": "Skip the generation of a unit test files `spec.ts`.",
           "type": "boolean",
           "default": false,
           "alias": "S"
@@ -975,39 +975,39 @@
         "skipPackageJson": {
           "type": "boolean",
           "default": false,
-          "description": "Do not add dependencies to the \"package.json\" file."
+          "description": "Do not add dependencies to the `package.json` file."
         },
         "minimal": {
-          "description": "Create a bare-bones project without any testing frameworks. (Use for learning purposes only.)",
+          "description": "Generate a minimal project without any testing frameworks. This is intended for learning purposes and simple experimentation, not for production applications.",
           "type": "boolean",
           "default": false
         },
         "skipInstall": {
-          "description": "Skip installing dependency packages.",
+          "description": "Skip the automatic installation of packages. You will need to manually install the dependencies later.",
           "type": "boolean",
           "default": false
         },
         "strict": {
-          "description": "Creates an application with stricter bundle budgets settings.",
+          "description": "Enable stricter bundle budget settings for the application. This helps to keep your application's bundle size small and improve performance. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode",
           "type": "boolean",
           "default": true
         },
         "standalone": {
-          "description": "Creates an application based upon the standalone API, without NgModules.",
+          "description": "Create an application that utilizes the standalone API, eliminating the need for NgModules. This can simplify the structure of your application.",
           "type": "boolean",
           "default": true
         },
         "ssr": {
-          "description": "Creates an application with Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering) enabled.",
+          "description": "Configure the application for Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering).",
           "type": "boolean",
           "default": false
         },
         "serverRouting": {
-          "description": "Creates a server application using the Server Routing and App Engine APIs (Developer Preview).",
+          "description": "Set up a server application using the Server Routing and App Engine APIs (Developer Preview).",
           "type": "boolean"
         },
         "experimentalZoneless": {
-          "description": "Create an application that does not utilize zone.js.",
+          "description": "Generate an application that does not use `zone.js`.",
           "type": "boolean",
           "default": false
         }
@@ -1016,12 +1016,12 @@
     "SchematicsAngularClassSchema": {
       "title": "Angular Class Options Schema",
       "type": "object",
-      "description": "Creates a new, generic class definition in the given project.",
+      "description": "Creates a new class in your project. Classes are the fundamental building blocks for object-oriented programming in TypeScript. They provide a blueprint for creating objects with properties and methods. This schematic helps you generate a new class with the basic structure and optional test files.",
       "additionalProperties": false,
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the new class.",
+          "description": "The name for the new class. This will be used to create the class file (e.g., `my-class.ts`) and, if enabled, the corresponding test file `my-class.spec.ts`.",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1033,31 +1033,31 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the class, relative to the workspace root.",
+          "description": "The path where the class file should be created, relative to the workspace root. If not specified, the class will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the class should be added. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new class.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the new class.",
           "default": false
         },
         "type": {
           "type": "string",
-          "description": "Adds a developer-defined type to the filename, in the format \"name.type.ts\"."
+          "description": "Adds a custom type to the filename, allowing you to create more descriptive class names. For example, if you set the type to `helper`, the filename will be `my-class.helper.ts`."
         }
       }
     },
     "SchematicsAngularComponentSchema": {
       "title": "Angular Component Options Schema",
       "type": "object",
-      "description": "Creates a new, generic component definition in the given project.",
+      "description": "Creates a new Angular component. Components are the basic building blocks of Angular applications. Each component consists of a TypeScript class, an HTML template, and an optional CSS stylesheet. Use this schematic to generate a new component in your project.",
       "additionalProperties": false,
       "properties": {
         "path": {
@@ -1066,49 +1066,49 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the component file, relative to the current workspace. Default is a folder with the same name as the component in the project root.",
+          "description": "The path where the component files should be created, relative to the current workspace. If not provided, a folder with the same name as the component will be created in the project's `src/app` directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the component should be added. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "name": {
           "type": "string",
-          "description": "The name of the component.",
+          "description": "The name for the new component. This will be used to create the component's class, template, and stylesheet files. For example, if you provide `my-component`, the files will be named `my-component.component.ts`, `my-component.component.html`, and `my-component.component.css`.",
           "$default": {
             "$source": "argv",
             "index": 0
           }
         },
         "displayBlock": {
-          "description": "Specifies if the style will contain `:host { display: block; }`.",
+          "description": "Adds `:host { display: block; }` to the component's stylesheet, ensuring the component renders as a block-level element. This is useful for layout purposes.",
           "type": "boolean",
           "default": false,
           "alias": "b"
         },
         "inlineStyle": {
-          "description": "Include styles inline in the component.ts file. Only CSS styles can be included inline. By default, an external styles file is created and referenced in the component.ts file.",
+          "description": "Include the component's styles directly in the `component.ts` file. By default, a separate stylesheet file (e.g., `my-component.component.css`) is created.",
           "type": "boolean",
           "default": false,
           "alias": "s"
         },
         "inlineTemplate": {
-          "description": "Include template inline in the component.ts file. By default, an external template file is created and referenced in the component.ts file.",
+          "description": "Include the component's HTML template directly in the `component.ts` file. By default, a separate template file (e.g., `my-component.component.html`) is created.",
           "type": "boolean",
           "default": false,
           "alias": "t"
         },
         "standalone": {
-          "description": "Whether the generated component is standalone.",
+          "description": "Generate a standalone component. Standalone components are self-contained and don't need to be declared in an NgModule. They can be used independently or imported directly into other standalone components.",
           "type": "boolean",
           "default": true
         },
         "viewEncapsulation": {
-          "description": "The view encapsulation strategy to use in the new component.",
+          "description": "Sets the view encapsulation mode for the component. This determines how the component's styles are scoped and applied.",
           "enum": [
             "Emulated",
             "None",
@@ -1118,7 +1118,7 @@
           "alias": "v"
         },
         "changeDetection": {
-          "description": "The change detection strategy to use in the new component.",
+          "description": "Configures the change detection strategy for the component.",
           "enum": [
             "Default",
             "OnPush"
@@ -1129,7 +1129,7 @@
         },
         "prefix": {
           "type": "string",
-          "description": "The prefix to apply to the generated component selector.",
+          "description": "A prefix to be added to the component's selector. For example, if the prefix is `app` and the component name is `my-component`, the selector will be `app-my-component`.",
           "alias": "p",
           "oneOf": [
             {
@@ -1142,7 +1142,7 @@
           ]
         },
         "style": {
-          "description": "The file extension or preprocessor to use for style files, or 'none' to skip generating the style file.",
+          "description": "Specify the type of stylesheet to be created for the component, or `none` to skip creating a stylesheet.",
           "type": "string",
           "default": "css",
           "enum": [
@@ -1155,60 +1155,60 @@
         },
         "type": {
           "type": "string",
-          "description": "Adds a developer-defined type to the filename, in the format \"name.type.ts\".",
+          "description": "Append a custom type to the component's filename. For example, if you set the type to `container`, the file will be named `my-component.container.ts`.",
           "default": "Component"
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new component.",
+          "description": "Skip the generation of unit test files `spec.ts`.",
           "default": false
         },
         "flat": {
           "type": "boolean",
-          "description": "Create the new files at the top level of the current project.",
+          "description": "Create the component files directly in the project's `src/app` directory instead of creating a new folder for them.",
           "default": false
         },
         "skipImport": {
           "type": "boolean",
-          "description": "Do not import this component into the owning NgModule.",
+          "description": "Do not automatically import the new component into its closest NgModule.",
           "default": false
         },
         "selector": {
           "type": "string",
           "format": "html-selector",
-          "description": "The HTML selector to use for this component."
+          "description": "The HTML selector to use for this component. If not provided, a selector will be generated based on the component name (e.g., `app-my-component`)."
         },
         "skipSelector": {
           "type": "boolean",
           "default": false,
-          "description": "Specifies if the component should have a selector or not."
+          "description": "Skip the generation of an HTML selector for the component."
         },
         "module": {
           "type": "string",
-          "description": "The declaring NgModule.",
+          "description": "Specify the NgModule where the component should be declared. If not provided, the CLI will attempt to find the closest NgModule in the component's path.",
           "alias": "m"
         },
         "export": {
           "type": "boolean",
           "default": false,
-          "description": "The declaring NgModule exports this component."
+          "description": "Automatically export the component from the specified NgModule, making it accessible to other modules in the application."
         },
         "exportDefault": {
           "type": "boolean",
           "default": false,
-          "description": "Use default export for the component instead of a named export."
+          "description": "Use a default export for the component in its TypeScript file instead of a named export."
         }
       }
     },
     "SchematicsAngularDirectiveSchema": {
       "title": "Angular Directive Options Schema",
       "type": "object",
-      "description": "Creates a new, generic directive definition in the given project.",
+      "description": "Creates a new directive in your project. Directives are used to extend the behavior or appearance of HTML elements and components. They allow you to manipulate the DOM, add custom attributes, and respond to events. This schematic generates the necessary files and boilerplate code for a new directive.",
       "additionalProperties": false,
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the new directive.",
+          "description": "The name for the new directive. This will be used to create the directive's class and spec files (e.g., `my-directive.directive.ts` and `my-directive.directive.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1220,19 +1220,19 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the interface that defines the directive, relative to the workspace root.",
+          "description": "The path where the directive files should be created, relative to the workspace root. If not provided, the directive will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the directive should be added. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "prefix": {
           "type": "string",
-          "description": "A prefix to apply to generated selectors.",
+          "description": "A prefix to be added to the directive's selector. For example, if the prefix is `app` and the directive name is `highlight`, the selector will be `appHighlight`.",
           "alias": "p",
           "oneOf": [
             {
@@ -1246,50 +1246,50 @@
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new class.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the new directive.",
           "default": false
         },
         "skipImport": {
           "type": "boolean",
-          "description": "Do not import this directive into the owning NgModule.",
+          "description": "Do not automatically import the new directive into its closest NgModule.",
           "default": false
         },
         "selector": {
           "type": "string",
           "format": "html-selector",
-          "description": "The HTML selector to use for this directive."
+          "description": "The HTML selector to use for this directive. If not provided, a selector will be generated based on the directive's name (e.g., `appHighlight`)."
         },
         "standalone": {
-          "description": "Whether the generated directive is standalone.",
+          "description": "Generate a standalone directive. Standalone directives are self-contained and don't need to be declared in an NgModule. They can be used independently or imported directly into other standalone components or directives.",
           "type": "boolean",
           "default": true
         },
         "flat": {
           "type": "boolean",
-          "description": "When true (the default), creates the new files at the top level of the current project.",
+          "description": "Creates the new directive files at the top level of the current project. If set to false, a new folder with the directive's name will be created to contain the files.",
           "default": true
         },
         "module": {
           "type": "string",
-          "description": "The declaring NgModule.",
+          "description": "Specify the NgModule where the directive should be declared. If not provided, the CLI will attempt to find the closest NgModule in the directive's path.",
           "alias": "m"
         },
         "export": {
           "type": "boolean",
           "default": false,
-          "description": "The declaring NgModule exports this directive."
+          "description": "Automatically export the directive from the specified NgModule, making it accessible to other modules in the application."
         }
       }
     },
     "SchematicsAngularEnumSchema": {
       "title": "Angular Enum Options Schema",
       "type": "object",
-      "description": "Generates a new, generic enum definition in the given project.",
+      "description": "Creates a new enum in your project. Enums (enumerations) are a way to define a set of named constants, making your code more readable and maintainable. This schematic generates a new enum with the specified name and type.",
       "additionalProperties": false,
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the enum.",
+          "description": "The name for the new enum. This will be used to create the enum file (e.g., `my-enum.enum.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1301,31 +1301,31 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the enum definition, relative to the current workspace.",
+          "description": "The path where the enum file should be created, relative to the current workspace. If not specified, the enum will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project in which to create the enum. Default is the configured default project for the workspace.",
+          "description": "The name of the project where the enum should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "type": {
           "type": "string",
-          "description": "Adds a developer-defined type to the filename, in the format \"name.type.ts\"."
+          "description": "Adds a custom type to the filename, allowing you to create more descriptive enum names. For example, if you set the type to `status`, the filename will be `my-enum.status.ts`."
         }
       }
     },
     "SchematicsAngularGuardSchema": {
       "title": "Angular Guard Options Schema",
       "type": "object",
-      "description": "Generates a new, generic route guard definition in the given project.",
+      "description": "Creates a new route guard in your project. Route guards are used to control access to parts of your application by checking certain conditions before a route is activated. This schematic generates a new guard with the specified name, type, and options.",
       "additionalProperties": false,
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the new route guard.",
+          "description": "The name for the new route guard. This will be used to create the guard's class and spec files (e.g., `my-guard.guard.ts` and `my-guard.guard.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1333,12 +1333,12 @@
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new guard.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the new guard.",
           "default": false
         },
         "flat": {
           "type": "boolean",
-          "description": "When true (the default), creates the new files at the top level of the current project.",
+          "description": "Creates the new guard files at the top level of the current project. If set to false, a new folder with the guard's name will be created to contain the files.",
           "default": true
         },
         "path": {
@@ -1347,25 +1347,25 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the interface that defines the guard, relative to the current workspace.",
+          "description": "The path where the guard files should be created, relative to the current workspace. If not provided, the guard will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the guard should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "functional": {
           "type": "boolean",
-          "description": "Specifies whether to generate a guard as a function.",
+          "description": "Generate the guard as a function instead of a class. Functional guards can be simpler for basic scenarios.",
           "default": true
         },
         "implements": {
           "alias": "guardType",
           "type": "array",
-          "description": "Specifies which type of guard to create.",
+          "description": "Specifies the type(s) of guard to create. You can choose one or more of the following: `CanActivate` (controls access to a route), `CanActivateChild` (controls access to child routes), `CanDeactivate` (asks for confirmation before leaving a route), `CanMatch` (determines if a route can be matched).",
           "uniqueItems": true,
           "minItems": 1,
           "items": {
@@ -1387,11 +1387,11 @@
       "title": "Angular Interceptor Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Creates a new, generic interceptor definition in the given project.",
+      "description": "Creates a new interceptor in your project. Interceptors are used to intercept and modify HTTP requests and responses before they reach their destination. This allows you to perform tasks like adding authentication headers, handling errors, or logging requests. This schematic generates the necessary files and boilerplate code for a new interceptor.",
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the interceptor.",
+          "description": "The name for the new interceptor. This will be used to create the interceptor's class and spec files (e.g., `my-interceptor.interceptor.ts` and `my-interceptor.interceptor.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1403,12 +1403,12 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the interceptor, relative to the workspace root.",
+          "description": "The path where the interceptor files should be created, relative to the workspace root. If not provided, the interceptor will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the interceptor should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
@@ -1416,16 +1416,16 @@
         "flat": {
           "type": "boolean",
           "default": true,
-          "description": "When true (the default), creates files at the top level of the project."
+          "description": "Creates the new interceptor files at the top level of the current project. If set to false, a new folder with the interceptor's name will be created to contain the files."
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new interceptor.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the new interceptor.",
           "default": false
         },
         "functional": {
           "type": "boolean",
-          "description": "Creates the interceptor as a `HttpInterceptorFn`.",
+          "description": "Creates the interceptor as a function `HttpInterceptorFn` instead of a class. Functional interceptors can be simpler for basic scenarios.",
           "default": true
         }
       }
@@ -1434,11 +1434,11 @@
       "title": "Angular Interface Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Creates a new, generic interface definition in the given project.",
+      "description": "Creates a new interface in your project. Interfaces define the structure of objects in TypeScript, ensuring type safety and code clarity. This schematic generates a new interface with the specified name and type.",
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the interface.",
+          "description": "The name for the new interface. This will be used to create the interface file (e.g., `my-interface.interface.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1450,23 +1450,23 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the interface, relative to the workspace root.",
+          "description": "The path where the interface file should be created, relative to the workspace root. If not provided, the interface will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the interface should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "prefix": {
           "type": "string",
-          "description": "A prefix to apply to generated selectors."
+          "description": "A prefix to be added to the interface name. This is typically not used for interfaces, as they don't have selectors like components or directives."
         },
         "type": {
           "type": "string",
-          "description": "Adds a developer-defined type to the filename, in the format \"name.type.ts\".",
+          "description": "Adds a custom type to the filename, allowing you to create more descriptive interface names. For example, if you set the type to `data`, the filename will be `my-interface.data.ts`.",
           "$default": {
             "$source": "argv",
             "index": 1
@@ -1477,12 +1477,12 @@
     "SchematicsAngularLibrarySchema": {
       "title": "Library Options Schema",
       "type": "object",
-      "description": "Creates a new, generic library project in the current workspace.",
+      "description": "Creates a new library project in your Angular workspace. Libraries are reusable collections of components, services, and other Angular artifacts that can be shared across multiple applications. This schematic simplifies the process of generating a new library with the necessary files and configurations.",
       "additionalProperties": false,
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the library.",
+          "description": "The name for the new library. This name will be used for the project directory and various identifiers within the library's code.",
           "pattern": "^(?:@[a-zA-Z0-9-*~][a-zA-Z0-9-*._~]*/)?[a-zA-Z0-9-~][a-zA-Z0-9-._~]*$",
           "$default": {
             "$source": "argv",
@@ -1492,37 +1492,37 @@
         "entryFile": {
           "type": "string",
           "format": "path",
-          "description": "The path at which to create the library's public API file, relative to the workspace root.",
+          "description": "The path to the library's public API file, relative to the workspace root. This file defines what parts of the library are accessible to applications that import it.",
           "default": "public-api"
         },
         "prefix": {
           "type": "string",
           "format": "html-selector",
-          "description": "A prefix to apply to generated selectors.",
+          "description": "A prefix to be added to the selectors of components generated within this library. For example, if the prefix is `my-lib` and you generate a component named `my-component`, the selector will be `my-lib-my-component`.",
           "default": "lib",
           "alias": "p"
         },
         "skipPackageJson": {
           "type": "boolean",
           "default": false,
-          "description": "Do not add dependencies to the \"package.json\" file. "
+          "description": "Do not automatically add dependencies to the `package.json` file."
         },
         "skipInstall": {
-          "description": "Do not install dependency packages.",
+          "description": "Skip the automatic installation of packages. You will need to manually install the dependencies later.",
           "type": "boolean",
           "default": false
         },
         "skipTsConfig": {
           "type": "boolean",
           "default": false,
-          "description": "Do not update \"tsconfig.json\" to add a path mapping for the new library. The path mapping is needed to use the library in an app, but can be disabled here to simplify development."
+          "description": "Do not update the workspace `tsconfig.json` file to add a path mapping for the new library. The path mapping is needed to use the library in an application, but can be disabled here to simplify development."
         },
         "projectRoot": {
           "type": "string",
-          "description": "The root directory of the new library."
+          "description": "The root directory for the new library, relative to the workspace root. If not specified, the library will be created in a subfolder within the `projects` directory, using the library's name."
         },
         "standalone": {
-          "description": "Creates a library based upon the standalone API, without NgModules.",
+          "description": "Create a library that utilizes the standalone API, eliminating the need for NgModules. This can simplify the structure of your library and its usage in applications.",
           "type": "boolean",
           "default": true
         }
@@ -1532,11 +1532,11 @@
       "title": "Angular Pipe Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Creates a new, generic pipe definition in the given project.",
+      "description": "Creates a new pipe in your project. Pipes are used to transform data for display in templates. They take input values and apply a specific transformation, such as formatting dates, currency, or filtering arrays. This schematic generates the necessary files and boilerplate code for a new pipe.",
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the pipe.",
+          "description": "The name for the new pipe. This will be used to create the pipe's class and spec files (e.g., `my-pipe.pipe.ts` and `my-pipe.pipe.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1548,12 +1548,12 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the pipe, relative to the workspace root.",
+          "description": "The path where the pipe files should be created, relative to the workspace root. If not provided, the pipe will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the pipe should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
@@ -1561,47 +1561,47 @@
         "flat": {
           "type": "boolean",
           "default": true,
-          "description": "When true (the default) creates files at the top level of the project."
+          "description": "Creates the new pipe files at the top level of the current project. If set to false, a new folder with the pipe's name will be created to contain the files."
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new pipe.",
+          "description": "Prevent the generation of a unit test file `spec.ts` for the new pipe.",
           "default": false
         },
         "skipImport": {
           "type": "boolean",
           "default": false,
-          "description": "Do not import this pipe into the owning NgModule."
+          "description": "Do not automatically import the new pipe into its closest NgModule."
         },
         "standalone": {
-          "description": "Whether the generated pipe is standalone.",
+          "description": "Generate a standalone pipe. Standalone pipes are self-contained and don't need to be declared in an NgModule. They can be used independently or imported directly into other standalone components, directives, or pipes.",
           "type": "boolean",
           "default": true
         },
         "module": {
           "type": "string",
-          "description": "The declaring NgModule.",
+          "description": "Specify the NgModule where the pipe should be declared. If not provided, the CLI will attempt to find the closest NgModule in the pipe's path.",
           "alias": "m"
         },
         "export": {
           "type": "boolean",
           "default": false,
-          "description": "The declaring NgModule exports this pipe."
+          "description": "Automatically export the pipe from the specified NgModule, making it accessible to other modules in the application."
         }
       }
     },
     "SchematicsAngularNgNewSchema": {
       "title": "Angular Ng New Options Schema",
       "type": "object",
-      "description": "Creates a new project by combining the workspace and application schematics.",
+      "description": "Creates a new Angular workspace and an initial project. This schematic sets up the foundation for your Angular development, generating the workspace configuration files and an optional starter application. You can customize various aspects of the workspace and the initial project, such as routing, styling, and testing.",
       "additionalProperties": false,
       "properties": {
         "directory": {
           "type": "string",
-          "description": "The directory name to create the workspace in."
+          "description": "The directory where the new workspace and project should be created. If not specified, the workspace will be created in the current directory."
         },
         "name": {
-          "description": "The name of the new workspace and initial project.",
+          "description": "The name for the new workspace and the initial project. This name will be used for the root directory and various identifiers throughout the project.",
           "type": "string",
           "$default": {
             "$source": "argv",
@@ -1609,18 +1609,18 @@
           }
         },
         "skipInstall": {
-          "description": "Do not install dependency packages.",
+          "description": "Skip the automatic installation of packages. You will need to manually install the dependencies later.",
           "type": "boolean",
           "default": false
         },
         "skipGit": {
-          "description": "Do not initialize a git repository.",
+          "description": "Do not initialize a Git repository in the new workspace. By default, a Git repository is initialized to help you track changes to your project.",
           "type": "boolean",
           "default": false,
           "alias": "g"
         },
         "commit": {
-          "description": "Initial git repository commit information.",
+          "description": "Configure the initial Git commit for the new repository.",
           "oneOf": [
             {
               "type": "boolean"
@@ -1644,22 +1644,22 @@
           "default": true
         },
         "newProjectRoot": {
-          "description": "The path where new projects will be created, relative to the new workspace root.",
+          "description": "The path where new projects will be created within the workspace, relative to the workspace root. By default, new projects are created in the `projects` directory.",
           "type": "string",
           "default": "projects"
         },
         "inlineStyle": {
-          "description": "Include styles inline in the component TS file. By default, an external styles file is created and referenced in the component TypeScript file.",
+          "description": "Include the styles for the initial application's root component directly within the `app.component.ts` file. By default, a separate stylesheet file (e.g., `app.component.css`) is created.",
           "type": "boolean",
           "alias": "s"
         },
         "inlineTemplate": {
-          "description": "Include template inline in the component TS file. By default, an external template file is created and referenced in the component TypeScript file.",
+          "description": "Include the HTML template for the initial application's root component directly within the `app.component.ts` file. By default, a separate template file (e.g., `app.component.html`) is created.",
           "type": "boolean",
           "alias": "t"
         },
         "viewEncapsulation": {
-          "description": "The view encapsulation strategy to use in the initial project.",
+          "description": "Sets the view encapsulation mode for components in the initial project. This determines how component styles are scoped and applied. Options include: `Emulated` (default, styles are scoped to the component), `None` (styles are global), and `ShadowDom` (styles are encapsulated using Shadow DOM).",
           "enum": [
             "Emulated",
             "None",
@@ -1677,18 +1677,18 @@
         },
         "routing": {
           "type": "boolean",
-          "description": "Enable routing in the initial project."
+          "description": "Enable routing in the initial application project. This sets up the necessary files and modules for managing navigation between different views in your application."
         },
         "prefix": {
           "type": "string",
           "format": "html-selector",
-          "description": "The prefix to apply to generated selectors for the initial project.",
+          "description": "The prefix to apply to generated selectors for the initial project. For example, if the prefix is `my-app` and you generate a component named `my-component`, the selector will be `my-app-my-component`.",
           "minLength": 1,
           "default": "app",
           "alias": "p"
         },
         "style": {
-          "description": "The file extension or preprocessor to use for style files.",
+          "description": "The type of stylesheet files to be created for components in the initial project.",
           "type": "string",
           "enum": [
             "css",
@@ -1698,23 +1698,23 @@
           ]
         },
         "skipTests": {
-          "description": "Do not generate \"spec.ts\" test files for the new project.",
+          "description": "Skip the generation of unit test files `spec.ts`.",
           "type": "boolean",
           "default": false,
           "alias": "S"
         },
         "createApplication": {
-          "description": "Create a new initial application project in the 'src' folder of the new workspace. When false, creates an empty workspace with no initial application. You can then use the generate application command so that all applications are created in the projects folder.",
+          "description": "Create a new initial application project in the new workspace. When false, creates an empty workspace with no initial application. You can then use the `ng generate application` command to create applications in the `projects` directory.",
           "type": "boolean",
           "default": true
         },
         "minimal": {
-          "description": "Create a workspace without any testing frameworks. (Use for learning purposes only.)",
+          "description": "Generate a minimal Angular workspace without any testing frameworks. This is intended for learning purposes and simple experimentation, not for production applications.",
           "type": "boolean",
           "default": false
         },
         "strict": {
-          "description": "Creates a workspace with stricter type checking and stricter bundle budgets settings. This setting helps improve maintainability and catch bugs ahead of time. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode",
+          "description": "Enable stricter type checking and stricter bundle budgets settings. This setting helps improve maintainability and catch bugs ahead of time. For more information, see https://angular.dev/tools/cli/template-typecheck#strict-mode",
           "type": "boolean",
           "default": true
         },
@@ -1735,29 +1735,29 @@
           "default": true
         },
         "ssr": {
-          "description": "Creates an application with Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering) enabled.",
+          "description": "Configure the initial application for Server-Side Rendering (SSR) and Static Site Generation (SSG/Prerendering).",
           "type": "boolean"
         },
         "serverRouting": {
-          "description": "Creates a server application using the Server Routing and App Engine APIs (Developer Preview).",
+          "description": "Create a server application in the initial project using the Server Routing and App Engine APIs (Developer Preview).",
           "type": "boolean"
         },
         "experimentalZoneless": {
-          "description": "Create an application that does not utilize zone.js.",
+          "description": "Create an initial application that does not utilize `zone.js`.",
           "type": "boolean",
           "default": false
         }
       }
     },
     "SchematicsAngularResolverSchema": {
-      "title": "Angular resolver Options Schema",
+      "title": "Angular Resolver Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Generates a new, generic resolver definition in the given project.",
+      "description": "Creates a new resolver in your project. Resolvers are used to pre-fetch data before a route is activated, ensuring that the necessary data is available before the component is displayed. This can improve the user experience by preventing delays and loading states. This schematic generates a new resolver with the specified name and options.",
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the new resolver.",
+          "description": "The name for the new resolver. This will be used to create the resolver's class and spec files (e.g., `my-resolver.resolver.ts` and `my-resolver.resolver.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1765,17 +1765,17 @@
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new resolver.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the new resolver.",
           "default": false
         },
         "flat": {
           "type": "boolean",
-          "description": "When true (the default), creates the new files at the top level of the current project.",
+          "description": "Creates the new resolver files at the top level of the current project. If set to false, a new folder with the resolver's name will be created to contain the files.",
           "default": true
         },
         "functional": {
           "type": "boolean",
-          "description": "Creates the resolver as a `ResolveFn`.",
+          "description": "Creates the resolver as a function `ResolveFn` instead of a class. Functional resolvers can be simpler for basic scenarios.",
           "default": true
         },
         "path": {
@@ -1784,12 +1784,12 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the interface that defines the resolver, relative to the current workspace.",
+          "description": "The path where the resolver files should be created, relative to the current workspace. If not provided, the resolver will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the resolver should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
@@ -1800,11 +1800,11 @@
       "title": "Angular Service Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Creates a new, generic service definition in the given project.",
+      "description": "Creates a new service in your project. Services are used to encapsulate reusable logic, such as data access, API calls, or utility functions. This schematic simplifies the process of generating a new service with the necessary files and boilerplate code.",
       "properties": {
         "name": {
           "type": "string",
-          "description": "The name of the service.",
+          "description": "The name for the new service. This will be used to create the service's class and spec files (e.g., `my-service.service.ts` and `my-service.service.spec.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1815,12 +1815,12 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the service, relative to the workspace root.",
+          "description": "The path where the service files should be created, relative to the workspace root. If not provided, the service will be created in the project's `src/app` directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the service should be added. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
@@ -1828,11 +1828,11 @@
         "flat": {
           "type": "boolean",
           "default": true,
-          "description": "When true (the default), creates files at the top level of the project."
+          "description": "Creates files at the top level of the project or the given path. If set to false, a new folder with the service's name will be created to contain the files."
         },
         "skipTests": {
           "type": "boolean",
-          "description": "Do not create \"spec.ts\" test files for the new service.",
+          "description": "Skip the generation of a unit test file `spec.ts` for the service.",
           "default": false
         }
       }
@@ -1841,7 +1841,7 @@
       "title": "Angular Web Worker Options Schema",
       "type": "object",
       "additionalProperties": false,
-      "description": "Creates a new, generic web worker definition in the given project.",
+      "description": "Creates a new web worker in your project. Web workers allow you to run JavaScript code in the background, improving the performance and responsiveness of your application by offloading computationally intensive tasks. This schematic generates the necessary files for a new web worker and provides an optional code snippet to demonstrate its usage.",
       "properties": {
         "path": {
           "type": "string",
@@ -1849,19 +1849,19 @@
           "$default": {
             "$source": "workingDirectory"
           },
-          "description": "The path at which to create the worker file, relative to the current workspace.",
+          "description": "The path where the web worker file should be created, relative to the current workspace. If not specified, the worker will be created in the current directory.",
           "visible": false
         },
         "project": {
           "type": "string",
-          "description": "The name of the project.",
+          "description": "The name of the project where the web worker should be created. If not specified, the CLI will determine the project from the current directory.",
           "$default": {
             "$source": "projectName"
           }
         },
         "name": {
           "type": "string",
-          "description": "The name of the worker.",
+          "description": "The name for the new web worker. This will be used to create the worker file (e.g., `my-worker.worker.ts`).",
           "$default": {
             "$source": "argv",
             "index": 0
@@ -1870,7 +1870,7 @@
         "snippet": {
           "type": "boolean",
           "default": true,
-          "description": "Add a worker creation snippet in a sibling file of the same name."
+          "description": "Generate a code snippet that demonstrates how to create and use the new web worker."
         }
       }
     },