Determine file placement by usage scope before creating artifacts.
npx skills add https://github.com/jota-batuta/batuta-dots --skill scope-rule
Please help me install this Agent Skill. Skill: scope-rule Source: https://github.com/jota-batuta/batuta-dots/tree/main/BatutaClaude/skills/scope-rule Command: npx skills add https://github.com/jota-batuta/batuta-dots --skill scope-rule
Before writing any file, you MUST determine who will use it to decide its location, preventing dumping-ground folders and inconsistent project structure.
Place your file only after answering "Who will use this?" and choose the location under features/{name}/{type}, features/shared/{type}, or core/{type} accordingly.
High-intent search queries and answers about installing and using this skill.
The scope rule enforces file location by determining usage scope before creation. It applies a mandatory decision tree to route artifacts into features/{name}, features/shared/{type}, or core/{type} directories, preventing dumping-ground folders.
The scope rule in software architecture enforces file location by determining usage scope before creation. It applies a mandatory decision tree to route artifacts into features/{name}, features/shared/{type}, or core/{type} directories, preventing dumping-ground folders.
Prevent dumping-ground folders by enforcing the scope rule, which requires asking who will use the item before creation. This guides placement into dedicated features/{name}, features/shared/{type}, or core/{type} directories instead of inconsistent root-level utils.
Place files in a shared directory when multiple consumers need the artifact, and use the core directory for foundational project elements. The scope rule decision tree routes items to features/shared/{type} or core/{type} based on actual usage scope.
Yes, you can use the scope rule for all artifact types in software engineering. It applies across files, utilities, and modules, ensuring correct placement in features/{name}, features/shared/{type}, or core/{type} before creation.
Inconsistent root-level components occur because files are created without determining usage scope. Applying the scope rule enforces a mandatory decision tree to route items into structured features/{name}, features/shared/{type}, or core/{type} directories.
netteDefine Nette project architecture across App, Core, Model, and Presentation layers.
thinhtt264Centralize Android Gradle build logic with convention plugins and version catalogs.
TeiNamRecord architectural decisions with context, alternatives, and consequences.
oogDZValidate SSOT structure across README, .instructions/, folder tree, and links.
