Design Cheat Sheets: Practical References for Designers

Route Decision Rules

Cheat sheets are for speed and consistency only. If the work requires value generation from inputs, pick interactive tools or workflow pages. If the work is about team memory, naming systems, and repeated checks, pick a cheat sheet first.

Workflow 1: New Asset, Unknown Constraints

1. Start with the goal: social post, website hero, UI card, banner ad, or print preview.
2. Set hard limits: target size, max file weight, allowed formats, and max colors.
3. If constraints are numeric and predictable, use the image cheat sheet and quick-check outputs before opening any advanced design tool.
4. Open Image Tools if you need dynamic resizing, metadata cleaning, or format conversion.
5. Open Guides Library only when a decision in the cheat sheet is unclear or platform specs changed.
6. Stop condition: do not publish if dimensions, color space, and weight checks are not all passed. Escalate to manual review at that point.

Workflow 2: UI and Visual System Decisions

This route is for repeated UI decisions where consistency is critical.

• Question to route: are you applying brand colors, tokens, spacing, or typography? If yes, open the Color and Token Cheat Sheets first.
• Use stop limits: if contrast is below 4.5:1 for body text, do not proceed to full guide writing. Rework palette first.
• If token names are unclear, check existing project documentation and map every token to a practical alias before coding.
• If CSS output depends on platform variables, use a tool output after reference checks, then validate in the production context.
• If team needs recurring references, save the cheat sheet in the release notes or handoff folder and link the exact rule version.

Workflow 3: AI Draft, Prompt Tuning, and Alt Text

Use this route when text quality and reproducibility matter more than speed alone.

• Start with the prompt template in the Prompt Cheat Sheets. If output is wrong in structure, stop and rewrite prompt blocks before generating more.
• Apply strict limits: one goal per generation, one banned behavior, one fallback style guide source.
• For every generated result, run two checks: prompt compliance and accessibility compliance. If either fails, route to Guides Library for deeper control.
• If repeated misses persist, switch to manual drafting and skip further generation for that run.

Photoshop-First Route

Use this path when pixel control, clipping, retouching, and precise masking are required.

• Open Photoshop Hub before making edits if output needs manual cleanup.
• Use cheat sheet references for shortcuts, layer naming, and preflight checks, then verify 1:1 export settings.
• Stop condition: if a file already breaks budget limits, skip additional stylistic edits and route back to image or prompt routes.

Handoff Rules, Limits, and Delivery

Use this section as a checklist before handing work to QA, PM, or clients.

• Keep the source path: which card above you used and why.
• Keep constraints list: size, format, contrast, naming format, and team-specific exceptions.
• Attach the matching download link only after validation; do not attach placeholders.
• Escalate to a guide or tool page whenever spec changes, platform updates, or compliance requirements are detected.
• Archive references by version when output is reused later; add a short note in your delivery notes.

Next Steps

• Tools Index - Open interactive tools for data-driven output.
• Guides Library - Read the process behind each rule.
• Free Downloads - Return to the downloads hub for file-based checklists.
• Archive - Track past references if the current source is deprecated.

Download Review Notes

Treat each cheat-sheet file as a starter reference. It is useful only after it is matched to the exact workflow, version, and audience.

• Match each file to a platform, tool version, or team workflow before sharing.
• Pair downloads with the related guide or tool link in your handoff message.
• Record a refresh date. Update when naming, shortcut, format, or brand rules change.
• Stop and escalate to the original guide if reviewers report mismatch or ambiguity.