<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ibrahima D.</title>
    <description>The latest articles on DEV Community by Ibrahima D. (@ibrahimdans).</description>
    <link>https://dev.to/ibrahimdans</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1002326%2F52fc8ac0-d5ec-492f-ab46-1fd9c95b716c.jpeg</url>
      <title>DEV Community: Ibrahima D.</title>
      <link>https://dev.to/ibrahimdans</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ibrahimdans"/>
    <language>en</language>
    <item>
      <title>Twelve Files for Twenty Lines: When Clean Code Becomes the Problem</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Wed, 18 Nov 2026 08:44:17 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/twelve-files-for-twenty-lines-when-clean-code-becomes-the-problem-2lg2</link>
      <guid>https://dev.to/ibrahimdans/twelve-files-for-twenty-lines-when-clean-code-becomes-the-problem-2lg2</guid>
      <description>&lt;p&gt;I've seen code that ticked every box. Small functions. One responsibility per class. Interfaces everywhere. Not a single line you could call ugly.&lt;/p&gt;

&lt;p&gt;And nobody could change it.&lt;/p&gt;

&lt;p&gt;I remember one ticket: add an optional phone number to a form. We estimated half a day. It took three, and twelve files. Most of that time didn't go into changing the code. It went into finding where things happened.&lt;/p&gt;

&lt;p&gt;To understand what happened when a user clicked "Save", you had to follow six jumps: a handler that called a service that called a factory that built a strategy that delegated to a mapper that finally touched the data. Twenty lines of real logic, spread thin over an architecture built for a future that never came.&lt;/p&gt;

&lt;p&gt;Everyone who had written it was proud of it. Everyone who had to maintain it was afraid of it. Not because any piece was hard. Because you had to hold all of them in your head at once.&lt;/p&gt;

&lt;p&gt;We don't talk about this enough. We have a hundred articles on how to clean up messy code. We have very few on the opposite failure, because the opposite failure looks like virtue.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it looks like
&lt;/h2&gt;

&lt;p&gt;Here's an illustration. Not real code from a real project, but if you've been around, you've met its cousins.&lt;/p&gt;

&lt;p&gt;The task: apply a discount to an order if the customer is a member.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// DiscountStrategy.ts&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategy&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// MemberDiscountStrategy.ts&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;MemberDiscountStrategy&lt;/span&gt; &lt;span class="k"&gt;implements&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategy&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;amount&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;0.9&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// NoDiscountStrategy.ts&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;NoDiscountStrategy&lt;/span&gt; &lt;span class="k"&gt;implements&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategy&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;amount&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// DiscountStrategyFactory.ts&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategyFactory&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;customer&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Customer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategy&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;customer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;isMember&lt;/span&gt;
      &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;MemberDiscountStrategy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
      &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;NoDiscountStrategy&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// OrderPricingService.ts&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;OrderPricingService&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;constructor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;private&lt;/span&gt; &lt;span class="n"&gt;factory&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;DiscountStrategyFactory&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nf"&gt;price&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Order&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;factory&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;customer&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Five files. Every one of them is "clean". Each class has one job, each name is honest, each piece is testable alone.&lt;/p&gt;

&lt;p&gt;And here's the same thing:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;priceOf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Order&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;discount&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;customer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;isMember&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="mf"&gt;0.9&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;amount&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;discount&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three lines. You read it once and you know everything.&lt;/p&gt;

&lt;p&gt;"But what if we add more discount types?" Then you'll change it, on the day you add them, knowing what they actually look like. Which is almost never what you imagined a year before.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cost nobody measures
&lt;/h2&gt;

&lt;p&gt;Count the files and you still miss the real price. The real price is paid in your head.&lt;/p&gt;

&lt;p&gt;To read the three-line version, you hold one thing in mind. To read the five-file version, you hold five: the interface, the two strategies, the factory, the service, and how they connect. None of them is hard. But you have to keep all of them loaded at once to answer one question: what does a member pay?&lt;/p&gt;

&lt;p&gt;That's cognitive load, and to me it's the main problem with this kind of code. Working memory is small. Every jump spends some of it on the structure instead of on the problem. By the sixth jump, you've forgotten why you opened the first file.&lt;/p&gt;

&lt;p&gt;No linter reports it. No coverage tool measures it. It shows up elsewhere: in onboarding that takes months, in estimates that double, in the bug nobody wants to pick up.&lt;/p&gt;

&lt;h3&gt;
  
  
  "AI will handle it"
&lt;/h3&gt;

&lt;p&gt;I hear this more and more. The model writes the twelve files in seconds, and it can walk you through them too. So who cares about the indirection?&lt;/p&gt;

&lt;p&gt;I do. Typing was never the bottleneck. Understanding is. AI makes structure cheap to produce, which makes it cheap to produce more structure than anyone can hold in their head.&lt;/p&gt;

&lt;p&gt;This part is personal opinion: the day you lose your grip on your own code, you lose the core of the job. My test is simple. When someone tells me "it's broken here", I want to know right away which file to open, where to put the breakpoint, what to test. If I need a tool to explain my own codebase before I can start debugging, it isn't really my code anymore.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we do it
&lt;/h2&gt;

&lt;p&gt;I've been that developer. I think most of us have, right after we discovered design patterns.&lt;/p&gt;

&lt;p&gt;The first reason is that rules are easier than judgment. "Functions should be short" can be checked by a linter. "This code should be easy to change" can't. So we optimize what we can measure, and a codebase can score perfectly on every rule and still be miserable to work in.&lt;/p&gt;

&lt;p&gt;The second is fear. An abstraction "just in case" feels like insurance. It isn't. Insurance pays when the accident happens. A speculative abstraction costs you every day, and when the real requirement arrives, it's usually the wrong shape, and now you have to undo it first.&lt;/p&gt;

&lt;p&gt;The third is harder to admit. Elegant code is satisfying to write. That's not a crime. But the reader doesn't get the pleasure. They only get the indirection.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I tell the difference now
&lt;/h2&gt;

&lt;p&gt;Clean code isn't the code that ticks the most rules. It's the code the next developer understands quickly and changes without fear.&lt;/p&gt;

&lt;p&gt;So I've replaced the rules with four questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;How many files do I open to change one behavior?&lt;/strong&gt; If the answer is more than two or three for a small change, the structure is working against me.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Can I point to the second use?&lt;/strong&gt; An interface with one implementation is a question, not an answer. I want to see the second caller before I build for it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Could a newcomer follow it in one sitting?&lt;/strong&gt; If understanding a click takes six jumps, the code isn't clean. It's hidden.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;When it breaks, do I know which file to open?&lt;/strong&gt; If a bug report doesn't point me somewhere within seconds, I've lost the map of my own code.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;And a habit that follows from them: sometimes I defend the ugly function. Thirty lines, top to bottom, a few &lt;code&gt;if&lt;/code&gt;s, readable at a glance. In review, someone suggests splitting it into five. I ask what we gain, and who it's for.&lt;/p&gt;

&lt;p&gt;Sometimes the answer is good, and we split it. Often there isn't one.&lt;/p&gt;

&lt;p&gt;What finally got that codebase simplified wasn't a refactoring plan. A new developer joined, spent two weeks on a one-line fix, and asked in a retro why saving a form needed six classes. Nobody in the room had a good answer. So we started inlining, one flow at a time, each time we had to touch one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm not saying
&lt;/h2&gt;

&lt;p&gt;I'm not saying patterns are bad, or that a 400-line function is fine. I wrote a whole article about &lt;a href="https://dev.to/ibrahimdans/the-principles-i-code-by-small-rules-big-difference-5d6a"&gt;the principles I code by&lt;/a&gt;, and I stand by them. KISS and YAGNI are on that list for a reason: they're the two principles that protect you from the others.&lt;/p&gt;

&lt;p&gt;The goal was never beauty. It's maintainability. Most of the time they agree. When they don't, I know which one I'm paid for.&lt;/p&gt;

&lt;p&gt;Have you ever worked in code that was too clean to maintain? What did it look like, and what finally got it simplified? And does AI change the answer for you?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and modernizing legacy code. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=clean-code-twelve-files" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>cleancode</category>
      <category>programming</category>
      <category>architecture</category>
    </item>
    <item>
      <title>"But We Had MFA": A Coffee, a Phishing Story, and Why I'd Bet on Passkeys</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Thu, 12 Nov 2026 15:47:24 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/but-we-had-mfa-a-coffee-a-phishing-story-and-why-id-bet-on-passkeys-5519</link>
      <guid>https://dev.to/ibrahimdans/but-we-had-mfa-a-coffee-a-phishing-story-and-why-id-bet-on-passkeys-5519</guid>
      <description>&lt;p&gt;Every other Friday, I have coffee with a friend who works in IT at a mid-sized company. Usually we talk about football, side projects, and which framework will be dead next year.&lt;/p&gt;

&lt;p&gt;Last time, my friend sat down, didn't even touch the cup, and said:&lt;/p&gt;

&lt;p&gt;"We got phished. And we had MFA."&lt;/p&gt;

&lt;p&gt;Then, after a pause: "I don't get it. We did everything right."&lt;/p&gt;

&lt;p&gt;That conversation lasted two hours and three coffees. I ended up drawing on a napkin. On the way home I thought: if a smart IT person is this confused, a lot of people must be. So here's the napkin, cleaned up.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;p&gt;Someone in their accounting team got an email: "A shared invoice is waiting, sign in to view it." The link opened a page that looked &lt;em&gt;exactly&lt;/em&gt; like their Microsoft login. Same logo, same font, same little loading dots.&lt;/p&gt;

&lt;p&gt;She typed her password. Then she received an SMS code, a real one, from her real company, and typed that too.&lt;/p&gt;

&lt;p&gt;Twenty seconds later, the attacker was in her mailbox. They set up a rule forwarding every invoice to a Gmail address. That's how IT noticed, two days later.&lt;/p&gt;

&lt;p&gt;"She didn't do anything stupid," my friend kept saying. And that's the point. She didn't.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft085gmv7s5a6ei5fsxrr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft085gmv7s5a6ei5fsxrr.png" alt="Real login page next to an identical mirror page, only the domain differs" width="800" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Napkin #1: the page wasn't fake, it was a mirror
&lt;/h2&gt;

&lt;p&gt;The first thing I drew was this:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F667zkt0xzm2nehjk84ds.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F667zkt0xzm2nehjk84ds.png" alt="AiTM phishing: the mirror page relays password and SMS code to the real login, then steals the session cookie" width="800" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is called &lt;strong&gt;AiTM phishing&lt;/strong&gt; (Adversary-in-the-Middle). The fake page doesn't just store your password. It sits between you and the real login page and forwards everything, live. The real server sees a perfectly valid login: right password, right code. And it hands the session cookie over to the attacker.&lt;/p&gt;

&lt;p&gt;"So our MFA was useless?" my friend asked.&lt;/p&gt;

&lt;p&gt;Not useless. It blocks the attacker who bought a list of leaked passwords. It doesn't block someone relaying your login in real time. Those kits are sold as a service now, with a monthly subscription and customer support. You don't need to be a genius to run one.&lt;/p&gt;

&lt;p&gt;The rule I wrote under the drawing: &lt;strong&gt;anything a human can type, a human can type in the wrong place.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Napkin #2: "Should we switch from SAML to OIDC?"
&lt;/h2&gt;

&lt;p&gt;That was the next question. Their security consultant had mentioned OIDC was "more modern", someone else wanted to replace SMS with an authenticator app, and it was all getting mixed up.&lt;/p&gt;

&lt;p&gt;So I drew a nightclub. 🎟️&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;bouncer&lt;/strong&gt; checks your ID at the door. That's &lt;strong&gt;authentication&lt;/strong&gt;: are you really you? Password, &lt;strong&gt;OTP&lt;/strong&gt;, fingerprint... these are the ways the bouncer checks.&lt;/li&gt;
&lt;li&gt;Once you're in, you get a &lt;strong&gt;wristband&lt;/strong&gt;. Every bar inside trusts it, nobody checks your ID again. That's &lt;strong&gt;federation&lt;/strong&gt;. &lt;strong&gt;SAML&lt;/strong&gt; and &lt;strong&gt;OIDC&lt;/strong&gt; are two kinds of wristband.&lt;/li&gt;
&lt;li&gt;The front desk that checks IDs and hands out wristbands is the &lt;strong&gt;IdP&lt;/strong&gt; (Identity Provider).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbteo19vjkhlshwqog92o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbteo19vjkhlshwqog92o.png" alt="Nightclub metaphor: bouncer for authentication, front desk for the IdP, wristband for SAML and OIDC" width="800" height="378"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;"So SAML versus OTP is a nonsense question," my friend said. Exactly. One is the wristband, the other is the ID check. You need both, and switching wristbands doesn't fix a bouncer who can be fooled.&lt;/p&gt;

&lt;h3&gt;
  
  
  SAML, the old wristband (2005)
&lt;/h3&gt;

&lt;p&gt;XML. The IdP sends your app a signed document: "this is Alice, finance group, valid for 5 minutes." It usually travels through the browser as an auto-submitted form.&lt;/p&gt;

&lt;p&gt;It's everywhere in big companies and it works. But verifying XML signatures correctly is hard. In 2024 and 2025, &lt;code&gt;ruby-saml&lt;/code&gt; (behind GitLab's SAML login, among others) had critical bugs where two XML parsers read the same document differently, letting an attacker log in as anyone.&lt;/p&gt;

&lt;p&gt;My advice: SAML is fine, as long as you &lt;strong&gt;never&lt;/strong&gt; write your own parser.&lt;/p&gt;

&lt;h3&gt;
  
  
  OIDC, the new wristband (2014)
&lt;/h3&gt;

&lt;p&gt;Built on OAuth 2.0. JSON and JWT instead of XML. It's what's behind "Sign in with Google", and it's much nicer for SPAs, mobile apps and APIs.&lt;/p&gt;

&lt;p&gt;For anything new: &lt;strong&gt;Authorization Code flow + PKCE&lt;/strong&gt;. If a tutorial tells you to use the "implicit flow" and grab the token from the URL, close the tab. It's deprecated, and OAuth 2.1 drops it.&lt;/p&gt;

&lt;h3&gt;
  
  
  OTP, one way of checking IDs
&lt;/h3&gt;

