AI Prompts for Claude Prompts for Organization

I am going to describe my current organization situation and I want you to diagnose what is actually broken, not give me generic tips. Here is my situation: [DESCRIBE: HOW YOU MANAGE FILES, TASKS, NOTES, EMAIL, PHYSICAL SPACE, PROJECTS]. The recurring problems: [DESCRIBE THE PAIN POINTS]. The systems I have tried that did not stick: [LIST]. Based on this, what are the 2-3 specific failure modes in how I am working, and what type of intervention is most likely to help someone with my pattern?

Help me honestly quantify what my disorganization costs me. In a typical week: [DESCRIBE: HOW MUCH TIME SEARCHING FOR THINGS, HOW MANY DROPPED BALLS, HOW MUCH MENTAL OVERHEAD, HOW OFTEN YOU BUY SOMETHING YOU ALREADY HAVE, HOW OFTEN DEADLINES SNEAK UP]. Convert that into: hours per week wasted, the downstream effects on work quality or relationships, and what I could do with that time if it were recovered. I want to understand the real cost before investing in a fix.

I suspect my organization system is too complicated. Current system: [DESCRIBE EVERY TOOL AND PROCESS YOU USE TO MANAGE WORK AND LIFE]. Audit it: how many decisions do I have to make about where something goes, how many places do I have to check to know what is outstanding, how much time maintaining the system itself takes per week, and where the system creates friction rather than reducing it. Then tell me what to cut. Simpler systems get used; complex ones get abandoned.

When I cannot find something, here is what I do: [DESCRIBE YOUR SEARCH BEHAVIOR: WHICH PLACES YOU CHECK, IN WHAT ORDER, HOW LONG IT TAKES, HOW OFTEN YOU GIVE UP AND RECREATE SOMETHING]. Analyze this: the search behavior reveals the organization problem more accurately than any self-report. What does my search pattern tell you about where my system is failing? Then design the file or information structure that matches how I actually look for things, not how I imagined I would when I set up the system.

I lose time to decision overhead, small daily decisions about where things go, what to do next, and what to keep. Inventory my typical decision overhead: [DESCRIBE: WHAT YOU TYPICALLY HAVE TO DECIDE EACH DAY ABOUT ORGANIZATION, TASK MANAGEMENT, OR INFORMATION STORAGE]. Identify which decisions I make repeatedly that I should decide once and then follow the rule, and which I should eliminate entirely by changing my system. The goal is zero recurring decisions about organization.

Design an information architecture for my work and life. I need to manage: [LIST TYPES: CLIENT PROJECTS, PERSONAL FILES, REFERENCE MATERIAL, ONGOING TASKS, SOMEDAY IDEAS, FINANCIAL RECORDS, COMMUNICATIONS]. For each type: the right home (which tool, which folder structure), the naming convention I should use, and the retrieval method (how I find things in each category). The architecture should feel natural to use and have a clear answer for where new things go.

I use these tools to manage my work and life: [LIST ALL: EMAIL, CALENDAR, TASK MANAGER, NOTES APP, FILE STORAGE, COMMUNICATION TOOLS, PROJECT TOOLS, ETC.]. Rationalize this stack: identify overlapping tools doing the same job, the minimum set of tools that cover my actual needs, and which tool should own which type of information. Then give me a consolidation plan: what to migrate from which tool first, and what to do with the content in the tools I am removing.

I need a task system that: captures everything without friction, helps me know what to work on right now, does not lose track of things I am waiting on, and is light enough that I will actually maintain it. My situation: [DESCRIBE: WORK TYPE, NUMBER OF TASKS, HOW OFTEN THINGS CHANGE, DO I WORK ALONE OR WITH A TEAM]. Design the specific system: the tool, the structure, the daily habits that keep it current, and what "done" looks like for my inbox and task list at end of each day.

Design a file organization system for [WORK TYPE]. I need to organize [TYPES OF FILES] and be able to find them [HOW LONG LATER]. Create: the folder hierarchy (maximum 3 levels deep), the file naming convention with examples for my most common file types, the rule for where something goes when it could fit in more than one place, and what to do with old files that do not fit the new structure. Run me through 5 example files using the system so I can see it in practice.

