Photoshop Resources

Open the right entry immediately

Do not start by reading everything. Start by choosing one route and follow only that workflow until you hit a stop condition.

Decision rulebook for quick routing

Pick one of these outcomes as your first page:

• Decision 1: I need a menu item, key, or shortcut name. Route: Keyboard shortcuts. Stop after confirming platform, version, and exact menu path.
• Decision 2: I have a file to load into preferences or custom setup. Route: KYS files. Stop before importing if you cannot verify source and backup intent.
• Decision 3: I need repeatable actions across many files. Route: Actions. Stop after a dry run on two sample files before applying batch scope.
• Decision 4: Photoshop is slow, laggy, or unstable. Route: Performance settings. Stop when issue reproduces after one tuning pass.

When to stay here vs leave

• Stay in this hub for planning: choosing a route, defining limits, and deciding handoffs.
• Leave now to Photoshop Shortcut Finder when you need command search across tools and fast validation of key names.
• Leave now to Image Tools after final image pass if you need resize, convert, or checksum checks before delivery.
• Leave now to Downloads when creating a file package, archive export, or share bundle.

Stop conditions and handoffs

Use these guardrails so the workflow does not expand into guesswork.

• Stop condition for shortcut lookup: if the key combo is version specific, open official Photoshop documentation when behavior differs between versions. Avoid copy-paste of old commands.
• Stop condition for KYS: if the file target is unknown or team shared, do not import until a rollback path is confirmed and test prefs are isolated.
• Stop condition for actions: if one file fails in a batch, pause the batch and route the remainder to manual review for the failed class of files.
• Stop condition for performance: if cache settings help only for one file type, document the exception and keep a short note for later review.

Practical routing flow

1) Define intent in one sentence. 2) Open the matching card above. 3) Run only one diagnostic action. 4) If that action proves it, complete a handoff and end the session on that route. If not, return here and switch route with explicit reason.

This keeps sessions short and avoids broad searching, especially for mixed tasks that include both setup and delivery. A good route chooser page should reduce clicks, not increase page depth.

Limits of this hub

This page is not a replacement for execution. It does not execute Photoshop actions, does not host commercial plans, and does not collect user files. It is a practical index for local workflow decisions only.

• Use it for direction, not for remote processing.
• Use explicit browser tools for final edits, conversions, and exports.
• Use it for routing boundaries, not as an archive dump.

Legacy boundary and archive context

Fundy avoids duplicating old GFX^TM content into new pages. When historical context explains old behavior, route to archive references and return with a current task choice.

• Keep current instructions separate from historical notes.
• Use archive links only after confirming the modern task is not already covered.
• Use the route map above to avoid mixing legacy guidance with current recommendations.

Useful next steps

• Keyboard shortcuts hub - Use for command name lookup, printable references, and cross platform differences.
• KYS file details - Use for setup changes, file import safety, and rollback planning.
• Action flow notes - Use for repeatable production edits and safe batch entry points.
• Performance notes - Use for large-file stability, redraw speed, and memory pressure checks.
• Photoshop Shortcut Finder - Search command names, platforms, and menu paths.
• GFX^TM Archive - Understand legacy context and route boundaries.