&lt;p&gt;Authenticator apps (TOTP), HOTP, SMS, email codes. It's a factor, not a protocol. It made stolen passwords far less useful, and I won't bash it.&lt;/p&gt;

&lt;p&gt;But as my friend's accountant learned: &lt;strong&gt;an OTP is a second password that expires quickly.&lt;/strong&gt; Quick enough to beat a leaked database. Not quick enough to beat a live relay.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;SAML 2.0&lt;/th&gt;
&lt;th&gt;OIDC&lt;/th&gt;
&lt;th&gt;OTP&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Nightclub version&lt;/td&gt;
&lt;td&gt;Old wristband&lt;/td&gt;
&lt;td&gt;New wristband&lt;/td&gt;
&lt;td&gt;One way to check your ID&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What it is&lt;/td&gt;
&lt;td&gt;Federation protocol&lt;/td&gt;
&lt;td&gt;Federation protocol&lt;/td&gt;
&lt;td&gt;Authentication factor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Format&lt;/td&gt;
&lt;td&gt;Signed XML&lt;/td&gt;
&lt;td&gt;JSON / JWT&lt;/td&gt;
&lt;td&gt;6-digit code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Good for&lt;/td&gt;
&lt;td&gt;Enterprise SSO, legacy apps&lt;/td&gt;
&lt;td&gt;Web, SPA, mobile, APIs&lt;/td&gt;
&lt;td&gt;Second factor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Classic trap&lt;/td&gt;
&lt;td&gt;Signature validation bugs&lt;/td&gt;
&lt;td&gt;Wildcard redirects, tokens in localStorage&lt;/td&gt;
&lt;td&gt;Phishing, SIM swap&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Napkin #3: "We have logins everywhere"
&lt;/h2&gt;

&lt;p&gt;Then my friend admitted the other problem. After the incident, they listed every internal app with a login. There were way more than they expected. Some used the company SSO, some had their own users table, and changing a rule meant touching each one.&lt;/p&gt;

&lt;p&gt;That's where an IdP like &lt;strong&gt;Keycloak&lt;/strong&gt; makes sense. It's open source, it speaks SAML &lt;em&gt;and&lt;/em&gt; OIDC, so old apps keep SAML and new ones use OIDC, on the same SSO session. It plugs into an existing Active Directory, so nobody recreates their account. And when an account is compromised, you disable it once and every session dies, everywhere.&lt;/p&gt;

&lt;p&gt;To try it in five minutes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker run -p 8080:8080 \
  -e &lt;span class="nv"&gt;KC_BOOTSTRAP_ADMIN_USERNAME&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;admin \
  -e &lt;span class="nv"&gt;KC_BOOTSTRAP_ADMIN_PASSWORD&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;admin \
  quay.io/keycloak/keycloak:latest start-dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(Pin a real version in production. &lt;code&gt;latest&lt;/code&gt; in prod is how you get surprised on a Friday.)&lt;/p&gt;