Design a capture system for everything that enters my life that needs to be done, remembered, or filed: tasks, ideas, information, follow-ups, and reference material. The system should: have as few capture points as possible (ideally one), work regardless of whether I am at my desk or not, require minimal in-the-moment categorization (capture now, sort later), and connect to the places where things actually live in my organization system. Make it so frictionless that I prefer it to mental notes.

I want to clean up [AREA: FILES / EMAIL / TASK LIST / DESKTOP / NOTES] in focused sessions this week. I have [TOTAL TIME] across [NUMBER] sessions. Plan the sessions: which area to tackle in each session (ordered for maximum impact and momentum), the decision rule I apply within each session, the target end state for each session (specific enough that I know when I am done), and what to do with things I cannot decide on quickly (the "decide later" parking lot with a deadline to actually decide).

My inbox has [NUMBER] emails going back [TIME PERIOD]. Build my triage protocol: the process to get through the backlog without reading everything, the categories I sort into and what happens to each, the types of emails I can unsubscribe from or filter without reading, and my end state after triage (not necessarily inbox zero, a manageable, organized state where nothing important is buried). Give me a triage script: what decision I make about each email and in how many seconds.

I am moving my information from [OLD SYSTEM] to [NEW SYSTEM]. Plan the migration: what to migrate now (active files and projects), what to archive without migrating (completed work), what to delete rather than move, the order to migrate in, and how to handle the transition period when I am working in both systems. The goal: complete the migration in [TIME FRAME] without losing anything and without the transition becoming a permanent in-between state.

I have accumulated reference material I might need: [DESCRIBE: ARTICLES SAVED, NOTES FROM BOOKS, RESEARCH DOCUMENTS, TEMPLATES, INSPIRATION FILES]. Help me organize it so it is actually retrievable when I need it: the categories that match how I would search for reference material (not how I created it), the naming or tagging approach, what to delete (most saved reference material is never accessed again), and the retrieval test: can I find what I need in under 2 minutes?

My physical workspace is: [DESCRIBE: HOME OFFICE / SHARED WORKSPACE / MOBILE / MULTIPLE LOCATIONS]. Design it for how I work: the items that should be within arm's reach versus stored away (based on frequency of use, not importance), the system for paper and physical materials I accumulate, the end-of-day reset that makes tomorrow's start easier, and the rule for what enters the physical workspace and what stays out. Physical organization and mental clarity are linked.

Design the minimum viable maintenance routine for my organization system: [DESCRIBE YOUR SYSTEM]. What is the smallest daily habit (under 5 minutes) that prevents buildup, the weekly check (under 15 minutes) that catches drift before it becomes a backlog, and the monthly review (under 30 minutes) that updates the system as my work changes. I want organization that sustains itself with minimal ongoing investment, not a system that requires constant tending.

Design the rules that prevent my [FILE SYSTEM / TASK LIST / EMAIL / NOTES] from decaying. I want decisions I make once that apply forever: the rule for what gets filed versus deleted immediately, the maximum I allow to accumulate before I process it, the trigger for a deeper cleanup when the system starts to drift, and the one maintenance habit that, if I do nothing else, keeps the system functional. Rules beat habits for maintenance because they require no daily willpower.

My organization system needs to evolve as my work changes. Design my system review process: how often I evaluate whether each part of the system is still serving me, the questions I ask to assess whether it is working (specific and observable, not just "does it feel good"), how I make changes without losing continuity, and how I decide between updating the current system versus replacing it. A system that does not evolve will stop fitting eventually.

I want my organization system to be legible to someone else. Document it: the one-page overview of where everything lives and why, the decision rules for where new things go, the naming conventions with examples, and how someone stepping in would find [SPECIFIC TYPES OF INFORMATION: CLIENT FILES, ONGOING PROJECTS, REFERENCE MATERIAL]. This is also the test of whether your system makes sense: if you cannot explain it in one page, it is probably too complicated.

My organization has fallen apart because [WHAT HAPPENED: BUSY PERIOD / LIFE DISRUPTION / SYSTEM ABANDONED / GRADUAL DRIFT]. I need to recover without starting over and without a week-long cleanup project. Design my recovery plan: the minimum I need to do this week to be functional (not perfect), the 3-day triage that brings the backlog under control, and the habit change that prevents the same thing from happening next quarter. Recovery should be fast and sustainable, not ambitious and unrepeatable.