Universal Command Tricks Power Users Swear By

The Command Line for Your Documents

You know that moment when you're hunting through folders, clicking menus, waiting for dialogs to load? Power users in AiFiler don't live there. They live in Universal Command.

Universal Command (Ctrl+Shift+A on Windows, Cmd+Shift+A on Mac) is the fastest way to move through AiFiler if you know what to ask for. Most users treat it like a search box. The people who save the most time? They treat it like a conversation with a very fast assistant who knows exactly where everything is and what to do with it.

Here are the tricks that separate the power users from everyone else.

1. Route Complex Queries With Context Keywords

What: Instead of "find contracts," try "show me all contracts signed in 2024 that mention renewal."

Why: Universal Command's intent routing system recognizes domain-specific language. When you add context keywords (signed, renewal, specific dates), the router matches your intent to the right handler instead of defaulting to generic search.

How: Open Universal Command and type your question naturally. The system parses keywords like dates, document types, and actions. For example:

• "Contracts signed in Q4" → Routes to document search with date filtering
• "Show me all PDFs larger than 5MB" → Routes to file property search
• "Documents I created last week" → Routes to metadata search with temporal context

Time saved: 2-3 minutes per query (vs. clicking filters manually)

2. Chain Actions With "Then" Syntax

What: Use "then" to queue multiple operations: "Find all invoices from Acme Corp then tag them as billable."

Why: This isn't just faster—it's a different way of thinking. Instead of find-then-manually-tag, you're describing the whole workflow upfront. The action executor handles it as a single operation.

How: The syntax is simple:

Find [documents] then [action]

Examples that work:

• "Find all Q3 reports then move them to Archive"
• "Show me unread documents then mark as reviewed"
• "Find PDFs without metadata then auto-tag"

The system executes these sequentially, so you can step away while it processes. Check the Action Center (Ctrl+Shift+T) to monitor progress.

Time saved: 5-8 minutes per workflow (eliminates manual batch operations)

3. Use Negation to Exclude Noise

What: "Show me all documents NOT in the Archive folder."

Why: Most people think Universal Command is additive—you keep adding search terms to narrow down. Power users use negation to eliminate what they don't want. It's often faster to exclude 90% than to include the 10% you need.

How: Prefix terms with "NOT" or use the minus sign:

• "NOT archived" → Excludes archived documents
• "NOT template" → Excludes template files
• "NOT draft" → Excludes draft status documents
• "Contracts NOT signed" → Shows unsigned contracts

You can stack negations:

Show me documents from 2024 NOT archived NOT templates NOT drafts

Time saved: 1-2 minutes per search (fewer refinements needed)

4. Leverage Temporal Shortcuts

What: Use natural language time references instead of picking dates from a calendar.

Why: "Last 7 days" is faster to type than opening a date picker, and it's more natural. The system understands dozens of temporal patterns.

How: These all work:

• "Documents from last week"
• "Everything modified today"
• "Created in the last month"
• "Touched since Tuesday"
• "Last 30 days"
• "Q3 2023"
• "January through March"

Combine with other filters:

Contracts created last month NOT signed

Hidden feature: The system understands "since [event]" phrasing. Try "Documents since the client call" if you've tagged the call in your workspace.

Time saved: 1-2 minutes per search (no date picker wrestling)

5. Ask FileMind Questions Instead of Commands

What: Phrase queries as questions, not commands. "What contracts are expiring soon?" instead of "Find expiring contracts."

Why: Ask FileMind (our Q&A routing layer) handles reasoning across your document graph. Questions often trigger smarter inference than commands.

How: Open Universal Command and ask:

• "Which clients have the most active projects?"
• "What documents reference the new pricing model?"
• "Are there any conflicting dates in our project timeline?"
• "Which templates haven't been used in 6 months?"

The system analyzes your documents and relationships, not just matching keywords. You get answers, not just lists.

Time saved: 5-10 minutes per research task (vs. manually cross-referencing documents)

6. Use Shorthand Prefixes for Speed

What: Memorize these single-character prefixes to route commands instantly.

Why: Once you internalize these, you don't even think about them—your fingers just know. A power user opens Universal Command and types "@recent contracts" in under a second.

How: Common prefixes:

• @recent → Recently modified documents
• @mine → Documents you created
• @shared → Documents shared with you
• @tagged: → Find by tag (e.g., @tagged:urgent)
• # → Search by hashtag in document content
• $ → Search by custom fields

Combine them:

@recent contracts @tagged:urgent

This finds your recently modified contracts tagged as urgent in one command.

Time saved: 30 seconds per query (vs. clicking filters)

7. Create Smart Aliases for Repetitive Workflows

What: Define custom command phrases that map to complex queries you run constantly.

Why: If you run the same Universal Command query 3+ times per week, it's worth aliasing. You type the alias once, and it expands to the full query.

How: In your workspace settings (Settings → Intelligence → Command Aliases), create entries like:

Alias	Expands To
pending-reviews	"Show me all documents with status=pending-review NOT archived"
client-assets	"Find all documents tagged with current client then show by date modified"
month-summary	"Documents created this month then generate summary"

Now instead of typing the full query, you just type:

pending-reviews

The system expands it and executes. Save this as a workspace default, and your whole team can use it.

Hidden feature: Aliases support parameter substitution. Define client:[name] and it fills in the current context. Try client:acme and it automatically uses your Acme Corp folder context.

Time saved: 2-3 minutes per query × 3+ times per week = 30+ minutes per month

The Real Power Move

The users who save the most time with Universal Command aren't the ones who know every feature. They're the ones who think in workflows instead of individual actions. They ask "What do I need to accomplish?" and let Universal Command figure out the steps.

Start with one trick from this list. Internalize it. Then add the next. Within a week, you'll be operating at 2-3x the speed of someone clicking through menus.

Open Universal Command right now. Press Ctrl+Shift+A (or Cmd+Shift+A). Try one of these patterns. You'll feel the difference immediately.