File Placement Rules

Enforce repository file placement rules and naming conventions for documentation and scripts.

2|1|Updated May 27, 2025

Search Tags:#documentation #file organization #code structure #script management #repository rules

Ready to run

npx skills add https://github.com/PAIPalooza/chicommerce --skill file-placement-rules

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: File Placement Rules
Source: https://github.com/PAIPalooza/chicommerce/tree/main/.ainative/skills/file-placement/compressed
Command: npx skills add https://github.com/PAIPalooza/chicommerce --skill file-placement-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses project clutter and inconsistent structure by enforcing strict rules for file placement within the repository, ensuring better organization and findability.

Core Features & Use Cases

Directory Enforcement: Ensures documentation and scripts are placed in designated directories (docs/, scripts/).
Filename Pattern Matching: Validates that filenames adhere to specific patterns for different types of content.
Use Case: When a new script or documentation file is created, this Skill automatically checks if it's in the correct location and follows naming conventions, preventing disorganization before it starts.

Quick Start

Use the file placement skill to ensure all new documentation is placed in the correct 'docs' subdirectory.

Frequently Asked Questions about File Placement Rules

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

FAQPage Schema

How do I enforce strict file placement rules in my repository?▼

You can enforce strict file placement rules by validating that new project assets are created in predefined directory structures, ensuring documentation goes into designated directories like docs/ and scripts into scripts/.

What's the best way to maintain code structure and naming conventions for scripts?▼

Maintaining code structure requires applying filename pattern matching to validate that scripts and other resources adhere to specific naming conventions before they are added to the repository.

How does directory enforcement prevent project clutter and inconsistent structure?▼

Directory enforcement prevents project clutter by automatically checking if newly created documentation and scripts are placed in their correct designated directories, stopping disorganization before it starts.

Can I use file placement rules for both backend and frontend resources?▼

Yes, file placement rules apply to the creation and management of both backend and frontend resources, requiring adherence to predefined directory structures and filename patterns across the project.

When do I need automated filename pattern matching for documentation?▼

You need automated filename pattern matching for documentation when you want to ensure new files follow specific naming patterns for different content types, preventing inconsistent structure and improving findability.