scope-rule

Name: scope-rule
Availability: InStock
Author: jota-batuta

Determine file placement by usage scope before creating artifacts.

Updated Feb 20, 2026

Search Tags:#software-architecture #decision-tree #project-organization #scope-rule #file-location

Ready to run

npx skills add https://github.com/jota-batuta/batuta-dots --skill scope-rule

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before writing any file, you MUST determine who will use it to decide its location, preventing dumping-ground folders and inconsistent project structure.

Core Features & Use Cases

Enforces the Scope Rule before file creation, ensuring correct placement (feature-specific, shared, or core).
Guides teams to structure new work by usage, helping to avoid root-level utils or global components.
Applies across all artifact types (files, utilities, modules) and supports sharing only when truly needed by multiple consumers.

Quick Start

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.

Frequently Asked Questions about scope-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I decide the correct file location for a new module in my project?▼

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.

What is the scope rule in software architecture?▼

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.

How do I prevent dumping-ground folders in my project organization?▼

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.

When do I need to place files in a shared directory versus a core directory?▼

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.

Can I use the scope rule for all artifact types in software engineering?▼

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.

Why does my project structure have inconsistent root-level components and utilities?▼

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.