Figma

**Judgment:** This is a strong, specialized skill for working with Figma files in a read-only, analysis-first manner. It is well-suited for teams that need systematic design system audits, accessibility checks, and reliable asset export rather than in-editor design manipulation. **What it’s good for:** - Turning Figma files into structured data (JSON, tokens) for engineering and documentation workflows. - Large-scale asset export in multiple formats and densities for product delivery. - Evaluating and maintaining design system quality and brand consistency across files. - Producing accessibility and quality reports suitable for audits and compliance tracking. **Key risks / limitations:** - **Read-only scope:** It cannot modify or create designs; all improvements must be done manually in Figma or via plugins. - **External dependency:** Relies on Figma’s API, so rate limits, API changes, or outages can impact performance and reliability. - **Access control:** Requires a Figma access token; sensitive tokens and private design data must be handled carefully in prompts and configuration. **Recommended scenarios:** - Product and design system teams needing repeatable audits, token exports, and documentation generation from Figma. - Engineering teams wanting a consistent pipeline from Figma to code-ready assets and design tokens. - Agencies or freelancers generating polished client deliverables and handoff packages from Figma projects. - Accessibility and UX specialists performing structured WCAG checks on Figma designs and exporting formal reports.