Know exactly what each choice creates.

Does: Names the generated project directory.

Optimize with: Always provide a clear, import-safe project name.

Does: Selects a supported blueprint and its framework-aware defaults.

Optimize with: The web builder generates the selected Init App blueprint, including dbt analytics.

Does: Creates and registers multiple Django application packages.

Optimize with: Use when the project has separate domains such as catalog, billing, and users; the first name owns the primary generated routes.

Does: Loads a JSON project specification; direct flags override it.

Optimize with: Use for repeatable team templates and automation.

Does: Selects standard, production, auto_config, or custom generation.

Optimize with: Use standard for a clean start, production for operational layers, and custom for exact folder control.

Does: Selects a Django-compatible runner.

Optimize with: Use gunicorn, waitress, or wsgiref for the generated Django project.

Does: Selects sqlite, postgresql, mysql, mongodb, or none.

Optimize with: Use sqlite for local work, PostgreSQL for production relational workloads, or none for framework-only projects.

Does: Enables Django REST Framework integration; Django only.

Optimize with: Use when Django is serving an API with serializers, routers, and REST settings.

Does: Controls whether Init App creates a project virtual environment.

Optimize with: Enable isolation for most local and team projects. Package tooling remains the user's choice.

Does: Selects a warehouse adapter such as Snowflake, Databricks, BigQuery, Redshift, Postgres, or DuckDB.

Optimize with: Init App checks dbt-core and the selected adapter in the chosen environment before native dbt initialization; use custom for any compatible PyPI adapter.

Does: Defines the PyPI package and dbt adapter type for a provider outside the built-in catalog.

Optimize with: Use both flags together only with --dbt-adapter custom.

Does: Creates or preserves the selected profile in project .dbt/profiles.yml and ~/.dbt/profiles.yml.

Optimize with: Credentials stay in environment variables, never in generated files or command output. dbt reads profiles.yml, not user.yml.

Does: Creates or reuses .venv, installs requirements, then runs Django's startproject and startapp commands.

Optimize with: Generated manage.py reuses .venv automatically, so team commands do not accidentally use a global Django install.

Does: Creates or reuses the selected environment, checks dbt-core and the selected adapter, then runs native dbt init without interactive profile setup.

Optimize with: The generated project keeps a portable .dbt/profiles.yml and uses --profiles-dir .dbt for dbt debug, deps, and run.

Does: Writes credential-free environment-variable placeholders and preserves an existing named profile instead of overwriting it.

Optimize with: Run dbt debug before dbt run; configure provider credentials in your environment or secret manager.

Does: Lists the folders to create.

Optimize with: Use when the default architecture does not match the project boundary.

Does: Marks selected folders for __init__.py generation.

Optimize with: Every package must also be listed in --folders; keep package initialization intentional.

Does: Chooses framework, python, django, dbt, node, cpp, or minimal ignore rules.

Optimize with: Use dbt to exclude artifacts, packages, and local dbt environment files.

Does: Adds custom ignore patterns.

Optimize with: Protect secrets, local data, generated assets, and machine-specific files.

Does: Disables the local safe file-inventory bundle.

Optimize with: Keep the default enabled when local tooling needs project context; disable it for minimal output.

Does: Adds selected Docker files.

Optimize with: Choose Dockerfile for a container image, compose files for local services, and DOCKER.md for notes.

Does: Adds selected GitHub workflow and issue-template files.

Optimize with: Start with ci.yml for pull-request checks and add security.yml for dependency scanning.

Does: Adds selected Kubernetes manifests.

Optimize with: Use deployment and service first; add ingress, secrets, storage, or autoscaling as needed.

Does: Adds selected Jenkins pipeline files.

Optimize with: Choose the Jenkinsfile and add build/deploy scripts when Jenkins owns delivery.

Does: Adds contribution, conduct, security, and changelog files.

Optimize with: Use for public repositories and teams that want contribution standards from day one.

Does: Adds package metadata files such as setup.py, setup.cfg, and requirements.txt.

Optimize with: Select only the packaging files your distribution or deployment workflow needs.

Does: Chooses the explicit parent directory for the generated project.

Optimize with: Use when the project should not be created in the current directory; leaving it empty keeps generation local.

Does: Creates the project in the current directory.

Optimize with: Use when the current directory is already the intended project root.

Does: Allows generation into a non-empty project directory.

Optimize with: Use carefully after reviewing existing files; the default refusal protects work.

Does: Prints the resolved configuration without writing files.

Optimize with: Use in CI, previews, and reviews before committing to a filesystem change.

Does: Sets one-off documents, current, or custom path behavior.

Optimize with: Use to override the saved default for one generation.

Does: Displays saved path defaults and exits.

Optimize with: Use when a project is appearing in an unexpected location.

Does: Resets saved path defaults and exits.

Optimize with: Use to return path resolution to its clean default state.