Figma

Figma is full of two basic roles for developers:

• it is the Source of True, i.e. the documentation of how the data presentation layer should look like;
• presentation of the business model and the use of data in the presentation layer.

Work rules

Below are some important rules for working with Figima:

• all features and their values defined in the design in Figma file should be reproduced in the Tailwind file configuration;
• components' naming should strive to fully reproduce the naming used in Figma;
• layers and groups of layers that have defined values should be reproduced by all values in the component;
• lack of variant for a component/group of components does not mean that they are not needed - the business requirements should be confirmed each time;
• images and files exports should always be limited to the format .png (ultimately .webp) or .svg;
• the first contact person on the project in Figma is UX/UI Designer, and in his/his absence of Project Manager or Product Owner;
• in the case of deficiencies in the project, the method and order of making changes is determined each time by the team;
• it is preferred to use direct communication instead of comments in Figma.