Mark Cianfrani

@cianfrani.me

design system engineer, design tokens + web components. Current status: A Pattern Language https://cianfrani.dev/

I just one person at my company to tell me about what new css stuff I can use and let me have the joy of ripping out abomination. What job title is that? Keeper of knowledge?

after having The Thing explain to me what “orthogonal” means like I’m six years old, I think I finally get it and the design token resolver spec is kind of cool, tho unnecessarily gate kept by jargon.

Documenting every single permutation of every component always felt redundant. If you have an input component, you can easily guess what the textarea will look like. Future of DS/AI is patterns. No need to waste context.

Idk if I were a manager id give everyone like a week to do their own project, prototype something, let em pick the tech, not have to use react, sing the songs they want want to sing and then never talk about it.

Playwright just dropped a super useful “ref” option that will add an aria-ref attr. Allows MCP to interact entirely with the aria snapshot instead of the whole DOM/images

> Ebbatson surveyed commercial pilots, asking them whether “they felt their manual flying ability had been influenced by the experience of operating a highly automated aircraft.” Fully 77 percent reported that “their skills had deteriorated”; just 7 percent felt their skills had improved

An MCP server for your design system, except it intentionally gaslights the LLM to make more API requests ($$$) if it detects the user is using Tailwind

Users don't fully understand what the design system is (neither do I sometimes). For many, it's a product requirement. That's a bad combo that creates fear and incentivizes a "hand held" expectation which no maintainer/s can live up to.

It’s actually pretty trivial to change 1 thing in 20 different places now and a lot of best practices were built on top of that being a hard thing to do. Idk