agent-project-structure

You can enforce a consistent agent project directory layout by running provided structure scripts with a target project path to generate the required directories and validate temp subdirectories. This ensures predictable automation, logging, and cleanup across teams.

The standard way to separate logs and temporary files is to use a standard directory layout that places logs, temp screenshots, cache, config, and data into clearly separated locations. This safe separation of concerns keeps the repository clean.

Yes, you can check an existing repository for compliance by executing validation scripts against the target project path. The scripts verify whether required directories and temp subdirectories exist before reporting any structural layout issues.

To scaffold a new agent project skeleton, execute the provided structure scripts with a target project path. This generates the full directory structure needed for new agent projects, including config, data, and temp subfolders.

Refactoring an existing project to match a standard directory layout requires no external dependencies. You execute the provided structure scripts with the target project path to ensure required directories and temp subdirectories exist before reporting issues.

Automation and cleanup workflows fail with inconsistent folder conventions because logs, temp files, config, and data are not in predictable locations. Enforcing a standard directory tree resolves this by guiding strict separation of concerns across the project.