&lt;p&gt;I told my friend: the first thing I'd check in any setup is the redirect URIs. If you see this, fix it today:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"redirectUris"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"*"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A wildcard means anyone can ask the IdP to send the authorization code to &lt;em&gt;their&lt;/em&gt; site. Here's what a SPA client should look like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"clientId"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"my-spa"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"publicClient"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"standardFlowEnabled"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"implicitFlowEnabled"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"directAccessGrantsEnabled"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"redirectUris"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"https://app.example.com/callback"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"webOrigins"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"https://app.example.com"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"attributes"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"pkce.code.challenge.method"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"S256"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No implicit flow. No password grant (your app should never see the user's password). Exact redirect URIs. PKCE required. That's 80% of the job.&lt;/p&gt;

&lt;h2&gt;
  
  
  Napkin #4: the one my friend didn't believe
&lt;/h2&gt;

&lt;p&gt;"Fine," my friend said, "but even with Keycloak, the mirror page can still relay a password and a code."&lt;/p&gt;

&lt;p&gt;True. Centralizing doesn't fix that. So I said the word: &lt;strong&gt;passkeys&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The look I got was the same look I get from everyone: "No password at all? That sounds like &lt;em&gt;less&lt;/em&gt; security."&lt;/p&gt;

&lt;p&gt;I get it. It sounds like removing the lock. It's actually replacing it with one that can't be picked.&lt;/p&gt;

&lt;p&gt;In plain words: when you register a passkey, your phone or laptop creates two keys. The private one &lt;strong&gt;never leaves your device&lt;/strong&gt;. The server only keeps the public one. When you log in, the server sends a challenge, your device signs it after you touch the fingerprint sensor or look at the camera, and the server checks the signature.&lt;/p&gt;

&lt;p&gt;And here's what would have saved the accountant: &lt;strong&gt;a passkey is tied to the real domain.&lt;/strong&gt; On &lt;code&gt;login-micros0ft-secure.com&lt;/code&gt;, the browser simply won't offer it. No code to type, nothing to relay. The mirror page gets nothing.&lt;/p&gt;

&lt;p&gt;Bonus: if the database leaks, the attacker gets a pile of public keys. Useless.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faee131e4bdsuhf8fbiey.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faee131e4bdsuhf8fbiey.png" alt="Passkey prompt on the real domain vs no passkeys available on the mirror domain" width="799" height="465"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Keycloak supports it natively. Roughly (menu names move a bit between versions):&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Authentication → Policies → WebAuthn Passwordless Policy&lt;/strong&gt;: set &lt;em&gt;User Verification Requirement&lt;/em&gt; to &lt;code&gt;required&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Duplicate the &lt;code&gt;browser&lt;/code&gt; flow and add the &lt;strong&gt;WebAuthn Passwordless&lt;/strong&gt; authenticator.&lt;/li&gt;
&lt;li&gt;Enable the &lt;strong&gt;Webauthn Register Passwordless&lt;/strong&gt; required action, so people enroll at their next login.&lt;/li&gt;
&lt;li&gt;Bind the new flow to the realm.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;My advice: start with the team that got hit. Offer passkeys next to the password first, then make them mandatory for the sensitive roles.&lt;/p&gt;

&lt;h2&gt;
  
  
  The text I got three weeks later
&lt;/h2&gt;

&lt;p&gt;My friend texted me a screenshot of their Keycloak config, then: "Finance is on passkeys. The guy who complained the most now asks why the other tools don't do it."&lt;/p&gt;

&lt;p&gt;Then, a week after: "Our CTO dropped his phone in a lake. Only passkey. Locked out. 🙃"&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6s9xm0c8yld6ay7sz234.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6s9xm0c8yld6ay7sz234.png" alt="Text messages from my friend: finance is on passkeys, then the CTO lost his phone" width="800" height="592"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That's the last thing I want you to take from this post. Once you go passwordless, attackers move to &lt;strong&gt;"I lost my device."&lt;/strong&gt; If your recovery process is "call support and give your date of birth", you've just moved the front door to the helpdesk. And attackers are very good on the phone, now with AI-cloned voices too.&lt;/p&gt;

&lt;p&gt;What I suggested:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;everyone registers &lt;strong&gt;at least two passkeys&lt;/strong&gt; (phone + laptop, or a hardware key in a drawer),&lt;/li&gt;
&lt;li&gt;recovery is as strict as login: identity check, a delay, a notification to the user,&lt;/li&gt;
&lt;li&gt;the helpdesk has one rule: &lt;strong&gt;never reset a factor based on a phone call alone.&lt;/strong&gt; Even if it sounds like the CEO. &lt;em&gt;Especially&lt;/em&gt; if it sounds like the CEO.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The CTO got back in. He now has a YubiKey on his keychain, and apparently mentions it in every meeting.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd want you to remember
&lt;/h2&gt;

&lt;p&gt;SAML and OIDC pass your identity between apps. OTP is one way to check it. An IdP like Keycloak puts it all in one place you can actually control.&lt;/p&gt;

&lt;p&gt;But the attacks that hurt today don't crack anything. They impersonate. And against impersonation, the only factors that hold are the ones with nothing to type into the wrong page.&lt;/p&gt;

&lt;p&gt;My friend's company had MFA. They still got phished. If you're still sending SMS codes to your users, no judgment, most of us are. But maybe put "try passkeys" in your next sprint before you need a coffee like that one.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Details changed to keep my friend's company anonymous. Did you roll out passkeys? Did someone on your team also drop their phone in a lake? Tell me in the comments.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>keycloak</category>
      <category>webdev</category>
      <category>authentication</category>
    </item>
    <item>
      <title>I Run Coding Agents in Parallel. A Markdown File Is Their Manager.</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Tue, 10 Nov 2026 08:36:01 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/i-run-coding-agents-in-parallel-a-markdown-file-is-their-manager-2jjg</link>
      <guid>https://dev.to/ibrahimdans/i-run-coding-agents-in-parallel-a-markdown-file-is-their-manager-2jjg</guid>
      <description>&lt;p&gt;On October 11, I opened GitHub and counted four pull requests. I was expecting two.&lt;/p&gt;

&lt;h1&gt;
  
  
  453 and #456 fixed the same thing. So did #454 and #452. Different branches, different code, same task. Two of my coding agents had each done the work perfectly, in two separate sessions, without knowing the other one existed.
&lt;/h1&gt;

&lt;p&gt;Nobody had made a mistake. That's what bothered me.&lt;/p&gt;

&lt;p&gt;Agent A had picked the tasks and started coding. Agent B, in another terminal, had looked at the list, seen two tasks nobody had claimed, and done the reasonable thing. If two human developers did this, you'd say "they should talk to each other". Agents don't talk to each other. They don't even remember yesterday.&lt;/p&gt;

&lt;p&gt;So I did what you do with a team that doesn't communicate: I gave them a manager. It's a Markdown file.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flotdvsnnbwj882tp4nz4.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flotdvsnnbwj882tp4nz4.gif" alt="Two agents, one task list: with no mark, both pick the same task. With the IN PROGRESS mark, the second one moves on." width="800" height="382"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  An employee with amnesia
&lt;/h2&gt;

&lt;p&gt;Picture a brilliant developer who joins your team every morning with no memory of the day before. Doesn't know what was decided. Doesn't know what was tried and abandoned. Doesn't know who's working on what.&lt;/p&gt;

&lt;p&gt;That's a coding agent. With one of them, you compensate: you explain again. With four in parallel, each in its own git worktree, you become a full-time switchboard operator, and the agents still step on each other.&lt;/p&gt;

&lt;p&gt;I build &lt;a href="https://github.com/IBRAHIMDANS/i18nSupportPlus" rel="noopener noreferrer"&gt;i18n Support Plus&lt;/a&gt;, an open source JetBrains plugin, this way. As I write this, the repository is past pull request #950, and more than 500 task entries have gone through two files at its root:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;TODO.md&lt;/code&gt;: what's left to do&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;TODO-DONE.md&lt;/code&gt;: what's finished&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No ticketing tool. Nothing to install. Nothing tied to one agent: anything that can read a file can join the team.&lt;/p&gt;

&lt;p&gt;It works because of five rules. I didn't design them. I collected them, one accident at a time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rule 1: write the task for someone who knows nothing
&lt;/h2&gt;

&lt;p&gt;Here's a real one, archived on November 8 (translated from French, shortened):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;#### [TASK-CADRAGE-CONFIG-KEYSTROKE-REBUILD] Every letter typed in an open
&lt;/span&gt;     &lt;span class="sb"&gt;`i18n-check.json`&lt;/span&gt; setting rebuilds the whole usage index

&lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="gs"&gt;**Added:**&lt;/span&gt; 2026-11-08
&lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="gs"&gt;**Exclusive scope:**&lt;/span&gt;
  &lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="sb"&gt;`.../settings/Settings.kt`&lt;/span&gt;
  &lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="sb"&gt;`.../usages/CodeUsageIndexService.kt`&lt;/span&gt;
  &lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="sb"&gt;`.../usages/CodeUsageIndexServiceTest.kt`&lt;/span&gt;
  &lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="sb"&gt;`CHANGELOG.md`&lt;/span&gt;
&lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="gs"&gt;**Context:**&lt;/span&gt; measured by #926. Typing &lt;span class="sb"&gt;`node_modules`&lt;/span&gt; in the excluded
  directories field triggers twelve full rebuilds, about 18 s each on
  300 files, with the CPU spinning.
&lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="gs"&gt;**Expected:**&lt;/span&gt; unsaved content is only read after a typing pause;
  a rebuild in progress is cancelled when the state changes again.
&lt;span class="k"&gt;- &lt;/span&gt;&lt;span class="gs"&gt;**Expected tests:**&lt;/span&gt; a burst of ten keystrokes = one rebuild.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Look at the title: it's the defect, in one sentence. Look at the context: a measurement, not an impression. An agent can pick this up cold and never ask me a question.&lt;/p&gt;

&lt;p&gt;It's also, I realized later, just a well-written ticket. Agents didn't need anything exotic. They needed what my human colleagues had been asking for all along.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rule 2: one task, one territory
&lt;/h2&gt;

&lt;p&gt;This is the rule that makes everything else possible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Two tasks of the same priority never touch the same files.&lt;/strong&gt; That's the "exclusive scope" line above. If two file lists overlap, one task moves to another priority level.&lt;/p&gt;

&lt;p&gt;Once that's true, parallel work stops being a coordination problem. I say "work through priority 2", the agents leave in a wave, each on its own files, and there is nothing to arbitrate because there is nothing to collide on.&lt;/p&gt;

&lt;p&gt;The parallelism isn't decided when the agents start. It's decided when the tasks are written.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rule 3: say "mine" before you touch anything
&lt;/h2&gt;

&lt;p&gt;An agent that takes a task writes &lt;code&gt;IN PROGRESS&lt;/code&gt; in front of its title. The others skip it.&lt;/p&gt;

&lt;p&gt;You already know how I learned that the timing matters. The mark is worthless if it goes on after the first line of code. It has to be the very first thing the agent does, the way you say "I'll take it" in a meeting before opening your laptop.&lt;/p&gt;

&lt;p&gt;Since October 11, there's a second check before any wave: look at the open branches and pull requests. Trust, but verify.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rule 4: finished means gone
&lt;/h2&gt;

&lt;p&gt;The natural reflex is to leave a completed task in the file with a nice green check mark. It feels good. Look at all that progress.&lt;/p&gt;

&lt;p&gt;Now look at what that feeling costs. Every agent reads &lt;code&gt;TODO.md&lt;/code&gt; at the start of every session. Every finished task still sitting there gets reread, by every agent, every time, forever. You end up spending tokens so that machines can admire your check marks.&lt;/p&gt;

&lt;p&gt;Now a finished task leaves. Its whole section moves to the end of &lt;code&gt;TODO-DONE.md&lt;/code&gt;, and it keeps one line in a table at the top of &lt;code&gt;TODO.md&lt;/code&gt;: what changed, which PR, what date. The archive is append-only. Agents write at the end of it and never read it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftk1u9s7nifstx0082685.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftk1u9s7nifstx0082685.png" alt="TODO.md stays at 24 KB while the archive grows to 1.28 MB" width="800" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Today &lt;code&gt;TODO.md&lt;/code&gt; weighs 24 KB. The archive weighs 1.28 MB. Every session starts by reading 52 times less than the project's real history, and nothing was thrown away.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rule 5: you see a bug, you write it down, you walk away
&lt;/h2&gt;

&lt;p&gt;Agents are helpful to a fault. Ask one to fix a typo, and if it notices a questionable function on the way, it will "also fix" it. That's how a ten-line task becomes a four-hundred-line pull request that conflicts with three others.&lt;/p&gt;

&lt;p&gt;So the rule is the one you'd give an eager intern. An out-of-scope problem doesn't get fixed. It gets an entry in a "to be framed" section: what you saw, which files, a possible approach, a rough cost. Then you go back to your task.&lt;/p&gt;

&lt;p&gt;I decide what happens next. Anything marked "awaiting decision" stays untouched. That section has turned into a bug tracker of its own, with one advantage: every entry comes from someone who was looking at the code when they wrote it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The days it failed anyway
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The day my own rule blocked me.&lt;/strong&gt; At one point, 10 tasks out of 13 needed to touch &lt;code&gt;plugin.xml&lt;/code&gt; or the label files. Strict exclusive scopes spread them over 10 priority levels. One task at a time: I had built a very sophisticated queue. But two tasks that each &lt;em&gt;add a line&lt;/em&gt; to the same file only create a trivial conflict. So on October 6 the rule got an exception, written at the top of the file: those files can be shared, as long as every task only adds lines.&lt;/p&gt;

&lt;p&gt;A rule that's too strict fails as surely as no rule. It just fails slowly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The day the agents fought over the machine.&lt;/strong&gt; Scopes protect files. They don't protect the computer. Two worktrees share one Gradle cache, so their builds collide. And one agent's &lt;code&gt;./gradlew --stop&lt;/code&gt; kills the other agent's daemon in the middle of its tests.&lt;/p&gt;

&lt;p&gt;The second agent then sees a failure that looks exactly like a regression, while its code is fine. And an agent that believes it broke something will try to fix it. Now test runs are serialized, or each agent gets its own &lt;code&gt;GRADLE_USER_HOME&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The day of the four pull requests.&lt;/strong&gt; You were there.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I can and can't tell you
&lt;/h2&gt;

&lt;p&gt;What I can tell you: more than 500 task entries, 24 KB to read at startup against 1.28 MB of history, waves of agents that don't need me to referee.&lt;/p&gt;

&lt;p&gt;What I can't tell you: how much faster this is than no file at all. I never ran the comparison. These numbers describe how the project runs. They don't prove a gain, and I'd be suspicious of anyone who gave you one.&lt;/p&gt;

&lt;p&gt;Here's what I believe after all this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An agent's memory should live in the repository, not in its session.&lt;/li&gt;
&lt;li&gt;Parallel work is prepared when the tasks are written. The number of agents matters less than the shape of the backlog.&lt;/li&gt;
&lt;li&gt;What gets read at every startup must stay small. Keep everything else, but out of sight.&lt;/li&gt;
&lt;li&gt;Most of what makes agents effective is what makes a team effective. We just never had to write it down this precisely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One question before you go. If two of your agents started right now, on the same repo, with the same instruction, what would stop them from doing the same task twice?&lt;/p&gt;

&lt;p&gt;If the answer is "me", you're the manager. Consider delegating to a text file.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This article was first published as a case study on &lt;a href="https://ibrahimadansoko.fr/en/case-studies/todo-agents-ia?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=todo-agents" rel="noopener noreferrer"&gt;my site&lt;/a&gt;, where I write about frontend architecture and coding agents in practice.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>opensource</category>
      <category>workflow</category>
    </item>
    <item>
      <title>I gave Claude Code 10 translation tools. One run in three, it ignored them.</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Fri, 06 Nov 2026 16:34:01 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/i-gave-claude-code-10-translation-tools-one-run-in-three-it-ignored-them-44gm</link>
      <guid>https://dev.to/ibrahimdans/i-gave-claude-code-10-translation-tools-one-run-in-three-it-ignored-them-44gm</guid>
      <description>&lt;p&gt;I asked Claude Code to translate the same 92 missing strings nine times. Three times it had only the JSON files. Six times it also had ten tools I wrote for exactly this job.&lt;/p&gt;

&lt;p&gt;I expected the first group to break my files. It broke nothing. And in the second group, two sessions out of six never called a single one of my tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I ran this
&lt;/h2&gt;

&lt;p&gt;I maintain a JetBrains plugin for translation keys. It exposes ten tools to AI agents through the IDE's MCP server: list the missing translations, write them, check the files, rename a key, and so on.&lt;/p&gt;

&lt;p&gt;My assumption was simple. An agent that edits locale files by hand will rewrite values it should leave alone and lose a &lt;code&gt;{{name}}&lt;/code&gt; on the way. The tools exist to prevent that. I had never measured it, so I did.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;A small React app with i18next, five namespaces, 54 keys in English.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Locale&lt;/th&gt;
&lt;th&gt;Keys present&lt;/th&gt;
&lt;th&gt;Keys missing&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;en&lt;/code&gt; (reference)&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;fr&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;44&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;es&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;26&lt;/td&gt;
&lt;td&gt;28&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;it&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That makes 92 values to write and 70 existing values that must not move. The missing ones include &lt;code&gt;{{name}}&lt;/code&gt; placeholders, &lt;code&gt;_one&lt;/code&gt; / &lt;code&gt;_other&lt;/code&gt; plural pairs, &lt;code&gt;&amp;lt;b&amp;gt;&lt;/code&gt; tags and a line break.&lt;/p&gt;

&lt;p&gt;The prompt is the same every time, and it never mentions a tool:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;This React app uses i18next; its translation files are in public/locales.
Translate the keys missing in fr, es and it from the English reference.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each run is a fresh headless session on a fresh copy of the project:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude -p &lt;span class="s2"&gt;"$PROMPT"&lt;/span&gt; \
  --model sonnet \
  --setting-sources project \
  --strict-mcp-config \
  --permission-mode acceptEdits \
  --settings &lt;span class="s1"&gt;'{"sandbox":{"enabled":true,"autoAllowBashIfSandboxed":true}}'&lt;/span&gt; \
  --allowedTools Read Edit Write Glob Grep \
  --no-session-persistence \
  --output-format stream-json --verbose
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is Claude Code 2.1.319 with Sonnet 5.5. &lt;code&gt;--setting-sources project&lt;/code&gt; keeps my personal settings out of the session. The runs with tools add &lt;code&gt;--mcp-config&lt;/code&gt; with the IDE's server, and the ten tool names to the allowed list.&lt;/p&gt;

&lt;p&gt;After each run, a script compares every file with the starting point: values written, existing values changed, placeholders and tags against the English text. Time, cost and turns come from the session's own report.&lt;/p&gt;

&lt;h2&gt;
  
  
  Without the tools: it just worked
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Written&lt;/th&gt;
&lt;th&gt;Placeholders or tags lost&lt;/th&gt;
&lt;th&gt;Existing values changed&lt;/th&gt;
&lt;th&gt;Time&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;th&gt;Turns&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;57 s&lt;/td&gt;
&lt;td&gt;$0.20&lt;/td&gt;
&lt;td&gt;33&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;57 s&lt;/td&gt;
&lt;td&gt;$0.19&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;85 s&lt;/td&gt;
&lt;td&gt;$0.27&lt;/td&gt;
&lt;td&gt;30&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Every placeholder survived. Every tag survived. The plurals came in pairs. My assumption was wrong.&lt;/p&gt;

&lt;p&gt;The agent read the files, then wrote again, in full, the eleven that needed a change. In one run it generated them with a Python script instead.&lt;/p&gt;

&lt;p&gt;The one changed value is in run 1. The French file had &lt;code&gt;login.title&lt;/code&gt; set to &lt;code&gt;"Login"&lt;/code&gt;. The agent replaced it, and said so in its summary:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Existing fr value changed:&lt;/strong&gt; &lt;code&gt;fr/auth.json&lt;/code&gt; had &lt;code&gt;login.title&lt;/code&gt; set to &lt;code&gt;"Login"&lt;/code&gt;, which was left in English. I changed it to &lt;code&gt;"Se connecter"&lt;/code&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It is probably right about the French. But I asked for the missing keys. In a real project, "Login" may be the word the product team chose, and one modified line in a diff of 205 added lines is easy to miss.&lt;/p&gt;

&lt;h2&gt;
  
  
  With the tools: less than half the time
&lt;/h2&gt;

&lt;p&gt;In four of the six sessions that had the MCP server, the agent used the tools.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Written&lt;/th&gt;
&lt;th&gt;Placeholders or tags lost&lt;/th&gt;
&lt;th&gt;Existing values changed&lt;/th&gt;
&lt;th&gt;Time&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;th&gt;Turns&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;25 s&lt;/td&gt;
&lt;td&gt;$0.14&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;22 s&lt;/td&gt;
&lt;td&gt;$0.13&lt;/td&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;25 s&lt;/td&gt;
&lt;td&gt;$0.13&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;92 / 92&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;35 s&lt;/td&gt;
&lt;td&gt;$0.15&lt;/td&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;On average that is 27 seconds against 66, and $0.14 against $0.22.&lt;/p&gt;

&lt;p&gt;The reason is easy to see in the transcript. The agent never opens a JSON file. It asks for the list of what is missing, once per locale:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"module"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"project"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"sourceLocale"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"en"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"locale"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"fr"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"total"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"items"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"dashboard:welcome"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Welcome back, {{name}}!"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"pluralFromOther"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"key"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"pagination.page"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"source"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Page {{current}} of {{total}}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"pluralFromOther"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(I kept two of the ten items.) Then it sends the translations back, once per locale, and the plugin writes them. That is about 4,000 output tokens instead of about 10,000.&lt;/p&gt;

&lt;p&gt;The write tool is also stricter than a file edit. I called it by hand to see what it refuses:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"written"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"rejected"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"auth:login.title"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Already filled and not stale: only a stale value is replaced"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"written"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"rejected"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"dashboard:welcome"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Placeholders differ from the source: Welcome back, {{name}}!"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The first line is the "Login" rewrite from above. Through the tool, it cannot happen. The second is a French value I sent without its &lt;code&gt;{{name}}&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two sessions out of six ignored the tools
&lt;/h2&gt;

&lt;p&gt;In runs 3 and 4 the server was connected and the ten tools were in the session's tool list. The agent wrote the files itself anyway.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Run&lt;/th&gt;
&lt;th&gt;Tools called&lt;/th&gt;
&lt;th&gt;Existing values changed&lt;/th&gt;
&lt;th&gt;Time&lt;/th&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;70 s&lt;/td&gt;
&lt;td&gt;$0.23&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;67 s&lt;/td&gt;
&lt;td&gt;$0.24&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Both made the same "Login" rewrite, once as "Se connecter" and once as "Connexion".&lt;/p&gt;

&lt;p&gt;As far as I can tell, this comes from how Claude Code handles MCP tools. It does not load their definitions up front. The four sessions that used my tools each ran a tool search that fetches them by name. The two other sessions never searched.&lt;/p&gt;

&lt;h2&gt;
  
  
  One line fixed it
&lt;/h2&gt;

&lt;p&gt;I added a &lt;code&gt;CLAUDE.md&lt;/code&gt; with a single line to the project:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;For translation files (public/locales), use the i18n_* MCP tools instead of editing the JSON files.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three more runs, same prompt. All three used the tools: 26 to 30 seconds, $0.13 each, nothing existing touched. Three runs prove little, but it went from four out of six to three out of three.&lt;/p&gt;

&lt;h2&gt;
  
  
  What 119 tools cost
&lt;/h2&gt;

&lt;p&gt;The JetBrains MCP server in my IDE exposes 119 tools: database, debugger, terminal, git and the rest. Their definitions weigh about 236,000 characters. My ten tools are 9,146 of them.&lt;/p&gt;

&lt;p&gt;I expected that to eat the context window. It does not. The first turn of a session holds 20,556 tokens without the server and 22,879 with it. That is 2,323 tokens for 119 tools.&lt;/p&gt;

&lt;p&gt;It is the same mechanism as the section above. The tools are cheap because they are loaded on demand, and they get ignored because they are loaded on demand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the agent alone did better
&lt;/h2&gt;

&lt;p&gt;Two things, and both are on my list now.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Terminology.&lt;/strong&gt; The existing French file keeps the word "trustee" in English. The existing Spanish file says "Panel" for &lt;em&gt;Dashboard&lt;/em&gt;. The agent that read the files reused both, in all three runs. Through the tools, the agent only sees the English text of what is missing. Over the seven sessions that used the tools, six translated "trustee" on their own, as "fiduciaires" or "personnes de confiance", and three wrote "Panel de control" where the file already said "Panel". Nothing was refused, because the placeholders were intact.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Key order.&lt;/strong&gt; In an empty file, the tools write the keys in alphabetical order: &lt;code&gt;errors&lt;/code&gt; before &lt;code&gt;login&lt;/code&gt;. The English file has &lt;code&gt;login&lt;/code&gt; first. The agent alone copied the order of the reference.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limits
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Twelve sessions, one model, a 54-key project. This is one afternoon of measurements, not a benchmark of Claude Code.&lt;/li&gt;
&lt;li&gt;In four of the five sessions that edited files, my sandbox refused two or three shell commands, which cost them a few turns. The one session without any refusal took 57 seconds and $0.20, so the gap remains.&lt;/li&gt;
&lt;li&gt;Small files help the agent alone. Reading and rewriting whole files grows with their size, while the tool returns only what is missing. I expect the gap to widen on a large project. I have not measured it.&lt;/li&gt;
&lt;li&gt;I did not grade the translations.&lt;/li&gt;
&lt;li&gt;The tools need a JetBrains IDE open on the project.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The plugin is &lt;a href="https://plugins.jetbrains.com/plugin/30971-i18n-support-plus" rel="noopener noreferrer"&gt;I18n Support Plus&lt;/a&gt;, free and open source (MIT), for JetBrains IDEs. The tools need version 2025.2.6 or later.&lt;/p&gt;

&lt;p&gt;1- In the IDE: &lt;strong&gt;Settings › Tools › MCP Server&lt;/strong&gt;, check &lt;strong&gt;Enable MCP Server&lt;/strong&gt;.&lt;br&gt;
2- Connect Claude Code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;   claude mcp add --transport http jetbrains http://127.0.0.1:64342/stream
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;3- Add the line above to your &lt;code&gt;CLAUDE.md&lt;/code&gt;, then ask for the missing translations.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://github.com/IBRAHIMDANS/i18nSupportPlus/blob/main/docs/translation.md" rel="noopener noreferrer"&gt;documentation&lt;/a&gt; covers Codex, Cursor and the other clients. The code is on &lt;a href="https://github.com/IBRAHIMDANS/i18nSupportPlus" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Update, November 7: I tested the fixes from the comments
&lt;/h2&gt;

&lt;p&gt;A commenter pointed out that tool definitions are loaded on demand, so the agent chooses from the tool names and reads a description only after it has decided to look. Two fixes followed from that: put "use this instead of editing the files" in the tool descriptions, and expose fewer tools. I shipped the first one (&lt;a href="https://github.com/IBRAHIMDANS/i18nSupportPlus/pull/870" rel="noopener noreferrer"&gt;PR #870&lt;/a&gt;) and reran the same prompt.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Setup&lt;/th&gt;
&lt;th&gt;Sessions that wrote through the tools&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;10 tools, new descriptions, no CLAUDE.md line&lt;/td&gt;
&lt;td&gt;0 of 6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Only the 2 translation tools exposed&lt;/td&gt;
&lt;td&gt;0 of 3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Control, with the CLAUDE.md line&lt;/td&gt;
&lt;td&gt;3 of 3 (22 to 24 s, $0.12 to $0.13)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In this setup the descriptions did nothing, and fewer tools did nothing either. Two sessions called &lt;code&gt;i18n_missing_translations&lt;/code&gt; after writing the files themselves, to check their work. The project-level line is still the only thing that worked. Small sample, one model, and a different IDE build from the first run, so don't compare these numbers with the 4 of 6 above.&lt;/p&gt;

&lt;p&gt;Another commenter suggested loading the tools up front instead of on demand. I haven't tested it yet.&lt;/p&gt;

&lt;p&gt;And since version 1.20.0 (November 9), &lt;code&gt;i18n_missing_translations&lt;/code&gt; returns the project glossary and the existing translations that share a word with the keys to translate, which targets the terminology drift described in "Where the agent alone did better".&lt;/p&gt;

&lt;p&gt;One question to finish. If you have MCP servers connected to your agent, have you ever counted how often it calls them? Run the same prompt three times and count. I would like to see your ratio.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build tools that cut the daily friction of front-end work. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=mcp-translation-tools" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>mcp</category>
      <category>claude</category>
      <category>i18n</category>
    </item>
    <item>
      <title>Your build passes, but the button says checkout.pay_nwo</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Thu, 05 Nov 2026 06:58:27 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/finding-missing-and-unused-i18next-keys-in-a-react-project-4k0a</link>
      <guid>https://dev.to/ibrahimdans/finding-missing-and-unused-i18next-keys-in-a-react-project-4k0a</guid>
      <description>&lt;p&gt;&lt;em&gt;A translation key is a string nobody checks. Here is how to check it by hand, in the IDE and in CI.&lt;/em&gt;&lt;br&gt;
Look at this line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;button&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;t&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'checkout.pay_nwo'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="n"&gt;button&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The build passes and so do the tests. In production, the button reads &lt;code&gt;checkout.pay_nwo&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;My own start with translation keys was a migration. An existing application was going international, so every text in the code had to move into JSON files, in French, English, Spanish and Italian. Carrying all of that over by hand was the hardest part of the job. It also left me with four files that had to stay in step with the code, and nothing to check that they did.&lt;/p&gt;

&lt;p&gt;Day to day, the cost is smaller but constant. To know whether a key exists, in which namespace and what it says, you open &lt;code&gt;en/common.json&lt;/code&gt;, hit Ctrl+F, scroll and come back. Multiply that by 200 keys and 5 locales.&lt;/p&gt;

&lt;p&gt;A translation key is a plain string that points to a line in a JSON file, and by default nothing verifies that the line exists. i18next's typed keys catch this particular typo, if you have set them up. They do not tell you that the German file lacks the key, or that half of your French file is no longer used by any component.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four ways a key goes wrong
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The code calls a key that no file holds.&lt;/strong&gt; A typo, or a key deleted during a cleanup. The user sees the raw key.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A key exists in English and not in French.&lt;/strong&gt; i18next falls back to English without a word, so nobody notices until a French customer does.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A file holds a key that no code calls.&lt;/strong&gt; It does no harm on screen, but translators keep translating it and the files keep growing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A placeholder changes in translation.&lt;/strong&gt; &lt;code&gt;Hello {{name}}&lt;/code&gt; becomes &lt;code&gt;Bonjour {{nom}}&lt;/code&gt;, and the French page greets the user with &lt;code&gt;{{nom}}&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of these fails a build.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking by hand
&lt;/h2&gt;

&lt;p&gt;The second case is the easiest to script. With &lt;code&gt;jq&lt;/code&gt;, list every key path of two files and compare them:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;diff &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;jq -r &lt;span class="s1"&gt;'paths(scalars) | join(".")'&lt;/span&gt; locales/en/common.json &lt;span class="o"&gt;|&lt;/span&gt; sort&lt;span class="o"&gt;)&lt;/span&gt; \
     &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;jq -r &lt;span class="s1"&gt;'paths(scalars) | join(".")'&lt;/span&gt; locales/fr/common.json &lt;span class="o"&gt;|&lt;/span&gt; sort&lt;span class="o"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each line of the output is a key one locale has and the other lacks.&lt;/p&gt;

&lt;p&gt;This works for one pair of files. Then the limits show:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You need one run per namespace and per locale.&lt;/li&gt;
&lt;li&gt;Unused keys need the opposite search, each key looked up in the code. A &lt;code&gt;grep&lt;/code&gt; for &lt;code&gt;user.name&lt;/code&gt; misses &lt;code&gt;t('common:user.name')&lt;/code&gt; written under &lt;code&gt;useTranslation('common')&lt;/code&gt;, and it cannot know that &lt;code&gt;t(`status.${kind}`)&lt;/code&gt; uses every key under &lt;code&gt;status&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;It runs when someone remembers to run it, which is after the bug.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the script is fine for an audit before a release. For daily work I wanted the editor to tell me.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking in the editor
&lt;/h2&gt;

&lt;p&gt;During that migration I used I18n Support, a plugin by Evgeniy Nyavro. That plugin was no longer maintained. Built for older versions of the IDE, it was buggy and kept crashing IntelliJ. When the job was over, I made myself a promise: with some free time, I would fork it and just update the dependencies.&lt;/p&gt;

&lt;p&gt;"Just" did not last. One feature followed another 😅, and the fork became &lt;a href="https://plugins.jetbrains.com/plugin/30971-i18n-support-plus" rel="noopener noreferrer"&gt;I18n Support Plus&lt;/a&gt;, an open-source (MIT) plugin for WebStorm, IntelliJ IDEA Ultimate and PhpStorm. I maintain it, and the rest of this article uses it, so read it with that in mind.&lt;/p&gt;

&lt;p&gt;With the plugin installed, a key gets an icon in the gutter: green when every locale holds it, yellow when some lack it, red when none does. Its value follows it as an inline hint, which saves opening the JSON file to remember what &lt;code&gt;checkout.pay_now&lt;/code&gt; says. Ctrl+hover gives the value in every locale, with a dash where one is missing, and Ctrl+click opens the translation file on the right line. For a whole file, &lt;em&gt;Show Translations Inline&lt;/em&gt; replaces each key by its value, and the JSX reads like the real UI.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ful7xz5sdc9tgjqxgk1gt.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ful7xz5sdc9tgjqxgk1gt.gif" alt="Ctrl+clicking a key opens its value in the translation file" width="799" height="452"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A red key is the typo from the top of this article, or a key that was never created. Either way, Alt+Enter and &lt;em&gt;Create missing key&lt;/em&gt; write the value in every locale without leaving the component.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgw8t4s999h6wqar4p9sa.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgw8t4s999h6wqar4p9sa.gif" alt="Creating an unknown key with its values" width="599" height="359"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The typo itself gets rarer, because completion after &lt;code&gt;t('&lt;/code&gt; lists the keys that exist, namespaces included, each with its value.&lt;/p&gt;

&lt;p&gt;For the key that French lacks, the tool window has a table with one column per locale and a filter that keeps the keys missing or empty somewhere. &lt;em&gt;Sync Keys&lt;/em&gt; then creates the absent ones in each locale, for every namespace at once, which is where the &lt;code&gt;jq&lt;/code&gt; one-liner stopped.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk7zitipmc1eooduhkqdj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk7zitipmc1eooduhkqdj.png" alt="The table view, one column per locale" width="800" height="181"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Unused keys are the hardest to find by hand. &lt;em&gt;Count Key Usages&lt;/em&gt; counts the code usages of every key, namespace included, and the ones at zero are the candidates for deletion. When a key needs a better name, Shift+F6 renames it in every locale and at every call site, like any other symbol.&lt;/p&gt;

&lt;p&gt;Then there is the task I started with, moving hard-coded text into the files. Alt+Enter turns a text into a key and writes the value in every locale, and &lt;em&gt;Internationalize…&lt;/em&gt; does the same for a whole file or folder, after a preview:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F09mtiromqwkcufuz50q4.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F09mtiromqwkcufuz50q4.gif" alt="Extracting a JSX text into a key, its value written in every locale" width="720" height="431"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Checking in CI
&lt;/h2&gt;

&lt;p&gt;An editor check helps the person who has the plugin. The pull request of a colleague who does not have it needs a second net. The same checks run without an IDE, as a GitHub Action:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;translations&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@v4&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;IBRAHIMDANS/i18nSupportPlus@v1.18.0&lt;/span&gt;
        &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;--code&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The job fails on a key missing from a locale, on a placeholder lost in a translation (the fourth case) and on a key the code calls that no file holds. With &lt;code&gt;--code&lt;/code&gt; it also reports the unused keys. It annotates the pull request, so the author sees the problem on the line that caused it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does not do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Keys built at runtime.&lt;/strong&gt; &lt;code&gt;t(`status.${kind}`)&lt;/code&gt; is read as &lt;code&gt;status.*&lt;/code&gt;: the keys under &lt;code&gt;status&lt;/code&gt; are not reported as unused, but the plugin cannot know which value &lt;code&gt;kind&lt;/code&gt; takes. A key that comes from a function parameter or a computed value is not followed at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;VS Code.&lt;/strong&gt; The plugin is for JetBrains IDEs, 2025.2 or later. On VS Code, i18n Ally covers the same ground.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Translating for you by default.&lt;/strong&gt; Machine translation exists (a local Ollama, DeepL, Google and others) but stays off until you turn it on, and nothing is written before a preview.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The plugin is free. Install it from the &lt;a href="https://plugins.jetbrains.com/plugin/30971-i18n-support-plus" rel="noopener noreferrer"&gt;JetBrains Marketplace&lt;/a&gt;, or search for &lt;em&gt;I18n Support Plus&lt;/em&gt; in &lt;strong&gt;Settings › Plugins&lt;/strong&gt;. A setup wizard detects the framework and the translation files on first launch. The examples here are i18next, but the plugin also reads vue-i18n, next-intl, Lingui, react-intl, Angular, Laravel and Symfony projects.&lt;/p&gt;

&lt;p&gt;The code, the documentation and a sample project for each framework are on &lt;a href="https://github.com/IBRAHIMDANS/i18nSupportPlus" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;. Issues and feature requests are welcome there, and a star helps if the plugin saves you time.&lt;/p&gt;

&lt;p&gt;One question to finish: how many times a day do you open a JSON file just to check whether a key exists? If the answer is not "never", I would like to hear how you deal with it.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build tools that cut the daily friction of front-end work. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=i18n-missing-keys" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>react</category>
      <category>webdev</category>
      <category>i18n</category>
    </item>
    <item>
      <title>Claude Wake Up ⏰: Start your Claude session at 5 AM (without getting up yourself)</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Thu, 16 Jul 2026 07:15:29 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/claude-wake-up-start-your-claude-session-at-5-am-without-getting-up-yourself-4ecn</link>
      <guid>https://dev.to/ibrahimdans/claude-wake-up-start-your-claude-session-at-5-am-without-getting-up-yourself-4ecn</guid>
      <description>&lt;p&gt;&lt;strong&gt;"usage limit reached." Mid-flow, at the worst possible moment. What if that line never landed when you need it most?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The thread running through this article fits in one sentence: &lt;strong&gt;your 5-hour window starts at your first prompt, so &lt;em&gt;you&lt;/em&gt; decide when your Claude day begins.&lt;/strong&gt; All that's left is to make that choice while you sleep.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: the 5-hour wall
&lt;/h2&gt;

&lt;p&gt;If you use Claude (and especially Claude Code) heavily, you know the moment: mid-refactor, mid-feature... &lt;strong&gt;"usage limit reached."&lt;/strong&gt; Blocked. Come back in a few hours.&lt;/p&gt;

&lt;p&gt;Why? Claude runs on a &lt;strong&gt;rolling 5-hour window&lt;/strong&gt;. And the detail that changes everything: that window doesn't start at midnight, or at any fixed time. &lt;strong&gt;It starts the exact moment you send your first prompt.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;First prompt at 9 AM → reset at 2 PM&lt;/li&gt;
&lt;li&gt;First prompt at 2 PM → reset at 7 PM&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the root cause of the waste isn't your quota, it's &lt;strong&gt;when you open the first window&lt;/strong&gt;, left to the chance of when you happen to sit down at your desk. And that's where it gets interesting: that moment is yours to choose.&lt;/p&gt;

&lt;h2&gt;
  
  
  The math: why 5 AM?
&lt;/h2&gt;

&lt;p&gt;Do the count. If your first session starts at &lt;strong&gt;5 AM&lt;/strong&gt;, here's your day:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Session&lt;/th&gt;
&lt;th&gt;Window&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;05:00 → 10:00&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;10:00 → 15:00&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;15:00 → 20:00&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;20:00 → 01:00&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;strong&gt;Four full sessions&lt;/strong&gt; that line up perfectly with a workday (and an evening of side projects 😏).&lt;/p&gt;

&lt;p&gt;Compare that with someone who fires their first prompt at 9:30 when they get to the office: their second window doesn't open until 2:30 PM, the third at 7:30 PM... They only really use two or three. By simply shifting the starting point, you reclaim a whole window per day: no plan change, no extra cost.&lt;/p&gt;

&lt;p&gt;The catch, obviously: &lt;strong&gt;nobody wants to get up at 5 AM to say hello to an AI.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The "hey Claude" trap (and the trap inside the trap)
&lt;/h2&gt;

&lt;p&gt;Most people's first instinct: open an interactive session and type a quick &lt;code&gt;"hello"&lt;/code&gt; or &lt;code&gt;"hey Claude"&lt;/code&gt; to kick off the window.&lt;/p&gt;

&lt;p&gt;It works, but it's wasteful. An interactive session loads a whole context (system prompt, CLAUDE.md, repo state...), and Claude generates a warm reply nobody will read. Tokens burned for nothing.&lt;/p&gt;

&lt;p&gt;Second instinct, smarter on the surface: &lt;em&gt;"what if I just use &lt;code&gt;/usage&lt;/code&gt;? That costs nothing!"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;That's exactly the trap: &lt;strong&gt;&lt;code&gt;/usage&lt;/code&gt; probably doesn't start the window.&lt;/strong&gt; It's a read-only lookup command: it shows your consumption and the next reset time, but it sends no prompt to the model. And the 5-hour window starts at your first &lt;em&gt;request to the model&lt;/em&gt;. No tokens spent = no session opened. This is consistent with the fact that everyone automating this strategy uses a real prompt, not &lt;code&gt;/usage&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  The actual trick: a real prompt, but minimal
&lt;/h3&gt;

&lt;p&gt;The principle is simple: you need a &lt;strong&gt;real request to the model&lt;/strong&gt;, but the smallest one possible. A one-word prompt, no useless context, ideally on the cheapest model (Haiku). Cost: a handful of tokens, negligible, including against your weekly quota. But the 5-hour window opens.&lt;/p&gt;

&lt;p&gt;The next section shows how to send this micro-prompt automatically, machine on or off.&lt;/p&gt;

&lt;p&gt;And what about &lt;code&gt;/usage&lt;/code&gt;? Keep it for its real job: &lt;strong&gt;verifying&lt;/strong&gt;. Open Claude Code after the automatic wake-up, type &lt;code&gt;/usage&lt;/code&gt;, and you'll see your "Current session" bar active with the reset time. That's your proof the wake-up worked.&lt;/p&gt;

&lt;p&gt;💡 &lt;em&gt;Want to check for yourself that &lt;code&gt;/usage&lt;/code&gt; isn't enough? Wait for your window to expire, run only &lt;code&gt;/usage&lt;/code&gt;, then look at claude.ai/settings/usage: no session timer starts.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The automation: Claude wakes up, not you
&lt;/h2&gt;

&lt;p&gt;The whole point of the strategy is that it runs &lt;strong&gt;in the background&lt;/strong&gt;. You sleep. Two methods, from simplest to most hands-on.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 1 (recommended): &lt;code&gt;/schedule&lt;/code&gt;, Claude Code's native routines
&lt;/h3&gt;

&lt;p&gt;This is the cleanest method, and it makes almost everything else obsolete. Claude Code has built-in &lt;strong&gt;routines&lt;/strong&gt;: automations you configure once, then run on Claude Code's cloud infrastructure. Translation: &lt;strong&gt;your machine can be off&lt;/strong&gt;, the routine runs anyway. No cron, no Raspberry Pi, no VPS.&lt;/p&gt;

&lt;p&gt;In a Claude Code session, just type:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/schedule a daily routine at 5:00 AM that just replies "ok" and does nothing else
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;(You can also create and manage your routines from claude.ai/code.)&lt;/p&gt;

&lt;p&gt;Why it's perfect for our case:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Available from the Pro plan&lt;/strong&gt; (as well as Max, Team, and Enterprise), with Claude Code on the web enabled.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Routines draw on the subscription's usage limits exactly like an interactive session.&lt;/strong&gt; That's the key point: the routine taps the same pool as your sessions → it does open your 5-hour window.&lt;/li&gt;
&lt;li&gt;Real cost: a minimal routine = a few tokens. Negligible.&lt;/li&gt;
&lt;li&gt;Limit to know: routines have a daily quota (5 per day on Pro, 15 on Max). For one wake-up a day, we're well within it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;⚠️ &lt;strong&gt;The winter-time trap&lt;/strong&gt;: routines are scheduled in &lt;strong&gt;UTC cron&lt;/strong&gt;, not your timezone. If you're in Paris, "5 AM" translates to &lt;code&gt;0 3 * * *&lt;/code&gt; in summer (CEST = UTC+2)... but that same cron will fire at &lt;strong&gt;4 AM&lt;/strong&gt; the moment daylight saving ends (CET = UTC+1). The shift is silent: nothing breaks, your window just opens an hour too early and your last session ends at midnight instead of 1 AM. Two options: accept the drift, or move the cron to &lt;code&gt;0 4 * * *&lt;/code&gt; in late October (and back in late March). Conversely, local cron (Method 2), launchd, and Task Scheduler follow your machine's local time and therefore &lt;em&gt;don't&lt;/em&gt; have this problem: it's specific to UTC-based schedulers (routines, GitHub Actions cron).&lt;/p&gt;

&lt;p&gt;💡 Side note: the scheduler adds a few minutes of random jitter. Your "5 AM" routine will land closer to 5:05–5:10. Irrelevant for the strategy.&lt;/p&gt;

&lt;p&gt;One command, once, and it's set for every morning.&lt;/p&gt;

&lt;h3&gt;
  
  
  Method 2 (alternative): cron / launchd / Task Scheduler
&lt;/h3&gt;

&lt;p&gt;If &lt;code&gt;/schedule&lt;/code&gt; isn't available in your environment (Claude Code web disabled, company policy...), you can schedule a minimal prompt in headless mode from your own machine.&lt;/p&gt;

&lt;p&gt;⚠️ &lt;strong&gt;Important warning&lt;/strong&gt;: Anthropic recently changed how non-interactive usage is billed. Since mid-June 2026, &lt;code&gt;claude -p&lt;/code&gt;, Agent SDK, and GitHub Actions calls are reportedly counted against a &lt;strong&gt;separate monthly credit&lt;/strong&gt; from your subscription (no longer the shared session pool). Possible consequence: a &lt;code&gt;claude -p&lt;/code&gt; in cron might no longer open the 5-hour window for your interactive sessions. Test at home before relying on it (see the &lt;code&gt;/usage&lt;/code&gt; check above). And if it stops working, Method 1 remains the safe bet.&lt;/p&gt;

&lt;h4&gt;
  
  
  Linux / macOS: cron
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;crontab -e
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Claude Wake Up: every day at 5:00 AM&lt;/span&gt;
0 5 * * * /usr/local/bin/claude --model haiku -p &lt;span class="s2"&gt;"ok"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;gt;&lt;/span&gt; ~/claude-wakeup.log 2&lt;span class="o"&gt;&amp;gt;&amp;amp;&lt;/span&gt;1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;💡 Check your binary's path with &lt;code&gt;which claude&lt;/code&gt;. The log lets you confirm at wake-up that everything ran fine.&lt;/p&gt;

&lt;h4&gt;
  
  
  macOS: launchd (more reliable than cron)
&lt;/h4&gt;

&lt;p&gt;The advantage of &lt;code&gt;launchd&lt;/code&gt;: if the Mac was asleep at 5 AM, the job runs when it wakes. Create &lt;code&gt;~/Library/LaunchAgents/com.claude.wakeup.plist&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="cp"&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;/span&gt;
&lt;span class="cp"&gt;&amp;lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
  "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;plist&lt;/span&gt; &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"1.0"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;Label&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;com.claude.wakeup&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;ProgramArguments&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;/usr/local/bin/claude&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;--model&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;haiku&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;-p&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;ok&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;StartCalendarInterval&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;Hour&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;integer&amp;gt;&lt;/span&gt;5&lt;span class="nt"&gt;&amp;lt;/integer&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;Minute&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;integer&amp;gt;&lt;/span&gt;0&lt;span class="nt"&gt;&amp;lt;/integer&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/plist&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;launchctl load ~/Library/LaunchAgents/com.claude.wakeup.plist
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Windows: Task Scheduler
&lt;/h4&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;schtasks&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;create&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;tn&lt;/span&gt; &lt;span class="s2"&gt;"ClaudeWakeUp"&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;tr&lt;/span&gt; &lt;span class="s2"&gt;"claude --model haiku -p ok"&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;sc&lt;/span&gt; &lt;span class="n"&gt;daily&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;st&lt;/span&gt; &lt;span class="mi"&gt;05&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;00&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Machine off overnight?
&lt;/h4&gt;

&lt;p&gt;With Method 1, the question is moot: routines run in the cloud. If you're set on home-grown cron, schedule the machine's wake in BIOS/UEFI (or &lt;code&gt;pmset repeat wakeorpoweron&lt;/code&gt; on Mac), or offload the job to an always-on machine: a Raspberry Pi, a small VPS (&lt;code&gt;claude setup-token&lt;/code&gt; to generate an OAuth token), or a scheduled GitHub Action (careful: GitHub's cron is UTC).&lt;/p&gt;

&lt;h2&gt;
  
  
  The limits of the trick (let's be honest)
&lt;/h2&gt;

&lt;p&gt;Two things to keep in mind:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;It doesn't create tokens.&lt;/strong&gt; There's also a weekly cap, shared across all your Claude usage. This strategy reshuffles your 5-hour windows so they fit your day; it doesn't raise your overall quota.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The window slides.&lt;/strong&gt; If you send nothing between 5 and 10 AM, your "real" activity at 10 simply opens the next window. The payoff is highest on days when you actually work from early morning and risk maxing out several windows in a day.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  In short
&lt;/h2&gt;

&lt;p&gt;One &lt;code&gt;/schedule&lt;/code&gt; command, zero dawn alarm, and your Claude day begins while you sleep:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The 5-hour window starts at your &lt;strong&gt;first prompt&lt;/strong&gt; → choose that moment strategically&lt;/li&gt;
&lt;li&gt;5 AM = &lt;strong&gt;4 aligned sessions&lt;/strong&gt; across your day (5, 10, 15, 20h)&lt;/li&gt;
&lt;li&gt;Neither an interactive "hello" nor &lt;code&gt;/usage&lt;/code&gt;: an &lt;strong&gt;automated micro-prompt&lt;/strong&gt; opens the session for a handful of tokens, and &lt;code&gt;/usage&lt;/code&gt; serves to confirm the wake-up worked&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/schedule&lt;/code&gt; (cloud routines, from the Pro plan) = it all happens &lt;strong&gt;in the background&lt;/strong&gt;, even with the machine off (cron/launchd as plan B)&lt;/li&gt;
&lt;li&gt;Watch out for &lt;strong&gt;UTC cron&lt;/strong&gt; (routines, GitHub Actions): remember to shift your expression at the time change, or your 5 AM wake-up drifts to 4 AM in winter&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the real question isn't &lt;em&gt;"how do I get more quota?"&lt;/em&gt;. It's:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;"What time do I actually want my Claude day to begin?"&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Answer that, schedule it once, and let the machine handle it. Claude, wake up. Me, I'm still asleep. 😴&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about the small automations that take friction out of a developer's day. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=claude-wake-up" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>claude</category>
      <category>ai</category>
      <category>productivity</category>
      <category>automation</category>
    </item>
    <item>
      <title>Build a multi-platform Design System, step by step</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Mon, 08 Jun 2026 09:11:30 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/ets-build-a-multi-platform-design-system-step-by-step-poc-4a7d</link>
      <guid>https://dev.to/ibrahimdans/ets-build-a-multi-platform-design-system-step-by-step-poc-4a7d</guid>
      <description>&lt;h2&gt;
  
  
  Let's build a multi-platform Design System, step by step
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Web, iOS, Android. One color definition. Changed once, propagated everywhere.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of a theory article, we're going to &lt;strong&gt;build a working POC&lt;/strong&gt;, step by step. By the end, you'll have a mini design system that generates CSS, Swift, and Kotlin from a single source, with two brands, light/dark themes, a demo, and regression tests. All the code is on &lt;a href="https://github.com/ibrahimdans/design-system-poc" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; — clone it and follow along.&lt;/p&gt;

&lt;p&gt;The guiding thread: &lt;strong&gt;a design decision should exist in only one place, in a neutral form; everything else is derived from it automatically.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem we're solving
&lt;/h2&gt;

&lt;p&gt;Your brand's primary color — a blue — lives in parallel in CSS variables (web), Swift (iOS), Kotlin (Android)… The problem isn't &lt;em&gt;creating&lt;/em&gt; those values, it's &lt;strong&gt;keeping them in sync over time&lt;/strong&gt;. One day someone changes the blue on web but not on Android, and the product becomes inconsistent. Multiply by 2 brands and 2 themes: the inconsistency becomes structural.&lt;/p&gt;

&lt;p&gt;The root cause: &lt;strong&gt;the same decision is copied by hand into different formats.&lt;/strong&gt; We're going to kill the copy.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 0 — The project
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mkdir design-system-poc &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nb"&gt;cd&lt;/span&gt; design-system-poc
npm init -y
npm install -D style-dictionary typescript @types/node
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://styledictionary.com/" rel="noopener noreferrer"&gt;Style Dictionary&lt;/a&gt; is the reference tool for turning "tokens → multiple targets". Add &lt;code&gt;"type": "module"&lt;/code&gt; to your &lt;code&gt;package.json&lt;/code&gt; (we write ESM) and a &lt;code&gt;tsconfig.json&lt;/code&gt; in &lt;code&gt;strict&lt;/code&gt; mode. We code in &lt;strong&gt;TypeScript&lt;/strong&gt;: Node 24 runs it natively (type stripping), so &lt;code&gt;node build.ts&lt;/code&gt; works with no compile step — &lt;code&gt;tsc --noEmit&lt;/code&gt; is only there for type-checking.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 1 — Primitives (the &lt;em&gt;ingredients&lt;/em&gt;)
&lt;/h2&gt;

&lt;p&gt;A &lt;strong&gt;design token&lt;/strong&gt; is a &lt;code&gt;name → value&lt;/code&gt; pair describing a design intent, independent of any language. We start with the raw palette, with no business meaning.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;tokens/primitives.json&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"color"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"blue"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"300"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#60A5FA"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
               &lt;span class="nl"&gt;"500"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#2563EB"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
               &lt;span class="nl"&gt;"700"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#1D4ED8"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"green"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"500"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#059669"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
               &lt;span class="nl"&gt;"700"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#047857"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"grey"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"0"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;   &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#FFFFFF"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
               &lt;span class="nl"&gt;"100"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#F3F4F6"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
               &lt;span class="nl"&gt;"900"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"#111827"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"space"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"2"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"8px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;  &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"spacing"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
              &lt;span class="nl"&gt;"4"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"16px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"spacing"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"radius"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"sm"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"4px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"borderRadius"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
              &lt;span class="nl"&gt;"md"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"8px"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"borderRadius"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These values "know" nothing about web or mobile. They're the &lt;strong&gt;neutral form&lt;/strong&gt; everything else will derive from.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 2 — Semantic tokens (the secret to multi-brand)
&lt;/h2&gt;

&lt;p&gt;The beginner trap: putting &lt;code&gt;#2563EB&lt;/code&gt; directly in components. Instead, we create a &lt;strong&gt;semantic level&lt;/strong&gt; that describes &lt;em&gt;usage&lt;/em&gt; and &lt;strong&gt;points to a primitive&lt;/strong&gt; (the &lt;code&gt;{color.blue.500}&lt;/code&gt; syntax is a Style Dictionary reference).&lt;/p&gt;

&lt;p&gt;&lt;code&gt;tokens/semantic.brandA.light.json&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"color"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"primary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.blue.500}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"primary-hover"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.blue.700}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"on-primary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.0}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;   &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.0}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;   &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"on-surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.900}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;strong&gt;dark&lt;/strong&gt; theme keeps the &lt;em&gt;same semantic names&lt;/em&gt;, but rewires to different primitives — &lt;code&gt;tokens/semantic.brandA.dark.json&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"color"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"primary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.blue.300}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.900}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"on-surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.100}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And a &lt;strong&gt;2nd brand&lt;/strong&gt; = just different wiring — &lt;code&gt;tokens/semantic.brandB.light.json&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"color"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"primary"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.green.500}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"primary-hover"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.green.700}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"surface"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"value"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"{color.grey.0}"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;    &lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"color"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Why this matters:&lt;/strong&gt; your components reference &lt;strong&gt;only&lt;/strong&gt; &lt;code&gt;color-primary&lt;/code&gt;, never &lt;code&gt;blue-500&lt;/code&gt;. Switching brand or theme = rewiring the semantic links, &lt;strong&gt;without touching a single line of any component&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 3 — Generate for each platform
&lt;/h2&gt;

