Free resources

Free Downloads

Use this hub as a route chooser. Pick a download path that keeps the work predictable, then move to the matching tool or guide when a file alone is not enough.

Choose the route

Open the Right Entry

The same question can land in three different destinations. Your first decision is whether the next output must be customized, whether it is reusable, and whether it can be shared safely. Use the cards below as the default entry choice before opening a deeper workflow.

Photoshop shortcut sheetPrintable shortcut resources for focused Photoshop workflows. Designer cheat sheetsQuick references for colors, prompts, image prep, and shortcuts. Tools directoryCreate fresh exports from browser tools when a static download is not enough.

Decision Rules

Use this checklist in order:

Need a stable reference that works across projects and teammates? Open a download page.
Need output based on current brand tokens, palette, dimensions, or customer inputs? Go to the relevant tool route.
Need a handoff artifact for review, ticket comments, or client notes? Use downloads only if paired with a source link and version note.
Need long-term storage, changelog, or historical context? Move to the Archive after the working task is done.

Concrete Routes and Limits

Use Photoshop shortcut sheet for in-session memory, keyboard training, and classroom checklists.
Use Designer cheat sheets when the target task is a repeatable rule set such as spacing, naming, contrast checks, or prompt structure.
Use Tools directory when output must change with user input, file names, or live constraints.

Limits are strict by design: static downloads should not be treated as final production truth. They are starters, not live systems. If the source constraints change, open the tool route and refresh the artifact.

What to do before you hand off

Before sending any file, run this final gate. If any item fails, stop and reroute to the related guide or tool immediately.

Check that the file matches the project question and scope.
Check language, format, and unit assumptions are still correct for the receiver.
Check whether the asset should include a date or source marker.
Check whether the output depends on a preference set in a guide, tool, or client instruction.

Stop Conditions

Do not continue with this hub if one of these triggers appears:

The requirement is variable, like custom prompt tokens from a live design system.
The user asks for batch conversion tied to uploaded or private inputs.
There is a compliance check needed that requires the workflow tool, an audit trail, or source attribution.

When a stop condition appears, hand off to the correct sibling route:

For token or JSON based workflows, use Design Token Converter.
For task-specific shortcut lists, use Shortcut Cheat Sheet Builder.

Route Examples by Goal

Goal: quick training Open a cheat or shortcut PDF, do a short print, then return only if the rules differ by software version.

Goal: project onboarding Start with download references for alignment. If values differ by brand, route to tool output and export updated starter files.

Goal: design handoff Export static notes from this hub only after attaching the source route and approval context in the same message thread.

Practical next action

Pick one starting route, then open exactly one adjacent page to avoid branching confusion.

Reference check: Designer cheat sheets
Software execution check: Photoshop shortcut sheet
Input driven generation: Tools directory

Downloads on Fundy are free static resources. They should be fast, low risk, and easy to replace with fresh output when inputs shift.