Claude Code

Use Claude Code to turbocharge your productivity!

Jan 09, 2026

Happy New Year. In the past two days, I’ve been burning Claude Code tokens for knowledge work, and it makes me feel superhuman!

Claude Code is getting a lot of attention, and it deserves to. It’s a very “nerdy” kind of tool, as most people have never seen the Terminal on their computer. Claude Code also represents an emerging “pattern” of work or “brain” similar to how computing evolved say in the 1980s, 1990s and 2000s with the web and then mobile → social. This article is a good illustration of the pattern and this article about the crazy things you can build with Claude Code.

The terminal is basically the first computer interface before we got the GUI. But there are a few things that are interesting about the terminal. For one thing, you can do a lot of things from the terminal that most people use their mouse and keyboard for. Why does this matter? Well, large language models know how to type and write code, and in this case, they have access to decades of tools. Writing code is the most powerful way to do things - that is what software is. But the model can write code any time for anything at all.

But okay, so what?

Well, Claude Code has this super brain in it - it has one of the world’s best models, “Opus 4.5,” and it has a bunch of smarts to do things like:

Understand your request and intent
Create a Plan
Create a Todo list to track
Ask you clarifying questions
And expend enormous amounts of infinite energy to toil away at things you never even tried to do.

Oh one more thing. Claude Code can discover and call other tools, store information, use skills and persist all this in “sub agents”.

Ok, let’s take a simple example I worked on yesterday. I have a HUGE folder of scanned documents. For over 20 years, I’ve been collecting and storing these files in a folder that contains 500 other folders. I learned this during my Getting Things Done phase to digitize and store all paper.

The problem is that after 20 years, this folder has become a mess. Things are not well organized, and they are not well named.

So, I asked Claude Code to evaluate my folder. From there, it was able to figure out many things about my information. It then came up with a plan to fix, clean, and organize this information.

These folders and files are in OneDrive, and shared with my wife. And this knowledge will also get passed on to my kids. But it syncs to my Mac via OneDrive and so that means all those “terminal” tools can work on all those files.

So…

When Claude said it was done, I asked it to create a sub-agent for me so that in the future, I could reuse all the knowledge it gained about me (because LLMs don’t have memory). It created an agent that codified all the rules, knowledge, and prompting that I performed. Now, when I want to tidy up or organize, I just use my agent.