&lt;p&gt;We give Style Dictionary the tokens + the target formats, and it generates the rest. The key point: &lt;strong&gt;ship idiomatic code per platform&lt;/strong&gt;, not raw JSON. An iOS dev wants typed Swift.&lt;/p&gt;

&lt;p&gt;We have 3 combinations (brand × theme) to generate, so we loop. &lt;code&gt;build.ts&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;StyleDictionary&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'style-dictionary'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nc"&gt;Config&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'style-dictionary/types'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;combinations&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;brand&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'brandA'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;theme&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'light'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;brand&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'brandA'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;theme&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'dark'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;brand&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'brandB'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;theme&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'light'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;platformsFor&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Config&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'platforms'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;css&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;transformGroup&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'css'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;buildPath&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'build/web/'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
         &lt;span class="n"&gt;files&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;destination&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${name}.css`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'css/variables'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;ios&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;transformGroup&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'ios-swift'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;buildPath&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'build/ios/'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
         &lt;span class="n"&gt;files&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;destination&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${name}.swift`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'ios-swift/class.swift'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                   &lt;span class="n"&gt;options&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;className&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Tokens'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;android&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;transformGroup&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'compose'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;buildPath&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'build/android/'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
             &lt;span class="n"&gt;files&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;destination&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${name}.kt`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'compose/object'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                       &lt;span class="n"&gt;options&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;className&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Tokens'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;packageName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'com.monorg.tokens'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;transformGroup&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'js'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;buildPath&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'build/json/'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
          &lt;span class="n"&gt;files&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;destination&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${name}.json`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'json/flat'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;brand&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;theme&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="n"&gt;combinations&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sb"&gt;`${brand}-${theme}`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;sd&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;StyleDictionary&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// Source = the common layer (primitives) + this combination's semantic links.&lt;/span&gt;
    &lt;span class="n"&gt;source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'tokens/primitives.json'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sb"&gt;`tokens/semantic.${brand}.${theme}.json`&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;platforms&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;platformsFor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;sd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;buildAllPlatforms&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;node build.ts
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And there's the same decision, translated into each language. &lt;strong&gt;Web&lt;/strong&gt; (&lt;code&gt;build/web/brandA-light.css&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;root&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nv"&gt;--color-primary&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#2563eb&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--color-on-primary&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#ffffff&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--color-surface&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#ffffff&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--color-on-surface&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mh"&gt;#111827&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--space-4&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;16px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nv"&gt;--radius-md&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;8px&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;iOS&lt;/strong&gt; (&lt;code&gt;build/ios/brandA-light.swift&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight swift"&gt;&lt;code&gt;&lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;Tokens&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;public&lt;/span&gt; &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;colorPrimary&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;UIColor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;red&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.145&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;green&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.388&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;blue&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.922&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;alpha&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="c1"&gt;// ...&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Android / Compose&lt;/strong&gt; (&lt;code&gt;build/android/brandB-light.kt&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight kotlin"&gt;&lt;code&gt;&lt;span class="k"&gt;package&lt;/span&gt; &lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;monorg&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;tokens&lt;/span&gt;
&lt;span class="k"&gt;object&lt;/span&gt; &lt;span class="nc"&gt;Tokens&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;val&lt;/span&gt; &lt;span class="n"&gt;colorPrimary&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Color&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mh"&gt;0xff059669&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;   &lt;span class="c1"&gt;// brandB → green&lt;/span&gt;
  &lt;span class="kd"&gt;val&lt;/span&gt; &lt;span class="n"&gt;colorPrimaryHover&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Color&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mh"&gt;0xff047857&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One source, three languages, &lt;strong&gt;idiomatic&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 4 — A component that consumes (and the magic of the switch)
