Skip to content
stackchainstackchain

Clean Architecture

YAML

Section titled “YAML”
stackchain:
  architecture: clean

Folder structure

Section titled “Folder structure”

Identical directory layout to Feature First:

lib/features/<name>/
  data/…
  domain/…
  presentation/…

Pros

Section titled “Pros”
  • Familiar Clean Architecture vocabulary (entities, use cases, repositories)
  • Same generator path as feature_first — low migration friction between the two labels

Cons

Section titled “Cons”
  • Does not invent a separate hexagonal/ports folder tree
  • Discipline is still yours — stackchain scaffolds; deeper architecture linting is on the roadmap

When to choose

Section titled “When to choose”

Teams that standardize on “clean” naming in RFCs/reviews. Functionally close to feature_first.

Preset

Section titled “Preset”
stackchain:
  preset: clean_cubit