设计资产规范检查 Design Asset Compliance Checker

About this plugin

【介绍】设计资产规范检查（Design Asset Compliance Checker）面向正在做多组件库治理、设计系统收敛或页面合规自查的团队。插件会扫描当前 Page 上的全部组件实例，按来源组件库分组展示，并汇总实例数、组件定义数、组件库数量，帮助你快速判断「这一页到底用了几个库、各占多少」，为统一组件库、减少混用提供依据。界面支持 21 种语言，打开插件后会自动开始统计，也可随时重新扫描。【功能说明】按组件库分类浏览：以标签形式切换不同来源（含本地组件、各团队库及未识别分组），查看每个库下的组件定义与实例数量。实例与定义统计：展示本页实例总数、组件定义数、涉及的组件库数量，以及未识别实例概况。一键定位：在结果列表中点击「定位」，可在画布上选中并聚焦对应实例。组件库 Key 映射（核心能力）：内置远程组件 Key → 库名映射表（可与「组件统计」类导出 JSON 配合），优先按 Key / 组件名匹配来源，避免仅依赖变量绑定造成的误判。未识别状态说明：对映射表未覆盖或插件 API 无法判定的实例，归入「未添加组件库」等分组，避免强行归到错误库名。多语言界面：支持简体中文、英文等 21 种语言切换。【使用方法】在 Figma 中打开需要检查的文件，并切换到目标 Page。从菜单运行插件 设计资产规范检查 / Design Asset Compliance Checker。等待首次自动统计完成（也可点击 「统计组件库使用」 重新扫描）。在顶部标签中选择某个组件库，查看该库下的组件列表与实例路径。需要核对具体位置时，点击实例旁的 「定位」 按钮。若团队维护了组件 Key 映射 JSON，请保持映射表与库内已发布组件同步；更新 JSON 后重新扫描即可。【注意事项】仅统计当前 Page，不会扫描整个文件的其他页面。Figma 插件 API 无法像右侧面板那样直接读取「Go to main component in library」的库名，准确归类主要依赖组件 Key 映射表；映射表未包含的组件可能显示为「未添加组件库」。库内组件 Publish / Reset 后 Key 可能变化，需同步更新映射 JSON，否则会出现识别缺失或分组不准。插件需访问已配置的远程地址以加载内置映射表；首次使用需允许网络权限。需在文件中启用相关团队库（Assets 面板），以便插件读取可用的库与变量信息。扫描结果用于辅助判断与治理，不能替代设计规范评审或完整的组件库权限管理。【Introduction】Design Asset Compliance Checker helps teams audit library usage on the current Page. It scans every component instance, groups them by source library, and summarizes instance counts, component definitions, and how many libraries are in use—so you can see whether a page relies on one system or several, and plan consolidation with confidence.The UI supports 21 languages. A scan runs automatically when you open the plugin; you can rescan anytime.【Function Description】Browse by library: Switch between libraries using compact chips. Review component definitions and instance counts per source, including local components and unrecognized groups.Usage summary: See total instances, definition count, library count, and how many instances could not be matched.Locate on canvas: Use Locate on any row to select and zoom to that instance in the file.Component key mapping (core): Loads remote JSON maps (component key → library display name). Matching uses keys and unique component names first—reducing wrong assignments from variable bindings alone.Clear fallback states: Instances not covered by the map are grouped separately instead of being forced into the wrong library name.Multilingual UI: 21 languages, including English and Simplified Chinese.【How to Use】Open your Figma file and go to the Page you want to audit.Run Design Asset Compliance Checker from the Plugins menu.Wait for the initial scan (or click Scan Library Usage to refresh).Select a library chip to view its components and instance paths.Click Locate next to an instance to jump to it on the canvas.Keep your team’s key-mapping JSON in sync with published library components; rescan after updates.【Notes】Scans the current Page only, not other pages in the file.The Figma Plugin API does not expose the same library label shown in the native instance attribution UI. Reliable grouping depends on your key-mapping JSON. Unmapped components may appear under Unadded library.After Publish or Reset, component keys may change—update your JSON maps accordingly.The plugin loads built-in maps from an allowed remote host; network permission is required.Enable relevant team libraries in Assets for best results.Results support design governance; they do not replace formal design reviews or access control.