&lt;/h2&gt;

&lt;p&gt;The component uses &lt;strong&gt;only&lt;/strong&gt; semantic tokens, no hard-coded colors. &lt;code&gt;demo/index.html&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"theme"&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"stylesheet"&lt;/span&gt; &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"../build/web/brandA-light.css"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;style&amp;gt;&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--color-primary&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;color&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--color-on-primary&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;padding&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--space-2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--space-4&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--radius-sm&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nc"&gt;.btn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="nt"&gt;hover&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;background&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nv"&gt;--color-primary-hover&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/style&amp;gt;&lt;/span&gt;

&lt;span class="nt"&gt;&amp;lt;button&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"btn"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Primary action&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;

&lt;span class="nt"&gt;&amp;lt;script&amp;gt;&lt;/span&gt;
  &lt;span class="c1"&gt;// The only switch: we swap the token stylesheet. The component does not change.&lt;/span&gt;
  &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getElementById&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'theme'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;href&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'../build/web/brandA-dark.css'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Change &lt;code&gt;brandA-light&lt;/code&gt; → &lt;code&gt;brandA-dark&lt;/code&gt; → &lt;code&gt;brandB-light&lt;/code&gt;: the button re-themes itself. &lt;strong&gt;Not a single line of the component moves.&lt;/strong&gt; That's the whole point of the semantic level.&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 5 — Test regressions (the indispensable safety net)
