From shortcut recall to a local working playbook

A shortcut solves a precise memory gap. Many interruptions are larger: the command you run before a release, the review checklist your team agreed on, the snippet that starts a handoff, or the definition that keeps a decision from drifting.

Those fragments are usually scattered across documents, chat history, shell history, and memory. FluentOverlay Pro treats them as content that can live in the same Windows overlay as shortcut discovery. The goal is not to replace those systems. It is to keep the next useful piece of working knowledge close to the application where you need it.

Recall is an event; a playbook is a system

Shortcut discovery answers “Which keys perform this action?” The answer can be enough, especially when Free is all you need.

A working playbook answers a different set of questions:

• What is the next repeatable step?
• Which command or snippet belongs here?
• What rule constrains the work?
• Which definition or decision should remain stable?
• What evidence tells us the workflow is complete?

FluentOverlay's Pro tabs separate those jobs instead of forcing every note into one generic document.

Use execution content for the next move

Prompts, Snippets, Commands, and Workflows hold material you can act on directly.

• A prompt can preserve the shape of a review or handoff request.
• A snippet can keep reusable Markdown, code, or structured notes ready to copy.
• A command can preserve a focused test, diff check, or other repeatable terminal action.
• A workflow can put a multi-step procedure in order.

The shipped starter content includes universal material as well as content for Cursor and VS Code. It covers practical patterns such as task intake, risk-first review, focused verification, handoffs, and turning repeated work into reusable knowledge. These are authored cards, not a claim that an AI assistant is part of FluentOverlay's core shipped behavior.

Use knowledge content for the decisions behind it

Terminology, Skills, Design Patterns, Agents, Rules, and Automations provide the supporting layer.

Terminology stabilizes a shared definition. Skills capture repeatable techniques. Design Patterns record a proven solution shape. Agent cards hold role-specific briefs. Rules preserve guardrails. Automations document reusable runbooks and handoffs.

The separation is useful because a command and the reason for running it have different lifecycles. You may update a test command without changing the review rule that requires focused verification. Keeping those cards distinct makes revision more deliberate.

Build one narrow lane first

Do not begin by migrating an entire knowledge base. Start with one recurring job that currently causes friction.

Consider a code-review handoff:

1. Create a Prompt for the review brief: scope, known risks, and the decision needed.
2. Add a Command for the focused checks that belong to that repository.
3. Create a Workflow that orders context gathering, diff review, verification, and handoff.
4. Add a Rule for the boundary that must not be crossed, such as preserving unrelated work.
5. Add a Terminology card if one project term is regularly misunderstood.

That is already a playbook. It is small enough to maintain and close enough to the work to prove whether it deserves to grow.

Pro also supports categories, custom sorting, favourites, tab presentation modes, and saved views. Use those controls after the content earns its place, not as a substitute for deciding what the lane is for.

Keep source boundaries visible

FluentOverlay's core behavior is local-first. Custom shortcuts and Pack Editor data are stored locally, and Free shortcut discovery does not require an account. Optional update, support, MCP, and marketplace features have their own configuration or network boundaries, so “local-first” should not be stretched into an absolute promise about every possible flow.

The same clarity applies to content. A card should say whether it is a command to run, a rule to follow, or a workflow to review. A local playbook becomes trustworthy through clear ownership and revision, not through volume.

Start at the layer you actually need

If the immediate problem is finding the right keys, begin with How FluentOverlay finds shortcuts and the Getting started guide.

If the repeated work needs a maintained shortcut reference, continue with Creating custom packs. For the current Free and Pro boundaries, see the FluentOverlay product page. Questions about fitting a workflow into the model belong in the contact form.