• Check outESLint config that contains more than 1200 rules for the tools that I and the team use.
  I review, update and extend it regularly (weekly, sometimes more often).
• Take a look onStyleLint config that contains more than 200 rules for CSS and 70+ for SCSS,including autoformatting to maintain order within rules and properties and other good practices.
• As a big fan of universal code beauty, I'm a member ofstylelint-stylistic organization.
  We're maintaining stylistic rules that areno longer supported in the core Stylelint project.
• Commitlint config provides a unified style of commits(usingConventional commits with ability to expand) and changelog generation.
• Myplatform agnostic solution for testing Stylelint plugins might help youif you're developing your own Stylelint plugin, I'm also including this as a sample of my technical writing -check out the documentation.

Of course, most solutions are under NDA, but there are also some in Open Source.

• @morev/utils
  100+ fully typed JavaScript utilities for everyday use.
• more-sass
  The library of useful SCSS mixins and functions.
• @morev/vue-transitions
  Reusable interface transitions library for Vue2/Vue3 both.
• @morev/equal-heights
  Framework agnostic solution to emulate CSS Subgrid.
• postcss-specificity-decorator
  PostCSS Plugin to increase the specificity of selectors via decorator-like syntax.

There are many others! You can find the rest under the"Repositories" tab in my account.

It's all about creating andmaintaining a design systems based on user analytics and the web in general.
This is the best way to speed up development and preserve maintainability and consistency. I know how to do this.
In general, I believe that "UX" is pretty good at standardizing and fitting into guidelines if there is enough visual experience and proper component design.

I'm a design-savvy programmer, not a designer who understands something about code.
This means I'm unlikely to create a "wow!" design concept, but I'm definitely the best person to tidy up an existing oneand ensure further communication between frontenders and designers in a way that doesn't hurt.

Lately I've been doing a lot more consulting than developing on my own,but either way it keeps me connected to real-world problems and lets me call myself a "playing coach".

Some of my publicly available projects that I can tell you about my participation in:

• https://uflor.ru/
• https://championtool.ru/
• https://prostudio.ru/

Familiar with React, but without a deep dive into the ecosystem.
I like Astro conceptually, right now I'm developing my own site on it,because I want to achieve maximum client performance keeping DX relatively compared to Vue.

I haven't come across Svelte, Solid and Angular in real work, but would like to get better with them, if there are any offers.

If I have a choice, I prefer to useVitest for unit testsandPlaywright for end-to-end testing, but I'm familiar with others as well.

Actually, I believe that the specific tool is not very important -it's the overall understanding and culture of testing that matters.

I prefer to useVite if possible - for ease of configuration, extensibility, speed and out-of-box TS support.
I've encountered writing plugins/transformers under Webpack and Vite (by the way, check outunplugin if need that too).

Task runners... for a while I thought they had their uses, but now I think it's easier to just use nativescripts instead,a task runner is just an unnecessary dependency that's losing popularity.

I'm following theVoid Zero initiative with interest and what it will evolve into.Might have to learn Rust :)

Well, this is a non-core thing at all, but do you know how many times I've seen project deadlines pushed backbecause there was a formal excuse like "the designer didn't finish something or did something wrong"? :)

If necessary I'll finish/draw/edit/fix icons/layouts/components/raster graphics on my own without involving a profile specialist.Sometimes it saves a lot of time and attention.

Years ago I was relatively good at it, but for the last 5 years or so I've hardly ever come across it, meaning developing on my own.
Nevertheless - understanding remains, which allows better communication with related specialists and this is important when designing systems.

I would say FrontOps, ha-ha. I once joked that I could replace a small IT department with just myself :)
But for now, it's the same as it is with the backend - my focus has shifted heavily towards the frontend in the last few years.