Prompts for Learning Keyboard Shortcuts

Help me with windows file management through an environment-specific starter reference. Goal: organizing folders, selecting files, renaming safely and navigating locations. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid destructive deletion or moving system folders; distinguish File Explorer from dialogs. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with windows file management through a task-based practice route. Goal: organizing folders, selecting files, renaming safely and navigating locations. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid destructive deletion or moving system folders; distinguish File Explorer from dialogs. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with windows file management through a non-working shortcut diagnosis. Goal: organizing folders, selecting files, renaming safely and navigating locations. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid destructive deletion or moving system folders; distinguish File Explorer from dialogs. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with windows file management through a seven-day shortcut learning plan. Goal: organizing folders, selecting files, renaming safely and navigating locations. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid destructive deletion or moving system folders; distinguish File Explorer from dialogs. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with macos finder navigation through an environment-specific starter reference. Goal: finding files, moving between locations and managing selection. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish Finder behavior from application dialogs and keyboard hardware. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with macos finder navigation through a task-based practice route. Goal: finding files, moving between locations and managing selection. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish Finder behavior from application dialogs and keyboard hardware. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with macos finder navigation through a non-working shortcut diagnosis. Goal: finding files, moving between locations and managing selection. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish Finder behavior from application dialogs and keyboard hardware. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with macos finder navigation through a seven-day shortcut learning plan. Goal: finding files, moving between locations and managing selection. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish Finder behavior from application dialogs and keyboard hardware. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser tab management through an environment-specific starter reference. Goal: switching, reopening and organizing browser tabs. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish browser version and operating system; preserve unsaved forms. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser tab management through a task-based practice route. Goal: switching, reopening and organizing browser tabs. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish browser version and operating system; preserve unsaved forms. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser tab management through a non-working shortcut diagnosis. Goal: switching, reopening and organizing browser tabs. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish browser version and operating system; preserve unsaved forms. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser tab management through a seven-day shortcut learning plan. Goal: switching, reopening and organizing browser tabs. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish browser version and operating system; preserve unsaved forms. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser reading and search through an environment-specific starter reference. Goal: finding text, adjusting readability and navigating page content. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Separate browser commands from website commands and avoid clearing user data. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser reading and search through a task-based practice route. Goal: finding text, adjusting readability and navigating page content. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Separate browser commands from website commands and avoid clearing user data. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser reading and search through a non-working shortcut diagnosis. Goal: finding text, adjusting readability and navigating page content. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Separate browser commands from website commands and avoid clearing user data. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with browser reading and search through a seven-day shortcut learning plan. Goal: finding text, adjusting readability and navigating page content. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Separate browser commands from website commands and avoid clearing user data. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel worksheet navigation through an environment-specific starter reference. Goal: moving through populated cells, worksheets and selection regions. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm Excel edition and keyboard layout; distinguish desktop from web. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel worksheet navigation through a task-based practice route. Goal: moving through populated cells, worksheets and selection regions. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm Excel edition and keyboard layout; distinguish desktop from web. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel worksheet navigation through a non-working shortcut diagnosis. Goal: moving through populated cells, worksheets and selection regions. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm Excel edition and keyboard layout; distinguish desktop from web. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel worksheet navigation through a seven-day shortcut learning plan. Goal: moving through populated cells, worksheets and selection regions. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm Excel edition and keyboard layout; distinguish desktop from web. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel data entry through an environment-specific starter reference. Goal: editing cells, filling values and moving through input fields. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid overwriting formulas or triggering unintended fill operations. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel data entry through a task-based practice route. Goal: editing cells, filling values and moving through input fields. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid overwriting formulas or triggering unintended fill operations. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel data entry through a non-working shortcut diagnosis. Goal: editing cells, filling values and moving through input fields. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid overwriting formulas or triggering unintended fill operations. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel data entry through a seven-day shortcut learning plan. Goal: editing cells, filling values and moving through input fields. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid overwriting formulas or triggering unintended fill operations. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel formula review through an environment-specific starter reference. Goal: editing formulas, inspecting references and locating dependencies. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Preserve calculations and confirm feature availability in the exact Excel version. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel formula review through a task-based practice route. Goal: editing formulas, inspecting references and locating dependencies. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Preserve calculations and confirm feature availability in the exact Excel version. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel formula review through a non-working shortcut diagnosis. Goal: editing formulas, inspecting references and locating dependencies. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Preserve calculations and confirm feature availability in the exact Excel version. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with excel formula review through a seven-day shortcut learning plan. Goal: editing formulas, inspecting references and locating dependencies. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Preserve calculations and confirm feature availability in the exact Excel version. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word editing and navigation through an environment-specific starter reference. Goal: moving through text, selecting passages and applying common formatting. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish document language, keyboard layout and Word platform. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word editing and navigation through a task-based practice route. Goal: moving through text, selecting passages and applying common formatting. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish document language, keyboard layout and Word platform. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word editing and navigation through a non-working shortcut diagnosis. Goal: moving through text, selecting passages and applying common formatting. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish document language, keyboard layout and Word platform. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word editing and navigation through a seven-day shortcut learning plan. Goal: moving through text, selecting passages and applying common formatting. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Distinguish document language, keyboard layout and Word platform. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word review workflow through an environment-specific starter reference. Goal: navigating comments, reviewing changes and controlling document views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not accept or reject changes without explicit intent; check review mode. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word review workflow through a task-based practice route. Goal: navigating comments, reviewing changes and controlling document views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not accept or reject changes without explicit intent; check review mode. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word review workflow through a non-working shortcut diagnosis. Goal: navigating comments, reviewing changes and controlling document views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not accept or reject changes without explicit intent; check review mode. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with word review workflow through a seven-day shortcut learning plan. Goal: navigating comments, reviewing changes and controlling document views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not accept or reject changes without explicit intent; check review mode. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint presenting through an environment-specific starter reference. Goal: starting a presentation, navigating slides and controlling views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Differentiate presenter view from slideshow and check the actual display setup. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint presenting through a task-based practice route. Goal: starting a presentation, navigating slides and controlling views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Differentiate presenter view from slideshow and check the actual display setup. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint presenting through a non-working shortcut diagnosis. Goal: starting a presentation, navigating slides and controlling views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Differentiate presenter view from slideshow and check the actual display setup. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint presenting through a seven-day shortcut learning plan. Goal: starting a presentation, navigating slides and controlling views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Differentiate presenter view from slideshow and check the actual display setup. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint slide editing through an environment-specific starter reference. Goal: selecting objects, arranging slides and navigating editing views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid shifting grouped objects or altering the theme unexpectedly. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint slide editing through a task-based practice route. Goal: selecting objects, arranging slides and navigating editing views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid shifting grouped objects or altering the theme unexpectedly. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint slide editing through a non-working shortcut diagnosis. Goal: selecting objects, arranging slides and navigating editing views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid shifting grouped objects or altering the theme unexpectedly. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with powerpoint slide editing through a seven-day shortcut learning plan. Goal: selecting objects, arranging slides and navigating editing views. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Avoid shifting grouped objects or altering the theme unexpectedly. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor navigation through an environment-specific starter reference. Goal: finding files, navigating symbols and moving between panels. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm exact editor, extensions and keymap before mapping commands. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor navigation through a task-based practice route. Goal: finding files, navigating symbols and moving between panels. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm exact editor, extensions and keymap before mapping commands. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor navigation through a non-working shortcut diagnosis. Goal: finding files, navigating symbols and moving between panels. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment and obtaining [shortcut that failed], [expected action] and [observed behavior], investigate causes without guessing the correct keys. Check focus, layout, app mode, OS conflicts, extensions and custom bindings. Return ranked causes, reversible checks and a verified replacement only when evidence supports it. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm exact editor, extensions and keymap before mapping commands. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor navigation through a seven-day shortcut learning plan. Goal: finding files, navigating symbols and moving between panels. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, build a seven-day plan for [available practice minutes] using a small verified set of task-relevant shortcuts. Give daily tasks, recall questions, visible success criteria and review days. Keep commands stable across the plan and give a fallback for unavailable bindings. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Confirm exact editor, extensions and keymap before mapping commands. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor refactoring through an environment-specific starter reference. Goal: renaming symbols, formatting code and inspecting changes. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, prepare a reference of up to twelve useful shortcuts for this workflow. Use columns for action, verified key combination, app context, prerequisites, official source and a safe check. Include alternatives only when platform documentation supports them. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not execute code or apply refactors blindly; use preview and undo checkpoints. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.

Help me with code editor refactoring through a task-based practice route. Goal: renaming symbols, formatting code and inspecting changes. Before giving any actual key combinations, ask me to confirm [operating system and version], [application name and exact version], [desktop or web interface], [keyboard layout], [device type] and [custom keymap or assistive software]. If required details are missing, ask focused questions and wait for my answers. After confirming the environment, turn [three everyday tasks] into a practice route. Give ordered actions, verified key combinations, expected visible states and a checkpoint after each task. Include a menu or mouse fallback and an undo path where appropriate. Verify platform-dependent keys against current official documentation for the exact environment, cite relevant links and clearly mark unavailable verification. Do not execute code or apply refactors blindly; use preview and undo checkpoints. Do not invent universal shortcut claims, execute actions, send messages, change settings or infer that a command worked. End with a brief check I can perform in a disposable document or harmless view, keeping real data and unsaved work protected.