Naming your symbols

Name your layers appropriately. We try and stick to all lower case, separated by dashes.

Sketch automatically organises Symbols into folders when you put a / in the name:

Input field dependencies are tidied away in the /in/ folder

I recommend a control/definingproperty-state naming convention. Default states shouldn’t have a state — tab-inactive and tab-active is redundant. tab, tab-active is the way to go. Your names shouldn’t be too tightly tied to a controls physical attributes, since they’re likely to evolve.

button/primary-mouseover button/primary-disabled in/input/field/active

Denote nested symbol dependencies

I also recommend using your naming convention to denote dependencies now that nested symbols are a thing. When you’re copying symbols between documents, it’s good to know that you need to copy all the symbols with the prefix in/ for input fields to behave as you expect. It also keeps your insert symbol panel tidy.

Organised symbols make your life easier

When using Sketch Runner, establishing a naming convention means you’ll always be able to find what you’re looking for because there’s a pattern to what you’re searching for.