All articles

Layer names as a contract: syncKey, duplicates and ordering

Why consistent naming improves accuracy more than visual similarity.

How matching worksHow to find duplicatesHow to rename safely
01

Coordinates are not enough

An element can move hundreds of pixels between breakpoints. TildEka therefore uses a stable key derived from structure and name while storing geometry separately for each width.

02

Duplicates inside a screen

Two Button layers inside one Frame are ambiguous. Diagnostics shows those pairs before export. Rename them by role: Button / Primary and Button / Secondary.

03

Matching entities across screens

Hero / Title should keep its name on desktop and mobile. Nesting may vary, but major hierarchy changes should use explicit names for parent containers.

04

Safe renaming

Rename the layer across all breakpoints and rerun diagnostics. If the block has already been imported, preserve the semantic part of the name so re-import updates the existing element correctly.