> For the complete documentation index, see [llms.txt](https://docs.devlaunchers.org/dl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/getting-started/design-stack/figma/overview.md). # Overview At **Dev Launchers**, Figma is our primary platform for **design, collaboration, planning** across the organization. Designers, product managers, developers, and researchers all use Figma as a shared workspace to align on ideas, explore solutions, and build accessible, scalable products together. Figma is not just a design tool for us, it’s a **collaboration hub**. *** ### How We Use Figma at Dev Launchers We use multiple Figma products together to support different stages of our workflow: #### Figma Design Figma Design is where we: * Design interfaces using the Universal Design System * Build and maintain components, patterns, and layouts * Apply design tokens, variables, and component properties * Prepare designs for developer handoff and implementation All production UI work should align with UDS foundations and components when working in Figma Design. *** #### FigJam FigJam is used for: * Early ideation and brainstorming * User journey mapping and flow diagrams * Workshops, critiques, and collaborative planning sessions * Cross-team alignment between Design, Product, Development, and Research FigJam allows teams to think together before committing to structured UI designs. *** #### Figma Slides Figma Slides is used to: * Communicate design decisions and progress * Share research findings and product updates * Present concepts, reviews, and roadmaps * Create consistent, reusable presentation decks Slides help us keep communication visual, lightweight, and accessible across the organization. *** ### Collaboration Across Teams Figma enables real-time collaboration between: * **Design** — crafting user experiences and system components * **Product** — defining requirements, priorities, and user needs * **Development** — reviewing specs, variables, and interaction logic * **Research** — documenting insights, feedback, and usability findings By working in a shared environment, we reduce handoff friction and maintain a common source of truth. *** ### Education & Community Dev Launchers is a **proud Figma Bootcamp partner**, and we actively invest in education and accessibility for our community. * All active members and educators are eligible for **Figma Education plans** * We support learning at all levels, from beginners to advanced contributors * We encourage exploration, experimentation, and continuous improvement Learning Figma is a core skill across multiple roles at Dev Launchers. *** ### Getting Started If you’re new to Figma or new to Dev Launchers: * **Learn more about getting started with Figma at Dev Launchers** *(View internal* [*Figma Verification Steps*](broken://spaces/d6zpw9BOPWT05kgMT88i/pages/2olvI6pub4KWrYl5Dk8f)*)* * **Check out our**[ **Figma Community Profile**](https://www.figma.com/@devlaunchers)\ *(Explore shared files, components, and public resources)* These resources will help you get access, understand our standards, and start contributing confidently. *** ### What to Explore Next * Learn how to work with **component properties** in Figma * Understand **Design + Dev Mode** workflows * Build responsive components using **Auto Layout** * Create interactive flows using **Prototyping** Figma is the foundation of how we design together — the following pages will help you use it effectively within the Universal Design System. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.devlaunchers.org/dl-docs/universal-design-system/universal-design-system/getting-started/design-stack/figma/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.