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).

When true, the 'type' option will be appended to the generated class name. When false, only the file name will include the type.

Automatically export the directive from the specified NgModule, making it accessible to other modules in the application.

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.

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.

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.

The name of the project where the directive should be added. If not specified, the CLI will determine the project from the current directory.

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).

Do not automatically import the new directive into its closest NgModule.

Skip the generation of a unit test file spec.ts for the new directive.

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.

Append a custom type to the directive's filename. For example, if you set the type to directive, the file will be named example.directive.ts.