BookSlash for Figma · Design

b/design-system.
b/figma. b/handoff.

Figma is where design lives; the URLs your team needs (the design system, the active project, the engineering handoff) live behind 80-character file IDs. BookSlash flattens them to memorable names every team — design, engineering, marketing — types.

figma

resolved

Figma

figma.com/files/team/{team-id}/{project-id}

landed in 38ms

other shortcuts you might save

b/figmab/design-systemb/uib/prototypes

Suggested slug patterns

Steal these. They work for most teams.

Battle-tested shortcut conventions for Figma, with notes on why each one survives the URL changes that break personal bookmarks.

  • b/figma

    Default project workspace.

    Design and engineering both reach it; saving as a slug ends the URL paste in handoffs.

    https://www.figma.com/files/team/{team-id}/{project-id}
  • b/design-system

    Design system file.

    Designers and engineers both reach it weekly. The file URL is brutal; the slug is memorable.

    https://www.figma.com/file/{file-key}/Design-System
  • b/ui

    Active UI / component library file.

    Engineers reach this during component implementation.

    https://www.figma.com/file/{file-key}/UI-Components
  • b/prototypes

    Active prototype links.

    PMs and stakeholders reach prototypes constantly.

    https://www.figma.com/proto/{file-key}/{prototype-id}
  • b/handoff

    Engineering handoff page or Dev Mode link.

    The standing handoff URL the engineering team uses every sprint.

    https://www.figma.com/file/{file-key}?mode=dev
  • b/figjam

    Active FigJam board.

    Cross-functional brainstorms always start with "where’s the FigJam?"

    https://www.figma.com/board/{board-key}/Brainstorm
  • b/workspace

    Figma workspace root.

    New designers reach it day one.

    https://www.figma.com/files/team/{team-id}

Common workflows

Three patterns that pay back in week one.

01

Engineering handoff every sprint

Engineers reach b/handoff once per sprint. The URL evolves as the design team uses Figma Dev Mode and updates the handoff doc; the slug stays. Replaces a fragile Slack pin to a Figma URL.

02

Cross-functional design review

PMs, engineers, and marketing all reach b/prototypes for prototype reviews. The slug carries to whoever clicks it; Figma’s share rules govern access.

03

Design system lookups

Engineers building a new component reach b/design-system to verify tokens, spacing, and behaviour. b/ui covers component-level details. Two slugs replace the design system URL paste in every Slack thread.

With and without

Same Figma. Different team experience.

Without shortcuts

Engineers paste 100-character Figma URLs in Slack. Marketing asks designers weekly for the prototype link. New designers learn the workspace through trial and error.

With BookSlash

b/figma, b/design-system, b/ui, b/prototypes, b/handoff, b/figjam. Six slugs cover the design surface for the whole org.

Frequently asked

BookSlash + Figma

Figma controls access. Make the file shareable in Figma → Share, then point the slug at the public-share URL. For internal-only files, the destination requires a Figma login.

You update the destination URL. Designers, engineers, and PMs keep typing the same shortcut. The audit log records who changed which slug.

b/handoff often points at a Dev Mode URL. Engineers click the slug and land in Dev Mode; the slug pattern stays as Figma evolves Dev Mode features.

Yes — on a BookSlash board, drop in a live Figma frame. Updates flow through automatically. The slug + the embed cover both navigation (slug) and visual (board embed).

Start with one team. Roll out when it sticks.

Your stack. Your shortcuts.
One keystroke for everyone.

2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.

Free for personal use · No credit card · 14-day team trial

BookSlash for Figma — Shortcuts to design systems, prototypes, and handoffs · BookSlash