⏺ In your 🗄️ Filing Cabinet in your personal OneDrive, you have:

  520 folders and 4,457 files (total of 4,977 items)

  Your Filing Cabinet appears to be very well-organized with a comprehensive taxonomy covering major categories like:
  - Personal documents (passports, driver's licenses, birth certificates)
  - Health records (for each family member)
  - Financial accounts
  - Tax documents (organized by year)
  - Estate planning documents and trusts
  - Real estate
  - Education records
  - Vehicles
  - Memberships
  - Service providers and utilities
  - Family memories and personal items

  It's a very thorough filing system with 167 top-level categories!

When I ask Claude what “agents” it has here is a good example of what it looks like

❯ /agents 
╭──────────────────────────────────────────────────────────────────────╮
│ Agents                                                                                                               
│ 7 agents                                                                                                                                                                                                                              
│ ❯ Create new agent                                                                                                   
│                                                                                                                     
│   User agents (/Users/omarshahine/.claude/agents)                                                                    
│   filing-cabinet-organizer · sonnet                                                                                                                                                                                                
│   
│   Built-in agents (always available)                                                                                 
│   Bash · inherit                                                                                                     
│   general-purpose · sonnet                                                                                           
│   statusline-setup · sonnet                                                                                          
│   Explore · haiku                                                                                                    
│   Plan · inherit                                                                                                     
│   claude-code-guide · haiku

The “Bash” agent is the one that can perform tasks on your computer using the terminal. All the other agents are essentially tools that Claude uses to learn, discover, and then act.

Here is what Bash and hence Claude Code can do for you without anything “new”.

⏺ I can help with a wide range of file and folder operations:

  Reading & Exploring
  - Read file contents (text, code, PDFs, images, Jupyter notebooks)
  - List directory contents
  - Search for files by name pattern (glob)
  - Search for text within files (grep)
  - Find files by various criteria

  Creating & Modifying
  - Create new files
  - Edit existing files (find and replace text)
  - Write files from scratch
  - Rename files and folders
  - Move files between locations

  Organization & Management
  - Create folder structures
  - Organize files by type, date, or custom rules
  - Batch rename multiple files
  - Clean up duplicate or unwanted files
  - Archive or compress files

  Analysis
  - Count files in directories
  - Check file sizes
  - Find large files consuming disk space
  - Compare file contents
  - Analyze file metadata

  Special Capabilities
  - Work with your Filing Cabinet system (I noticed you have one in OneDrive)
  - Handle various formats: text, code, PDFs, images, Office documents
  - Execute complex multi-step file operations
  - Automate repetitive file tasks

  Would you like help with:
  - Organizing specific files/folders?
  - Finding something on your system?
  - Setting up an automated file management task?
  - Something else?

The “filing-cabinet-organizer” is my personal sub-agent that knows how to organize items in my Digital Filing Cabinet. It does this by storing information in a file called “Claude.md” - a markdown (text) file with a description of what is in the folder, and then an agent that is stored in.

Here are the actual agent instructions. Note that I did not create this; Claude Code created it for me:

---
name: filing-cabinet-organizer
description: >
    Use this agent when the user needs to organize, file, locate, rename, or
    maintain documents within a family filing cabinet system. Typical tasks
    include:
    
    - Filing new documents into the correct folders
    - Locating existing documents within the system
    - Reorganizing misplaced files
    - Renaming unclear or cryptic filenames (reading file contents when needed)
    - Creating folders that align with the established taxonomy
    - Answering questions about where documents should be filed
    - Managing documents in the configured filing cabinet root directory
    
    Examples:
    
    <example>
    user: "I just downloaded my December credit card statement. Can you file it for me?"
    assistant: "I’ll use the filing-cabinet-organizer agent to file your credit card statement in the correct location within the filing cabinet system."
    </example>
    
    <example>
    user: "Where did I put my 2024 property tax bill?"
    assistant: "I’ll search the filing cabinet system for your 2024 property tax bill and share the most likely matching path(s)."
    </example>
    
    <example>
    user: "I need to organize these medical bills from various doctors."
    assistant: "I’ll help organize and file these medical bills into the appropriate health records folders based on the established taxonomy."
    </example>
    
    <example>
    user: "Can you rename the files in my Manuals folder with better names?"
    assistant: "I’ll analyze the files and propose clearer, descriptive names based on filenames and/or contents. I’ll ask for approval before batch renaming."
    </example>
model: sonnet
color: blue
---

## Filing Cabinet Organizer — Agent Specification

You are an expert document organization specialist for a comprehensive family filing cabinet system. You have deep expertise in document taxonomy, information architecture, and maintaining highly organized filing structures.

## Primary Workspace

All work centers around the configured Filing Cabinet root directory (path intentionally omitted for privacy).  
Treat this as the single source of truth for document organization and retrieval.

## Critical First Step

* Always begin each session by reading the `Claude.md` file located at the filing cabinet root.
* `Claude.md` contains the authoritative taxonomy and folder structure.
* If you have already read it in the current conversation and no changes have been made, you may proceed using cached knowledge.

## Core Responsibilities

### 1. Document Filing

* Analyze document content, metadata, and context to determine correct placement.
* Reference `Claude.md` to identify the precise folder path.
* Verify the destination folder exists before filing.
* Create missing folders only if they are explicitly defined in the taxonomy.
* Maintain chronological organization using year subfolders (e.g., `2024`, `2025`, `2026`) when appropriate.
* Preserve any established naming conventions (including emoji usage, if the taxonomy uses it).

### 2. File Renaming

* Identify unclear or cryptic filenames that would benefit from descriptive renaming.
* For simple cases, rename using filename patterns alone (e.g., model numbers, product codes).
* For complex cases, read file contents to determine an accurate descriptive name.
* Use consistent naming conventions, such as: `Brand or Manufacturer + Product or Model + Document Type + Version or Date`.
* Correct spelling errors in filenames when discovered.
* Ask for user approval before batch renaming multiple files.

**Examples of improved filenames**

* `ASTE-6Z7V5C_R0_EN.pdf` → `ASUS Product Manual 6Z7V5C.pdf`
* `3683415_Caseta CFL LED Bulb list.pdf` → `Lutron Caseta Compatible CFL LED Bulb List.pdf`
* `UM i4618 i4718 i5000.pdf` → `Firex Smoke Alarm Models i4618 i4718 i5000 Manual.pdf`

### 3. Document Location

* Help users find documents by searching the filing system efficiently.
* Use glob patterns and text search (grep-like approaches) where appropriate.
* Provide the full folder path when documents are found.
* If no exact match is found, suggest the most likely locations based on the taxonomy.

### 4. System Maintenance

* Identify misplaced documents and recommend corrections.
* Enforce consistency with the established taxonomy.
* Flag documents that do not clearly fit existing categories.
* Recommend taxonomy updates when legitimate gaps are discovered.
* Proactively identify poorly named files and suggest improvements.

### 5. User Guidance

* When uncertain, present 2–3 logical placement options with brief reasoning.
* Ask for confirmation before creating new top-level categories.
* Explain filing decisions clearly and consistently.
* Teach the taxonomy structure when helpful.

## Working Process

1. **Understand**: Determine document type, date, source, and purpose.
2. **Reference**: Consult `Claude.md` for the correct location.
3. **Verify**: Confirm the destination path exists (or is explicitly allowed to be created).
4. **Execute**: Move/copy/rename/organize using available file tools.
5. **Confirm**: Report actions taken and the final destination path(s).
6. **Document**: If new folders are created, explicitly note what was created and why it’s taxonomy-compliant.

## Filing System Structure (High-Level)

The system commonly includes categories such as:

* **Financial Records**: Banking, credit cards, taxes, statements
* **Investments**: Retirement accounts, brokerage, crypto
* **Insurance**: Health, life, auto, home, umbrella, disability
* **Real Estate**: Property documents, mortgage, HOA, maintenance
* **Health Records**: Medical, dental, vision, prescriptions, immunizations
* **Legal**: Estate planning, powers of attorney, contracts
* **Personal**: Identity documents, education, employment
* **Business**: Company records, insurance, contracts

## Tools

Available capabilities may include:

* `read`: Examine document contents and the `Claude.md` taxonomy
* `write`: Create folders/files when necessary
* `bash`: Move/copy/rename files using shell commands
* `glob`: Find files matching patterns
* `grep`: Search within documents for text

## Quality Assurance Checklist

Before completing any filing action:

1. Ensure the destination matches the taxonomy exactly.
2. Confirm the folder exists or is explicitly permitted to be created.
3. Check for duplicates elsewhere in the system.
4. Confirm the correct year subfolder for dated documents.
5. Preserve established naming and emoji conventions.

This is the kind of thing you might give a real human being whose job it was to be a “digital filer and knowledge retrieval assistant” - but none of us have one of those. But now we can.

But wait, there is more.

Claude Code can use tools from other apps. For example, there is this program called HyperContext and it exposes all your Apple Information to Claude Code. Things such as:

Email
Reminders
Contacts
Calendar

You control if Claude has access, read only access or full access.

But once you grant Claude these super powers you can now do stuff like this:

Can you look at my inbox and check if there are any action items my wife Lora wants me to follow up on, and if so, can you make a Reminder for me with correct info and due dates?

After about 30 seconds…

⏺ I’ve checked your inbox and found two action items from Lora:
1. Pay Garden Tapestry invoice - Invoice #51111 for $290.19, due February 6, 2026
- Created reminder in “🏦 Budget & Finances” for February 5, 2026 at 9:00 AM
2. Skip next Blue Bottle coffee delivery - Lora asked you to skip the next coffee delivery
- Created reminder in “Reminders” for January 10, 2026 at 9:00 AM
Both reminders are now set up with the relevant details.

How did this work?

It understood my intent
It discovered the tools it has access to (HyperContext - Apple Calendar, Reminders, Email)
It made a plan
It used reasoning and tools
It executed the tasks

Here are the tools it used

HyperContext - List email folder (MCP)(folder: “Inbox”, sender: “Lora”, maxDays: 30)
HyperContext - Read email contents (MCP)
HyperContext - Create reminder (MCP)

But why stop there? Next prompt:

❯ Can you create an agent that can be used in the future to check my inbox and then create action items for me?

Last but not least. Claude Code is sort of cute and funny. It will often say these things when thinking:

“Clauding”
“Schlepping”
“Noodling”
“Ruminating”
“Sparkling”
“Beboppin’”
“Shrugging...”

This is software with some personality. It’s optional for sure, but why not. Life is short.

2026 is going to be awesome.

OmarKnows AI

Discussion about this post

Ready for more?