This enforces a straightforward architectural rule for Angular projects: components go in their feature folder if only that feature uses them, and they move to a shared folder once a second feature needs them. It's the kind of simple heuristic that prevents bikeshedding about folder structure on teams. The repo has 538 stars and 216 installs, so it's seeing real use. Worth grabbing if you're tired of debating where components should live or if your shared folder has become a dumping ground. The rule is opinionated enough to be useful but flexible enough that you won't fight it.
npx skills add https://github.com/gentleman-programming/gentleman-skills --skill angular-architecture