Prompt

You are a documentation organization expert. Develop a set of naming conventions and a folder structure to organize [SPECIFIC DOCUMENTS OR PROJECT FILES]. The output should include:

• File Naming Rules: Guidelines on how to name each file. (For example: include date in YYYY-MM-DD format at the start, a brief descriptive title or project code, and a version number at the end. Avoid spaces by using hyphens or underscores, and use lowercase for consistency.)

• Folder Structure: A hierarchical outline of folders (and subfolders if needed) to store the files logically. (For example: a main folder per client or project, with subfolders for each year or for categories like "Design", "Contracts", etc.)

• Best Practices: Tips to maintain this system (like "enforce the convention when saving files", "archive older files annually"), and any tools or automations that could help (such as using a script or tool like Zapier to auto-rename files or move them to the right folder).

  Provide the naming convention rules clearly (you can show an example file name following the rules) and then describe the recommended folder structure.

How to Use

• Define Your Inputs: Identify the scope of what needs organizing. Note:
  • The types of documents and their purpose (e.g., "marketing materials like proposals, contracts, and reports", "project files for multiple client projects").
  • Key attributes that should be reflected in names or folders (dates, project/client names, document type, version number, etc.).
  • Current challenges or goals (e.g., "we have too many files named 'final' confusingly", "need to quickly find last year’s reports").

• Customize the Prompt: Plug your document context into the prompt. If you have preferences, include them. For instance, specify if you want dates at the beginning or end of file names, if you prefer underscores vs. hyphens, or if there are standard abbreviations to use for project names. The more details you provide, the more tailored the convention will be.

• Optional Add-ons: You could ask for multiple naming convention options if you're unsure which style your team will prefer (e.g., "give two possible naming schemes: one with short codes, one with full words"). You might also request the output in a shareable format (like a brief guideline document outline). If you use a particular storage system (Google Drive, SharePoint, etc.), mention it so the advice can align with that system’s features (for example, SharePoint metadata vs folder use).

• Run the Prompt: Run your customized prompt. The AI will generate a set of naming rules and a proposed folder structure.

• Review & Select: Go over the suggested convention and structure. Imagine renaming a few existing files and placing them in folders according to the plan – does it feel logical and scalable? If something is too complex or not suitable, refine the prompt (for example, "simplify the naming rules, fewer elements" or "include client name in every file name"). Make sure the final convention is intuitive enough that everyone on your team can follow it. You might even test it on a handful of files to ensure it works well.

• Expected Outcome: A well-defined file naming convention and directory structure tailored to your needs. This will transform disorganized files (like "Document_final_FINAL(2).docx") into consistent names (for example, "2025-07-01_project-alpha_contract_v1.docx") and organize them in a clear folder system, so anyone can quickly find what they need. Once adopted, you can maintain consistency manually or even use automation tools to help enforce the rules (like scripts to batch-rename files or automatic folder rules in your cloud storage service).