&lt;/h2&gt;

&lt;p&gt;In a system consumed everywhere, a silent regression spreads &lt;em&gt;everywhere&lt;/em&gt; at once. We add a net, with zero dependencies, using &lt;code&gt;node:test&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A deliberate choice: writing these tests in Gherkin&lt;/strong&gt; (&lt;code&gt;Feature&lt;/code&gt; / &lt;code&gt;Scenario&lt;/code&gt; / &lt;em&gt;Given / When / Then&lt;/em&gt;). Why? Because a design system is consumed as much by &lt;strong&gt;non-developers&lt;/strong&gt; (designers, PMs) as by devs. Phrased this way, the tests become &lt;strong&gt;documentation that reads like sentences&lt;/strong&gt;: "&lt;em&gt;Given&lt;/em&gt; brand A in dark, &lt;em&gt;when&lt;/em&gt; generated, &lt;em&gt;then&lt;/em&gt; primary points to blue 300". No need to read code to know what the system guarantees. &lt;code&gt;test/tokens.test.ts&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;it&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'node:test'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;assert&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'node:assert/strict'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;readFileSync&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'node:fs'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;read&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;combo&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Record&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
  &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;parse&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;readFileSync&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="no"&gt;URL&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`../build/json/${combo}.json`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;meta&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'utf8'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="nf"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Feature: semantic links resolve to the right primitives'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Scenario: the dark theme reuses the same semantic names'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nf"&gt;it&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Given brand A in dark, When generated, Then primary points to blue 300'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;tokens&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;read&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'brandA-dark'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="n"&gt;assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;equal&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tokens&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;ColorPrimary&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'#60a5fa'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="n"&gt;assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;equal&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tokens&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;ColorSurface&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'#111827'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="nf"&gt;describe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Scenario: switching brand is just re-wiring the links'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nf"&gt;it&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Given brand B in light, When generated, Then primary = green'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="n"&gt;assert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;equal&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;read&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'brandB-light'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;ColorPrimary&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'#059669'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;node build.ts &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; node --test &lt;span class="s2"&gt;"test/**/*.test.ts"&lt;/span&gt;
&lt;span class="c"&gt;# ✔ Feature: semantic links resolve to the right primitives&lt;/span&gt;
&lt;span class="c"&gt;#   ✔ Scenario: the dark theme reuses the same semantic names&lt;/span&gt;
&lt;span class="c"&gt;#   ✔ Scenario: switching brand is just re-wiring the links&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If someone breaks a primitive or a link, the test &lt;strong&gt;fails before&lt;/strong&gt; the regression reaches the products. The repo wires this into a &lt;strong&gt;GitHub Actions CI&lt;/strong&gt; that, on every push, builds all combinations, &lt;strong&gt;checks the multi-platform artifacts were actually generated&lt;/strong&gt;, and runs the tests — so a broken link never reaches &lt;code&gt;main&lt;/code&gt;. In production, you complement this with &lt;strong&gt;snapshot tests&lt;/strong&gt; on the generated files (any change to an output becomes explicit in review) and, on the component side, a &lt;strong&gt;Storybook&lt;/strong&gt; + &lt;strong&gt;automated visual review&lt;/strong&gt; (Chromatic-style).&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 6 — Assets (the real challenge: icons &amp;amp; fonts)
&lt;/h2&gt;

&lt;p&gt;Colors are the easy part. Where a design system earns its stripes is on &lt;strong&gt;assets&lt;/strong&gt;: an icon or a font must also start from a &lt;strong&gt;single source&lt;/strong&gt; and be translated into each platform's format.&lt;/p&gt;

&lt;p&gt;The most telling case: &lt;strong&gt;Android doesn't read SVG natively&lt;/strong&gt;, it needs a &lt;em&gt;Vector Drawable&lt;/em&gt; XML. So we write a small &lt;code&gt;SVG → Vector Drawable&lt;/code&gt; converter (excerpt):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;svgToVectorDrawable&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;svg&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;size&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;24&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;w&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;h&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;svg&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;match&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;viewBox&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"([\d.\s-]+)"&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;split&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;\&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="o"&gt;+/&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Number&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;paths&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;svg&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;matchAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;path&lt;/span&gt;\&lt;span class="n"&gt;b&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt;\&lt;span class="n"&gt;bd&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"([^"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="s2"&gt;"[^&amp;gt;]*&amp;gt;/gi)].map((m) =&amp;gt; {
    const fill = (m[0].match(/fill="&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&lt;/span&gt;&lt;span class="s2"&gt;"]+)"&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="s1"&gt;'currentColor'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;color&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;fill&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s1"&gt;'currentColor'&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="s1"&gt;'#FF000000'&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`#FF${fill.slice(1).toUpperCase()}`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sb"&gt;`    &amp;lt;path android:fillColor="${color}" android:pathData="${m[1]}" /&amp;gt;`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sb"&gt;`&amp;lt;vector xmlns:android="http://schemas.android.com/apk/res/android"
    android:width="${size}dp" android:height="${size}dp"
    android:viewportWidth="${w}" android:viewportHeight="${h}"&amp;gt;
${paths.join('\n')}
&amp;lt;/vector&amp;gt;`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;From a single &lt;code&gt;assets/icons/check.svg&lt;/code&gt;, the pipeline produces:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Web&lt;/strong&gt; → the SVG as-is + a JSON manifest;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;iOS&lt;/strong&gt; → a &lt;em&gt;type-safe&lt;/em&gt; &lt;code&gt;enum Icon&lt;/code&gt; (no more "magic strings") + the SVG;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Android&lt;/strong&gt; → &lt;code&gt;ic_check.xml&lt;/code&gt; (Vector Drawable) + an &lt;code&gt;enum Icon&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Same logic for the &lt;strong&gt;font&lt;/strong&gt;: one &lt;code&gt;Inter.ttf&lt;/code&gt; → &lt;code&gt;@font-face&lt;/code&gt; (web), &lt;code&gt;FontRegistrar.swift&lt;/code&gt; (iOS), &lt;code&gt;res/font/&lt;/code&gt; (Android). The full code is in the repo (&lt;code&gt;src/buildAssets.ts&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;&lt;em&gt;That's&lt;/em&gt; the difference between "a shared color file" and a real design system: &lt;strong&gt;the multi-platform asset chain.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Step 7 — Distribute it like a real product
&lt;/h2&gt;

&lt;p&gt;A design system only has value if it's &lt;strong&gt;easy to consume&lt;/strong&gt;. Never ask people to copy files: publish to native package managers, and &lt;strong&gt;version with SemVer&lt;/strong&gt; (with &lt;code&gt;alpha / beta / rc / stable&lt;/code&gt; channels).&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install @monorg/design-tokens@1.2.0      &lt;span class="c"&gt;# web&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight kotlin"&gt;&lt;code&gt;&lt;span class="nf"&gt;implementation&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"monorg:design-tokens:1.2.0"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;// android (Maven)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Automate it via CI: a &lt;strong&gt;version tag&lt;/strong&gt; triggers a pipeline that &lt;em&gt;builds&lt;/em&gt; all formats and &lt;em&gt;publishes&lt;/em&gt; each package to its registry (npm / SPM / Maven). No manual step = no drift between the repo and what's shipped.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="c1"&gt;# pseudo-pipeline
&lt;/span&gt;&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;tag 'tokens-v*'&lt;/span&gt;
&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;build&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;   &lt;span class="s"&gt;node build.ts&lt;/span&gt;
  &lt;span class="na"&gt;publish&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt; &lt;span class="s"&gt;npm&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;spm&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;maven&lt;/span&gt; &lt;span class="p"&gt;]&lt;/span&gt;   &lt;span class="c1"&gt;# one job per registry
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  The real win: each consumer pins ITS version
&lt;/h3&gt;

