archify

Archify is now driven entirely by a single archify.yaml file you control, instead of hardcoding one architecture.

New commands

• init — creates the default archify.yaml. Running it again when the file already exists just reports that instead of overwriting it.
• configure — reads archify.yaml and scaffolds the project from it. Creates archify.yaml first (via init) if it doesn't exist yet, then continues in the same run.
• templates — lists every built-in template key, split into what's in the default archify.yaml and what's opt-in. Reads from the same registry configure/generate use, so it can't drift out of date.
• reset-project — modeled on Expo's npm run reset-project. Resets lib/ to a blank single-screen starter, optionally moving your existing code to example/ first instead of deleting it.

Breaking changes

• configure no longer scaffolds a project immediately — see init/configure above. Automation/CI relying on the old one-shot behavior now needs to call init then configure.
• generate <feature> is driven by archify.yaml's feature_root/feature_template keys instead of a hardcoded data/domain/presentation layout.
• archify.yaml uses a simpler nested-mapping schema instead of the old {name, type, children, template} list. A key with nested keys is a folder; a key mapped to a template name is a file:

  structure:
    lib:
      core:
        api:
      shared:
        theme:
          app_colors.dart: theme_colors
  

  Any archify.yaml written before this version needs converting to this shape — run dart run archify init in an empty folder to see the new format.
• Archify no longer edits pubspec.yaml. configure prints the exact flutter pub add ... command instead, for the packages the optional Cubit/Bloc templates need.
• The default architecture is leaner: core/config, the dio/navigation/route/storage helpers under shared/utils, injection_container.dart, and a generated feature's Cubit/state files are no longer scaffolded by default. All of them are still available — add the template name back into archify.yaml yourself (dart run archify templates lists them). main.dart, app.dart, and root.dart no longer import any third-party package; MultiBlocProvider, error logging, local storage, and DevicePreview are left as commented-out examples.

Also

• Removed the now-unused yaml_edit and path dependencies.
• Cleaned up generated boilerplate — files now carry at most one short "add your X here" comment instead of speculative example code.
• Documented that Archify is architecture-agnostic, not DDD-specific: rewriting structure/feature_template to MVVM, MVC, or anything else works with zero code changes.

• Added custom command to generate fully custom features based on YAML templates.
• Custom feature generation now supports dynamic placeholders like {feature_name} in folder and file names.
• Improved YAML parsing and validation for nested folders and files.
• Added backup of existing feature folders if the feature already exists before regeneration.
• Updated README with custom command usage examples.
• Minor improvements and bug fixes in fs_utils and custom_creator.