Command palettes that actually understand context

Every design tool has a command palette now. But they're all the same—static lists that react to what you type, not proactive assistants that understand when and why you work.

I wanted to build something different. A palette that learns your patterns and suggests different actions at 9 AM versus 4 PM. One that remembers you always export assets before reviews and nudges you toward the right workflow steps.

Dynamic suggestions, not static lists

The magic happens in how this palette builds context in real-time:

Time awareness: Morning suggestions focus on planning and continuation. Afternoon prompts encourage creative breaks. Evening actions emphasize wrap-up and documentation.

Project momentum tracking: If you're 89% done with something, it pushes completion actions rather than exploratory ones. The urgency adapts to where you actually are.

Workflow memory: Each action influences future suggestions. Open Figma once, and it starts showing handoff-related tasks. Review feedback, and implementation actions bubble up.

The interface updates every 30 seconds—not just the time display, but the actual available actions.

Real execution, not concept demos

Every suggestion connects to concrete actions:

• Export assets → Opens file preparation workflow
• Run accessibility audit → Launches audit checklist
• Sync with dev team → Opens handoff documentation tools
• Schedule feedback session → Connects to calendar integration

The execution feedback is immediate and realistic, with loading states and confirmation messages that feel like real tool integrations, not placeholder text.

Why traditional palettes fall short

Most command interfaces treat context as metadata—a filter applied to existing commands. This treats context as the primary interface, generating suggestions from your current situation rather than just filtering through it.

It's the difference between a tool that responds to what you search for versus one that anticipates what you need before you know you need it.

Building patterns, not just shortcuts

The palette tracks your work rhythms:

// Morning patterns
if (timeOfDay === "morning") {
  suggestions.push({
    label: `Continue ${activeProject.name} (${progress}% complete)`,
    urgency: progress > 80 ? "high" : "medium"
  });
}
 
// Behavioral patterns  
if (userActions.includes("opened_figma")) {
  suggestions.push({
    label: "Sync components with development team",
    category: "workflow"
  });
}

It's learning what you actually do, not what productivity frameworks think you should do.

When this works vs. traditional palettes

Traditional command palette: When you know exactly what you need and want to get there fast.

This contextual version: When you know you need to make progress but aren't sure on the next step. When you're switching contexts and need to reorient. When you want your tools to help you think, not just execute.

It's designed for the messy, non-linear reality of creative work.

The shift from reactive to proactive

Instead of waiting for you to remember what needs doing, it surfaces the right actions at the right time. That design review you've been putting off gets suggested as a Friday afternoon task. Asset organization appears when projects near completion.

Try the palette above (⌘K) at different times of day. Notice how the suggestions adapt to when you're using it. That's technology working with human rhythms instead of against them.

The future of design tools isn't more features—it's better context awareness.