Have Autohand Code apply file organization skill patterns to propose or perform a low-risk project structure cleanup.
Make folders and ownership easier to navigate
Architecture Discovery and planning Planning Refactoring
autohand -p "Propose a safer project structure for this area and identify the first low-risk move"
A structure plan or small move with updated imports, tests, and ownership notes.
Organize project structure with Autohand Code is an architecture workflow that reviews folders, ownership boundaries, naming, imports, and generated files before proposing or applying a low-risk organization change. ### At a glance | Question | Answer | | --- | --- | | Best for | crowded directories, unclear feature ownership, duplicated helpers, and codebases where new work starts with file hunting | | Primary inputs | Target directory or subsystem; Current pain points and owner expectations; Import, test, and generated-file constraints | | Autohand Code returns | A structure plan or small move with updated imports, tests, and ownership notes. | | Avoid when | a broad restructure would create churn without improving an immediate workflow | ### How Autohand Code handles this workflow 1. Maps files by responsibility and dependency direction. 2. Separates safe moves from risky ownership or public API changes. 3. Applies one low-risk structure move when requested. 4. Updates imports, tests, and docs that rely on the moved files. ### Best inputs - Target directory or subsystem - Current pain points and owner expectations - Import, test, and generated-file constraints ### Strong prompt autohand -p "Propose a safer project structure for this area and identify the first low-risk move" ### Autohand Code CLI options - Use `/skills use file-organization` for project-structure conventions. - Run `autohand -p "Propose a safer project structure for this area and identify the first low-risk move"` before moving files. - Use `--patch` when the team wants to review rename and import churn first. ### Review before accepting A good result names the proposed boundaries, changed imports, validation command, and future moves left out of scope. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Organize project structure with Autohand Code? Organize project structure with Autohand Code is an architecture workflow that reviews folders, ownership boundaries, naming, imports, and generated files before proposing or applying a low-risk organization change. ### When should a team use Organize project structure? Use it when project structure slows onboarding or makes ownership unclear. ### What evidence should reviewers check for Organize project structure? A good result names the proposed boundaries, changed imports, validation command, and future moves left out of scope.
Skill Skilled: File Organization Use folder, naming, and ownership structure guidance. https://skilled.autohand.ai/skill/file-organization Guide Code Refactoring Refactor structure without behavior changes. /docs/guides/code-refactoring.html Guide Technical Debt Prioritize structure debt by impact. /docs/guides/technical-debt.html