.png)
Frontend architecture you’ll never need to refactor
Hello, dear reader. My name is David Shekunts, and I am a Tech Lead with 12 years of experience.
WSD is one of the best discoveries of my programming career. It maps so naturally onto how frontend is structured that it fits almost any task.
I have been using this approach for about 7 years, and I have never had a case where it created problems or failed me.
Does this sound like magic / a silver bullet? I may be a fool, but damn it, I will say “yes.” Surprisingly, I have not yet found a case where this structure does not work.
And now, dear reader, I challenge you to a duel: find such a case, show it to me, and do the most important thing in human history — destroy the first and last silver bullet.
<aside> 📮
Subscribe on X channel [ $davids.sh ] , where announcements of new chapters and updates to existing ones will be posted.
</aside>
Applications written using WSD:
(coming soon)
Before we start doing anything, remember one important capability we now have in 2026: you can simply add a link to this page into AGENTS.md and other AI instruction documents like this:
“When structuring the application, follow the instructions from widget-sliced-design.davids.sh”
This way, you can immediately get the benefits of WSD while also gradually learning how to use it yourself.
<aside> ⚠️
The examples use React + TypeScript, BUT you can use absolutely anything: any language, platform, or point in the space-time continuum.
WSD naturally mirrors any system that can be described as: “A tree-like UI that can be manipulated with functions and can work with variables” — yes, in exactly that crude wording. That is why it has worked, works now, and will keep working.
</aside>