directory-structure

Validate project directory structure against feature-sliced architecture standards.

3|3|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/CodySwannGT/lisa --skill directory-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: directory-structure
Source: https://github.com/CodySwannGT/lisa/tree/main/plugins/lisa-expo/skills/directory-structure
Command: npx skills add https://github.com/CodySwannGT/lisa --skill directory-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all code files and directories within the project adhere to a strict, predefined structure, preventing disorganization and improving maintainability.

Core Features & Use Cases

  • Directory Validation: Verifies that files and folders are placed in their correct locations according to project standards.
  • Pattern Enforcement: Enforces the Container/View pattern for components and screens, and ensures test files are correctly placed.
  • Use Case: When creating a new feature, use this skill to confirm that its components, screens, and hooks are organized correctly within the features/ directory.

Quick Start

Run the directory structure validation script to check the current project's organization.

Frequently Asked Questions about directory-structure

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

FAQPage Schema
How do I validate directory structure standards in a feature-sliced architecture?

You can validate directory structure standards by running a Python script that checks feature module organization, container/view pattern compliance, and test file placement to ensure codebase adherence to predefined conventions.

How do I enforce the Container/View pattern for components and screens?

To enforce the Container/View pattern, the validation script checks that components and screens are correctly organized within their designated directories according to your project's structural conventions.

What is the best way to automate code organization checks for new feature modules?

Automating code organization checks involves running a validation script that verifies files, hooks, and utilities are placed correctly within the features directory during feature creation.

Do I need Python to validate project structure and naming conventions?

Yes, you need Python3 installed as a dependency to execute the validation script that enforces your project's directory structure and naming conventions.

Can I use this directory validation for codebases with custom test file placement rules?

Yes, the directory validation script ensures test files are correctly placed according to specific predefined conventions within your feature-sliced architecture codebase.