@viasat/beam-react-claude-plugin 2.70.0 → 2.71.0

package/.claude-plugin/plugin.json

@@ -3,7 +3,7 @@
   "name": "beam-react-claude-plugin",
   "displayName": "Beam React Claude Plugin",
   "description": "Equips AI tools with Beam Design System context for building, auditing, and answering implementation questions across tokens, components and data sources in React.",
-  "version": "2.70.0",
+  "version": "2.71.0",
   "author": {
     "name": "Viasat",
     "url": "https://git.viasat.com/vega/beam"
@@ -15,7 +15,7 @@
       "command": "npx",
       "args": [
         "-y",
-        "@viasat/beam-react-mcp@2.70.0"
+        "@viasat/beam-react-mcp@2.71.0"
       ]
     }
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viasat/beam-react-claude-plugin",
-  "version": "2.70.0",
+  "version": "2.71.0",
   "description": "Claude Code plugin that reduces AI hallucinations on Beam usage. Ships skills, reference docs, and a user-invocable token audit command.",
   "license": "MIT",
   "author": "Viasat",

package/references/data-sources.md

@@ -24,10 +24,21 @@ Data comes from `beam-manifest.json`, bundled in the npm package. Zero network c
 | `listComponents`    | Discover components (optional `query`/`category` filter).               |
 | `getComponent`      | Full API for one component: props, story index, `pairedHooks`.          |
 | `getComponentStory` | Source of a specific usage example/story.                               |
-| `listIcons`         | Available icon names.                                                   |
+| `listIconGroups`    | Icon groups with `importPath` and `iconCount` — no names.               |
+| `searchIcons`       | Find icons by name (required `query`, optional `group`/`limit`).        |
 | `listConcepts`      | Discover concept docs (theming, styling, tokens, getting started, …).   |
 | `getConcept`        | Full MDX content for one concept doc, by slug or title.                 |
 
+Icons are a two-step lookup: `listIconGroups` to see which families exist, then `searchIcons('close')` — optionally scoped with `group` (full `importPath` or its last segment, e.g. `flags`). Results come back grouped by import path, best-matching group first. `matchCount` is the total before `limit` (default 50) is applied, so if it far exceeds the returned icons, narrow the query instead of paging. There is no tool that dumps the full catalog — it's several thousand names.
+
+**The main icon set uses Material Symbols names — search for those, not industry nicknames.** `@viasat/beam-icons/icons` (2,714 of the 3,777 icons) is Material-derived: the Material name, PascalCased. `access_alarm` → `AccessAlarm`, `wb_incandescent` → `WbIncandescent`, `close_fullscreen` → `CloseFullscreen`. About half the set ships Material's filled/outlined pairs (`Delete` and `DeleteOutlined`). If you know the Material icon you want, you already know Beam's name for it.
+
+One wrinkle: the snake_case → PascalCase conversion is inconsistent, so don't assume exact Material casing. Material's `AccountCircle` is `Accountcircle` here, and `ArrowDropDown` is `ArrowDropdown`. Search is case- and separator-insensitive precisely for this reason — type the name as words (`arrow drop down`) and let it match.
+
+The other two families are **not** Material. `illustrative-icons` are Beam-authored spot illustrations (`AccountManagement`, `ActiveCyberDefense`, `RecycleBin`), and `logos/*` are proper nouns (`Delta`, `ApplePay`, `ViasatLogoDefault`) — search those by the brand or subject name.
+
+**Icon search is literal, not semantic.** Matching is substring over icon names, so industry nicknames fail in two ways. Some return nothing — there is no `hamburger` (it's `Menu`), no `cog` (it's `Settings`), no `spinner`, `ellipsis`, `avatar`, or `envelope`. Others return a confident wrong answer: `mute` surfaces `Commute` before `VolumeMute`, and `bin` returns `Plumbing` before `RecycleBin`. Zero results does **not** mean Beam lacks the icon — retry with the Material name, and read the returned name to confirm it describes the glyph you want before using it.
+
 ### Concept docs (and tokens)
 
 Concept docs are MDX guides bundled in the manifest — theming, styling, getting started, and the token reference tables. Discover them with `listConcepts`, then fetch full content with `getConcept('<slug-or-title>')` (case-insensitive; returns `{ title, slug, description, type, mdxContent }`).