What problem does it solve? When converting Figma designs into code, inconsistent layer naming and ambiguous styling rules cause wrong image exports, missing backgrounds, incorrect colors, and broken layouts. This Skill provides a single lookup manual of naming prefixes and implementation rules so design-to-code output stays consistent and predictable. ## Core Features & Use Cases - Layer Prefix Semantics: Defines how prefixes like sub-, block-, img-, bg-, bgc-, btn-, scrollx-, scrolly-, fixed-, and x- map to code generation behavior, including multi-prefix priority ordering. - Image Export Rules: Specifies Figma REST API export with use_absolute_bounds, SVG vs PNG selection, kebab-case file naming, and a strict imageBaseUrl + assetsDir + filename URL formula. - Styling & Unit Rules: Covers bgc- CSS mapping (fills, strokes, cornerRadius, effects), fixed positioning from constraints, Alibaba PuHuiTi font handling, multi-layer TEXT fills resolution, and px/vw/rem unit conversion. - Use Case: A developer converting a Figma page to React + SCSS consults this manual to decide whether a gradient button layer should be exported as an image or expressed as CSS, and how to name the resulting component and asset files. ## Quick Start Ask the AI to look up the pp-style rules for handling a bg- prefixed layer with a gradient fill before generating the component code.