Assuming knowledge of how to write style rules, what style sheet types exist, and setting aside components for this portion, I see 4 areas of #CSS where we may find insight into refind authorship. I encourage #Javascript and framework devs to er, react. You have keys I don't. OK

'Specificity First Style' Step 1. ORIGIN Where we (not our tools) know our style rules are including all sheet types, inherited style, global style, undefined style. #CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking

'Specificity First Style' Step 2. RULE. ORDER This is where we (not our tools) examine all rule order and correct where a conflict or override due to calculation results is found. #CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking

'Specificity First Style' Step 3. PRESENCE OR ABSENCE OF INLINE STYLES If present, why? Will step 1 or 2 eliminate or require inline style to achieve the most specific rule. #CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking

'Specificity First Style' Step 4. PRESENCE OR ABSENCE OF !Important If present, why? Will steps 1-3 resolve? !Important should balance power between user and author styles only. #CSS #Cascade #Javascript #Frameworks #Webdev #Solutions #Education #Process #DecisionMaking

It's problematic for many reasons one being way too easy to abuse.