inventory-snapshot

Snapshot Figma component library into a markdown inventory with traceability and delta reporting.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill inventory-snapshot-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inventory-snapshot
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/inventory-snapshot
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill inventory-snapshot-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design teams lose track of which Figma components have corresponding spec docs, code, and Storybook stories, making it impossible to measure design-system coverage or prioritize what to build next. ## Core Features & Use Cases - Figma Library Enumeration: Calls Figma MCP tools to list every component in the upstream library with name, node ID, and variant info. - Tier Classification & Traceability: Infers each component's tier (atom, molecule, organism, layout) and checks whether its spec doc, code directory, and Storybook story exist in the project. - Delta & Priority Queue: Computes ADDED, RENAMED, DEPRECATED, and RESCOPED changes versus the previous snapshot and refreshes a priority queue of components needing attention. - Use Case: After design ships a Figma library update, run this to refresh docs/research/_inventory/figma_components.md, see which new components lack code, and identify the top 5 candidates for component-spec work. ## Quick Start Snapshot the Figma component library from this file URL into the inventory and show me the delta versus the last snapshot.

Frequently Asked Questions about inventory-snapshot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track which Figma components have code and stories?▼

Run an inventory snapshot that enumerates every Figma component via Figma MCP tools, then checks for the matching spec doc, code directory, and Storybook story file in the project. The result is a markdown table with per-component traceability and a coverage percentage.

How to detect changes between Figma library versions?▼

Compare the current Figma library enumeration against the previous snapshot stored in the inventory file. Components are classified as ADDED, RENAMED, DEPRECATED, or RESCOPED, with ambiguous renames flagged as open questions for human review.

Does this work without a Figma source available?▼

No. The snapshot requires a Figma file URL and access to Figma MCP tools such as get_libraries or get_metadata to enumerate components. Without a Figma source, use a single-component audit approach like design-spec-review instead.

Will the inventory snapshot modify my component code or stories?▼

No. The operation is read-only against the design-system surface; it only writes to the inventory markdown file. Spec docs, code directories, and Storybook stories are checked for existence but never modified.

How are Figma components classified into design system tiers?▼

Each component is classified as atom, molecule, organism, or layout using composition rules: atoms use only tokens, molecules compose atoms, organisms compose molecules and atoms, and layouts are page-level containers. Ambiguous cases are marked as proposed and surfaced as open questions.