v1.29.2 — faithful component-doc rendering + atomic-level detection
Bug-fix patch: figma_generate_component_doc now renders Figma component descriptions faithfully and reliably tags each component's atomic-design level.
Fixed
- Component descriptions render their sections instead of leaking heading markup. Figma descriptions using single
#headings (e.g.# Usage Guidelines,# Accessibility Requirements) were only parsed at##/###, so they leaked into output as literal- # Headinglist items. The parser now recognizes single-#headings, so Usage Guidelines, Implementation Considerations, Accessibility Requirements, and Content Configuration render as proper sections. - Frontmatter
descriptionno longer truncates mid-sentence. It previously split on the bare word "Accessibility"; it now takes the first sentence up to the first heading or blank line. - Figma URL no longer contains a doubled
?node-id=. The existing pagenode-idquery param is now stripped before the target node id is appended. - Atomic-design
levelis detected without relying on published-library metadata. Detection previously depended oncontaining_frame.pageIdfrom/components+/component_sets, which is often empty over REST even for components with publish keys. It now resolves the home page via a singleids=<node>file request and walks back to the nearestATOMS/MOLECULES/ORGANISMS/TEMPLATESdivider — emittinglevel:frontmatter plus a matching tag, with no dependency on library publishing.
No new tools; plugin re-import not required.
Full changelog: https://github.com/southleft/figma-console-mcp/blob/main/CHANGELOG.md#1292---2026-06-02