Folder Organization Best Practices

How you organize your folders directly impacts how well your AI agents can help you. This guide shows you recommended folder structures and organization strategies.

Why Folder Organization Matters

Agents in FabriXWork work with files in their connected folder. A well-organized folder structure helps agents:

Find context faster — Clear structure means less time searching
Understand relationships — Folder hierarchy shows how files relate
Avoid mistakes — Organized files reduce confusion about which file to use
Work autonomously — Agents can navigate and create files confidently

Recommended Folder Structure

General Project Structure

For most projects, this structure works well:

Project-Name/
├── 01-admin/
│   ├── project-brief.md
│   ├── timelines.md
│   └── stakeholders.md
├── 02-research/
│   ├── background/
│   ├── competitors/
│   └── interviews/
├── 03-working/
│   ├── drafts/
│   ├── versions/
│   └── scratch/
├── 04-deliverables/
│   ├── presentations/
│   ├── reports/
│   └── exports/
├── 05-resources/
│   ├── templates/
│   ├── references/
│   └── assets/
└── 06-archive/
    ├── old-versions/
    └── deprecated/

Why This Structure Works

Folder	Purpose	Agent Usage
01-admin	Project overview, briefs, timelines	Reference for context and goals
02-research	Background materials, data, interviews	Source material for analysis
03-working	Active work-in-progress files	Where agent creates and edits
04-deliverables	Final outputs, client-ready files	Agent saves completed work here
05-resources	Templates, style guides, references	Agent uses for formatting guidance
06-archive	Old versions, deprecated content	Keeps workspace clean

Numbering Folders

The numbers (01, 02, 03...) ensure folders stay in logical order when sorted alphabetically. This helps both you and the agent navigate more efficiently.

Folder Structures by Use Case

NGO Campaign Example

Fundraising-Campaign-2026/
├── 01-campaign-brief/
│   ├── objectives.md
│   ├── target-audience.md
│   └── budget.md
├── 02-meeting-notes/
│   ├── 2026-02-23-kickoff.md
│   ├── 2026-03-02-planning.md
│   └── 2026-03-09-review.md
├── 03-content/
│   ├── presentation-drafts/
│   ├── email-templates/
│   └── social-media/
├── 04-sponsors/
│   ├── prospect-list.md
│   ├── outreach-tracking.md
│   └── sponsor-packages/
└── 05-deliverables/
    ├── campaign-proposal.md
    ├── sponsor-deck.md
    └── timeline.md

Business Analysis Example

Q1-Analysis/
├── 01-data-sources/
│   ├── sales-data/
│   ├── customer-feedback/
│   └── market-research/
├── 02-analysis/
│   ├── sales-trends.md
│   ├── customer-insights.md
│   └── competitive-landscape.md
├── 03-findings/
│   ├── key-discoveries.md
│   ├── risks-identified.md
│   └── opportunities.md
├── 04-recommendations/
│   ├── strategic-actions.md
│   ├── resource-requirements.md
│   └── implementation-plan.md
└── 05-executive-summary/
    └── q1-report-final.md

Software Development Example

Web-App-Project/
├── 01-requirements/
│   ├── user-stories.md
│   ├── functional-specs.md
│   └── technical-requirements.md
├── 02-design/
│   ├── wireframes/
│   ├── mockups/
│   └── design-system/
├── 03-development/
│   ├── src/
│   ├── components/
│   └── utils/
├── 04-testing/
│   ├── test-cases/
│   ├── bug-reports/
│   └── qa-notes/
├── 05-deployment/
│   ├── config/
│   ├── scripts/
│   └── release-notes/
└── 06-documentation/
    ├── user-guide/
    ├── api-docs/
    └── changelog/

File Naming Conventions

Good file names help agents (and humans) understand content at a glance.

Recommended Patterns

Pattern	Example	When to Use
Date prefix	`2026-03-09-meeting-notes.md`	Meeting notes, logs, journals
Version suffix	`proposal-v3.md`	Documents with multiple iterations
Type prefix	`draft-outline.md`, `final-report.md`	Distinguish draft vs final
Descriptive	`customer-feedback-summary.md`	Most general documents

Best Practices

✅ Use lowercase with hyphens: meeting-notes.md
✅ Include dates in ISO format: 2026-03-09
✅ Be descriptive but concise
✅ Avoid spaces and special characters
❌ Don't use: Meeting Notes (FINAL) (2).docx

One Folder Per Agent

Important: Each agent in FabriXWork connects to one folder at a time.

Strategy for Multiple Agents

If you're using multiple agents on the same project:

Option 1: Shared project folder

Project-X/
├── agent-alex-research/    (Alex's working folder)
├── agent-sarah-writing/    (Sarah's working folder)
└── shared-deliverables/    (Final outputs from all agents)

Option 2: Agent-specific subfolders

Project-X/
├── research/      (Alex works here)
├── content/       (Sarah works here)
├── design/        (Alex works here)
└── final/         (All agents contribute)

Switching Agent Folders

To change an agent's connected folder:

Click the agent in the sidebar
Open the workspace panel
Disconnect current folder
Connect new folder

Tips for Agent-Friendly Folders

1. Create a README File

Add a README.md or PROJECT-BRIEF.md at the root:

# Project Overview

**Objective:** [Brief description]
**Key Files:** 
- `01-admin/brief.md` — Project goals
- `02-research/` — Background research
- `04-deliverables/` — Final outputs

**Current Phase:** [Phase name]
**Last Updated:** 2026-03-09

Agents will read this first to understand context.

2. Use Index Files

For complex folders, add an index.md that lists contents:

# Research Files Index

| File | Description | Date |
|------|-------------|------|
| competitor-analysis.md | Top 5 competitors | 2026-02-15 |
| customer-interviews.md | 10 interview transcripts | 2026-02-20 |
| market-trends.md | Industry trends report | 2026-03-01 |

3. Archive Old Files

Move outdated files to an archive/ folder instead of deleting:

Keeps workspace clean
Preserves history for reference
Agents can still access if needed

4. Separate Drafts from Finals

Always keep working drafts separate from final deliverables:

03-working/drafts/ — Work in progress
04-deliverables/ — Client/stakeholder ready

5. Add Context Files

Before asking an agent to work, add brief context files:

01-admin/
├── project-brief.md      (What we're doing)
├── style-guide.md        (How we write)
└── glossary.md           (Key terms and definitions)

Common Mistakes to Avoid

Mistake	Problem	Solution
Flat structure (all files in root)	Agent can't understand relationships	Create logical subfolders
Vague file names (`doc1.md`, `new.md`)	Agent doesn't know what files contain	Use descriptive names
No version control	Agent might edit outdated file	Use `/versions/` folder or version suffixes
Mixing drafts and finals	Agent might use wrong version	Separate working and deliverable folders
Overly deep nesting	Agent takes longer to navigate	Keep max 3-4 levels deep
No README or context	Agent lacks project understanding	Add brief overview file

Quick Reference: Folder Checklist

Before connecting a folder to an agent:

[ ] Clear purpose — Folder has a defined project/goal
[ ] Logical structure — Subfolders organized by category or phase
[ ] README file — Brief overview at root level
[ ] Descriptive names — Files and folders clearly labeled
[ ] Draft/final separation — Working files separate from deliverables
[ ] Archive folder — Place for old versions
[ ] Relevant files only — Remove unrelated content

What's Next?

Now that your folders are organized:

Learn to choose the right agent → Agent Selection
Explore real use cases → Use Cases Directory