&lt;p&gt;This is the point people underestimate at first. Once tokens are published as versioned packages, &lt;strong&gt;each application picks the version it consumes&lt;/strong&gt; — and that's what makes the system usable at scale:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Total decoupling.&lt;/strong&gt; The design team can publish &lt;code&gt;1.3.0&lt;/code&gt; today without breaking anything: the iOS app stays on &lt;code&gt;1.2.0&lt;/code&gt; until it decides to bump. Nobody is forced to move at the same time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Progressive rollout.&lt;/strong&gt; You test a new palette on &lt;strong&gt;one&lt;/strong&gt; product (which goes to &lt;code&gt;1.3.0-alpha.1&lt;/code&gt;) while the others stay stable. If it breaks, the blast radius is &lt;em&gt;one&lt;/em&gt; repo, not all of them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reproducible builds.&lt;/strong&gt; A lockfile pinned to &lt;code&gt;1.2.0&lt;/code&gt; produces &lt;em&gt;exactly&lt;/em&gt; the same rendering in six months. A "shared folder" that changes under your feet does not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;History and rollback.&lt;/strong&gt; A visual regression in prod? Revert to the previous version in one line (&lt;code&gt;@1.1.0&lt;/code&gt;) while you fix it. No panicked hotfix across 6 codebases.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;design-tokens   v1.3.0  ← latest published
   ├── web app      "@monorg/design-tokens": "1.3.0"   (up to date)
   ├── iOS app      from: "1.2.0"                       (bumps when it wants)
   └── Android app  "monorg:design-tokens:1.2.0"         (same)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The design system becomes &lt;strong&gt;a dependency like any other&lt;/strong&gt;: you update it when you're ready, you read the CHANGELOG, you pin, you roll back. It's exactly this versioning mechanism that turns a "shared folder" into &lt;strong&gt;infrastructure&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;A design system is &lt;strong&gt;not a button library&lt;/strong&gt;. It's infrastructure, and its value is in the &lt;em&gt;chain&lt;/em&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A single source of truth&lt;/strong&gt;: the tokens, in neutral form.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Three levels&lt;/strong&gt;: primitives → semantic → component. That's what makes multi-brand manageable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A generation&lt;/strong&gt; to idiomatic code per platform (Style Dictionary).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A distribution&lt;/strong&gt; versioned with SemVer, via native package managers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tests&lt;/strong&gt; (Gherkin + snapshots + visual review) to change without fear — and that document the system, even for non-devs.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The full POC code is here → &lt;strong&gt;&lt;a href="https://github.com/ibrahimdans/design-system-poc" rel="noopener noreferrer"&gt;github.com/ibrahimdans/design-system-poc&lt;/a&gt;&lt;/strong&gt;. Clone it, &lt;code&gt;npm install&lt;/code&gt;, &lt;code&gt;npm run demo&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The real question isn't &lt;em&gt;"which components should go in my design system?"&lt;/em&gt;. It's:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;"Do my design decisions have a single source of truth, or are they copied by hand?"&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Start there.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Unifying several products or several platforms? I design design systems that scale. The full case study is on &lt;a href="https://ibrahimadansoko.fr/en/case-studies/design-system-cross-plateforme?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=design-system" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>styledictionary</category>
      <category>tutorial</category>
      <category>node</category>
      <category>programming</category>
    </item>
    <item>
      <title>The Principles I Code By: Small Rules, Big Difference</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Sat, 06 Jun 2026 16:09:32 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/the-principles-i-code-by-small-rules-big-difference-5d6a</link>
      <guid>https://dev.to/ibrahimdans/the-principles-i-code-by-small-rules-big-difference-5d6a</guid>
      <description>&lt;p&gt;&lt;strong&gt;Frameworks come and go. Principles stay.&lt;/strong&gt; ✨&lt;/p&gt;

&lt;p&gt;After a few years of writing software — from MVPs built from scratch 🚀 to legacy systems nobody dared to touch 👻 — I've come to realize something: the developers I admire most aren't the ones who know the most frameworks. They're the ones who follow a few simple principles, consistently, on every line they write.&lt;/p&gt;

&lt;p&gt;Over time, I've collected my own set of principles. They act like a compass 🧭: whenever I'm unsure how to approach a problem, I come back to them. None of them are mine — they've been shaped by people much smarter than me — but together they form the way I work. Let me walk you through each one, with examples from real life. 👇&lt;/p&gt;

&lt;h2&gt;
  
  
  ⚡ Make it work, make it right, make it fast
&lt;/h2&gt;

&lt;p&gt;This one, from &lt;strong&gt;Kent Beck&lt;/strong&gt;, is the backbone of everything else. It's an order of priorities, and the order matters:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;✅ &lt;strong&gt;Make it work&lt;/strong&gt; — first, get a working solution. Don't optimize, don't over-engineer. Just solve the problem.&lt;/li&gt;
&lt;li&gt;🧹 &lt;strong&gt;Make it right&lt;/strong&gt; — now refactor. Clean names, clear structure, tests. Make it readable for the next person (often your future self).&lt;/li&gt;
&lt;li&gt;🏎️ &lt;strong&gt;Make it fast&lt;/strong&gt; — only then, &lt;em&gt;if needed&lt;/em&gt;, optimize for performance.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; You need to display a list of users. The trap is to immediately think about caching, pagination, and database indexes. Don't. First, fetch the list and render it (&lt;em&gt;it works&lt;/em&gt;). Then extract a clean component and add a test (&lt;em&gt;it's right&lt;/em&gt;). Then, &lt;em&gt;only if the page is actually slow&lt;/em&gt;, add caching (&lt;em&gt;it's fast&lt;/em&gt;).&lt;/p&gt;

&lt;p&gt;Most performance problems we obsess over never materialize. Respect the order, and you'll move faster overall. 🎯&lt;/p&gt;

&lt;h2&gt;
  
  
  🔮 YAGNI — You Aren't Gonna Need It
&lt;/h2&gt;

&lt;p&gt;We love to build for a future that rarely comes. 🔭 &lt;em&gt;"We might need this option later"&lt;/em&gt;, &lt;em&gt;"let's make it configurable just in case"&lt;/em&gt;... and we end up maintaining code nobody uses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; You're asked to export data as CSV. You think: "I'll build a generic exporter that also supports JSON, XML, and PDF, so we're ready for anything." Six months later, only CSV is used — but you're still maintaining (and debugging 🐛) three formats nobody asked for.&lt;/p&gt;

&lt;p&gt;YAGNI is a reminder: &lt;strong&gt;build for the need you have today, not the one you imagine for tomorrow.&lt;/strong&gt; ⏳ When tomorrow actually arrives, you'll have better information to build the right thing.&lt;/p&gt;

&lt;h2&gt;
  
  
  🎲 The Principle of Least Surprise
&lt;/h2&gt;

&lt;p&gt;Code should behave the way the reader &lt;em&gt;expects&lt;/em&gt; it to. The best code is boring: when someone opens your file, nothing makes them go &lt;em&gt;"wait, what?"&lt;/em&gt; 😵 Surprise is where bugs hide.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; A function called &lt;code&gt;getUser()&lt;/code&gt; that &lt;em&gt;also&lt;/em&gt; silently updates the last-login timestamp in the database. The name promises a read; the body does a write. Six months later, someone calls it in a loop to display names — and accidentally hammers the database. The code wasn't complex. It was &lt;em&gt;surprising&lt;/em&gt;. A function should do what its name says, nothing more.&lt;/p&gt;

&lt;p&gt;Here's a subtle one — and it sets up the next principle nicely: &lt;em&gt;predictable&lt;/em&gt; often wins over &lt;em&gt;simple&lt;/em&gt;. Sometimes slightly more verbose, "boring" code that follows the conventions of your codebase beats a clever one-liner that makes the next reader stop and squint. Be the developer whose code holds no surprises. 🧘&lt;/p&gt;

&lt;h2&gt;
  
  
  ✂️ KISS — Keep It Simple
&lt;/h2&gt;

&lt;p&gt;The simplest solution that solves the problem is almost always the best one. Complexity is easy to add and very hard to remove. 🧨&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; I've seen a single function grow to 200 lines because it tried to handle every imaginable case with a pile of flags: &lt;code&gt;processData(data, true, false, true)&lt;/code&gt;. 😵‍💫 Nobody could read it. Split into three small, well-named functions, the same logic became obvious at a glance.&lt;/p&gt;

&lt;p&gt;Before writing a clever abstraction, ask yourself: &lt;em&gt;do I really need this, or am I just showing off?&lt;/em&gt; 🤔 Simple code is code your teammates can read, debug, and change without fear. That's worth more than cleverness — but remember the previous principle: if "simple" means "surprising," go for predictable instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  ♻️ DRY — Don't Repeat Yourself
&lt;/h2&gt;

&lt;p&gt;Every piece of knowledge should have a single source of truth in your codebase. When the same logic lives in three places, fixing a bug means remembering all three — and you never do.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; A password validation rule (8 characters, one uppercase, one digit) copy-pasted into the signup form, the reset form, and the back-end. The day the rule changes, you'll fix two of them and ship the bug in the third. 😬 Extract it once, use it everywhere.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;But be careful ⚠️&lt;/strong&gt; — don't apply DRY too early. Two pieces of code that &lt;em&gt;look&lt;/em&gt; similar today might evolve in different directions tomorrow. Forcing them into one abstraction creates a tangled mess. As the saying goes: &lt;em&gt;duplication is cheaper than the wrong abstraction.&lt;/em&gt; Wait until you see the pattern repeat a third time before extracting it.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧱 SOLID — Five Letters for Maintainable Code
&lt;/h2&gt;

&lt;p&gt;SOLID is a set of five principles for object-oriented design. People recite them like a spell, but each one solves a very concrete pain:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;S — Single Responsibility.&lt;/strong&gt; A class (or function) should have one reason to change. A &lt;code&gt;User&lt;/code&gt; class that handles authentication &lt;em&gt;and&lt;/em&gt; sends emails &lt;em&gt;and&lt;/em&gt; formats invoices will break in three different ways. Split responsibilities.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;O — Open/Closed.&lt;/strong&gt; Open for extension, closed for modification. Adding a new payment method shouldn't mean editing a giant &lt;code&gt;if/else&lt;/code&gt;. You should be able to &lt;em&gt;plug in&lt;/em&gt; the new case without touching the existing, tested code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;L — Liskov Substitution.&lt;/strong&gt; A subtype must work anywhere its parent is expected. If your &lt;code&gt;Square&lt;/code&gt; extends &lt;code&gt;Rectangle&lt;/code&gt; but breaks when you set width and height independently, your hierarchy is lying to you.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;I — Interface Segregation.&lt;/strong&gt; Many small, focused interfaces beat one giant one. Don't force a class to implement methods it doesn't need just because they live in the same interface.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;D — Dependency Inversion.&lt;/strong&gt; Depend on abstractions, not concrete details. Your business logic shouldn't know &lt;em&gt;which&lt;/em&gt; database you use. Pass it an interface, and you can swap the implementation (or mock it in tests) freely.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You don't need to recite them. You need to feel them: code that's &lt;strong&gt;easy to extend and hard to break.&lt;/strong&gt; 💪&lt;/p&gt;

&lt;h2&gt;
  
  
  👣 Baby Steps — Small, Validated Increments
&lt;/h2&gt;

&lt;p&gt;Big changes are scary because they fail in big, mysterious ways. Small changes fail small, and they tell you exactly what went wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; Instead of writing 300 lines and running everything at the end (then spending an hour figuring out which part broke), I write a few lines, run the tests, commit, and repeat. When something fails, I know it's in the last tiny change — not somewhere in 300 lines. And because I commit often, &lt;code&gt;git bisect&lt;/code&gt; becomes a superpower. 🦸&lt;/p&gt;

&lt;p&gt;Progress made of tiny, reversible steps is faster than it looks — and far less stressful. 😌&lt;/p&gt;

&lt;h2&gt;
  
  
  🌳 The Mikado Method — Taming the Big Refactor
&lt;/h2&gt;

&lt;p&gt;Sometimes a change looks simple, then you pull the thread and the whole sweater unravels. 🧶 The &lt;strong&gt;Mikado Method&lt;/strong&gt; is how I handle that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An example 💡.&lt;/strong&gt; You want to upgrade a library. You change it — and 12 files break. The naive approach is to fix them all at once and pray. 😅 The Mikado approach: try the change, &lt;em&gt;see&lt;/em&gt; what breaks, write down the prerequisites, then &lt;strong&gt;revert&lt;/strong&gt;. Now tackle one prerequisite at a time, each as its own small, safe commit. Once the groundwork is done, the original change becomes trivial.&lt;/p&gt;

&lt;p&gt;The result: no more half-finished refactors stuck in a branch for three weeks. You always have working code, and a clear map of what's left. 🗺️&lt;/p&gt;

&lt;h2&gt;
  
  
  🧩 How they fit together
&lt;/h2&gt;

&lt;p&gt;None of these principles work alone:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🪶 &lt;strong&gt;KISS&lt;/strong&gt;, &lt;strong&gt;YAGNI&lt;/strong&gt; and &lt;strong&gt;Least Surprise&lt;/strong&gt; keep me from building too much — and from building it weird.&lt;/li&gt;
&lt;li&gt;🛠️ &lt;strong&gt;DRY&lt;/strong&gt; and &lt;strong&gt;SOLID&lt;/strong&gt; keep what I build maintainable.&lt;/li&gt;
&lt;li&gt;🛡️ &lt;strong&gt;Baby Steps&lt;/strong&gt; and &lt;strong&gt;Mikado&lt;/strong&gt; keep me safe when I change existing code.&lt;/li&gt;
&lt;li&gt;🧭 And &lt;strong&gt;"make it work, make it right, make it fast"&lt;/strong&gt; sets the order for all of it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But here's the uncomfortable truth nobody tells you when you first learn these: &lt;strong&gt;principles contradict each other.&lt;/strong&gt; 💥 YAGNI says &lt;em&gt;don't build it&lt;/em&gt;, while SOLID says &lt;em&gt;add this layer of abstraction&lt;/em&gt;. DRY says &lt;em&gt;extract the duplicate&lt;/em&gt;, while Least Surprise says &lt;em&gt;keep it consistent and obvious&lt;/em&gt;. So which one wins?&lt;/p&gt;

&lt;p&gt;The trick is to treat them as a &lt;strong&gt;hierarchy, not a checklist.&lt;/strong&gt; 🏛️ The foundational ones come first, and a "higher" principle is only allowed to apply when it doesn't break a "lower" one. Roughly: &lt;em&gt;make it work&lt;/em&gt; → &lt;em&gt;YAGNI&lt;/em&gt; → &lt;em&gt;least surprise&lt;/em&gt; → &lt;em&gt;KISS&lt;/em&gt; → &lt;em&gt;DRY&lt;/em&gt; → &lt;em&gt;SOLID&lt;/em&gt; → and &lt;em&gt;make it fast&lt;/em&gt; dead last. When two principles clash, the more foundational one wins. That's how you stop arguing in circles in code review.&lt;/p&gt;

&lt;p&gt;They're not rules I follow blindly — every one of them has a &lt;em&gt;"but"&lt;/em&gt; attached, as you've seen. They're a starting point, a default. The judgment of when to bend them — and which one outranks which — comes with experience.&lt;/p&gt;

&lt;p&gt;So next time you're staring at a problem, unsure where to start, ask yourself the simplest question:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;"What's the smallest, simplest thing that makes this work?"&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Start there. Your code, your teammates, and your future self will thank you. 🙌&lt;/p&gt;




&lt;p&gt;These are &lt;em&gt;my&lt;/em&gt; principles — but I'm always looking to sharpen my compass. 🧭&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What about you?&lt;/strong&gt; Which principle has saved you the most pain? Is there a rule you swear by that I didn't mention here? Or maybe one of these you've learned to &lt;em&gt;break&lt;/em&gt; on purpose?&lt;/p&gt;

&lt;p&gt;👇 &lt;strong&gt;Drop your favorite tip in the comments&lt;/strong&gt; — I read every one, and I'd love to learn from yours. And if this article resonated with you, a ❤️ or a 🔖 helps it reach another dev who needs it.&lt;/p&gt;

&lt;p&gt;Happy coding! 🚀&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and coding agents in practice. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=principles" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>webdev</category>
      <category>cleancode</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How to use two instances of Claude Code</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Tue, 19 Aug 2025 15:24:44 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/how-to-use-two-instances-of-claude-code-2nae</link>
      <guid>https://dev.to/ibrahimdans/how-to-use-two-instances-of-claude-code-2nae</guid>
      <description>&lt;p&gt;&lt;strong&gt; You have reached the limit for Claude Code &lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F288ry0oj49fc9yg4aooj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F288ry0oj49fc9yg4aooj.png" alt=" " width="800" height="38"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It's quite frustrating, especially since it often happens when our treatment isn't finished.&lt;br&gt;
It's not ideal to have two instances of Claude, because it means paying for Claude Pro twice, but it's cheaper than having Claude Max, which costs over €100.&lt;/p&gt;

&lt;p&gt;First, at the root of your account, create a new folder that will hold your Claude configurations, credentials, etc.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpna116amqbdoptd8ptzv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpna116amqbdoptd8ptzv.png" alt=" " width="191" height="65"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you have specific configurations such as commands, don't forget to copy them. That's what I do when I activate another instance of Claude.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;cp -R .claude .claude-2&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;in zshrc &lt;code&gt;$HOME/.zshrc|.bashrc&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;cc() {
 claude
}

