Software UI Design

What to consider before installing or using this skill: - The package is incomplete: several scripts and reference files listed in SKILL.md are missing. Expect parts of the described workflow (Sketch/XD parsing, export, design-to-code) to be unimplemented. - Data-format mismatch: figma_parser outputs keys like 'colors', 'textStyles', and 'components', while ui_checker expects a report with an 'elements' array. You will likely need to transform outputs locally or update scripts to interoperate. - Token handling: The skill requires a Figma Personal Access Token to call api.figma.com. Only provide a token with the smallest possible scope (read-only, limited to specific files if possible) and prefer using a temporary token. If unsure, run the provided Python scripts locally yourself rather than handing the token to a remote agent. - Code review: The two included scripts are short and readable and call only api.figma.com and local file I/O; no obfuscated code or hidden endpoints were found. Still, review or run the scripts in a sandbox first. - If you need the missing features, ask the publisher for the complete source or the missing scripts (sketch_parser.py, annotate.py, export_assets.py, design_to_code.py and referenced docs). Consider forking and implementing the missing pieces locally rather than trusting an incomplete third-party package. Recommended actions: 1) Do not share broad-scope or long-lived Figma tokens; create a token with minimal permissions and expire it after use. 2) Test the scripts locally on a disposable account or test file before using real project files. 3) Verify/patch the data-flow between figma_parser output and ui_checker input before relying on automated checks. 4) If you want full functionality described in SKILL.md, request the missing scripts or choose another tool with a complete implementation. Confidence note: Assessment is "medium" because the code that exists is benign-looking and coherent for Figma parsing, but the missing files and documentation discrepancies create ambiguity about the package's completeness and intent.