ccp() {

CLAUDE_CONFIG_DIR=~/.claude-2 claude

}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Now you just need to launch &lt;strong&gt;cc&lt;/strong&gt; for claude or &lt;strong&gt; ccp  for claude-2.&lt;/strong&gt;&lt;/p&gt;
&lt;strong&gt;

&lt;p&gt;Note: &lt;strong&gt;cc&lt;/strong&gt; and &lt;strong&gt;ccp&lt;/strong&gt; are arbitrary you can call them whatever you want.&lt;/p&gt;

&lt;p&gt;Enjoy &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9l5gkm9tirlo25v5hc6e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F9l5gkm9tirlo25v5hc6e.png" alt=" " width="500" height="500"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and coding agents in practice. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=two-claude-instances" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;/strong&gt;

</description>
      <category>programming</category>
      <category>ai</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Essential Code Review Terms Every Developer Should Know</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Mon, 07 Jul 2025 09:12:09 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/essential-code-review-terms-every-developer-should-know-2dp6</link>
      <guid>https://dev.to/ibrahimdans/essential-code-review-terms-every-developer-should-know-2dp6</guid>
      <description>&lt;p&gt;When I first started out in this profession, I would often come across certain terms and acronyms in code reviews and team discussions, and I always wondered what they meant. If you’re new to software development or just want a refresher, here’s a handy list that might help you navigate those conversations more confidently.&lt;/p&gt;

&lt;p&gt;Common Terms and Acronyms&lt;br&gt;
&lt;strong&gt;WIP&lt;/strong&gt; (Work In Progress): Indicates that the work or pull request is not finished yet and is not ready for a full review.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;LGTM&lt;/strong&gt; (Looks Good To Me): The proposed code looks correct and can be merged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;NIT&lt;/strong&gt; (Nitpick): A minor suggestion or remark, often about style or readability, with no functional impact.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;ACK&lt;/strong&gt; (Acknowledge): Confirms that a comment has been read and considered.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PTAL&lt;/strong&gt; (Please Take A Look): A request to review or re-review the code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RFC&lt;/strong&gt; (Request For Comments): An invitation for feedback or opinions on a proposal or change.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;IMO/IMHO&lt;/strong&gt; (In My [Humble] Opinion): Indicates that what follows is a personal opinion.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Blocking&lt;/strong&gt;: A comment or issue that must be addressed before the code can be merged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Non-blocking&lt;/strong&gt;: A suggestion or remark that does not prevent the code from being merged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ship It&lt;/strong&gt;: Informal way of saying the code is ready to be delivered or merged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stale&lt;/strong&gt;: A review or pull request that hasn’t seen activity in a long time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Self-review&lt;/strong&gt;: Reviewing your own code before submitting it to others.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Refactor&lt;/strong&gt;: Rewriting code to improve its structure or readability without changing its functionality.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Patch&lt;/strong&gt;: A software fix or update.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hotfix&lt;/strong&gt;: A quick fix for a critical bug, usually deployed urgently.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DRY&lt;/strong&gt; (Don’t Repeat Yourself): Principle to avoid code duplication.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bump&lt;/strong&gt;: To increase or update a version number, or to make a small improvement or fix.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chore&lt;/strong&gt;: A technical or maintenance task that doesn’t add a new user-facing feature, but is necessary for the health of the project (e.g., code cleanup, updating dependencies, configuring tools).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;FYI&lt;/strong&gt; (For Your Information): Sharing information without expecting an immediate response or action.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TBR&lt;/strong&gt; (To Be Reviewed): Indicates that a piece of code or change is waiting for review.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Dead code&lt;/strong&gt;: Unused or obsolete code that should be removed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Needs Rebase&lt;/strong&gt;: The branch needs to be updated to resolve conflicts or incorporate the latest changes from the main branch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Outdated&lt;/strong&gt;: A comment made on an older version of the code, often after a rebase or new commit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;TBD&lt;/strong&gt; (To Be Determined/Defined): Something that still needs to be specified or decided.&lt;/p&gt;

&lt;p&gt;If you know more terms or acronyms that are commonly used in code reviews, feel free to share them in the comments! This list is not exhaustive, and your input can help others in the community. &lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fu8fy543e9m32kkikg57b.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fu8fy543e9m32kkikg57b.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and coding agents in practice. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=code-review-terms" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>development</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Enhancing Testability with Dynamic Data-testid Attributes</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Thu, 28 Mar 2024 14:21:39 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/enhancing-testability-with-dynamic-data-testid-attributes-4407</link>
      <guid>https://dev.to/ibrahimdans/enhancing-testability-with-dynamic-data-testid-attributes-4407</guid>
      <description>&lt;p&gt;We've all been faced with the challenge of choosing a better test ID for our component at some point. Why not leverage the logic we already use for CSS, like BEM (Block Element Modifier)? What is the best solution for achieving consistent and logical IDs across the board? What are the existing best practices?&lt;/p&gt;

&lt;p&gt;✅ The Solution:&lt;br&gt;
The best solution I've found with React is to create a custom hook that generates an ID, making it easier to locate them in our tests.&lt;/p&gt;

&lt;p&gt;📚 Code Examples:&lt;/p&gt;

&lt;p&gt;Create a custom hook useTestIdGenerator.ts:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkqnvgc5lhoukytfjaamb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fkqnvgc5lhoukytfjaamb.png" alt=" " width="800" height="333"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Use the custom hook in your grid component:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhwpfp2r0u86mian29dbh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fhwpfp2r0u86mian29dbh.png" alt=" " width="800" height="652"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Now, each element in your grid has unique "data-testid" attributes!&lt;/p&gt;

&lt;p&gt;This approach greatly facilitates testing of dynamic components while maintaining the cleanliness and maintainability of your code. 🔥&lt;/p&gt;

&lt;p&gt;An example test using this unique attribute:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fokwy6vh5loza5pgpcehp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fokwy6vh5loza5pgpcehp.png" alt=" " width="800" height="155"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Don't hesitate If you have another even better solution, to suggest it in the comments.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and coding agents in practice. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=data-testid" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>react</category>
      <category>testing</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>The boy scout rule : Small Steps, Big Impact</title>
      <dc:creator>Ibrahima D.</dc:creator>
      <pubDate>Mon, 04 Sep 2023 10:01:31 +0000</pubDate>
      <link>https://dev.to/ibrahimdans/the-boy-scout-rule-small-steps-big-impact-1dp6</link>
      <guid>https://dev.to/ibrahimdans/the-boy-scout-rule-small-steps-big-impact-1dp6</guid>
      <description>&lt;p&gt;In his book 'Clean Code,' &lt;strong&gt;Robert C. Martin&lt;/strong&gt; introduces us to an essential principle for writing beautiful code, the famous Boy Scout Rule, which can be summed up in one sentence: 'Always leave a place in a better state than you found it.'&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fps8rj3njw0f26s8tzg2i.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fps8rj3njw0f26s8tzg2i.jpg" alt=" " width="640" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As developers, we are constantly faced with challenges to produce clean, readable, and maintainable code. One of the simplest yet most powerful methods to achieve this goal is the Boy Scout Rule. Inspired by the idea of leaving the environment in a better state than we found it, this rule can have a significant impact on the quality of our code. In this article, we will explore this concept and discover how it can enhance our development process&lt;/p&gt;

&lt;p&gt;The Boy Scout Rule, popularized by software engineering veteran Robert C. Martin, encourages us to improve the code with every change we make, even if that change is not directly related to our current task. This can include minor adjustments such as renaming variables for clarity, adding comments to explain complex parts of the code, or reorganizing sections for better readability.&lt;/p&gt;

&lt;p&gt;The Benefits of Following the Rule&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cleaner Code&lt;/strong&gt;: By adopting this rule, we ensure that our code remains consistently clean and organized. The cumulative effect of small improvements over time contributes to overall quality maintenance.&lt;/p&gt;

&lt;p&gt;Ease of Maintenance: Well-maintained code is easier to understand and modify. Future development teams will appreciate code that reads like a well-written book.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reducing Technical Debt&lt;/strong&gt;: By preventing the accumulation of poor code, we avoid technical debt, allowing development to proceed smoothly without being hindered by quality issues.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to Apply the Boy Scout Rule&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Be Conscious&lt;/strong&gt;: Every time you modify a part of the code, be mindful of opportunities for improvement. Ask yourself, "How can I leave this part of the code in a better state?"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prioritize&lt;/strong&gt;: Not all improvements are equal. Focus on changes that will have the most impact on code readability, maintainability, and clarity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Communicate&lt;/strong&gt;: Share the Boy Scout Rule with your colleagues. Encourage a development culture where a commitment to quality is valued.&lt;/p&gt;

&lt;p&gt;The Boy Scout Rule is a simple yet effective approach to ensuring the ongoing quality of our code. By incorporating this philosophy into our development process, we contribute to an environment where code respect and a continuous improvement mindset are at the core of our work. So, the next time you make a change, ask yourself, &lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;'Am I leaving the code in a better state than I found it?'&lt;/strong&gt;&lt;/em&gt; &lt;/p&gt;

&lt;p&gt;Your code, your colleagues, and your future self will thank you.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fv5fz7p8sic5xl3rzmjqr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fv5fz7p8sic5xl3rzmjqr.png" alt=" " width="800" height="405"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I write about front-end architecture and coding agents in practice. More on &lt;a href="https://ibrahimadansoko.fr/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=boy-scout-rule" rel="noopener noreferrer"&gt;my site&lt;/a&gt;. Let's talk on &lt;a href="https://linkedin.com/in/ibrahimadansoko" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>beginners</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
